Company
Rhea Holdings SRL — building data authority infrastructure.
Rhea is the company behind one layer above all data: authority, authentication and identity. It separates the infrastructure that holds or moves information from the authority that determines when, how and by whom it may be read or executed — and backs that authority with proof anyone can verify offline.
Mission
As institutions add applications and autonomous agents, every one of them becomes another actor asking for data. Rhea's purpose is to make authority reusable across all of them — people, executive quorums, software and agents — without Rhea ever becoming its owner. Rhea Data governs the estate, Rhea Key holds the authority, Rhea ID answers who the counterparty is.
Who we serve today
Rhea Data is for institutions that must decide who may act on the storage and databases they already run — and keep the record. The systems keep the data. Rhea Key grants the action. An agent signature is never a human approval.
Prerequisite: a storage account your organization owns — AWS S3, Azure Blob, Google Cloud Storage, Oracle, Cloudflare R2 or MinIO.
Rhea Data serves people, executive quorums, applications and AI agents through one authority model: scoped, expiring, revocable and recorded.
Three horizons
One authority model spans the three products and every connected estate: object storage, relational databases, applications and agents. An institution begins wherever its exposure is greatest and extends the same model outward, because the model does not change with the surface it governs.
01
Near term — the regulated flagships
Institutions whose supervisors already require demonstrable control: financial infrastructure, government estates, health and legal custodians. They adopt because the alternative is an assurance they can no longer defend.
02
Middle term — agents and reusable identity
As autonomous software acts on institutional data, bounded delegated authority becomes the default way to grant it. Identity answers become questions asked and signed, not documents copied and stored.
03
Long term — the authority standard
Transport encryption became a default nobody argues about. Proof of authority follows the same path: an ordinary, expected property of any system that holds information worth protecting.
How we build
These are operating invariants, not values on a wall. Each one constrains what we are allowed to ship.
Honest engineering
We describe what the system does, including what it cannot do. A capability is either in the product or it is not on the site.
Fail-closed by default
When policy cannot be evaluated with certainty, the operation does not proceed. Ambiguity resolves against access, never towards it.
Rhea cannot grant the action
Only a Rhea Key signature grants. Policy narrows and never grants. Rhea records that work happened; it cannot cause it. Standard custody holds provider credentials, and we say so.
Evidence that outlives us
Audit records are hash-chained and verifiable independently. Proving what happened must never require asking Rhea to vouch for it.
Measured, plaintext billing
Operations are counted and priced openly. There is no consumption the customer cannot reconstruct from their own records.
No lock-in as strategy
Storage stays customer-owned and portable. Customers remain with Rhea because leaving is easy and staying is better.
Operating entity
The public Rhea website and its products are operated by Rhea Holdings SRL.
Founder
Rhea was founded and is being built by Loránd Kismihály.
Contact
Direct contact addresses are listed below. For a structured inquiry, use the contact page.
- General
- contact@rhea.llc
- Enterprise
- contact@rhea.llc
- Security
- security@rhea.llc
- Support
- contact@rhea.llc