Protect
Content is encrypted on the device with a key the institution controls, before it reaches any provider.
Rhea Data
One environment for your organization's data.
Rhea Data brings protected documents, permissions and data workflows into one environment. Connect supported storage, organize information, control sharing and collection, move protected documents and review recorded activity. File content is encrypted on the device before it reaches storage.
The seven operations
Everything an institution does to data, governed as one model.
Rhea Data does not add another place to put files. It governs the seven things that actually happen to information, wherever that information already lives.
Organise
A catalog of every protected object and record across every connected estate, with classification, placement policy and search.
Authorise
Policy decides whether an operation may run; a customer-held key proves the authority to run it. Sensitive operations require quorum.
Access
Content becomes readable only through an authorised, short-lived, single-use release, evaluated fail-closed.
Share
Protected sharing inside and outside the institution, and controlled inbound collection, without handing out links that outlive the relationship.
Move
Movement between locations and across providers as one governed operation, verified at the destination.
Audit
Every operation writes a hash-chained record of actor, action, resource, time and outcome, verifiable offline.
One authority model.
The same key, the same policy evaluation and the same evidence chain apply to all seven, across every connected estate.
Zero Custody architecture
Rhea coordinates the operation and cannot perform it alone.
The asymmetry is deliberate. Authority is manufactured on the institution’s side of the boundary, and execution happens there too. Rhea holds the workflow, the policy decision and the evidence — never the keys that make data readable.
Institution
Holder key
A person or an executive quorum signs the request on their own device with Rhea Key. The private key never leaves it.
Holds: Private signing key
Rhea
Coordination
Rhea evaluates policy, sequences the operation and records it. It carries a signed instruction, not a credential.
Holds: Ciphertext and metadata
Institution
Connector in your VPC
A connector inside the customer's own network holds every provider credential and every decryption key, and performs the operation.
Holds: Provider credentials · decryption keys
Institution
Your storage and databases
Object storage and relational estates the institution already owns. Nothing is migrated and nothing is copied to Rhea.
Holds: The data itself
Five planes
One architecture, five separated responsibilities.
- Authority
- Who may act. Keys held by people and executive quorums, delegations held by machines, all revocable and all expiring.
- Catalog
- What exists. Every protected object and governed record across every connected provider and database, classified and placed by policy.
- Policy
- What is permitted. Rules evaluated fail-closed: if policy cannot be read, the operation is denied rather than allowed.
- Execution
- What actually runs. Standard, Hardened or Zero Custody — in the strongest mode, entirely inside the customer's own VPC.
- Evidence
- What can be proven. A hash-chained ledger where each entry commits to the last, so retroactive edits break verification.
Execution modes
Choose how much Rhea is allowed to touch.
Standard
Rhea operates the execution path. Content is still encrypted on the device before it reaches storage, so Rhea handles ciphertext and metadata.
Fast onboarding for regulated mid-market teams.
Hardened
Storage credentials are sealed on the customer's own device and opened only in browser memory. Rhea holds an envelope it has no key for, and signed requests go straight from the browser to the customer's storage account.
Organisations that cannot let a vendor hold cloud credentials.
Zero Custody
A connector inside the customer's VPC holds every provider credential and every decryption key. Rhea coordinates the workflow and is cryptographically blinded to its contents.
Central banks, governments and sovereign defence.
Bring your own storage
Your estate stays yours. Rhea never becomes the storage.
Institutions connect the object storage and relational estates they already operate. There is no migration programme, no second copy of the data, and no dependency that makes leaving expensive.
AWS S3
Customer-owned buckets
MinIO / S3-compatible
Customer-owned, connected in place
Microsoft Azure Blob Storage
Customer-owned, connected in place
Google Cloud Storage
Customer-owned, connected in place
Oracle Cloud Object Storage
Customer-owned, connected in place
Cloudflare R2
Customer-owned, connected in place
Private and on-premises infrastructure
Customer-owned, connected in place
Databases (PostgreSQL and supported relational estates)
Governed in place, no migration
Provider names describe the architecture and its direction. Inclusion does not imply partnership, endorsement, certification, or a current integration. Each environment carries its own status.
Maturity
What Rhea Data is today
Rhea Data governs data across customer-owned object storage and relational estates. Organisations connect the infrastructure they already run — AWS, Azure, Google Cloud, Oracle, Cloudflare, MinIO, on-premises — without migrating anything.
Use Rhea Data to organize protected documents and Secure Notes, request files from outside parties, share with defined members, approve sensitive actions and review what happened. The Command Center brings operational usage and organizational visibility together.
Ownership
Who deploys and uses Rhea Data.
Rhea Data is for organizations that need important information to remain protected and usable across teams, with controlled access, customer-owned storage and recorded activity. Security and infrastructure teams configure the environment; business teams use it for everyday data work.
- Sponsored by: Security, technology, data-protection or operational leadership.
- Operated by: Security, platform, cloud or data-infrastructure teams.
- Used by: Teams handling important organizational files.
- Extended to: Clients, partners and contractors through controlled sharing and collection.
LimitationRhea Data serves human-controlled organizational file workflows today. Application authority, AI-agent authority, database connectivity and public integration interfaces are Planned.
Data operations
Put protected information to work.
Documents and Secure Notes, organized for the people authorized to use them.
Protected documents
Organize sensitive files in a document vault with folders, search, filters and per-item actions.
The organization keeps one place for the files it cannot afford to lose control of.
Evidence Access, sharing and lifecycle events are recorded.
Read moreClient-side protection
File contents are encrypted on the device with AES-256-GCM before connected storage receives them.
Storage receives protected objects, not readable content.
Rhea Data does not protect plaintext after an authorized decryption, and cannot eliminate risk on a compromised authorized endpoint.
Read moreSecure Notes
Keep passwords, recovery information, private keys, procedures and sensitive text inside controlled human workflows.
Secrets stop living in chat messages, spreadsheets and personal note apps.
Evidence Creation, access and sharing of a note are recorded.
Secure Notes serve human-managed secrets. They are not a machine-secrets manager for application runtime injection.
Read moreEncrypted filename and folder metadata
Protect filenames and folder structure in addition to contents.
Closes the most significant remaining metadata exposure.
Exchange
Getting data in and out under control.
Collection and sharing stay inside the organization's protection model.
Secure File Requests
Request and receive sensitive files from people inside or outside the organization without defaulting to ordinary attachments or uncontrolled upload links.
Inbound sensitive material enters the organization's protection model at the point of collection.
Evidence Request creation, submission and receipt are recorded.
Read moreShared Access Control
Share protected folders and files with defined members and keep the organization's access model intact.
Sharing does not mean handing out a link that outlives the relationship.
Evidence Member additions, removals and file access are recorded.
Read moreSecurity operations
Running protection as an operation, not an assumption.
Access and approvals
Apply roles and permissions, and require Rhea Key approval for sensitive actions.
Authority to read is a decision the organization makes, not a side effect of infrastructure access.
Evidence Authorization decisions and approvals are recorded.
Read moreEncryption health
Review protection coverage, key versions, and re-wrapping state across the organization's documents.
Protection state becomes an operational metric instead of an assumption.
Read moreSessions and security alerts
Review active sessions and security alerts, and end sessions when required.
Access that is no longer appropriate can be ended immediately.
Read moreGuardian key recovery
Recover organizational key material through a configured threshold of guardians who each hold their own key and give a signed, single-use consent.
Continuity does not require Rhea to hold a copy of the organization's authority.
If a guardian loses both their Recovery Kit and its passphrase, that guardian's share is permanently lost.
Read moreRetention and archive
Configure retention, archive documents, and control trash behavior.
Sensitive material has a defined end of life.
Read moreClassification
Classify documents so that policy and review operate on sensitivity, not only on location.
Controls follow the sensitivity of the information.
Infrastructure
Your storage. Your account. Your control.
Rhea Data connects to storage the organization already owns and operates.
AWS S3 connection (Bring Your Own Storage)
Connect the organization's own AWS S3 environment, validate it, test the transfer path, and operate it from Rhea Data.
The organization keeps ownership of the storage account holding its protected objects.
Read moreMovement between connected S3 locations
Move protected data between the organization's connected AWS S3 locations, with checking, transfer, verification and audit handled by Rhea Data.
Storage layout can change without the organization abandoning its protection and evidence model.
A move copies the protected data to the destination and verifies it there. Deletion of the source object is a separate, explicitly authorised operation.
Read moreCross-provider movement
Move protected data between different providers — for example AWS S3 to Azure Blob Storage — as one governed operation.
Changing provider becomes an operation rather than a migration project.
Read moreDatabase connections (BYOD)
Govern relational estates in place under scoped authority, starting with PostgreSQL. The database stays where it is; no migration is required.
Structured data faces the same control problem as documents, and answers to the same authority model.
Rhea Data API and SDK
Interfaces for approved applications to request supported data operations under bounded, expiring authority.
Applications become authorised actors instead of standing exceptions with permanent tokens.
Category
How Rhea Data fits into your stack.
Rhea Data combines data workflows, protection, permissions and recorded activity. These responsibilities explain its role:
- Your connected provider continues to hold the stored data.
- Rhea Data provides the environment for supported data operations.
- Encryption protects file content before storage.
- Rhea Key supports authentication and approvals.
- Your existing identity and security controls still matter.
- In Zero Custody mode, execution credentials and decryption keys never leave your own environment.
Administration
Members, roles and evidence.
Organization administration
Manage members and roles, review usage and system health, and configure the organization.
One control surface for the people and settings around protected data.
Read moreAudit and evidence
Review access, approval, administrative and security events, and verify the hash chain over cryptographic events.
The organization can show what happened, not only assert it.
The hash chain covers cryptographic and key-management events. It is not a claim that every record of every type is immutable.
Read moreRhea Data pricing
Priced on the data Rhea Data processes, not on the storage you own.
Rhea Data usage is based on the amount of data Rhea Data processes each month, including encryption, decryption and related processing. VAT may apply. Plans are activated inside Rhea Data after organization setup.
All plans include encryption on the device before storage and Bring Your Own Storage. Rhea Data offers a native 7-day trial.
- Operations are billed at €0.01 per 1,000 operations.
- Only relay-processed data is charged at 10× the selected plan's data rate. The relay portion is charged once, not at both the standard and relay rate.
- Customer-owned storage-provider charges are separate and paid directly by the customer.
Launch
€399
/ organization / month
€0.60
/ GiB processed
- Encryption on the device before storage
- Bring Your Own Storage
- Access, permission and approval activity recorded
Growth
€1,499
/ organization / month
€0.15
/ GiB processed
- Encryption on the device before storage
- Bring Your Own Storage
- Access, permission and approval activity recorded
Expand
€2,799
/ organization / month
€0.08
/ GiB processed
- Encryption on the device before storage
- Bring Your Own Storage
- Access, permission and approval activity recorded
Scale
€4,999
/ organization / month
€0.05
/ GiB processed
- Encryption on the device before storage
- Bring Your Own Storage
- Access, permission and approval activity recorded
Custom
For requirements outside the standard plans.
Estimate monthly usage
Pricing estimator
Enter the data Rhea Data processes each month and the number of operations. The cheapest standard plan is selected for you.
GiB
Everything Rhea Data encrypts, decrypts or otherwise processes for your organization.
GiB
Data that goes through the Rhea Data relay instead of the direct storage path. This portion is billed once, at 10× the plan rate.
ops
Counted per request, metered at €0.01 per 1,000 operations.
Estimated monthly total
€1,601.50
on the Launch plan (cheapest at this usage)
- Base fee
- €399
- Direct data — 2,000 GiB
- €1,200
- Relay data — 0 GiB at 10×
- €0
- Operations — 250,000
- €2.50
- Estimated monthly total
- €1,601.50
Relay-processed data is charged once, at the relay rate only. This is an estimate, not an invoice or binding quote. It excludes VAT, external storage charges and contract-specific terms. Actual billing is determined inside Rhea Data.
Start inside Rhea Data.
Explore Rhea Data, connect supported customer-owned storage and work through a document workflow. Review permissions and recorded activity in the same environment.