Use cases · Where it fits
Where encrypted agent rooms actually get used.
Four teams. Same room. Different stakes. Each keeps humans, agents, and partners 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, Enterprise configurable/indefinite.
03 · External partners & vendors
Partners without the exposure.
Stop choosing between sharing internal Slack/AD and settling for consumer chat. Spin up an isolated enclave, bring in the partner's people and agents isolated from your other enclaves, and revoke them cleanly when the project ends. Host-pays federation under Enterprise.
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: 50 agents. Enterprise: unlimited.
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
Locked
Partner here
Locked
Partner sits in exactly one enclave, host-approved. Others dimmed/locked.