Continuity is the product
Missing media never becomes dead air. ModernPlay steps through filler, station slate, then generated black and silence—bounded to the exact gap.
Controlled pilot · commissioned deployment
Run a 24/7 channel
straight from your object storage.
ModernPlay turns prepared media in your S3 or R2 bucket into a timed, continuously encoded RTMP feed. Schedule it, monitor it, and keep a durable record from one operator console.
- Ingest
- S3 / R2 direct
- Encode
- FFmpeg + NVENC
- Egress
- RTMP / RTMPS
- Record
- Durable as-run
01 The platform
Playout software usually fails at 03:00.
This one is built for 03:00.
ModernPlay is scheduled-VOD playout for broadcast and FAST channels, designed around the three failures that cost operators airtime: continuity, timing, and missing evidence.
The clock is the contract
Schedules resolve to absolute channel-time intervals. Broadcast-day starts, timezones, daylight-saving changes, and hard boundaries stay deterministic.
Everything is evidence
Transitions, fallbacks, and outages land in a durable as-run record. What aired is queryable evidence, not a reconstruction from encoder logs.
02 Current product UI
See the operating loop,
not a feature list.
Build the day, hold the channel, keep the evidence. These are current ModernPlay operator surfaces, captured with representative commissioning data.
Open full interface in a new tabA broadcast day that refuses ambiguity.
The Rundown makes authored state, unresolved time, and publish blockers visible before a plan can reach air. Operators work against the channel clock, not a loose playlist.
Open full interface in a new tabEvery assigned channel in one control surface.
Master Control shows the exact state of each channel—on air, off, or needing attention—with now/next context, controls, alerts, and a direct path to evidence.
Open full interface in a new tabThe transmission record stays queryable.
Every transition becomes a channel-timezone record with clip type, scheduled and actual times, duration, and drift—ready to inspect or export without reconstructing encoder logs.
03 The signal path
Prepare once. Schedule exactly.
Run with evidence.
The operating model is three decisions, not six layers of infrastructure. Technical detail stays available below when your engineering team needs it.
- 01
Prepare once
Upload straight to S3 or R2. ModernPlay checks eligibility, keeps the source untouched, and creates one predictable house mezzanine.
- 02
Schedule exactly
Build the broadcast day with reusable programmes and hard anchors. Validation resolves the channel clock before anything can publish.
- 03
Run with evidence
Prefetch the accepted plan, encode on the GPU, push RTMP or RTMPS, cover failures, alert operators, and record every transition.
04 Technical detail
Open the specification
only when you need it.
The operating story stays short. Engineering detail remains here for fit checks, without making every visitor read a twelve-card inventory.
Scheduling and timingRundown authoring, channel time, and safe boundaries.
- Build broadcast days with reusable programmes, hard anchors, day copy, and planning notes that never air.
- Resolve channel timezones, broadcast-day starts, midnight rollover, and daylight-saving changes into absolute intervals.
- Validate the full day before publication and cut over only at a boundary the accepted plan can honour.
Media and playoutObject-storage ingest, one house profile, and bounded recovery.
- Upload directly to S3 or R2; the local cache remains a rebuildable layer for the accepted plan.
- Return readable eligibility states and rejection reasons for container, codec, frame rate, streams, and audio.
- Normalise accepted media once so every on-air clip shares one stream layout and timebase.
- Encode one approved H.264/AAC profile per channel with FFmpeg and NVIDIA NVENC.
- Preflight RTMP or RTMPS destinations before the operator can start the channel.
- Cover missing media with filler, station slate, then generated black and silence, bounded to the remaining gap.
Operations and evidenceMaster Control, alerting, recovery, and durable records.
- Compare desired and actual state with now/next, remaining time, cache readiness, preview, drops, and restarts.
- Recover from encoder, daemon, and host restarts at the position the channel clock requires.
- Page operators by email or webhook and keep transitions, fallback, outages, exports, XMLTV, and the schedule widget queryable.
05 Deployment
It runs on your node,
under your control.
ModernPlay is commissioned into your infrastructure. Your media, stream keys, database, and network path stay yours; capacity is measured against the channels you intend to run.
FAST and streaming channels
A continuous, well-timed feed for a CDN or aggregator.
Broadcasters with prepared media
A VOD library in object storage, without a traditional playout rack.
Networks and ministries
Multiple channels, one operator surface, and evidence under your control.
Reference deployment
- Host
- Linux + Docker, NVIDIA GPU with NVENC
- Services
- Management app · PostgreSQL · playout daemon
- Storage
- AWS S3, Cloudflare R2, or another S3-compatible bucket
- Cache
- One persistent volume shared by app and daemon
- Egress
- RTMP or RTMPS to your CDN or media server
- Access
- Browser console, session auth, per-channel roles
- Operations
- Preflight, backup, restore, upgrade, rollback, e-stop
06 Scope, stated plainly
What it does today—
and where the boundary sits.
Playout is bought on trust. Start with the three shipped outcomes; open the complete boundary when a specific requirement decides whether ModernPlay fits.
Prepare and schedule
Direct object-storage ingest, eligibility, normalisation, and a channel-time Rundown that must validate before publication.
Run and recover
GPU playout, destination preflight, bounded fallback, and durable desired state across process and host restarts.
Monitor and prove
Master Control, live preview, metrics, alert delivery, audience-side probing, and durable as-run evidence.
Review the complete capability boundary
Shipped today
- S3/R2 browser-direct ingest with eligibility reporting
- Ingest normalisation to a single house mezzanine
- Broadcast Rundown with programmes, hard anchors, and notes
- Timezone and daylight-saving aware plan compilation
- NVENC playout with a fixed H.264/AAC output profile
- RTMP and RTMPS egress with destination preflight
- Filler, slate, and black/silence fallback chain
- Durable desired state with automatic recovery
- Operator console with live preview and controls
- Prometheus metrics, alert rules, email, and webhook
- As-run log, export, XMLTV, and embeddable schedule widget
- Scripted install, backup, restore, upgrade, and rollback
Not shipped
- Logos, clocks, tickers, and lower-third graphics
- Live break-in, RTMP/SRT ingest, and manual switching
- SCTE-35 ad markers and SRT egress
- Multi-node cache distribution and active/passive HA
- Multi-tenant organisations and self-serve billing
07 Questions
Before you
get in touch.
Do you host the channel for us?
No. ModernPlay is installed on a GPU host you own or rent, alongside its database and cache volume. We commission it with you, and you keep control of the media, the keys, and the network path.
What does it cost?
There is no price list, because there is no one-size deployment. Scope depends on channel count, host, storage, distribution, and how much of the commissioning and operations you want us to carry. Send an enquiry and we will scope it against your actual channels.
What media does it accept?
MP4 files up to 5 GB, uploaded straight to your bucket from the browser. Each accepted file is probed and normalised once into a house mezzanine so every clip on air shares one stream layout. Anything that cannot be made to conform is rejected with the reason, before it can reach a schedule.
Where does the output go?
Wherever takes RTMP or RTMPS: a CDN ingest, a Wowza server, or another packaging layer. ModernPlay produces the continuous encoded feed and probes the resulting HLS to confirm the audience side is actually up. It does not package or serve HLS itself.
How many channels can one node run?
That is a GPU, profile, and schedule question, so we measure it rather than guess. Capacity qualification is part of commissioning, and the monitoring that proves it is part of the product.
What happens when something breaks at 3am?
Missing or invalid media is skipped and covered by filler, slate, or generated black and silence. Encoder crashes, daemon restarts, and host reboots resume at the position the wall clock says should be airing. Alert rules page you by email or webhook, and the as-run log records exactly what the audience got.
Controlled pilot · commissioned with your team
Bring us the shape of your channels.
Tell us where the media lives, where the feed must land, and what failure coverage matters. We will confirm fit, qualification needs, and what commissioning would involve.