Keep your infrastructure
Your provider accounts, storage contracts and bills remain yours. Connecting an environment does not migrate every byte.
Enterprise & public sector
Keep the systems your organization chooses. Bring supported data workflows under defined authority with Rhea Data, or add independent passwordless sign-in to your services with Rhea Key.
Why an independent layer
Your provider accounts, storage contracts and bills remain yours. Connecting an environment does not migrate every byte.
People, applications and assistants have distinct entry points. Access follows the defined resource, action and grant.
Data plans include a monthly data allowance with unlimited seats and connections, rather than purchased storage capacity. Provider storage charges remain separate.
Practical evaluation
Start with the outcome: who needs to act, on which data, through which interface. Then map the technical, security and commercial responsibilities for your environment.
Bring supported data work under consistent control while keeping your providers.
What Rhea provides
Independent permissions and supported data work across customer-connected infrastructure. People use the workspace; applications use enabled APIs; assistants work inside Data on read-only organization metadata.
Evaluate for your environment
Your providers, where provider credentials are held in your chosen mode (client-held or server-managed), the operations you need and end-to-end operation in your environment. Direct SQL query execution is disabled.
Let people sign in to your services without passwords.
What Rhea provides
Passwordless sign-in your websites can add without adopting Rhea Data. The person approves on their device; your website verifies the signed proof for its own domain.
Evaluate for your environment
Which integration path you use (RK-1 or registered OIDC), your challenge store and replay protection, and end-to-end sign-in on your website domain.
Keep the storage contracts you already have.
What Rhea provides
You select your storage services. They keep storing and billing; connecting them does not automatically move content.
Evaluate for your environment
Provider contracts, data residency, service limits, credentials and any explicit transfer requirements.
Know which party handles content, metadata and keys.
What Rhea provides
Client-side encryption of protected file content, scoped authorization and recorded Rhea Data activity, with Rhea Key approvals where applicable.
Evaluate for your environment
Where keys, encrypted content and operational metadata are handled in your selected product mode, and the evidence your security team requires.
Start from published plans and request applicable terms.
What Rhea provides
Published Rhea Data plan allowances and Rhea Key's free and unlimited saved-connection terms, with official Rhea contacts for documentation requests.
Evaluate for your environment
The contracting entity, approved terms, privacy and subprocessor materials and any deployment-specific arrangements.
Evidence and contact
Use the Trust and developer references to map the proposed workflow. Bring your providers, required operations, credential mode and security requirements to a focused conversation with Rhea.
Tell us which providers you use, the work you want to enable and your security requirements. We can discuss the relevant integration scope and commercial documents for your evaluation: [email protected].
Security and privacy requests: [email protected] · [email protected].