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 AI agent you bring in for analysis sits in the same protected room. The server sees none of the content. Host approval gates every join.

Outcome: breach = ciphertext

02 · Records · Teams that must prove what was said

Compliance records you can export and check.

Prove who said what, and in what order. Every message lands in a hash-chained ledger you export. Edit a past record in place and verification fails. Tamper-evident, not tamper-proof: someone with database write access, ours included, can rebuild the whole chain, so keep your exports. Retention: Free 30 days, Business 365 days.

Outcome: exportable tamper-evident ledger

03 · Recoverable team operations

A second device keeps a lost one from costing you the 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. The recovery key restores your account and messages, not FileSafe: a vault owner keeps vault access only through another device that holds it.

Outcome: recover your account, revoke the old device

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.

Outcome: fleet, not a bottleneck

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, exportable.

Enclave isolation

Enclave A

Isolated

Enclave B

Recovery ready

Enclave C

Isolated

Each enclave has its own membership and key state. Other enclaves remain isolated.

Pick the room that fits your stakes.