VOD (Video on Demand)
Full VOD catalogue management: filter by status and category, tag by resolution and audio, upload new content and move titles through the set-up → uploaded → encoding → ready pipeline.
Catalogue filters
Status, category and tag filtering.
Rich metadata
Per-asset category, tags, size and status.
Ingest and the asset lifecycle
Every title moves through the same states - set up, uploaded, encoding, ready - which gives editorial and operations one shared vocabulary for where an asset is. Upload is drag-and-drop for one-off titles and watch-folder or API-driven for bulk ingest from a distributor or MAM.
Encoding profile selection happens at ingest, so a 4K feature and a 720p archive interview do not get the same ladder. Failed jobs stay visible with their error rather than silently disappearing, because a title stuck in encoding is the failure that most often reaches a viewer as a broken tile in the catalogue.
Metadata, categories and merchandising
A VOD catalogue is only as usable as its metadata. Titles carry categories, tags, resolution and audio attributes, artwork in the aspect ratios each platform demands, and the descriptive fields that feed both on-screen browsing and search. Filtering in the CMS by status, category and tag is what makes a catalogue of thousands of assets maintainable.
Merchandising - rows, collections, featured positions - is edited server-side and applies across every client at once. Artwork is worth particular attention on TV: the same title needs a wide hero image, a poster and a tile, and platforms reject submissions over artwork that does not meet their spec.
Publishing and entitlement
A ready asset becomes visible when it is published, and what a given viewer may actually play is decided by the subscription tier and, where DRM is enabled, by the licence policy. Availability windows let a title appear and expire on schedule without manual intervention - important when distribution rights are time-limited.
Because the apps read the catalogue from the backend rather than bundling it, adding, removing or re-ordering content never requires an app store release.
Inside the CMS
Frequently asked questions
- What source formats can we upload?
- Common mezzanine and delivery formats including MP4, MOV/ProRes, MXF and MKV. Sources are probed on ingest and normalised before encoding, so mixed-format catalogues are not a problem.
- Can we bulk-import an existing catalogue?
- Yes. Metadata can be imported from a spreadsheet or an existing system via API, and media can be ingested from a watch folder or object storage rather than uploaded by hand.
- How long does a title take to become playable?
- It depends on runtime, ladder and available encoding capacity. Encoding is parallelised across renditions, and the asset state in the CMS shows progress rather than leaving you to guess.