Rhea Key
One key instead of every password.
Rhea Key is built to be the first factor for every app, website and platform in the digital world — and it is the only way into Rhea Data. No email and password. No magic link. No SMS. Before you sign, Rhea Key shows the action in plain language — for example: Approve: share “Q3 board pack.pdf” with the external auditor, read-only, for 7 days. You read it, then you sign.
Category
Not a second factor. The first one.
Most phone sign-ins add a code after a password. Rhea Key removes the password entirely.
Password + 2FA
It is notA secret you type, then a code. Both can be phished or redirected.
It isReplaced. There is nothing to type and no shared secret.
Password manager
It is notStores many passwords in one vault.
It isRhea Key has no passwords to store. One key signs.
Rhea Key
It is notNot a hardware wallet, not a crypto product. Hardware is optional.
It isYou see the action in plain language, then your key signs it. Web and app.
01 — Why it exists
The end of the password.
A person maintains credentials for more than a hundred accounts. They are memorised, reused, written down, or handed to a vault that becomes a single target. An emailed link can be read by whoever reads the inbox. A one-time code can be redirected with the phone number. Each of these is a secret that someone other than the holder can end up possessing.
Rhea Key is not an accessory to Rhea Data. It is the first factor itself — the thing you present before anything else. A key generated on your own device, held by you, and used to sign in instead of typing a password. One key, every service that accepts it.
A signature is produced against a challenge bound to the exact origin requesting it. A copied sign-in page on a different domain receives a signature that does not verify anywhere. There is no shared secret to phish, because the holder never transmits one.
The same key model covers applications and autonomous agents. An agent receives a bounded delegation — one operation, one time window, revocable — rather than a permanent API token that lives in a configuration file.
How it feels
The key is the product.
- A key you hold signs every action — that key is Rhea Key
- The QR code only carries the request; the face or passcode unlock only releases the key
- The action is shown in plain language before you sign
02 — Modes
One key, two modes.
Person mode
Free, for anyone.
A key on your own device signs you in. Nothing to memorise, nothing to type, nothing a copied website can capture. A device-local biometric or passcode gate releases the signature.
Organisation mode
Several holders must agree.
Quorum governance, device fleet management and bounded machine delegations. Data exports, policy changes and key rotations proceed only when M of N named holders have each signed.
Rhea Key is free for individuals in person mode. Organisation mode adds quorum governance, device fleet management and bounded machine delegations, and is included with Rhea Data.
Private authentication material remains protected by the user's device and is not transmitted to Rhea. Rhea does not operate a key-recovery service.
Quorum approval
Some operations should require more than one person.
An export of a sensitive dataset, a change to policy, a key rotation — in organisation mode these can be bound to an M-of-N quorum of executive keys. The operation stays suspended until enough independent holders have signed, and neither Rhea nor any single administrator can complete it on their own.
- Each signature is produced on its holder’s own device.
- A quorum that is never reached simply expires; the default is denial.
- The approval, its signers and its timing become part of the evidence record.
Pending operation
Export — customer records, EU region
- Chief Financial OfficerSigned on device
- Chief Information Security OfficerSigned on device
- Head of Data GovernanceAwaiting signature
The export remains unexecuted until the third holder signs. Until then there is no decryption, no release and no copy.
Illustrative representation of a quorum approval
03 — Clients
Where Rhea Key runs today.
Rhea Key platforms
| Client | Meaning |
|---|---|
| Webrheakey.com | rheakey.com |
| AndroidStatus: Coming soonNative application | Native application |
| iOSStatus: Coming soonNative application | Native application |
04 — How it works
A trusted device becomes the key.
Authentication and signing
Private authentication material stays protected by the device. Authentication and approvals are signed on-device and verified downstream.
Connection approval
Users approve or reject trusted connection requests instead of relying on shared secrets that can leak.
Rhea Data sensitive-action approval
Sensitive actions in supported Rhea Data workflows can require an approval signed through Rhea Key on the user's device.
Device-local biometric gate
Biometrics act as a device-local gate to the Rhea Key application. They are not an identity-verification mechanism and are not transmitted to Rhea.
Authentication and authorization are separate: connecting Rhea Key proves control of a key, while organizational permissions determine which resources and actions it can access.
05 — Recovery
Two recoveries that are often confused.
Rhea Key authentication keys
Rhea does not hold, escrow or recover a Rhea Key authentication key. If the key and its backup are lost, Rhea cannot restore it. That is the property that makes the key authoritative.
Rhea Data organisational-data recovery
Organisational-data recovery is guardian-based threshold recovery with browser-side reconstruction. A configured threshold of guardians, each holding their own key, gives a signed single-use consent; reconstruction happens only in the initiating administrator's browser.