Client workspaces with zero data bleed
A workspace per client with separate data and domains, team roles, and a public API with scoped keys.
- Per workspace
- Videos, analytics, domains, integrations
- Roles
- Owner and admin, invites
- Security
- Audit log, hashed API keys
- API keys
- Scoped, with honest rate-limit headers
- Usage
- Plays per workspace
Separate clients, one account
Nothing leaks between clients.
A workspace per client
Separate videos, analytics, domain allowlist, integrations and reporting timezone.
Teams with real roles
Owner and admin roles, invites, ownership transfer, an audit log and hashed API keys.
An API that covers the product
Scoped keys, rate limits with honest headers, idempotency keys and a server-to-server conversions endpoint.
Built for the retainer conversation
Usage bars break plays down per workspace, so you see which client used the quota and invoice from one report.
The whole player, on every plan
Questions about workspaces and the API
What is separated between workspaces?
Each workspace has its own videos, analytics, domain allowlist, integrations and reporting timezone. Nothing leaks between clients.
What team roles are there?
Owner and admin roles, with invites and ownership transfer. Every workspace has an audit log.
What does the API offer?
Scoped, hashed API keys, rate limits with honest headers, idempotency keys, and a server-to-server conversions endpoint.
Can I see usage per client?
Yes. Usage bars break plays down per workspace, so you can see which client consumed the quota and invoice from the same report.
Are reports in the client’s timezone?
Yes. Each workspace has its own reporting timezone, so Monday means the client’s Monday in every chart.