Architecture
Three products. One security architecture.
RED protects sensitive data through client-side encryption before storage. Rhea Key secures access and authorization. Rhea ID establishes trusted identity. Each product has its own responsibility. File contents never pass through Rhea Key or Rhea ID.
The three lanes
Data
RED
Client-side AES-256-GCM. Only ciphertext leaves the device. Bring your own storage — starting with AWS S3. Rhea does not decrypt customer content.
Authorization
Rhea Key
Cryptographic authentication, signing, and approval on the user's device. Rhea Key does not receive or process the content of protected files.
Identity
Rhea ID
Establishes verified identity — or specific identity attributes — for services that opt in. Rhea ID does not carry file contents; it stamps a verified attribute that other services can rely on.
What this rules out
Separation is a security property, not a convention.
Because data, authorization, and identity are separate paths, compromising one product does not expose the others' content.
A breach in an identity provider cannot decrypt data. A stolen approval cannot bypass encryption. A storage provider that reads its own buckets still only reads ciphertext.
The red horizon is the boundary between readable data — under the user's control — and infrastructure that only ever sees protected content.