Questions and answers
Still unanswered? Ask us directly.
CDNLive charges per GB delivered, on marginal tiers: €0.080/GB on the first 10 TB each month, €0.060/GB on the next 40 TB, and €0.050/GB beyond 50 TB. Tiers are marginal, so each rate applies only to the volume inside its band — at 100 TB a month you would pay €5,700.00, an effective €0.057/GB. Server-side ad insertion is priced separately, at a flat €1.35 per 1,000 ads inserted, and is charged only on streams that carry ads. There are no contracts and no minimums.
No. Credit is prepaid. You load a balance, set a monthly ceiling, and delivery draws that balance down at the per-GB rates above. If usage approaches your limit you are warned, and automatic safeguards can pause delivery before the budget is exceeded. You cannot be invoiced for more than you have loaded.
AWS CloudFront lists $0.085/GB for delivery in Europe, and it does not insert ads at all — that is a separate service, billed separately again, usually across several line items. CDNLive starts at €0.080/GB, falls to €0.050/GB at volume, and offers ad insertion built in at a flat €1.35 per 1,000 ads, covering packaging, transcoding, delivery and reporting together. Comparisons on this site convert published USD list prices to euros, so the delivery figures are like for like.
Ad insertion is a flat €1.35 per 1,000 ads inserted — the same rate for live and on-demand, with no volume ladder. A viewer watching for an hour with four breaks of four ads costs about €0.022. That one rate covers the whole path: reading the SCTE-35 markers in your stream, packaging and re-encoding the ad creatives to match your renditions, personalising each viewer's manifest, delivering the ad segments over the same network as your content, and reporting every break in your dashboard. There is no separate packaging, transcoding, session or reporting fee. It is charged per ad actually inserted, so streams without ads cost nothing extra, and it is billed against the same prepaid balance as delivery.
SSAI creates a stream manifest with ads inserted for the viewer before playback reaches the device. It can provide a smoother transition between content and advertising and reduces reliance on a separate client-side ad player.
No. You can use CDNLive only for live CDN delivery and add SSAI later. Your delivery service is not tied to whether advertising is enabled.
Both options are supported. CDNLive can manage SSAI for you, or you can connect a supported SSAI environment that you control. This lets you choose between a simpler managed service and keeping your existing provider relationship and billing.
The stream needs reliable ad-break signalling, compatible manifests, and an ad decision source. Depending on your workflow, that can include SCTE-35 markers, VAST or VMAP responses, a slate, and creatives prepared for the stream’s playback profiles.
Shared media segments can remain cacheable at the edge, while viewer-specific manifests must be treated as session-specific. This keeps one viewer’s ad decisions from being reused for another viewer while preserving CDN efficiency for the underlying video.
CDNLive is a live streaming content delivery platform for teams that already produce HLS, DASH, or CMAF streams. Connect one packaged origin, deliver it worldwide through a branded address, monitor delivery health and usage, and add server-side ad insertion only if you need it.
A live streaming CDN delivers manifests and media segments from locations closer to viewers. This reduces the distance each request travels, protects the origin from direct audience load, and helps a stream handle viewers in different regions or sudden traffic peaks.
CDNLive delivers over the Amtecco global edge network: 4,200+ edge servers across 130+ countries, built for always-on live video. CDNLive adds a simpler control panel, branded delivery addresses, monitoring, spend controls, and optional SSAI on top of it.
CDNLive is designed for packaged HLS, MPEG-DASH, and CMAF live streams. Your manifest and media segments must already be available from a healthy origin before delivery is activated.
No. CDNLive focuses on live content delivery, optional SSAI, monitoring, analytics, and spend control. Keep using the encoder and packager that already produce your HLS, DASH, or CMAF output.
Not in the first release. CDNLive delivers standard HLS, MPEG-DASH and CMAF. Low-latency HLS relies on partial segments and blocking playlist reloads, and low-latency DASH on chunked-transfer delivery — both change how the edge must handle manifests and segments, and we would rather support them properly than claim them early. If glass-to-glass latency below a few seconds is a hard requirement for you today, tell us and we will be straight about whether we are a fit.
Yes, when server-side ad insertion is enabled. SCTE-35 markers in your stream signal where an ad break starts and how long it runs. CDNLive calls your ad decision server, which responds with VAST or VMAP, and the returned creatives are stitched into the manifest before it reaches the viewer. If you run SSAI in your own environment, CDNLive delivers the stream and your setup continues to handle the ad decisioning.
Egress is the data your viewers actually download from the edge — manifests and media segments. CDNLive bills on edge bytes delivered, measured in gigabytes, where 1 TB = 1000 GB. You are not billed for data between your origin and the edge, and you are not billed for requests.
Edge caching means many viewers requesting the same segment result in one fetch from your origin, which is the main protection your origin gets. A dedicated origin shield tier — a single mid-tier cache that further collapses origin requests — is not something we expose as a customer-configurable feature today.
Delivery capacity comes from the Amtecco global edge network — 4,200+ edge servers across 130+ countries — so concurrency is bounded in practice by your origin and packaging, not by the edge. Note that CDN request counts are not a viewer count: one viewer makes many manifest and segment requests, switches bitrate, and may retry. Accurate audience numbers need player-side measurement.
You add credit, choose a monthly budget, and set alerts before delivery starts. Usage reports can arrive after traffic occurs, so a small safety buffer may cause delivery to pause before the full displayed balance is used. The dashboard will show the available balance, current estimate, and protection point clearly.
Stream health can be checked quickly, but complete traffic and billing data may arrive later. CDNLive shows when each view was refreshed and whether recent figures are still updating, ready for reporting, or matched to billing.
Delivery views can include traffic, data transfer, requests, errors, locations, origin behaviour, and cache performance. When you use CDNLive-managed SSAI, available advertising and SSAI operational insights can be shown alongside delivery information.
Not exactly. One viewer can make many manifest and segment requests, change bitrate, retry a request, or use more than one playback session. Accurate audience size, startup time, buffering, and other quality-of-experience measures require player-side information in addition to CDN traffic.
Choose an available name of at least five characters under cdnlive.io, such as arena.cdnlive.io. Early-access delivery uses a CDNLive address; ask our team if your project has custom-domain requirements.
Controlled MCP access is planned for early access. CDNLive is being designed so approved AI assistants can help check delivery health, review usage, and perform permitted routine actions while you control and can revoke their access.
CDNLive is for broadcasters, OTT services, FAST channel operators, live sports and event teams, streaming platforms, and media engineers that already create packaged live streams and want simpler global delivery with clearer cost control.
A video hosting platform usually manages uploaded files, libraries, players, and on-demand publishing. CDNLive is focused on delivering already packaged live streams, monitoring their health and usage, and optionally adding server-side advertising.
You join a product contact list so we can learn about your stream and invite suitable teams as access opens. The form does not create a paid account, start delivery, collect credentials, or create a payment obligation.