What a video CMS manages
- Content: uploads, encoding status, titles, descriptions, artwork, trailers, subtitles and audio tracks
- Structure: series, seasons, episodes, collections and genres
- Availability: publish and expiry dates, regions and release windows
- Commerce: plans, prices, rentals, coupons and bundles
- Audience: users, devices, entitlements and support actions
- Experience: home page rows, navigation, branding and languages
Video CMS vs a general CMS
A website CMS manages pages and articles. A video CMS is built around the video asset: it triggers encoding on upload, understands series and seasons, attaches rights and prices to each title and pushes changes to every app at once, without an app update.
What to look for
- Roles and permissions, so editors, finance and support each see only what they need
- Bulk upload and metadata import for large catalogs
- Scheduling: publish and unpublish automatically by date and region
- Layout control: change the home page without a developer
- An API and webhooks, to connect other systems
Last reviewed