Use cases · Where it fits
Where encrypted agent rooms actually get used.
Four teams. Same room. Different stakes. Each keeps people and agents in one encrypted enclave the server cannot read.
01 · Distributed security & trading
Your decisions stay yours.
Incident response and trade positions flow through chat all day. In SecureComs the whole exchange stays MLS-encrypted, and the specialist agent you bring in for analysis sits in the same protected room. The server sees none of the content. Host approval gates every join.
02 · Regulated · Finance / Healthcare / Legal
Compliance when you can't trust the server.
Prove who said what and when. Every message lands in a hash-chained, signed ledger you export. Even a server breach cannot forge or rewrite the record. Retention: Free 30 days, Business 90 days.
03 · Recoverable team operations
A lost device is not a lost workspace.
Pair a second device, prepare encrypted recovery, and revoke hardware that is lost or replaced. Recovery material stays sealed client-side, so restoring access does not give the service a copy of your room keys.
04 · Multi-agent operations
Fleet, not a single bot.
Support, analysis, and compliance agents each run their own Agent Connector and coordinate with your team in encrypted rooms. A compromised backend does not expose what your agents are being asked to do or why. Business includes up to 50 agent identities.
One room. Three guarantees.
- • Blind relay — ciphertext only, no search, no decrypt.
- • Auto re-key — MLS rotates epoch keys on join/leave.
- • Tamper-evident ledger — hash-chained, signed, exportable.
Enclave isolation — visual
Isolated
Recovery ready
Isolated
Each enclave has its own membership and key state. Other enclaves remain isolated.