For teams
Made for teams thatship video every week.
Marketing teams, L&D departments and the agencies working for both. Shared assets, clear approvals, visible cost and a record of every decision.
Shot 1 · 5sv3
Regenerate · 10 crApproveEvery attempt is kept. Approve the one you want; the rest cost you nothing more.
A studio, not a toy.
Workspaces and roles
Each studio is its own isolated workspace with owners, editors and viewers. Invite the agency, the client and the reviewer without mixing their work.
Approvals, not guesswork
Shots move through ready, review and approved. Nothing lands in the final cut until someone on the team has signed it off.
Libraries
Finished cuts, characters, voices and locations live in shared libraries, so the next production starts from what already works.
Cost you can see
Every production shows what it will spend before it renders and what it has spent as it goes, so budgets stay predictable.
Isolated by design
Row-level security keeps every workspace's characters, voices and renders separate. Your cast is yours.
Audit trail
Who briefed, who regenerated, who approved: an activity log records every decision on every shot, and Director notes keep the conversation with it.
Connect Claude or ChatGPT and it works as the person who connected it: same role, same studio, same audit trail, quoted before it spends. Admins see every connection and can cut one off.
How it worksWho ends up living in it.
The teams that get the most out of Backlot are the ones making the same kind of video over and over.
Marketing teams
One recognisable spokesperson across a year of campaigns, without re-booking a studio or hoping the same actor is free. Spin up a vertical cut the same afternoon the idea lands.
Learning and development
Every SOP you have already written becomes a sixty-second refresher with the same host, module after module, and the same host again when the procedure changes next year.
Agencies
A separate workspace per client, with their cast, their voices and their libraries kept apart. Invite the client in as a viewer and let them approve shots themselves.
Questions teams ask
Something we haven't answered? Talk to us.
- How are workspaces kept separate?
- Every row of every table is scoped to a workspace and enforced in the database with row-level security, not just in the application. A member of one studio cannot read another's characters, voices or renders.
- Who can spend credits?
- Owners and admins buy credits; owners, admins and editors can spend them. Viewers can watch, comment and approve without ever being able to start a render.
- Can the client approve without an account in our workspace?
- Invite them as a viewer on their own login. They see the shots and the cut, leave notes and approve, and they cannot change the brief or trigger spend.
- Do you offer single sign-on or volume pricing?
- Yes, on enterprise agreements, along with custom domains. Tell us about the team and we'll put numbers to it.
Bring the whole team in.
Create the studio, invite two people and run one real production through it. That's usually enough to know whether it fits how you work.