A build is the single most valuable file a studio produces, and it usually travels through the least controlled channel available.
“Every build hand-off is scoped, timed and traceable.”
For producers, build engineers and studio it distributing milestone builds to publishers, qa vendors, platform holders and press.
Chunked uploads with checkpointing survive a crash, a closed laptop or a hotel connection and resume where they stopped.
Content hashes and authenticated encryption confirm the stored build matches what left the machine.
Each recipient gets a link with its own expiry, view budget and passphrase — no permanent distribution URL.
Watermarked viewing for cinematics, art and documents makes a leaked frame traceable to a distribution channel.
Every revision is retained with history, so 'which build did they actually play' has an answer.
An append-only record of who was granted access, when it was used and when it was cut off.
Builds end up on personal drives and generic file-transfer services because they are big and deadlines are tight. Those services hold the keys, generate previews, keep links alive indefinitely and give you almost no visibility once the URL is sent.
Sending the same URL to a publisher, an agency and three influencers makes attribution impossible. Separate links with separate expiries turn a leak into a narrow, answerable question.
Revocation is immediate and recorded. Because content is sealed client-side, revoking a link removes the practical path to the file rather than relying on an access rule inside a provider you cannot inspect.
Transfers are chunked and resumable; the practical limit is your plan's storage rather than a per-file ceiling.
Yes — a shared folder or a room gives them an encrypted return path instead of email attachments.
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.
