Frequently Asked Questions

Yes, but it leads to delays, inefficiencies, and poor user experience.

Robust content delivery networks keep streams smooth and uninterrupted during high-demand events, delivering content reliably and at scale to viewers regardless of geographical location.

Embeddings are numerical representations of meaning for each chunk of text. Semantic search is the process of comparing those embeddings to find the chunks most relevant to a query. Embeddings are the data; semantic search is the action performed on that data.

Vodlix provides enterprise-grade integrations such as open APIs, connections with payment gateways, CRM systems (e.g. Salesforce, HubSpot), marketing tools (like Mailchimp), ad servers, etc. These integrations help enterprises build a cohesive streaming ecosystem.

Vodlix integrates with catalogue and metadata sources such as TMDB, CRM and marketing platforms, email and SMS messaging providers, payment gateways and other external systems through connectors and the REST API.

No. Connecting an integration to Vodlix is straightforward. The care lies in choosing integrations deliberately and maintaining them, since each one is a credential and a dependency.

Every integration is a stored credential, a dependency that can break and behaviour a new colleague must learn. Choosing them deliberately keeps a Vodlix platform stable and understandable.

Vodlix tracks which API keys and credentials are held by which external systems, so they can be reviewed, rotated and revoked from the admin area rather than forgotten until they cause a problem.

A well behaved one should not, because it either runs on a schedule or reacts to events rather than sitting in the path of a viewer. The ones that cause problems are usually those doing work synchronously that did not need to be.

As few as do the job. Each one is a credential to look after and a dependency that can fail, and platforms accumulate them without anybody deciding to. Keeping a list of what is live is worth more than it sounds.

Some are read only and some are not, and it is worth knowing which is which before enabling one. An integration that can create or modify records is a considerably larger trust decision than one that only reads.

VAST is the standard format ad servers and networks use to hand an ad to a video player. Point a break at a VAST tag and the ad is requested at playback, which means campaigns can change without anyone editing the title. It is the route to take when you are selling through a network or filling programmatically.

Yes. Any ad server or network that issues VAST tags can fill your breaks, so you are not locked into one source of demand, and campaign targeting decides which countries, categories, apps and titles each one reaches.

Partly. The Vodlix API reports an order's status, returns a viewer's own purchases and rentals and issues refunds. For finance, the Invoices screen exports what you have filtered and Reports gives revenue and new orders for any date range, all from the same paid orders.

Vodlix brings support inside the product where the platform can see the account, which removes most identity questions. You can still run email support alongside it if you choose.

When you have a rota, service level commitments or multiple channels to manage. Deciding that before you commit is worth the thought, because moving support tooling later is more disruptive than choosing correctly at the outset.

No. Vodlix recommends first checking whether a requirement is a platform setting or an existing integration, since both cost far less than custom code and are often already available.

Yes. Vodlix builds custom and tailor made features when a requirement is genuinely bespoke. The approach is simply to reach for custom work last, once configuration and integration are ruled out.

A feature delivered as configuration is the cheapest, because it is already built, tested and maintained by Vodlix and costs nothing after it is enabled.

Keep the custom surface small. The less bespoke logic your platform carries, the less there is to break when the underlying platform is upgraded, and the cheaper it is to run.