Team file sharing with controls that survive contact with reality.
Internal drives with per-member keys, external links that expire by default, and an access log you can hand to a client or a legal team.
“Every share has an owner, an expiry and a trail.”
For teams sending builds, masters, contracts, designs and datasets to colleagues, clients, partners and freelancers.
Built for confidentiality
Passphrase-protected links
The key lives in the URL fragment and never reaches the server; a passphrase derived with Argon2id gates the actual decryption.
Expiry by default
Public links carry a maximum lifetime and are destroyed automatically — a forgotten link is not a permanent hole.
View-once and view counters
Limit a link to a single view or a fixed number of opens, and see exactly how many times it was used.
Watermarked viewing
Sensitive material can be displayed in a protected viewer with watermarking, so a screenshot carries context with it.
Access logs
Creation, views, revocation and expiry are recorded in an append-only trail without revealing the file contents.
Very large files
Multi-gigabyte transfers with chunked resumable upload, crash recovery and integrity verification after upload.
Why 'anyone with the link' became the default failure
The convenience of a permanent public link is exactly its danger: it outlives the project, gets forwarded, ends up in a ticket and remains valid years later. Making expiry the default, and revocation instant, changes the shape of the risk.
Sharing without giving the provider a copy in the clear
Files are sealed before upload. A recipient's browser gets the key material through the fragment and the passphrase, decrypts locally, and the platform never observes plaintext at any point of the exchange.
Internal sharing is a key problem, not a permission problem
Instead of an access-control list a server enforces, each member holds a copy of the folder key sealed to their own public key. Removing them rotates the remaining copies, so revocation is cryptographic rather than a promise from the backend.
Frequently asked questions
Can recipients use it without installing anything?
+
Yes. Protected links open in any modern browser; decryption happens in the page.
Can we prove a partner accessed a file?
+
You can show the access log entries for that link — creation, view events and revocation — with no content exposure.
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.