Channels, threads, mentions, reactions, file drops and calls — with every message sealed on your device before it leaves it.
“Work like Slack. Leak like nothing.”
For studios, agencies, legal and finance teams, r&d groups and anyone working under nda who needs slack-grade usability without provider-side access.
The messaging patterns your team already knows — @mentions, threads, reactions, pinned messages, search — with sealed payloads.
Each message is encrypted with XChaCha20-Poly1305 under a room key wrapped per member with X25519. The server relays envelopes it cannot open.
Drop files into a conversation and they are encrypted before upload, with client-side previews, galleries and one-click encrypted ZIP downloads.
Audio and video run peer-to-peer over DTLS-SRTP, with a relay mode when you prefer not to expose participant IPs.
Every room has an encrypted drive behind it, so conversations and deliverables live in the same sealed space.
Removing a member rotates keys. There is no admin console that can retroactively read history.
Mainstream team chat protects data in transit and at rest, and that is genuinely useful. But the provider still holds the keys: content can be indexed, scanned, exported by an administrator, or produced in response to a legal request. For a team working under NDA, that is not a policy detail — it is the whole threat model. DRIVUNO removes the provider from the trust chain instead of asking you to trust it more.
We can see that an account exists, which rooms it belongs to, when messages were sent and how large the ciphertext is. We cannot see message text, file contents, file names, channel names or thread topics — those are encrypted client-side, and search runs on blind indexes rather than plaintext.
Invite your team by email, they create keys on first login, and channels are sealed per member from the first message. Files can be dragged in from any folder, and Live Clone can mirror an entire project folder or external drive into the encrypted workspace continuously.
No. Messages and files are encrypted on the device before they are sent. DRIVUNO Rooms seals every message with XChaCha20-Poly1305 under a room key that is itself wrapped per member with X25519. Servers relay and store ciphertext only.
Slack and Teams encrypt data in transit and at rest, but the provider holds the keys, so administrators, automated systems and legal requests can reach message content. DRIVUNO is designed so that this is technically impossible on our side: we never hold a key that opens your content.
Removing a member revokes their sealed copy of the room or folder key and triggers a key rotation, so future content is sealed under a key they never had.
Only what is strictly required to operate: account identifiers, membership, timestamps, sizes and security/audit logs. File and channel names are encrypted; search runs on blind indexes (HMAC tags), not on plaintext.
Yes. The free plan includes 1 GB with the exact same zero-knowledge architecture — encrypted drive, Rooms messaging and encrypted sharing.
Start free with 1 GB. Zero-knowledge encryption from the first upload — no admin override, no AI scanning, no plaintext on the server.
