Live Clone7 min read•
Encrypted continuous backup for NDA creative studios: PSD, RAW and 4K rushes without exposure
Client work under NDA cannot sit readable on a provider's disk. Here is how a studio mirrors terabytes of active project files with zero-knowledge encryption and per-folder read-only sharing.
Try it in one click.
Three private surfaces. Same zero-knowledge architecture.
The contractual problem Almost every serious client contract contains a confidentiality clause. Most creative teams then store the same material on a cloud whose terms allow provider-side processing for indexing, safety and product features. The gap between the contract and the infrastructure is rarely inspected until something leaks.
What studios actually need - Terabytes of active project data mirrored continuously, not weekly. - Large binary formats — PSD, PSB, RAW, PRPROJ, AEP, 4K/6K rushes — handled without RAM explosions. - Read-only access for a client or a producer, folder by folder, revocable. - A verifiable statement that the vendor cannot read the files.
How Live Clone handles this Folders are watched continuously and diffed by SHA-256. Only changed files are encrypted and uploaded, in streaming chunks so a 40 GB export never has to fit in memory. Version history means yesterday's grade is still there after today's overwrite.
Encryption model in one paragraph Each file gets a fresh XChaCha20-Poly1305 key generated in the browser. That key is wrapped with your X25519 account key, derived from your passphrase with Argon2id. The server receives ciphertext plus a wrapped key it cannot open. Filenames are encrypted; search runs on blind indexes.
Sharing with a client without giving away the vault Share a single cloned folder read-only with named email addresses. Each recipient receives a key envelope sealed to their public key — access is cryptographically scoped to that folder and nothing else. Removing a recipient triggers key rotation on the remaining envelopes.
What your NDA answer becomes Instead of "our provider promises not to look", it becomes "our provider is architecturally unable to look, and access to this project folder is limited to these three named people". That is a materially stronger position in any audit or client review.
Rolling it out Mirror one project first, verify the integrity report, then add the rest of the working disk. Exclusion globs keep caches and render temp directories out of the pipeline.
Try it in one click.
Three private surfaces. Same zero-knowledge architecture.