Skip to content

Security

Your productions stay yours.

How the studio keeps one org’s work away from another, and your files away from everyone.

  • Isolation

    • Every row carries its org and row-level security checks it on every query.
    • The database itself refuses another org’s rows, on every query, and we test that it still holds.
    • The app never connects as the database owner.
  • Sign-in

    • Google or a one-time sign-in link; no passwords to leak.
    • Sessions are bound to the address that made them.
    • Owners, admins and members; editors and reviewers per production.
  • Files

    • Every file leaves storage through our media service, with a token for one file and one org that expires.
    • Originals are copied into our storage the moment they land; providers’ links are never shown.
    • Deleting a production deletes its files.
  • Guests

    • A guest is never a member of your org and reads only what their link allows.
    • Links can need a password, a confirmed email, an expiry; revoking is instant.
    • Downloads can be watermarked with the guest’s email on every frame.
    • Rate limits on every guest action.
  • Memory

    • Your story bible, canon and lessons never leave your org.
    • Your notes on what works per model stay private. Opt in, and you share yours and see other studios’.
  • Where it runs

    • US East (Vercel iad1, Neon us-east-1), with each org’s home region recorded. The EU follows.
    • SSO and SCIM on Enterprise.

Start with the script.

Bring a Final Draft or Fountain file, or open our sample production, and scene one is waiting. Or talk to us, and we’ll show you the studio on your own script.