Veset Nimbus imports your playlists, keeps the media library the schedule plays from, and generates the EPG. Schedules arrive from your traffic system, a watch folder, the REST API or MCP, and every channel in the account works from the same library.
Keep your traffic or scheduling system. Nimbus takes its playlists in the format it already produces.
BXF · XML · XLSX · CSV · JSON
Playlist formats Nimbus imports. A custom format gets its own parser during onboarding.
S3 watch folder · SFTP watch folder
Drop a playlist into an S3 or SFTP folder and Nimbus picks it up.
Console upload · REST API · MCP
Upload in the console, push schedules from scripts or a traffic system through the REST API, or let an AI assistant edit them through the Nimbus MCP server.
The EPG comes out of the same schedule as XMLTV. Platform-specific XML formats are available on request.
From any S3-compatible storage or SFTP, and from AWS Glacier, Azure Blob and Google Cloud Storage. Third-party MAM and CMS systems can be integrated.
Video, audio, subtitles, graphics, and XML or other metadata.
Edit, cut and copy, metadata, tagging, cue points, archiving and a folder structure.
Asset metadata is compared against rules you set. Third-party video analysis connects through the API.
Channels in the same Nimbus account share the content library and schedules.
The same operators work on every channel in the account, without switching accounts through SSO.
Base a new channel on a main channel by transposing its playlists to another time zone or a time delay.
A channel where most content matches the main one, but the ad breaks, compliance edits or graphics differ.
HTML5 graphics templates can take their data from the schedule.
L-shape, credit squeeze and picture-in-picture, triggered from the schedule.
SCTE-35 markers from the schedule, on TS-based outputs, for ad insertion downstream.
XMLTV generated from the schedule, with platform-specific XML on request.
Live events sit in the schedule alongside file events.
Build schedules from reusable blocks and plan templates.
Validate a schedule before it goes to air.
A CSV or JSON report of scheduled assets that aren't in the library yet.
Lock a channel while you edit it, so two people's changes don't clash.
BXF, XML, XLSX, CSV and JSON. If your system produces another format, Veset builds a parser for it during onboarding.
Yes. Push them through the REST API, or drop the files into an S3 or SFTP watch folder.
Yes, as XMLTV from the schedule. Platform-specific XML formats are available on request.
Yes. Validate the schedule, and run the missing-assets report to list scheduled assets that aren't in the library yet.
Yes. Channels in one Nimbus account share the content library and schedules, and a time-zone or time-delay version of a channel can be made by transposing its playlists.
Yes. The Nimbus MCP server exposes the full Nimbus API, so an assistant can read and change a channel's schedule.
Tell us which traffic or scheduling system you use and the format it exports, and we'll show it running in Nimbus.
Or email sales@veset.tv.
We'll reply to . Sales requests get an answer within five business days.