Media generation your finance team can read
One pooled balance, a published price for every run, and access that follows your identity provider. Open weights underneath, so standardising on us is not a bet on us.
What a conversation with us looks like
We would rather find out quickly whether this fits than run you through a funnel. Tell us what you make, how much of it, and which constraints are hard, and we will tell you if another tool is the better answer.
Start the conversation- 01A working session, not a demoWe price a real workload of yours against the catalogue.
- 02Security review up frontThe packet goes to your reviewers before it becomes a blocker.
- 03A workspace, then a pilotSSO, pooled balance, and a team rendering by the end of it.
The parts procurement asks about
SSO and SAML
Sign-in follows your identity provider, so access is granted and removed where the rest of your access already lives.
SCIM provisioning
People arrive and leave through the same directory sync as everything else. No spreadsheet of who still has a login.
Role-based access
Separate who can spend from who can render, and keep admin rights with the people who own the budget.
Pooled spend, itemised runs
One balance for the team, with every run attributable to a person and a model. Costs are known per job rather than reconstructed at month end.
One contract, not six
Veo, Sora, Kling, Runway and FLUX reach you through one account, one invoice and one security review, instead of a separate vendor relationship for each.
Security review materials
SOC 2 materials, a DPA, a subprocessor list and an architecture overview, provided during review.
What comes with a workspace
Team and workspace
- Shared workspace with pooled balance
- Per-member usage attribution
- Admin-managed catalogue access
- Invoiced billing available
Control
- Spend limits and auto top-up thresholds
- Role-based permissions
- Audit trail of runs and spend
- Access revoked through your directory
Security and compliance
- SSO / SAML with SCIM provisioning
- SOC 2 materials on request
- DPA and MSA available
- Subprocessor list and retention policy
Questions
How is enterprise priced?+
On the same per-run catalogue as everyone else, with a pooled balance and invoiced billing instead of a card. The unit price is the published one; what changes is how you pay and who can spend.
Do you train on our prompts or outputs?+
No. Your inputs and outputs are yours. The specifics, including retention windows, are in the security review packet.
Can we run the models inside our own environment?+
For the open-weight ones, in principle: Wan and FLUX publish weights, so the same models can run on your hardware. Sora, Veo and Kling do not publish weights at all, and no reseller can grant what the vendor withholds. Tell us which models your policy covers before you plan around it.
What compliance evidence can you provide?+
SOC 2 materials, a DPA, an MSA, a subprocessor list, a data-retention policy and an architecture overview, shared during a security review.
How long does onboarding take?+
A workspace with SSO and pooled billing is a short setup. The longer part is usually your security review, which is why the materials are ready before you ask.
What happens to our work if we leave?+
Outputs are yours to take, and every model here is the vendor’s own, reachable directly from that vendor if you leave. You are standardising on models that exist without us, not on an endpoint only we can serve.
Bring us a real workload
We will price it against the catalogue in front of you, and say so if the numbers do not work.