Positioning

The only zero-knowledge Dropbox + Slack built for teams that actually can't be read.

Most companies run chat in one product, files in another, and hope neither provider is ever compelled, breached or curious. DRIVUNO merges both into a single workspace where the server only ever holds ciphertext.

One workspace. Two products replaced. Zero readable data on our side.

For game studios, agencies, legal and finance teams, and privacy-conscious companies that need slack-style collaboration and dropbox-style storage without handing a provider readable access.

Built for confidentiality

Channels, DMs and threads

Real-time messaging with reactions, threads, tasks and search — every message sealed on the sender's device for the exact set of recipients.

Team Drive that cannot be indexed

Shared folders with per-member sealed keys, versioning and a 30-day trash. File names and structure are protected too, not just contents.

Encrypted calls and screen share

Voice, video and screen sharing with media encrypted end-to-end between participants — no server-side recording surface.

External sharing with real controls

Protected links with passphrase, expiry, view-once, view counters, watermarking and revocation — for people who will never create an account.

Audit trail you can defend

Membership changes, share creation, revocations and access events are written to an append-only log, without exposing content.

Usable by non-technical teams

No self-hosting, no key servers to run, no PGP rituals. People invite each other by email and the cryptography stays invisible.

Why 'encrypted' usually stops at the transport layer

Mainstream chat and storage products encrypt data in transit and at rest, but the provider holds the keys — that is what makes server-side search, previews, moderation and admin recovery possible. It also means a breach, a subpoena, a rogue insider or a misconfigured integration can expose readable content. Zero-knowledge removes that entire class of risk by never giving the server a key in the first place.

What you actually get by merging chat and storage

When your messages and your files live in the same encrypted workspace, a build no longer travels through a chat product into a storage product into a share link, collecting readable copies along the way. One identity, one key hierarchy, one audit trail, one place to revoke someone the day they leave.

Designed for teams that are not security engineers

Self-hosted encrypted stacks fail for the same reason every time: somebody has to operate them. DRIVUNO ships as a hosted product with the same convenience curve as the tools it replaces — desktop, mobile and web, offline-capable, with search that works because your device computes blind indexes locally.

Migration without a big-bang cutover

Import existing exports from Slack, Teams, Notion, Google and messaging apps into channels and drives, keep Live Clone mirroring a local folder continuously, and move team by team. Nothing is re-uploaded in the clear at any point.

Frequently asked questions

Is this really a replacement for both Slack and Dropbox?

+

For most teams, yes: channels, DMs, threads, calls, shared drives, external links and search are all in the product. What it deliberately does not offer is anything that requires a server to read your content, such as server-side content indexing or provider-side previews.

How is this different from Mattermost, Element or Wire?

+

Those focus on messaging; storage and external file sharing are separate problems you still have to solve, and some require self-hosting. DRIVUNO is a single hosted workspace covering chat, calls, drive and external sharing under one zero-knowledge key hierarchy.

How is this different from Tresorit, Sync.com or Proton Drive?

+

Those are encrypted storage products with lighter or separate collaboration layers. Here, the team chat and the drive share the same membership model, so revoking someone removes both at once.

Can DRIVUNO read our messages, files or builds?

+

No. Everything is encrypted on the device before it leaves it, with XChaCha20-Poly1305, using keys derived locally with Argon2id and wrapped per member with X25519. Our servers hold ciphertext and sealed key envelopes, so there is no admin view, no support tool and no classifier that can reach your content.

Do we need a technical team to run it?

+

No. There is nothing to self-host and nothing to configure: you create an account, invite people by email, and encryption happens transparently in the browser and apps. Zero-knowledge here is the default, not an expert mode.

Is there a free plan?

+

Yes. The free plan includes 1 GB with exactly the same zero-knowledge architecture as paid plans, so you can validate the workflow before moving a studio onto it.

What happens if someone leaves the team?

+

Removing a member revokes their access and rotates the remaining key envelopes, so their old copy of the key stops opening anything new. Every membership change is written to an append-only audit trail.

What if we lose a password?

+

Because we cannot read your data, we cannot reset it for you. Each account creates a Recovery Kit — a printable PDF with a QR code — to keep offline. That is the same property that stops anyone else, including us, from reading your workspace.

Related

Your sensitive files deserve more than a traditional cloud.

Start free with 1 GB. Zero-knowledge encryption from the first upload — no admin override, no AI scanning, no plaintext on the server.

1 GBfree vault
Encrypted on your device · upload in 1 click
Upload