Skip to content

MSOOCast LLC is opening U.S. operations. We're scheduling launch consultations for FAST, OTT, and IPTV channels now. Book a consultation

Platform

One platform from playout to proof of play

MSOOCast connects the steps that are usually separate systems: scheduling and playout, live control, ad signaling, ad decisions, stitching, and delivery. One control plane configures them, and one data plane reports what actually aired.

Book a demoArchitecture

Five products, one signal chain

  1. 1. Originate

    Channel Foundry

    Cloud playout and channel origination

    Channel Foundry is the playout and scheduling layer. Programmers build the day, apply the channel's look, and place ad breaks once. The same channel then plays out to FAST platforms, your own apps, IPTV headends, and in-room TV without a second system.

  2. 2. Go live

    Live Desk

    Live workflow and event control

    Live Desk brings every live source into a single operating view: program and preview, automatic failover, live graphics, and a break button that sends a correct SCTE-35 cue every time. It is built for sports, news, and any event that cannot miss a cue.

  3. 3. Insert

    Edge Splice

    SCTE-35 server-side ad insertion

    Edge Splice reads SCTE-35 cues in the stream, asks for a decision, and stitches the ads into the stream on the server side, frame-accurately. Viewers get a broadcast-smooth break, ad blockers have nothing to block, and you get proof of what aired in every session.

  4. 4. Decide

    Moment Exchange

    AI-powered advertising and yield

    Moment Exchange decides what runs in each break. It reads the scene that leads into the break, the session, and every source of demand, then builds the pod that earns the most within your rules on brand safety, separation, and frequency.

  5. 5. Deliver

    Network Fabric

    Distribution and delivery

    Network Fabric takes one channel and delivers it to every destination: FAST platforms, your OTT apps, IPTV headends, and hospitality properties. Each destination gets the format, markers, and program guide it needs, and you see what is on air everywhere from one view.

Four planes, clearly separated

Configuration, media, decisions, and data are separate layers. That is what lets media nodes run at a headend while decisions and reporting stay in the cloud.

  • Control plane

    Channels, schedules, live events, destinations, users, and rules. Everything an operator configures, exposed through the console and the API.

    • Console and REST API
    • Webhooks and event stream
    • Roles, SSO, and audit log

  • 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.

    • Ingest and transcoding
    • Playout engines
    • Packagers and splicers

  • Decision plane

    Context analysis, demand integration, and pod construction. Decisions are made ahead of the break so stitching never waits.

    • Context models
    • Ad server and OpenRTB connectors
    • Rules and floors

  • Data plane

    As-run logs, ad delivery, session quality, and proof of play. Exportable to your warehouse or BI tools.

    • As-run and proof of play
    • Session and QoS metrics
    • Exports and reporting API

Read the architecture

Services every product shares

Operators learn one console. Engineers integrate one API.

  • Monitoring and alerts

    Stream health, cue validation, and destination status, with alerts to email, Slack, PagerDuty, or a webhook.

  • Analytics and proof of play

    As-run, ad delivery, and session data in the console and as exports for billing and reconciliation.

  • APIs and webhooks

    Create channels, change schedules, take breaks, and read results from your own systems.

  • Roles and single sign-on

    Permissions by team, channel, and action, with SAML or OIDC single sign-on.

  • Audit log

    Every change to a schedule, break, rule, or destination is recorded with who made it and when.

  • Environments

    Separate staging and production environments, so changes are tested before they reach air.

Run it where you need it, operated by whoever you choose

  • 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.