FAST and DR
from $499per channel per month
cloud infrastructure included
- Standard configuration, including cloud infrastructure
- CDN usage billed pay-as-you-go
- DR: 24 hours of active playback a month included
- FAST: pay-as-you-go, no lock-in
Veset Nimbus plays out 24/7 linear channels from AWS. Run it from the console, the REST API, or an AI agent over the public Nimbus MCP server.
The Nimbus MCP server exposes the full Nimbus API to AI assistants, with the same interface for every Nimbus type. An agent can read the timeline, change the schedule and check playout status in the same calls your team would make through the REST API.
To connect, add the endpoint to an OAuth-compatible MCP client such as Claude or Codex, sign in with your Nimbus account and approve the mcp:read and mcp:write permissions. The agent then works with that user's role permissions. Service providers can manage the playouts of every organisation they run from one MCP connector. The MCP server is included in every Nimbus plan and in the 7-day trial.
https://mcp.veset.tv/mcpWhat's on Channel 1 after 21:50, and are its outputs healthy?
get_channel_timeline(channel: "Channel 1", from: "21:50") 21:52:10 Ad break [SCTE-35]21:54:10 City council, live [SRT in]22:30:00 Late film: Harbour Lightsget_playout_extended_status(channel: "Channel 1") playout A on air outputs 4/4 okplayout B in sync outputs 4/4 okAn ad break at 21:52, the live council session at 21:54, then the late film at 22:30. Both playouts are running and all four outputs report OK.
Nimbus takes content from where it already is and schedules from the system you already use.
S3‑compatible storage · SFTP · Azure Blob · Google Cloud Storage
Ingest from any S3‑compatible storage, SFTP, Azure Blob or Google Cloud Storage. MAM and storage can stay on another cloud while playout runs on AWS.
SRT · HLS · ABR HLS · RTMP · RTP‑FEC 2D · CDI · JPEG XS
Native live inputs. Zixi, RIST and other protocols come in through AWS MediaConnect, which Nimbus sets up automatically.
BXF · XML · XLSX · CSV · JSON
Import playlists through the console, the API or MCP, or an S3/SFTP watch folder. Custom formats get a parser during onboarding.
If a live input drops, the playout falls back to a backup input or the emergency playlist, returns to live when the signal comes back, and sends an alert.
All inputs and file formatsEach channel's playout runs on an instance sized to the channel. No licence limits on inputs, outputs or resolution.
Playlists and secondary events from the console, API or MCP. An XMLTV EPG is generated from the schedule.
Files and live inputs on time, 24/7. Live input to output is typically 2‑5 s with SRT in and SRT or TS out.
HTML5 graphics rendered in the playout, with logos, tickers, lower-thirds, L-shape and picture-in-picture.
SCTE‑35 from the schedule or the API on TS‑based outputs, for downstream ad insertion such as AWS Elemental MediaTailor.
Several outputs per playout, each with its own encoder. H.264, HEVC or MPEG‑2, SD to 4K UHD at up to 60 fps.
Nimbus can run two synchronised playouts with the same outputs, in one AWS region or two. You receive both feeds, and your receiver or MCR chooses which one goes on air. Nimbus doesn't switch between them.
For multi-region operation there is Nimbus HA.
Both feeds identical and in sync.
Illustration. Regions and output settings are examples.
Several outputs per playout, each with its own encoder settings.
UDP · RTP‑FEC 2D · Dual RTP · SRT · RTMP · HLS
UDP, RTP/UDP, RTP‑FEC and Dual RTP (SMPTE 2022‑7) for path redundancy. SRT caller and listener, RTMP push and server, HTTP, HLS and HLS push. Zixi, RIST and RTP through AWS MediaConnect.
H.264 · HEVC · MPEG‑2 · AAC · AC‑3 · E‑AC‑3
SD, HD and 4K UHD up to 60 fps. HEVC isn't available on RTMP. E‑AC‑3 5.1, PCM / SMPTE 302M in TS, AC‑3 and E‑AC‑3 passthrough, Dolby E passthrough.
CEA‑608/708 · DVB bitmap · WebVTT · XMLTV
CEA‑608/708, DVB bitmap, WebVTT for HLS, burn-in, and ARIB B24/B40. XMLTV EPG from the schedule, platform-specific XML on request.
AWS by default, with dedicated Hetzner support. Run in your own cloud account or on resources Veset provides. Same features on both, except AWS-specific services such as MediaConnect.
Channels in one account share the content library and schedules, and the same operators run all of them.
Playouts can run on demand, for a channel that exists only for an event.
Veset is a technology partner. You own the channel and its revenue.
SSO (SAML/OIDC), MFA, role-based access, encrypted storage and transport, and an audit log of user and API actions.
Email helpdesk and phone in all offers. Support on request, not an eyes-on monitoring service.
from $499per channel per month
cloud infrastructure included
from $999per channel per month
excluding AWS
Custom
Try it first: a 7-day trial with all features and the REST API, and no automatic billing. Full terms on the pricing page.
More than 100 broadcast channels, mostly traditional 24/7 curated channels that have run for years.
With its advanced capabilities and extensive feature list, Veset Nimbus met all our requirements, which included enhanced flexibility and redundancy, efficient day-to-day management, dynamic graphics capabilities, and multiple-user access.
Number of channels, how they're delivered and when you need them on air. A demo is an online call of 30 to 60 minutes and covers the whole Nimbus workflow: file and live ingest, asset management, scheduling, playout and outputs.
Or email sales@veset.tv.
We'll reply to . Sales requests get an answer within five business days.