Enterprise
Filmsquare for studios.
Several productions. One process.
For studios with crews across several productions at once: a plan set up with you, controls per production and per department, and hosting on our servers in the EU, with self-host coming soon.
01 · Plans
A plan set up with your studio.
Studio and Production are paid by card, per seat. Enterprise is agreed with you and invoiced outside the card payments.
| Studio | Production | Enterprise | |
|---|---|---|---|
| Price | €59 per seat per month, €49 on annual | €149 per seat per month, €125 on annual | From €2,000 a month, agreed |
| Seats | From 2 | From 3 | Agreed |
| Credits | 1,500 per seat a month, one pool | 3,750 per seat a month, one pool | Committed volume |
| Productions | No limit | No limit | No limit |
| Storage | 50 GB per seat, pooled | 50 GB per seat, pooled | Agreed |
| Reviewers and viewers | Free | Free | Free |
| Payment | Card | Card | Invoice |
Every credit shows what it costs, with the euros next to the credits. A model costs the same credits on every plan.
02 · Control
Who sees what, who decides, what it costs.
Roles and access
Six roles, from owner to viewer. Makers, reviewers and viewers see all productions, the ones you tick, or only what they are assigned.
Sign-off per department
Per department you choose who works on it, who signs off, and whether one of them or everyone must. Finals wait for the steps you lock.
Budget per episode
An episode can carry a budget cap. A take that would go past it is refused before anything is sent to a model.
Everything on record
Who signed off what, with which model, references and version. Picks, sign-offs and costs are only ever added to, and nothing is hard-deleted.
03 · Connect
One API for the app, your scripts and your Claude.
Everything the studio does goes through one REST API, described in OpenAPI 3.1. The app, a person's own Claude and your scripts call the same routes, with the same roles and the same rules. An API key belongs to one person in one workspace and never acts above that person's role.
Webhooks send an event to your URL when a take finishes, fails or is picked, signed with an HMAC of the body. Every crew member can connect their own Claude over MCP; it works in their name, on their own Claude subscription, and costs no Filmsquare credits.
04 · Where it runs
Hosted in the EU. Self-host coming soon.
| Hosted | Self-host (coming soon) | |
|---|---|---|
| Database | EU, Ireland (Dublin) | Your own Postgres |
| Files | Cloudflare R2 | S3-compatible storage, such as MinIO |
| Server | Run by us | One Node.js process: API and workers; several instances are fine |
| Sign-in | Filmsquare accounts | Any OIDC provider that issues JWTs, or API keys only |
| Billing | Credits and euros | Not metered; usage still shown in credits and euros |
05 · Questions
Questions.
What is the Enterprise plan?
A plan we set up with a studio, outside the card payments, from €2,000 a month of committed volume. Seats, credits and storage are agreed with you. Reviewers and viewers stay free.
Where is our data stored?
On the hosted version, the database with workspaces, scripts, comments and accounts is in the EU, in Ireland. Files are stored with Cloudflare R2. The data processing agreement is part of the terms, and a signed copy is available on request.
Can we run Filmsquare on our own servers?
Not yet. Self-host is coming soon: one Node.js process with your own Postgres database and S3-compatible storage such as MinIO. Until then, Filmsquare runs hosted in the EU.
Can we cap what an episode spends?
Yes. An episode can carry a budget cap, set through the API. A take that would take the episode past it is refused before it renders, counting what was spent and what is still rendering.

Tell us about your studio.