Skip to content

Compare · checked 16 October 2026

Cloud playout, compared.

APlayout keeps library, schedule, ad breaks, guide and delivery in one service, on an engine of your own. Here is how that compares, including where others are stronger.

Capability by capability.

Columns describe kinds of service, with examples you can check. “Not stated” means we could not verify it publicly.

APlayout compared with enterprise cloud playout, mid-market cloud playout and creator channel tools
Capability APlayout At launch Enterprise cloud playout e.g. Amagi CLOUDPORT, Harmonic VOS360 Mid-market cloud playout e.g. Veset Nimbus, Cinegy Creator channel tools e.g. Viloud, Castr
How you buy Self-serve subscription Sales-led contract Self-serve or 12-month listing Self-serve
Media library and uploads Yes Yes Watch folders or your own cloud Yes
MRSS catalogue, fetched just in time and released after air Yes MRSS ingest Not stated Not stated
Frame-accurate cue points Yes Yes Yes Not stated
SCTE-35 in the output Yes — TS and HLS Yes Yes Partly
Commercial pods with advertiser separation Yes Not stated Not stated Not stated
DVB EIT (now/next and schedule) in the stream Yes Not stated Not stated No
XMLTV guide Yes Not stated Not stated Not stated
SRT, HLS and UDP multicast All three Yes Yes HLS only
Dedicated engine per customer Yes Not stated Your own cloud (Cinegy) Not stated
FAST distribution network and ad sales No Yes (Amagi) No Partly
1+1 or N+1 redundancy No Yes Not stated Not stated
Live inputs, SDI, ST 2110 No Yes Partly Partly

Where APlayout leads

One path, one engine.

  • Catalogues, not copies. MRSS titles are fetched just before air and released after — no bulk copying, no double storage.
  • Broadcast and FAST output from one engine. SCTE-35 in the TS and in HLS, DVB EIT and XMLTV — no separate EPG server.
  • Pods an operator can run. Frame cue points, break rules, advertiser separation and rotation in a six-page console.
  • An engine of your own. A dedicated playout server per customer, not a shared multi-tenant pool.

Where others are stronger

Choose them if you need this.

  • Distribution and ad sales: Amagi and Wurl place channels on FAST platforms and sell the ads. APlayout delivers to any platform that accepts SRT, HLS or UDP, but does not broker distribution.
  • Redundancy: enterprise services offer 1+1 and N+1 playout. APlayout’s first release runs one engine per customer.
  • Scale and certification: the largest vendors run hundreds of channels with security certifications APlayout does not yet hold.
  • Live and studio workflows: live inputs, SDI and ST 2110 belong to broadcast vendors such as Grass Valley, Imagine and Evertz.

Comparison questions.

How is APlayout different from other cloud playout services?
It keeps the whole path in one service — library, catalogues fetched just in time, rules, rundown, frame-accurate pods, DVB EIT and XMLTV, and SRT, HLS and multicast — on an engine of your own, run from a six-page console. Enterprise services are stronger on distribution networks, redundancy and scale.
Is APlayout an alternative to Amagi or Veset?
For independent and mid-size channels, yes: it covers scheduling, SCTE-35 breaks, guide data and IP delivery. It does not offer a FAST distribution network or ad sales, which Amagi does, and its first release does not offer 1+1 or N+1 redundancy.

Be first on air.

Join the waitlist. One confirmation e-mail, then only launch news.

Join the waitlist