The full stack
Catalogue, entitlements, billing, live and VOD pipeline, admin console and the native apps for web, phone and television.
Licence the platform. Run it yourself.
For teams who already operate infrastructure well and want the platform rather than the project. You get the stack and the Terraform that deploys it; you run it, with support available when you want a second pair of eyes.
Who a licence is for
A licence assumes an operations capability that already exists. Where it does not, implementation or a managed agreement is the honest recommendation.
- OTT platforms
- Services with their own platform team who want the software and not the engagement.
- Telcos and ISPs
- Operators with a mature NOC that runs its own infrastructure and intends to run this too.
- Enterprise network operators
- Organisations whose policy requires software to be operated in-house by their own staff.
For teams who do not need the project
If you have an experienced platform team, the expensive part of an implementation engagement is work you can do yourself. Licensing exists so that you are not paying for it twice.
What you are actually buying is the integration — the fifteen components that already agree with each other about identity, entitlement, encryption and playback state — plus the Terraform that stands the whole thing up. What you are not buying is somebody to run it, which is the point.
What's included
The Terraform that deploys it
The modules that build the estate — on Proxmox, on AWS, or the hybrid split — so you are not reverse-engineering a deployment.
Architecture and runbooks
The high-level design, service documentation and the operational runbooks the managed service itself runs against.
Platform releases
New versions, security patches and upgrade notes for the term of the licence.
Available, not mandatory
A support channel for the times a second opinion is worth more than another hour of reading. Priced separately so you only pay if you want it.
A running start
A short onboarding so your team does not spend the first fortnight discovering things that could have been said in an afternoon.
How licensing runs
Fit check
A short conversation about your team and estate. If implementation would serve you better, that is what we will say.
Onboarding
Architecture walkthrough and the first deployment done together, into your own environment.
You deploy
Your team runs the rollout on your timeline, with the support channel open if you want it.
Ongoing releases
Versioned updates and security patches, with upgrade notes for each.
Is this the right engagement?
You run infrastructure already
Terraform, containers and an on-call rota are normal for you. You want the platform, not the hand-holding.
This would be your first platform
A licence with nobody to run it is shelfware. Implementation or managed is the honest recommendation, and it is the one you will get.
The things people ask first
Is the source code included?
That depends on the licence tier and is one of the first things to settle in a conversation, because it changes both the price and what you are able to do afterwards.
Can we modify it?
Within the licence terms, yes — and the Terraform is meant to be adapted to your estate rather than used untouched.
What if we get stuck mid-deployment?
That is what the support tier is for. It is optional precisely so that it is there when it is needed rather than billed when it is not.
Ask about licensing
Tell us about your team and your estate. If you already run infrastructure well, this is usually the cheapest route to the same outcome.