Build a reusable video library
Upload, search, preview, download, reformat, and reuse media in the managed File Manager, then connect the same asset to one player, many player groups, or several business use cases over time.
Playback
Video on demand hosting and branded playback
Turn uploaded or recorded media into a managed library, then publish branded players and playlists with viewer access controls.
Playback
Build a reusable video library
Organize managed files, playback surfaces and access settings in one workflow.
Publish one player across devices
Use a player surface that stays consistent across browsers and screen sizes instead of rebuilding playback logic for every destination.
Control branding and access
Set branding and choose open, password, email-and-password, or unique-credential access for the playback surface instead of building those controls from scratch.
Workflow
Deliver globally without rebuilding playback
Keep playback stable for distributed audiences while preserving one player model and one operational surface for your team.
Monetize selected assets or collections
Use paywalled playback when a single video, playlist, or grouped page needs access control instead of open public playback.
Adapt playback to connection quality
Use adaptive playback so the same asset can remain watchable across a wide range of viewer connections and devices.
Keep files and storage under control
Keep assets on the instance or connect reviewed AWS S3 and Backblaze targets. Copy managed files between storage destinations so retention, migration, and persistence stay explicit.
Technical specification
What the product supports, and what to verify
Supported behavior sits beside a practical acceptance check. The installed Callaba interface and the real source, destination, and infrastructure profile remain authoritative.
View technical specifications
| Capability | Supported behavior | Acceptance check |
|---|---|---|
| Build a reusable video library | Upload, search, preview, download, reformat, and reuse media in the managed File Manager, then connect the same asset to one player, many player groups, or several business use cases over time. | A VOD workflow prepares managed video files for viewer playback. In Callaba, File Manager holds the asset, Web Player defines playback and access behavior, and grouped playback pages organize what viewers see. |
| Publish one player across devices | Use a player surface that stays consistent across browsers and screen sizes instead of rebuilding playback logic for every destination. | Yes. Create a Web Player from a verified managed file, configure its playback and access settings, then use the player surface or embed where it fits your site. Test the viewer path before sharing it. |
| Monetize selected assets or collections | Use paywalled playback when a single video, playlist, or grouped page needs access control instead of open public playback. | Yes. Once a recording has finished and been checked in File Manager, it can become the source for a Web Player or grouped playback page. Recording, playback and audience access remain separate workflow decisions. |
| Control branding and access | Set branding and choose open, password, email-and-password, or unique-credential access for the playback surface instead of building those controls from scratch. | Yes. Create a Web Player from a verified managed file, configure its playback and access settings, then use the player surface or embed where it fits your site. Test the viewer path before sharing it. |
| Adapt playback to connection quality | Use adaptive playback so the same asset can remain watchable across a wide range of viewer connections and devices. | VOD costs depend on the deployment, storage, processing and playback workflow you choose. Review the current Callaba pricing and test the required file and player path rather than assuming a generic VOD cost model. |
| Keep files and storage under control | Keep assets on the instance or connect reviewed AWS S3 and Backblaze targets. Copy managed files between storage destinations so retention, migration, and persistence stay explicit. | Yes. Web Player groups organize several assets or languages in one playback surface. Use Files for asset control, Web players for playback, and Web player groups for grouped viewing. |
Continue in the product
Set it up in Callaba. Then check the full path.
You have seen what the product does. These three guides take you into the exact controls, show what to connect next, and give you a practical check before the workflow goes live.
Workflow
Keep files and storage under control
Keep assets on the instance or connect reviewed AWS S3 and Backblaze targets. Copy managed files between storage destinations so retention, migration, and persistence stay explicit.
Cloud VOD streaming software pricing
The pay-as-you-go cloud tariff is ideal for those who need all the advantages of the cloud, such as instant deployment of Callaba, low latency due to the global network of data centers, server reliability, data backup, scalability, managed services, and much more.
Self-hosted unlimited VOD streaming pricing
The unlimited tariff is a good fit for actively growing broadcasting organizations of medium and large size that would like to have no limitations like those in the bundled tariff, while also maintaining full control over their data.
Video on-demand API
Video on-demand REST APIAutomate files, players, and playback surfaces with API modules
A real VOD product is not one upload endpoint. In practice, teams manage files, players, grouped playback pages, branding, and storage as separate workflow pieces. Use the API when playback needs to behave like part of your own app, CMS, or customer portal.
Frequently Asked Questions
What is a video-on-demand platform?
A VOD workflow prepares managed video files for viewer playback. In Callaba, File Manager holds the asset, Web Player defines playback and access behavior, and grouped playback pages organize what viewers see.
Can I embed VOD on my website?
Yes. Create a Web Player from a verified managed file, configure its playback and access settings, then use the player surface or embed where it fits your site. Test the viewer path before sharing it.
Can I publish recordings as VOD?
Yes. Once a recording has finished and been checked in File Manager, it can become the source for a Web Player or grouped playback page. Recording, playback and audience access remain separate workflow decisions.
Can I build VOD playlists or grouped viewing pages?
Yes. Web Player groups organize several assets or languages in one playback surface. Use Files for asset control, Web players for playback, and Web player groups for grouped viewing.
Is VOD free?
VOD costs depend on the deployment, storage, processing and playback workflow you choose. Review the current Callaba pricing and test the required file and player path rather than assuming a generic VOD cost model.
Is VOD free?
VOD is not automatically free. A software module or trial can have its own price, while the audience-facing service also needs delivery bandwidth, storage, transcoding, and usually a player or CDN. Check those infrastructure costs separately from the Callaba deployment or module cost.
How do I start a video-on-demand website?
Start with a media library, an encoding and delivery plan, a browser player, and the access rules your audience needs. Then connect the player to your site and test upload, playback, entitlement, and delivery costs with real media before opening it to viewers.
What is a VOD channel?
A VOD channel is an organised collection of on-demand programmes that viewers choose and play when they want, rather than a scheduled live channel. It can be public, restricted, or tied to a subscription or purchase rule.
What are VOD, VODs, and a vodcast?
Video on demand (VOD) is video a viewer chooses to play when ready rather than a live scheduled feed. “VODs” is the plural. A vodcast is commonly a podcast-style programme distributed as video; it can be published as on-demand media, but the term does not describe a separate playback technology.