Product status
Everything, with its real status.
RED is generally available. AWS S3 is the approved public storage path; every other environment carries its own status.
Capabilities
What RED does, and where each capability stands.
| Capability | Status | What it does |
|---|---|---|
| Protected documents | Status: Available today | Organize sensitive files in a document vault with folders, search, filters and per-item actions. |
| Client-side protection | Status: Available today | File contents are encrypted on the device with AES-256-GCM before connected storage receives them. |
| Secure Notes | Status: Available today | Keep passwords, recovery information, private keys, procedures and sensitive text inside controlled human workflows. |
| Secure File Requests | Status: Available today | Request and receive sensitive files from people inside or outside the organization without defaulting to ordinary attachments or uncontrolled upload links. |
| Shared Access Control | Status: Available today | Share protected folders and files with defined members and keep the organization's access model intact. |
| Access and approvals | Status: Available today | Apply roles and permissions, and require Rhea Key approval for sensitive actions. |
| Encryption health | Status: Available today | Review protection coverage, key versions, and re-wrapping state across the organization's documents. |
| Sessions and security alerts | Status: Available today | Review active sessions and security alerts, and end sessions when required. |
| Guardian key recovery | Status: Available today | Recover organizational key material through a configured threshold of guardians who each hold their own key and give a signed, single-use consent. |
| Retention and archive | Status: Available today | Configure retention, archive documents, and control trash behavior. |
| Audit and evidence | Status: Available today | Review access, approval, administrative and security events, and verify the hash chain over cryptographic events. |
| Organization administration | Status: Available today | Manage members and roles, review usage and system health, and configure the organization. |
| AWS S3 connection (Bring Your Own Storage) | Status: Available today | Connect the organization's own AWS S3 environment, validate it, test the transfer path, and operate it from RED. |
| Classification | Status: Coming soon | Classify documents so that policy and review can operate on sensitivity, not only on location. |
| Incident response workflows | Status: Coming soon | Coordinate response steps and record decisions against affected protected data. |
| Cross-storage move | Status: Planned | Select protected data, choose another connected destination, and move it — with RED handling checking, transfer, verification, cutover, cleanup and audit. |
| Database connections (BYOD) | Status: Planned | Extend the same protection, authorization and audit model to connected databases. |
| RED API and SDK | Status: Planned | Defined interfaces for applications to operate against protected data under scoped authority. |
| Controlled agent authority | Status: Planned | Scoped, revocable, recorded authority for AI agents and other non-human callers. |
| Encrypted filename and folder metadata | Status: Planned | Protect names and structure in addition to contents. |
Environments
Storage environments.
AWS S3 is the approved public storage path today. Every other environment carries its own status.
| Environment | Status | Note |
|---|---|---|
| AWS S3 | Status: Available today | Approved public storage path today |
| MinIO / S3-compatible | Status: Coming soon | Implemented; enabled per deployment |
| Microsoft Azure Blob Storage | Status: Coming soon | Implemented; enabled per deployment |
| Google Cloud Storage | Status: Coming soon | Implemented; enabled per deployment |
| Oracle Cloud Object Storage | Status: Planned | Direction |
| Cloudflare R2 | Status: Planned | Direction |
| Private and on-premises infrastructure | Status: Planned | Direction |
| Databases | Status: Planned | Direction |
Provider names describe the architecture and its direction. Inclusion does not imply partnership, endorsement, certification, or a current integration. Each environment carries its own status.