01 / Control your data
Your infrastructure. One independent control layer.
Rhea Data brings permissions, protection and supported data work together across your connected infrastructure. Your provider accounts, storage and billing remain yours.
One control layer. Three ways to work.
Your provider accounts, storage and billing remain yours.
The Rhea Data workspace
Work directly with permitted data.
Bring supported data work across your connections into one coherent workspace, with the access your organization grants.
- Illustrative request
- Review a permitted data inventory
- Permitted result
- The selected collection is visible within your access rules.
Content access and changes depend on the enabled connection and your permissions.
What it is
Choose the infrastructure. Keep the authority.
Your providers
Your providers continue storing and billing under your accounts. Connecting them brings supported work under control; it does not migrate everything.
Your workflows
People work directly, applications integrate through enabled interfaces, and assistants act inside Data. Each experience follows a defined scope.
Your control
Decide who can act, review recorded Rhea Data activity and withdraw further access when needed.
A common control model
Seven actions. One control model.
- 01
Protect
Protect sensitive content before storage, with authorized-client encryption where the protection model applies.
- 02
Organize
Bring permitted data collections into a coherent workspace across connected providers.
- 03
Authorize
Define which person, application or assistant can act, on which data and within which scope.
- 04
Access
Receive the result your permissions allow, through the workspace or an enabled interface.
- 05
Share
Give the intended collaborator bounded access under your sharing rules.
- 06
Move
Transfer deliberately between connected providers when the connection and operation support it.
- 07
Audit
Review recorded Rhea Data activity by person, application or assistant to see who acted and when.
Supported routine work can continue within an authorized session or connection. Sensitive operations can require a separate explicit approval. Review activity and disconnect when needed. Disconnecting stops further access. It cannot undo completed actions or data already disclosed.
How it works
The controls behind your work.
Explore the responsibilities behind supported work: requester, identity, permission, execution and evidence. Select one to see its role.
Connection reference
Amazon S3
Connection reference
Microsoft Azure Blob Storage
Connection reference
Google Cloud Storage
Connection reference
Oracle Object Storage
Connection reference
MinIO / S3-compatible
Connection reference
Cloudflare R2
Responsibility · Who
People · Apps · AI agents
People work directly in the Rhea Data workspace. Applications use supported enabled API operations. AI assistants work inside Data from chat under one explicitly scoped connection.
Example journey
One team. Several providers. Shared access rules.
An organization keeps its data in existing provider accounts. It needs consistent permissions for teams, a defined application interface and accountable assistant work, with deliberate transfers when a supported connection allows them.
- 01
An admin connects the company’s existing providers to Rhea Data.
→ configured connections, with provider accounts and billing unchanged
- 02
The admin grants a team access to a selected collection across connected providers.
→ shared access rules within supported integrations
- 03
An AI agent connects with one explicit approval, then reviews permitted organization metadata from chat.
→ activity is logged; disconnecting stops further access
- 04
An internal app requests permitted inventory metadata through an enabled Data API operation.
→ the result is returned and attributed to the application; operation support depends on the enabled integration
- 05
The company chooses a supported transfer to a different provider.
→ the selected connection and transfer mode determine the path; recorded Rhea activity identifies the work
Illustrative work across connections. Operation availability and execution paths depend on the enabled interface and connection mode.
Who it’s for
For organizations that need control across connections.
- 01
Enterprises and organizations
Consistent access, storage mobility and activity history across supported connected cloud and object storage providers. Database query support is a separate capability.
- 02
Teams and professionals
A coherent place for permitted work across services, with clear access and sharing rules.
- 03
Developers
One integration model for supported operations across configured providers, with application identity, permissions and activity records. Check which API operations are enabled before deploying.
- 04
AI-enabled workflows
An accountable way to delegate read-only organization-metadata review inside Data from chat, with recorded activity and a connection you can disconnect.
How security works
Safeguards built into the layer.
Protected content, access checks and activity history showing who did what work together to support customer control.
Encryption before storage
Protected file content is encrypted on the authorized client; your provider stores ciphertext.
Policy before access
Supported requests are checked against the actor, target and granted scope before work proceeds.
Authorize once, work in scope
Supported routine work can continue within an authorized session or connection. Sensitive operations can require a separate explicit approval. Review activity and disconnect when needed.
Activity history
Review recorded Rhea Data activity by person, application or assistant.
Emergency recovery
Set up emergency recovery for your organization in advance. You print a recovery sheet and keep it offline. Rhea never holds a copy.
What Rhea Data includes
- Three distinct experiences: a workspace for people, enabled API operations for applications, and assistants working inside Data from chat. Each follows defined permissions and the capabilities of its interface.
- Implemented object-storage signing paths are documented in the integration guide. Enabled storage operations depend on each connector and its permissions. Database connection types can be configured separately; direct database query execution is disabled.
- Your storage provider continues to store your data — and bill you for it. See Pricing.
See a protected-content example
Example · a person opens a permitted file
Customer storage
Amazon S3 · object storage
Workspace file
Project folder · brief.pdf
Requested action
Open this file · no transfer
Access policy
Example activity
- PersonRequested brief.pdf in the Rhea Data workspace
- SystemRhea Data checked the person’s granted access
- SystemThe connected provider served the permitted file
- SystemActivity recorded: person · open · brief.pdf
The provider keeps storing and billing. Opening the file does not move it or grant access to other files. Enabled operations must be checked for the actual connection.
Rhea Data facts and scope
Available providers and capabilities depend on the integration.
Continue
Find the right fit for your data.
Compare monthly usage allowances, then assess your providers, access requirements and integration with your team.