✓
Files on your disk
All production data — scripts, characters, prompts, takes — lives as plain files in your workspace folder. The workspace folder is the product.
Your workspace stays under your control.
Genlock has no production cloud. Only the prompts, references, and media you intentionally send reach a provider—and they travel under your own account.
✓
Offline license verification
Ed25519-signed keys are re-verified locally on every boot. Licensing and the full editing suite work air-gapped; generation needs whatever network your providers require.
✓
Bring your own credentials
You supply generator and LLM API keys. Genlock uses them locally and never forwards them through Genlock servers.
✓
No Genlock cloud
There is no Genlock server that receives your story data. No upload step, and no telemetry on story content.
How it works in practice
Files live on your disk. License keys are verified offline; nothing is sent to a Genlock server. Provider credentials stay with their owning tools, and generation sends only the inputs you choose.
For teams, git-native collaboration rides your existing GitHub / GitLab / Gitea credentials—no tokens stored in Genlock Studio and no Genlock collaboration server in the middle.