Frequently Asked Questions

The behaviour is the same and its value is not. On television, stopping means finding a remote and navigating a menu, so autoplay does more work. On a phone, stopping is one tap and sessions are usually shorter anyway.

Video demand arrives in bursts: storage jumps when a catalogue lands, processing peaks when files arrive together and delivery surges at a premiere. Vodlix's elastic cloud infrastructure absorbs those bursts automatically.

Vodlix transcoding capacity scales up to process the batch in parallel and scales back down when the queue clears, so ingest is fast without idle capacity sitting unused in between.

Vodlix delivery capacity expands for the peak hours of a premiere or live event and contracts afterwards, so the platform is strongest exactly when the audience is largest.

With Vodlix on elastic cloud infrastructure you do not pay for a peak you rarely use, and you do not fail when demand spikes. Capacity follows the audience rather than a forecast.

Less than operators usually expect. What determines reliability is whether transcoding recovers from failures without losing files, whether delivery has a fallback, and whether you can see what is happening. Those are platform properties.

They solve adjacent halves. Infrastructure is where things are stored and processed, the delivery network is how they reach a viewer quickly. A service can get one right and the other wrong and still feel slow.

How it behaves when something fails, and what you can see when something is slow. Those questions distinguish platforms far better than which provider is named, and they are the ones that matter at three in the morning.

Yes. Vodlix lets you create custom entity labels to categorise content by genre, industry, format or any scheme that suits your business, alongside standard categories.

Yes. Most billing enquiries are simply about identifying a charge. Because Vodlix makes orders and invoices visible to subscribers, those questions are answered without a ticket.

Tickets raised inside a Vodlix service arrive attached to the subscriber's account, with device, plan and history already visible, so your team skips the identity questions and addresses the actual problem first.

A Vodlix support ticket includes the account, the device and app in use, the subscription status and the relevant viewing history the platform already holds, without the subscriber having to explain it.

The whole conversation lives in one place inside Vodlix, tied to the subscriber's account, so nothing is scattered across inboxes and the full history is at hand when they write in again.

Problems are solved faster without wasted replies, at exactly the moment a frustrated subscriber is deciding how they feel about your service, which makes support a retention tool.

Billing questions, playback on one particular device, and sign in problems. All three have factual answers already recorded in the platform, which is why keeping support close to those records shortens them so much.

The session and order records show what reached the platform and what was charged, which is usually the difference between a fault and a misunderstanding. Signing in as the viewer to reproduce something is available separately for the cases that need it.

User levels separate viewers, staff and administrators, so access to billing, settings and account records can be kept away from people whose job is publishing content. Everybody signs in as themselves rather than sharing a login, which also means you can tell who did what afterwards.

CDN analytics for video reports how your content delivery network delivers your streams: how much bandwidth and how many requests it served, how much came from cache, how your origin storage performed, where the traffic was served from and how many requests failed. In Vodlix it is a screen in your admin under Stats & Report.

No. CDN analytics shows how well the network delivered your video, while viewer analytics shows what people watched. Requests are not views, because one play is delivered as many small segments. Use Reports & Analytics for views and watch time.

The higher the better, because cached requests are answered from a data centre near the viewer. A falling rate means more traffic is going back to your origin, which makes playback slower and delivery more expensive. A short dip after publishing new titles is normal and recovers as the cache warms up.