Media Fabric Cloud

We build the fabric.
You choose the rest.

An MXL-aligned, NMOS-controlled, ST 2110 / IPMX-compatible media platform for public and private cloud — engineered so every application above the fabric stays yours to choose. No walled garden. No single-vendor lock-in.

fig. 01 — the weave
13platforms
L3 vendors mapped
4layers
media-exchange mechanisms
1brand
we own — the fabric
0lock-in
above the fabric
§01 philosophy

Open by design.
Not by accident.

Most cloud broadcast platforms make a deal with you on day one: take our entire application stack, or take nothing. Thomson Cloud inverts that. The fabric is ours. Everything you do on top of it — playout, MAM, live sports, graphics, news, monitoring — stays an open choice, sourced from whichever best-of-breed vendor wins the workflow.

closed platform
The walled-garden model
  • One vendor's apps, one vendor's billing, one vendor's roadmap
  • Token-based pricing with up to 95% spread between disciplined and undisciplined operation
  • Reselling a competitor's brand on every customer deal
  • Migration cost compounds with every channel you add
  • Procurement teams flag “vendor lock-in” in tier-1 RFPs
vs.
open fabric
Thomson Cloud
  • One fabric, MXL-aligned and standards-first — open at every seam
  • Best-of-breed application layer: pick the playout, MAM, sports, news, graphics vendor that wins the workflow
  • Predictable infrastructure pricing. No token roulette
  • Adding a 13th, 40th or 100th channel costs near-zero in license terms
  • Procurement-winning answer to “does this avoid lock-in?”
§02 what we brand

The fabric is the only thing we own.

The whole platform is engineered around a single discipline: Thomson brands and operates the media-exchange fabric — the layer that makes uncompressed media available, in real time, between software functions running on cloud or on-prem infrastructure.

Everything above it is a partner. Everything below it is a standard. That separation is the product.

Thomson Cloud uses the EBU / Linux Foundation MXL specification for in-cluster software-to-software media exchange via shared-memory ring buffers, RDMA fabric for cross-host exchange, and ST 2110 / SRT / JPEG XS for facility and inter-region transport.
Applications choose any vendor
Playout · MAM · Sports · News · Graphics · MCR · Monitoring
Best-of-breed partner ecosystem — swappable per workflow
↑ NMOS IS-04 / IS-05 connection control ↑
L3 — Workflow Platform Thomson brand
Thomson Cloud — operator UX, alliance program, billing, orchestration
Customer relationship, application catalog, operations wrapper
L2 — Media Exchange Fabric Thomson brand
MXL shared-memory · RDMA (Rivermax / EFA) · NMOS control plane
Zero-copy in-cluster exchange · microsecond cross-host · frame-accurate switching
↑ ST 2110 · SRT · JPEG XS · NDI · IPMX ↑
L1 — Network Fabric vendor-neutral
Cisco IPFM · Arista MCS · NVIDIA Spectrum · public cloud transit
Physical IP transport — multicast, hitless protection, PTP
§03 the signal journey

From the venue
to the viewer.

Every frame on Thomson Cloud takes the same standards-aligned journey. Contributed at the edge, exchanged across the fabric at microsecond latency, processed by any partner application, distributed to any audience. Here is what happens between the stadium and the screen.

VENUE SRT · JPEG XS EDGE contribution THE FABRIC MXL · RDMA · NMOS APPS any vendor VIEWER linear · FAST · OTT SRT ingestST 2110 / MXLNMOS routingCDN / DTH / DTT
fig. 02 — signal journey · venue → fabric → viewer
step 01

Contribute

Live cameras, OB trucks, news crews and remote contributors enter the fabric via SRT, JPEG XS or ST 2110 — through any vendor's edge gateway.

step 02

Exchange

The Thomson fabric exchanges uncompressed media between software functions — MXL shared-memory in-cluster, RDMA across hosts. Microsecond latency.

step 03

Process

Best-of-breed partner applications — playout, MAM, sports, news, graphics, monitoring — read from and write to the fabric using NMOS control.

step 04

Distribute

Frame-accurate output to linear channels, FAST, OTT, ATSC 3.0 and DTH — across any region, any CDN, any audience.

§04 built for

Wherever broadcast
meets the cloud.

Six environments shape the modern broadcast cloud. Thomson Cloud is engineered for all of them — same fabric, same standards, same openness.

live sports

Tournaments & live events

Multi-camera contribution, slo-mo, replay and live graphics — ingested at the venue, processed in the cloud or on-prem, distributed worldwide with sub-second glass-to-glass latency.

LIVE · BREAKING NEWS · LIVE · BREAKING LIVE
news

24/7 news production

NRCS, MOS-controlled graphics, remote contribution, automated playout and ticker — every newsroom workflow runs on the same open fabric, with rundown-grade reliability.

CH 01CH 02CH 03CH 04CH 05CH 06CH 07CH 08CH 09CH 10CH 11CH 12
fast / ott

FAST & streaming channels

Scale to dozens or hundreds of linear channels in the cloud — playout, scheduling, branding, ads, transcoding, packaging — with per-channel economics, not per-token surprises.

THOMSON
mobile production

OB trucks & remote production

Run the fabric inside the truck for full on-prem operation, or bridge to the cloud for hybrid remote production — the same MXL fabric on both sides, same control plane, same workflows.

EUAPACLATAMMENA
sovereign broadcast

National broadcasters & tenders

Country-resident deployments, air-gapped operation, regulator-aligned data residency — the same fabric runs inside your sovereign infrastructure with no dependency on US hyperscalers.

PGM
mcr-as-a-service

Master control & multiviewer

Remote MCR with 2110-native multiview, loudness, SCTE compliance and full operator surfaces — driven from anywhere, displayed anywhere, with no specialist hardware required.

§05 the application layer

Eight workflow domains.
Your vendor in every one.

We do not ship a closed app catalog. Above the fabric, every workflow domain is open to the best vendor for the job. Below are the eight domains we certify against the Thomson fabric — alongside the partners customers are already deploying.

01 / playout

Channel origination & playout

Cloud, on-prem and hybrid playout for linear and FAST channels — with branding, transmission, scheduling and as-run.

Imagine Aviator · Evertz Mediator-X · Techex tx darwin · Norsk
02 / MAM

Media asset management

Ingest, archive, search, rights, metadata, AI enrichment and content lifecycle across the production chain.

Avid MediaCentral · Dalet · Cantemo · Iconik
03 / live sports

Sports, slow-mo & live production

Replay, super-slo-mo, OB and live sports workflows — fully integrated with the Thomson fabric.

EVS LiveCeption · Ross Video · Hawk-Eye · Simplylive
04 / news

News production & NRCS

Newsroom computer systems, rundowns, MOS-controlled graphics, story-centric editorial workflows.

Avid iNEWS · Dalet Galaxy · Octopus · Ross Inception
05 / graphics

Branding & real-time graphics

Browser-rendered overlays, AR / VR, virtual studio and data-driven motion graphics for any channel.

Singular.live · Vizrt · Ross XPression · Brainstorm
06 / MCR & control

Master control & operator UX

Vendor-neutral operator surfaces, panels and macros — designed to abstract every application below.

Bitfocus Companion · Stream Deck Studio · Lawo VSM · custom UX
07 / contribution

Contribution & transport

Protected SRT / JPEG XS contribution into the cloud, satellite replacement, multi-region distribution.

Techex tx edge · TVU Networks · AWS MediaConnect · Haivision
08 / monitoring

Quality, monitoring & multiview

MXL-native and 2110-native monitoring, multiview, QC, loudness and SCTE compliance.

TAG Video Systems · Bridge Technologies · Telestream · Qligent
+ partners

Your vendor not listed?

If your preferred partner speaks MXL, NMOS, ST 2110 or SRT — they already integrate. If they don't yet, we'll get them there.

§06 public & private cloud

One fabric.
Two deployments.

The same Thomson fabric runs on the public cloud of your choice, inside your own data center, or as a hybrid that bridges both. Standards-aligned at every interface — so the deployment topology is a procurement decision, not a re-engineering one.

EU-WEST PRIMARY APAC US-EAST MENA ○ PUBLIC CLOUDAWS · GCP · AZURE
○ public cloud

Thomson Cloud — Public

A managed multi-tenant service running on AWS, GCP or Azure. Per-channel economics, elastic burst capacity, region failover, and Marketplace billing.

  • HostsAWS · GCP · Azure (customer choice, or multi-cloud)
  • TransportAWS CDI / MediaConnect, NVIDIA Rivermax, ST 2110, SRT
  • BillingPer-channel, predictable. No token roulette.
  • BurstingElastic capacity for events, sports tournaments, breaking news
  • SLAs99.99% managed service with regional failover
  • Best forFAST channels, OTT, contribution-in, multi-region playout
YOUR DATA CENTER MXL RDMA ● PRIVATE CLOUDON-PREM · SOVEREIGN
● private cloud

Thomson Cloud — Private

The same fabric deployed inside your facility, on COTS Linux servers and your existing IP network. Air-gapped, sovereign, or regulator-compliant — your call.

  • HostsCustomer data centers, on-prem Kubernetes, OB trucks
  • TransportST 2110, IPMX, JPEG XS, MXL shared-memory, RDMA
  • SovereigntyAir-gapped, country-resident, regulator-aligned
  • HardwareVendor-neutral COTS — Cisco, Arista, NVIDIA, Mellanox
  • OperationsManaged by Thomson or operated by your team
  • Best forNational broadcasters, sovereign tenders, ATSC 3.0, OB trucks
§07 standards we ride on

Standards-first.
Always.

The dominant criterion in tier-1 broadcaster RFPs is now “does this avoid lock-in?” Standards-first positioning is the highest-leverage decision a cloud broadcast platform can make. Here is the full standards stack the Thomson fabric is built on.

MXL
EBU / Linux Foundation media exchange — shared-memory ring buffers between software functions
NMOS
AMWA IS-04 discovery & IS-05 connection management — the control plane
ST 2110
SMPTE -20 / -22 / -30 uncompressed IP for facility and inter-region transport
IPMX
Open AV / broadcast convergence standard — mandatory for enterprise & education tenders
SRT
Secure Reliable Transport — internet-friendly protected contribution
JPEG XS
Visually lossless mezzanine compression for cost-efficient contribution links
RDMA
Rivermax / EFA cross-host kernel-bypass exchange — microsecond latency
NDI
Practical edge-production gateway — PTZ, software production, fast deployment
rfp-ready answer · how does your platform make media available between functions?
Thomson Cloud uses the EBU / Linux Foundation MXL specification for in-cluster software-to-software media exchange via shared-memory ring buffers, RDMA fabric (Rivermax / EFA) for cross-host exchange, and ST 2110 / SRT / JPEG XS for facility and inter-region transport. Connection management is NMOS IS-04 / IS-05. This avoids vendor lock-in at the media exchange layer while supporting MXL-aligned partner applications from any vendor.”
talk to thomson cloud

Let's talk about your fabric.

Sovereign deployments, tier-1 broadcaster RFPs, FAST playout, MCR-as-a-service, ATSC 3.0, sports rights workflows — wherever you are on the road to cloud, we'd like to hear what you're building.

Email us at