01
Content systems
Ingestion, catalogue, metadata, taxonomy and the editorial tooling around them.
Platforms
Complete platforms, built to be operated by someone else.
Technology developed for licensing has to survive contact with an operator who did not write it. That single constraint shapes how everything here is designed, documented and released.
- Form
- Deployable product, not a project
- Release
- Versioned with a reproducible build
- Integration
- Documented, stable interfaces
- Support
- Defined in the licence
01 / Components
What a platform is made of.
02
Media delivery
Transcoding, packaging and origin serving, with delivery routed across multiple providers.
03
Playback
A player and playback layer tuned for real devices and real networks, not for a demonstration reel.
04
Accounts and identity
Registration, authentication, session handling and single sign-on across multiple properties.
05
Entitlement and billing
Subscription state, payment provider integration, renewals, refunds and reconciliation.
06
Operations tooling
The administration, monitoring and recovery tooling an operator needs on day one.
02 / Architecture
Layered so parts can be licensed on their own.
A licensee rarely wants everything. The layers are separable, and each has its own interface, so a licence can cover the analytics layer alone or the whole platform.
Separation is enforced at the interface rather than by convention, which is what makes a partial licence practical instead of theoretical.
L5Product interfacesWeb · API · admin
L4Application servicesAccounts · billing
L3Media servicesTranscode · package
L2AnalyticsIngest · store
L1InfrastructureOrigin · CDN · storage
03 / Engineering for load
Designed for sustained traffic.
Platforms are built for continuous high request volume rather than for a launch spike: caching at every appropriate layer, database access patterns designed rather than discovered, and delivery that can be moved between providers without a rewrite.
Capacity, cost and failure behaviour are engineering inputs from the beginning, because an operator inherits all three.
P1
Caching
Layered caching from edge to object, with explicit invalidation paths.
P2
Data access
Query patterns designed against the schema rather than emerging from it.
P3
Portability
Delivery and storage providers are configuration, not architecture.
P4
Failure behaviour
Degradation paths defined so a component failing does not take the product down.