Server-side ad insertion has become the standard way to monetize live streams and video-on-demand, because it stitches ads directly into the video so they can’t be blocked and don’t buffer. But when operators go to budget for it, they hit a wall: the pricing is quoted in units that are hard to translate into a real monthly bill, and the number on the pricing page is rarely the number you actually pay. AWS Elemental MediaTailor is the most visible name in this space, and its pricing page looks simple — until you realize how many separate line items stack up, and how much of what you genuinely need to run ad insertion isn’t on that page at all.
This article is a direct, honest cost comparison between AWS MediaTailor and 5centsCDN for server-side ad insertion, worked through with real numbers at two realistic scales. We’ll show exactly how each platform counts a billable ad, what each charges, and — the part that matters most — what the *total* monthly cost looks like once you include the things ad insertion actually requires to work, especially transcoding. All the AWS figures here come straight from the public MediaTailor pricing page; all the 5centsCDN figures are our actual pricing. Where our billing method differs from theirs, we’ll say so plainly, because the comparison holds up even when we count against ourselves.

How Each Platform Counts a Billable Ad
Before comparing prices, you have to compare units, because the two platforms don’t count the same way — and being clear about this upfront is the only honest way to do the math.
AWS MediaTailor bills on ad insertions, where one ad insertion is one ad served to one viewer. Their own example on the pricing page makes it concrete: a live stream with 1,000 viewers and 3 ad breaks of 5 ads each produces 3 × 5 × 1,000 = 15,000 ad insertions. The rate is $0.50 per 1,000 ad insertions for live (effectively $500 per million) and $0.25 per 1,000 for VOD ($250 per million). So MediaTailor counts purely at the impression level — one ad, one viewer, one billable insertion.
5centsCDN bills on ad requests plus impressions. For each viewer at each ad break, that’s one ad request plus one impression per ad served — so a 5-ad break counts as 6 billable events per viewer (1 request + 5 impressions), where MediaTailor would count 5. In other words, for the same stream, our raw event count is modestly higher than theirs — about 1.2× in a typical 5-ad break. We’re stating this deliberately, because it’s the one place our method looks less favorable on paper, and the comparison still comes out decisively in our favor once you see the rates. Our rate is a flat $50 per million ad insertions, with a 1-million-event minimum on the recurring plan.
What the Difference Means in Real Cost
Hold those two facts side by side: AWS charges $500 per million (live) counting only impressions; we charge $50 per million counting requests plus impressions. Even after our higher event count inflates the number of billable events by roughly 20%, our effective cost for the same workload is a fraction of theirs. The rest of this article shows that in hard numbers — and then shows why the ad-insertion line is only the beginning of the AWS bill.
Worked Example 1: One Million Ad Insertions (Live)
Take a live channel whose viewership and ad load produce one million ad insertions in a month by MediaTailor’s counting method — a realistic figure for a mid-sized live service.

On AWS MediaTailor, one million live ad insertions at $0.50 per thousand is $500 for the month — for the ad-insertion line alone.
On 5centsCDN, the same workload counts as roughly 1.2 million events once ad requests are included (one request plus five impressions per viewer per break). At our flat $50 per million, that’s about $60 — and against our one-million-event recurring minimum, the ad-insertion line lands at roughly $50–60. Call it $60 to be conservative and to count against ourselves.
So on the ad-insertion line by itself: $500 on AWS versus about $60 on 5centsCDN for the same live workload, even though we’re billing on a larger event count. That alone is a roughly 8x difference. But the ad-insertion line is not the whole bill on either side, and this is where the comparison gets more revealing rather than less.
Worked Example 2: Five Million Ad Insertions (Live)
Now scale up to a larger live service producing five million ad insertions a month, to show how the gap behaves as volume grows.
On AWS MediaTailor, five million live ad insertions at $0.50 per thousand is $2,500 for the month, again for the ad-insertion line alone.
On 5centsCDN, five million insertions counts as roughly six million events with ad requests included, at $50 per million = about $300 for the ad-insertion line.
So at 5x the scale: $2,500 on AWS versus about $300 on 5centsCDN. The gap doesn’t shrink as you grow — it widens in absolute terms, because our flat per-million rate stays flat while the per-thousand rate keeps multiplying. And we still haven’t added the costs that make ad insertion actually work.
The same pattern holds for video-on-demand, where MediaTailor’s rate is half the live rate — $0.25 per 1,000 ad insertions, or $250 per million. That’s cheaper than their live rate, but it’s still five times our flat $50 per million, which applies the same way to live and VOD. Whichever model you run, the per-million gap is the same order of magnitude, and the transcoding point below applies to VOD catalogs just as it does to live channels: the ads still have to match the renditions of the content they’re inserted into.
The Line Item AWS Doesn’t Put on the Headline: Transcoding
Here is the single most important thing to understand about the real cost of ad insertion, and it’s the thing the MediaTailor pricing page quietly assumes without charging you for on that page: ad insertion requires your main program to be transcoded into an adaptive bitrate ladder, and that transcoding is a substantial, mandatory cost that AWS bills separately.

Why Transcoding Is Required for Ad Insertion
Why is transcoding mandatory for ad insertion? Because for an ad to stitch seamlessly into a stream, the ad — typically returned by an ad server as a VAST response pointing to a creative — has to be delivered in the same set of quality renditions as the main program, the same resolutions and bitrates, so the player can switch from content to ad and back without a visible break or a quality jump. That only works if your main program is already running as a proper adaptive bitrate ladder in the first place. AWS’s own pricing page gives this away: in its ad-transcode example, it states that “the main program uses an adaptive bitrate group with 5 streams.” That ABR ladder is a prerequisite for the whole thing to function — but producing it is not included in the MediaTailor price. It’s billed separately through AWS’s transcoding services (MediaConvert or MediaLive).
The Real Monthly Transcoding Cost
How much separately? For a 24/7 live channel transcoded into a four-profile ABR ladder, AWS’s transcoding runs well into four figures a month. Using the on-demand basic rates AWS itself quotes ($0.015 per minute for HD, $0.0075 for SD), a 24/7 month of a four-profile ladder (two HD, two SD) works out to roughly $1,971 per month — and that’s via the batch-oriented service; the service actually designed for 24/7 live typically costs more. So a buyer who reads “$500 for a million ad insertions” on the MediaTailor page and budgets for it is, in reality, looking at that plus roughly $2,000 a month for the transcoding that makes it work — a cost that never appeared on the page they were reading.
5centsCDN bundles transcoding with ad insertion, because we consider the two inseparable — you can’t run ad insertion well without it, so we don’t pretend they’re unrelated line items on different pages. Our 24/7 four-profile live transcoding is a flat $210 per month. Against AWS’s roughly $2,000 for the equivalent, that single line is where the comparison stops being close and becomes decisive.
The Full Monthly Bill, Side by Side
Let’s assemble the real recurring monthly cost on each side for the one-million-insertion live channel — not the headline line, but what you’d actually pay to run ad insertion properly.
5centsCDN — recurring monthly:
- 24/7 four-profile live transcoding: $210
- Ad insertion (flat, 1-million-event minimum): $50
- License: $50
- Total recurring: $310 per month
Plus a one-time setup fee — and we’re transparent that we charge one — which averages around $750 depending on the features you need, paid once, not monthly. Advanced, detailed analytics are available as separate add-ons; basic analytics are included. Ad delivery isn’t a separate line at all, because your content is already being delivered over our CDN, so the ad segments ride the bandwidth you’re already paying for.
AWS MediaTailor — recurring monthly (same channel):
- Ad insertion (1M live): $500
- Main-program transcoding for the ABR ladder (separate, via MediaConvert/MediaLive): ~$2,000
- Ad transcoding beyond the free allowance (10 per 1,000 insertions free, then MediaConvert rates): variable, extra
- Channel assembly if you use it: basic VOD channels are hourly, standard live channels $0.35/hour (~$255/month) per running channel
- Ad delivery out (per GB, or via CloudFront): variable, extra
- Logs beyond the included allowance: variable, extra
The contrast is stark, and it’s the honest headline of this whole comparison: 5centsCDN’s entire recurring stack — $310 a month, with 24/7 four-profile transcoding included — costs less than AWS’s ad-insertion line alone ($500), and a small fraction of AWS’s real all-in cost once the mandatory transcoding is added. At the five-million-insertion scale, where AWS’s ad line alone is $2,500 before transcoding, the comparison isn’t a contest.
Where AWS and 5centsCDN Actually Match (and Where We Don’t Charge)
To keep this fair, it’s worth naming where the two are genuinely comparable and where we simply don’t bill for something AWS does.
Basic channel assembly — scheduling content into a linear channel — is free with 5centsCDN, and AWS’s channel assembly is a per-running-hour charge even for basic channels. We also offer an advanced cloud playout system that does considerably more than basic channel assembly, and that carries its own cost because it’s a genuinely more capable product — but the basic equivalent of what AWS charges hourly for, we don’t charge for at all. On ad delivery, AWS lists per-gigabyte ad-delivery-out charges (and recommends you add CloudFront on top); with us there’s no separate ad-delivery line because delivery runs through the CDN you’re already using. The net effect is that several of AWS’s metered line items simply don’t exist on our bill.
We’re not claiming AWS MediaTailor is a bad product — it’s a capable, deeply-integrated service, and for an organization already all-in on the AWS ecosystem that integration has real value. What we are saying is specific and verifiable: for the concrete job of inserting ads into a live or VOD stream, with the transcoding that job actually requires, the total cost on 5centsCDN is dramatically lower, and the pricing is far easier to predict because it doesn’t fragment across half a dozen separately-metered services.
Why Our Pricing Is Simpler by Design
The deeper difference underneath the numbers is philosophy. AWS prices each micro-service independently — ad insertions here, ad transcodes there, channel hours, ad-delivery gigabytes, log volume, monetization-function invocations — which is flexible but means your true cost is scattered across many meters you have to assemble yourself to know what you’ll pay. It also means the number you see first ($500 per million) is the smallest part of what you’ll actually spend.
5centsCDN deliberately bundles the things that always go together. Ad insertion and transcoding are sold as one proposition because you can’t sensibly run one without the other, so you get a single, predictable figure rather than a headline rate plus a transcoding bill you discover later. The flat per-million ad rate doesn’t climb with scale the way per-thousand pricing does. And delivery folds into the CDN bandwidth you’re already paying for rather than becoming its own line. The result is a bill you can predict before you sign, which for most operators is worth as much as the lower absolute number — because an unpredictable bill that balloons with usage is its own kind of cost. For the fundamentals of how the underlying technology works, our guides to server-side ad insertion and OTT monetization models cover the ground beneath the pricing.
A Cost-Comparison Summary
Pulling the whole comparison into one view for a one-million-insertion live channel: AWS MediaTailor charges $500 for the ad-insertion line alone, then adds roughly $2,000 for the main-program transcoding that ad insertion requires but the MediaTailor page doesn’t include, plus separate charges for ad transcoding overflow, standard channel assembly, ad delivery, and logs. 5centsCDN charges $310 a month all-in — $210 transcoding, $50 ad insertion, $50 license — with a one-time setup fee averaging around $750, delivery riding existing CDN bandwidth, basic channel assembly free, and advanced analytics as optional add-ons. The ad-insertion unit is counted slightly differently on each side — AWS per impression, 5centsCDN per ad request plus impression — but even counting against ourselves, our total is a fraction of theirs. And the gap only widens with scale. That is the comparison in a sentence: our entire bill comes in under AWS’s first line item.
Ad Insertion That’s Priced for the Real World
The honest takeaway is that the true cost of server-side ad insertion is not the per-thousand rate on the pricing page — it’s that rate plus the transcoding, delivery, channel, and logging costs that the job actually requires, and on AWS those are scattered across separate services that add up to many times the headline. 5centsCDN prices the whole job as one predictable figure, bundles the transcoding that ad insertion genuinely needs, folds delivery into the CDN you’re already using, and comes in — all in, with transcoding — below what AWS charges for ad insertion alone. For an operator trying to monetize a stream without a surprise bill, that difference is the whole point.
5centsCDN delivers server-side ad insertion bundled with the live transcoding it requires, over the same purpose-built CDN your content already runs on — one pipeline, one predictable bill, with cloud playout available when you need more than basic channel assembly. If you’re weighing the real cost of ad insertion for your live or VOD service and want a figure you can actually budget against, talk to our team for a quote mapped to your exact requirements.
At-a-glance cost comparison (1M live insertions/month)
| Line item | AWS MediaTailor | 5centsCDN |
| Ad insertion | $500 (1M × $0.50/1,000, per impression) | ~$50–60 (flat $50/M; req+impression, 1M min) |
| Main-program transcoding (4-profile, 24/7) | ~$2,000/mo (separate, MediaConvert/MediaLive) | $210/mo (bundled) |
| Ad transcoding | Free ≤10/1,000, then MediaConvert rates | Included |
| Basic channel assembly | Hourly (standard live ~$255/mo) | Free |
| Ad delivery | Per GB (or via CloudFront), extra | Rides existing CDN bandwidth |
| Logs | Included allowance, then per GB | Basic included |
| License | — | $50/mo |
| Recurring total | $500 ad line + ~$2,000 transcoding + extras | $310/mo all-in |
| One-time setup | None stated | ~$750 avg (one-time, feature-dependent) |
All AWS figures from the public MediaTailor pricing page (US East, N. Virginia); transcoding figure illustrative via MediaConvert on-demand basic rates. 5centsCDN figures are actual pricing. Advanced analytics available as separate add-ons.
Frequently Asked Questions
How much does AWS MediaTailor cost for ad insertion?
$0.50 per 1,000 ad insertions for live ($500/million) and $0.25 per 1,000 for VOD ($250/million), counted per impression (one ad, one viewer). But that line excludes the main-program transcoding ad insertion requires, which AWS bills separately.
How does 5centsCDN’s ad insertion pricing compare?
A flat $50 per million ad insertions (counted as ad requests plus impressions), bundled with 24/7 transcoding. For a 1M-insertion live channel, 5centsCDN’s entire recurring stack is $310/month — less than AWS’s ad-insertion line alone ($500).
Why is transcoding part of the ad insertion cost?
Because ads must be delivered in the same bitrate renditions as the main program to stitch in seamlessly, which requires the program to run as an adaptive bitrate ladder. AWS assumes this ABR ladder but bills it separately (~$2,000/mo for 24/7 4-profile); 5centsCDN bundles it at $210/mo.
Do AWS and 5centsCDN count ad insertions the same way?
Not quite. MediaTailor counts per impression (one ad per viewer). 5centsCDN counts ad requests plus impressions (about 1.2× the events for a 5-ad break). Even with the higher event count, 5centsCDN’s total is a fraction of AWS’s because the flat rate is far lower.
Is there a setup fee with 5centsCDN ad insertion?
Yes, a one-time setup fee averaging around $750 depending on features — paid once, not recurring. The recurring cost is $310/month (transcoding + ad insertion + license), with advanced analytics as optional add-ons.
What extra AWS charges should I budget for beyond ad insertion?
Main-program transcoding (separate), ad transcoding beyond the free allowance, channel assembly hours for standard channels, ad delivery out per GB (plus CloudFront), and logs beyond the included allowance. These make the real bill several times the headline rate.