Technology
Architecture built for channels that run around the clock
MSOOCast separates configuration, media, decisions, and data. Media runs wherever it needs to, close to the source, the headend, or the viewer, while operators work from one console.
How the pieces fit
Content and live feeds enter on the left and leave as packaged, ad-stitched streams on the right. The control plane configures every step; the data plane records every result.
Sources enter on the left: library files and live feeds. Ingest and QC checks format, loudness, and captions. Originate runs Channel Foundry and Live Desk. Insert and package runs Edge Splice with Moment Exchange. Deliver sends Network Fabric output to FAST platforms, apps, headends, and rooms. The control plane configures every step. The data plane records every result.
Control plane
Channels, schedules, live events, destinations, users, and rules. Everything an operator configures, exposed through the console and the API.
Media plane
Ingest, playout, packaging, and splicing. Media plane nodes run in the cloud or at the edge, close to the source or the viewer.
Decision plane
Context analysis, demand integration, and pod construction. Decisions are made ahead of the break so stitching never waits.
Data plane
As-run logs, ad delivery, session quality, and proof of play. Exportable to your warehouse or BI tools.
Deployment options
The same software runs in three places. Many customers combine them, for example cloud playout with ad insertion on servers at the headend.
Managed cloud
MSOOCast runs the platform for you in redundant cloud regions. Nothing for your team to install, patch, or scale.
Your cloud account
The platform is deployed into your AWS, Google Cloud, or Microsoft Azure account, so media stays in your account and usage counts toward your committed spend.
On-premises and hybrid
Edge Splice and Network Fabric nodes run at your headend, facility, or property, with control in the cloud or on site.
| Topic | Managed cloud | Your cloud account | On-premises and hybrid |
|---|---|---|---|
| Control plane | MSOOCast cloud | MSOOCast cloud or your account | MSOOCast cloud or on site |
| Media processing | MSOOCast cloud regions | Your AWS, Google Cloud, or Azure account | Your servers at the headend, facility, or property |
| Infrastructure upkeep | MSOOCast | Shared: MSOOCast software, your account | Shared: MSOOCast software, your hardware |
| Typical use | FAST channels, publishers, and new streaming launches | Broadcasters and streaming services with existing cloud agreements | IPTV operators, hotel groups, venues, and air-gapped facilities |
Reliability practices
A channel that drops costs viewers and revenue. These are the defaults, not add-ons.
Redundant origination
Each channel can run on two playout instances in separate zones, with automatic switchover.
Input failover
Primary and backup sources are monitored for loss, black, freeze, and silence.
Never dead air
If an ad decision fails or a break is unsold, the break falls back to promos, slate, or the original content.
Multi-CDN
Streams publish to more than one CDN, with traffic steered by health.
Change safety
Schedule and configuration changes are versioned and can be rolled back.
Observability
Metrics, logs, and traces for every channel, available to your team and ours.