Seats, shared drives, admin controls and audit logs — with encryption that happens before anything leaves an employee's device.
“The only people who can read company data are the people you gave keys to.”
For companies from five to several hundred people that treat their documents as a liability if exposed.
Invite by email, manage seats, pool storage across the team and see who has access to what.
Every member of a drive receives their own sealed envelope of the folder key; removal rotates the rest.
Append-only records of membership, sharing and access events for internal review.
Protected links with expiry, passphrase, watermark and revocation for clients and vendors.
Passkeys, TOTP, step-up verification and reviewable device trust across the organisation.
Hourly encrypted snapshots to immutable object storage, with restore tooling.
In a conventional cloud, an access-control list decides who may decrypt, and the decryption itself happens on a server that can always do it. In a zero-knowledge system, the ability to decrypt is the access control: no envelope, no key, no read — regardless of a bug, a misconfiguration or an administrator's mistake.
The riskiest week for company data is the one after someone leaves. Removing a member here revokes their session, rotates the remaining key envelopes for their drives and writes the change to the audit trail, in one operation.
Replacing separate storage, chat, calls, mail and password tooling with one encrypted workspace usually reduces both spend and the number of places a copy of your data can exist.
No. Administrators manage membership, seats and billing. They cannot decrypt content they were not given a key envelope for, and every membership change is logged.
Revoke the device from the session list; its cached material becomes useless without credentials, and passkey or password re-authentication is required to reconnect.
No. Everything is encrypted on the device before it is uploaded, 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.
No. There is nothing to self-host and no key server to operate. You create an account, invite colleagues and clients by email, and the encryption happens transparently in the browser, desktop and mobile apps.
We do not currently hold SOC 2 or ISO 27001 certification, and we say so publicly rather than implying otherwise. Our compliance page documents where we are, what is in progress, and what is planned. What we can demonstrate today is the architecture itself: client-side encryption, per-member key envelopes and an append-only audit trail.
Removing a member revokes access and rotates the remaining key envelopes, so an old copy of a key stops opening anything new. Every membership change, share creation and revocation is written to an append-only log.
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 be stored offline. That is the same property that stops anyone else, including us, from reading the account.
Yes. The free plan includes 1 GB with exactly the same zero-knowledge architecture as paid plans, so you can validate a real client workflow before committing.
Start free with 1 GB. Zero-knowledge encryption from the first upload — no admin override, no AI scanning, no plaintext on the server.
