Security
Your footage stays yours.
goframe was built for client work. The guarantees below are architecture, not policy: the system is shaped so the pixels stay under your control.
Rendering never leaves the device
Preview and export run in the browser with WebCodecs. Frames are composed and encoded on your hardware; there is no render farm to upload to.
Media in your own storage
Source files live in your storage bucket and cache locally for offline work. Deleting them there deletes them, full stop.
No training on your content
Your footage, transcripts, and projects are never used to train models. AI providers process requests under no-training terms.
Every change on the record
Human and agent edits are committed to a git-style project history with semantic descriptions. Any state can be audited and restored.
Access enforced at the row level
Roles and invites are backed by row-level security in the database, not just hidden buttons in the interface.
Workspace isolation
Clients and teams live in separate workspaces with separate membership. Cross-workspace access does not exist.
0
frames uploaded to render servers
0
models trained on customer content
100%
of changes logged and restorable
Controls that scale with the team.
The same primitives work for a two-person studio and a hundred-seat organization.
Roles and invites
Owners, editors, and reviewers per project. Invites are revocable and expire.
Audit history
Who changed what, when, and with which tool: the project log answers compliance questions.
Credit governance
AI spend is metered per workspace with a shared pool, so budgets are visible and capped.