Repositories, engine forks, internal tools and signing material are the crown jewels of a studio — and they are routinely mirrored onto consumer clouds and chat products.
“Your codebase should not be readable by a company you have never met.”
For technical directors, build engineers and studio it protecting proprietary engines, tooling and pipelines.
Snapshots, engine forks and tool distributions stored as ciphertext, with names and structure protected as well as contents.
Each engineer holds their own sealed copy of the folder key; there is no shared credential to leak or rotate manually.
Offboarding a contractor rotates the remaining envelopes so their retained copy stops working on anything new.
Live Clone watches a local directory and mirrors it encrypted, giving a versioned off-site copy without a manual ritual.
Hourly snapshots are written to EU object storage under an immutability window, which is what makes ransomware recovery realistic.
Membership and access events are appended to a tamper-evident log without exposing any code.
Code loss splits into three scenarios: exfiltration by an outsider, exfiltration by someone who legitimately had access, and destruction through ransomware. Encryption at the client addresses the first, key rotation and logging address the second, and immutable snapshots address the third.
Patches, credentials, config files and internal tools circulate as chat attachments. If the messaging platform can read its own history, so can every integration attached to it and anyone who obtains a workspace export.
Keep your version control where it is. Use an encrypted workspace for the artefacts that VCS handles badly: large binaries, engine distributions, signing material handled through the password vault, milestone archives and the discussions around them.
Yes — the built-in encrypted vault stores passwords, keys and attachments with the same client-side model, and can import from common password managers.
No. Administration is limited to membership, billing and policy; content access requires a key envelope sealed to a specific device.
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.
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.
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.
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.
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.
Start free with 1 GB. Zero-knowledge encryption from the first upload — no admin override, no AI scanning, no plaintext on the server.
