How Is Akamai Priced? Key Costs to Clarify in an Enterprise Quote
According to Akamai channel pricing published by CDN World, the entry rate is USD 0.05/GB, with a USD 499 monthly minimum and a 12-month term. Using 1 TB = 1,000 GB, delivering 1 TB or 5 TB per month both incur a base charge of USD 499; 10 TB costs USD 500, and 50 TB costs USD 2,500. Low-traffic websites should first consider the minimum commitment, while high-traffic businesses should compare commitment tiers rather than simply multiplying total traffic by a per-GB price.
This pricing comes fromCDN World's Akamai pricing pageThe pricing information is dated November 18, 2026, applies to the plans published by that channel, and excludes delivery within mainland China. All amounts are in USD and cover base delivery charges first; taxes and separately purchased services must be listed separately. Published channel pricing can serve as a reference for budgeting and requests for quotation, while orders through other channels or direct contracts should be calculated under their respective terms.
What an enterprise quote really needs to resolve is which tier the traffic falls into, whether the minimum commitment will go unused, which type of bytes the bill measures, and which products are metered separately. Only by calculating these points can you determine whether a heavily discounted quote is genuinely suited to your business.
How Is Akamai Pricing Calculated? Start with the Published Monthly Commitment Tiers
This channel publishes seven Akamai rate tiers. The table below follows the tier thresholds on the page. The 100 TB tier corresponds to a monthly commitment starting at 100 TB; it should not be understood as a second block of traffic that receives a discount only after the entry allowance is used up.
Monthly commitment tier | Published rate | What to consider when choosing a tier |
|---|---|---|
Entry tier | USD 0.0500/GB | Whether the USD 499 monthly minimum can be fully used |
100 TB tier | USD 0.0375/GB | Whether committing to 100 TB is cheaper than staying on the entry tier |
200 TB tier | USD 0.0280/GB | Compare the full-tier cost when traffic approaches the next tier |
300 TB tier | USD 0.0210/GB | Whether off-peak traffic can support this commitment |
500 TB tier | USD 0.0160/GB | Choose a tier based on stable delivery volume, not event peaks |
750 TB tier | USD 0.0120/GB | Verify the scope of commitments shared across businesses |
1 PB tier and above | USD 0.0090/GB | The low unit rate corresponds to a PB-level commitment and does not apply to low-traffic use |
The key here is “commitment.” The rate is determined by the monthly commitment selected and applies to all traffic in that tier; usage above the commitment is charged at the same tier rate. The channel'stiered and minimum-spend rulesalso state that the minimum spend is prepaid and offsets usage; if a higher commitment tier is actually cheaper, the higher-tier plan will be offered.
The published pricing page also states that special traffic patterns, workloads with a large gap between peak and average, or businesses with a significant share of dynamic content are priced separately. This table is suitable for an initial estimate of delivery costs under standard plans; for download events concentrated at peak times or heavily dynamic applications, you should not enter a single month's total and treat the table result as a final quote.
Cost calculation therefore involves at least two steps: first determine the purchased tier and its commitment, then calculate actual billable usage at that tier's rate. Do not assume that the range into which month-end traffic falls will automatically move the contract up or down a tier, and do not multiply any small website's usage by the lowest rate of USD 0.009/GB just because you see it.
How the USD 499 Charge Works: It Is Not Added on Top of Traffic Fees
For the entry tier, the most practical formula is: the base monthly fee is the greater of “billable GB × USD 0.05” and “USD 499.” The USD 499 offsets that month's base usage; it is not a fixed service fee added on top of traffic charges.
Monthly billable usage | At USD 0.05/GB | Base monthly fee after applying the minimum spend |
|---|---|---|
1 TB (1,000 GB) | USD 50 | USD 499 |
5 TB (5,000 GB) | USD 250 | USD 499 |
10 TB (10,000 GB) | USD 500 | USD 500 |
50 TB (50,000 GB) | USD 2,500 | USD 2,500 |
If 10 TB of usage is calculated as USD 500 plus USD 499 for a total of USD 999, the offsetting minimum spend has been counted twice. Conversely, if you use only 1 TB per month, you should not budget just USD 50.
The delivery volume that exactly uses up the minimum is USD 499 divided by 0.05, or 9,980 GB—9.98 TB. Below that volume, further reducing base delivery traffic does not necessarily reduce the monthly payment. For example, reducing from 5 TB to 4 TB lowers the usage charge from USD 250 to USD 200, but the base monthly fee remains USD 499.
This changes how small websites should understand “cost per GB.” At 1 TB of usage, the actual charge is USD 499, or USD 0.499/GB; at 5 TB, it is USD 0.0998/GB. These are effective costs obtained by dividing the monthly spend by actual usage, not additional unit prices offered by the channel.
A lower effective unit price does not mean the service has become cheaper. Going from 1 TB to 5 TB leaves the payment at USD 499; the lower average cost simply spreads the same minimum spend across more traffic. Only from 10 TB to 50 TB does the payment increase at USD 0.05/GB. Budgets should consider both average cost and the incremental spend from added traffic, rather than using the average alone to forecast the next expansion.
The plan has a 12-month term. If only the USD 499 minimum is triggered every month, the base cost over twelve months totals USD 5,988. For businesses planning only a short-term campaign, the term and minimum spend should both factor into the purchasing decision; do not estimate the entire commitment from two or three months of campaign usage.
9.98 TB is only the mathematical threshold for fully using the minimum, not a business threshold at which the service becomes worth buying. Even if traffic exceeds it, compare alternatives under the same regions, product scope, and maintenance responsibilities; for lower-traffic but critical transaction entry points, first specify which delivery capabilities are actually needed. A price list can provide costs, but the reason to buy must still rest on business value.
Why Committing to 100 TB Can Be Cheaper Than Using Only 80 TB
Full-tier pricing and tiered accumulation produce very different bills. Take actual monthly usage of 80 TB: staying on the entry tier gives 80,000 GB × 0.05 = USD 4,000; choosing the 100 TB commitment tier gives 100,000 GB × 0.0375 = USD 3,750.
Under this published pricing, committing to 100 TB costs USD 250 less than delivering 80 TB at the entry rate and leaves 20 TB of additional commitment headroom.So “the smaller the commitment, the more you save” does not always hold. At 75 TB of entry-tier usage, the charge is already USD 3,750—exactly the same as the commitment cost of the 100 TB tier.
Now consider 150 TB. Choosing the 100 TB tier with actual delivery of 150 TB gives 150,000 GB × 0.0375 = USD 5,625. Choosing the 200 TB tier instead, with the commitment cost calculated as 200,000 GB × 0.028, gives USD 5,600. The latter costs USD 25 less and leaves 50 TB of headroom. This is exactly the specific result of the published rule that “a higher commitment tier may be cheaper.”
But headroom in a higher tier is not a cash refund. If traffic later falls to 30 TB, the 100 TB tier still carries its commitment; savings in a 150 TB month do not prove the choice will pay off all year. Before choosing a tier, compare both stable months and off-peak months rather than showcasing the discount using only the highest-traffic month.
Another common miscalculation is to split 150 TB into the first 100 TB at USD 0.05 and the next 50 TB at USD 0.0375, producing USD 6,875. This incorrectly treats a full-tier rate as a tiered rate. When choosing the 100 TB tier, the entire volume is priced at USD 0.0375, yielding USD 5,625; whether to move up to the 200 TB tier should be compared separately.
When you see USD 0.009/GB, also put it in scale. With 1 PB equal to 1,000,000 GB in decimal terms, delivering 1 PB corresponds to a base charge of USD 9,000. This unit rate is appropriate for discussion at the corresponding commitment scale; it should not be used to claim that “a website using a few TB can buy at this price.”
Using 120 TB in a Year Does Not Mean It Costs Only USD 6,000
A monthly minimum spend means the distribution of traffic over time affects annual costs. Arrange the same 120 TB annual volume in two different distributions and calculate month by month at the entry rate and the USD 499 monthly minimum; the results differ.
One distribution is a steady 10 TB per month: USD 500 per month, or USD 6,000 for the year. The other is 5 TB per month for six months and 15 TB per month for six months: USD 499 per month in off-peak months and USD 750 per month in peak months, totaling (6 × 499) + (6 × 750) = USD 7,494, which is USD 1,494 more than the steady distribution, an increase of 24.9%.
The second distribution does not deliver more traffic. The extra cost comes from off-peak usage charges not covering the monthly minimum and peak-month charges rising with that month's usage. Simply dividing annual traffic by twelve would smooth away this difference.
The channel's published rules clearly state that the prepaid minimum spend does not roll over to the next month, and excess peak-season traffic cannot offset unused off-peak allowance. A 12-month service term is not the same as pooling usage across twelve months for offset. When comparing other orders, if there are separate annual sharing or cross-business consumption arrangements, recalculate according to their scope rather than assuming they match this price list.
More reliable budgeting inputs are month-by-month billable usage over the past twelve months plus confirmed business growth. Customers not yet signed and one-off traffic peaks are not suitable bases for a high annual commitment. Commitments should be supported by stable demand as much as possible, leaving uncertain growth to be handled by overage rules.
Also compare same-tier overage with forced early tier upgrades. Overage is charged at the original tier's unit rate, which does not mean that exceeding the volume requires taking on the next tier's commitment; whether to change tiers should consider the current month's cost, demand in later months, and the conditions for changes taking effect.
Less Browser Download Does Not Necessarily Mean Fewer Akamai Billable Bytes
“My browser only downloaded this much” cannot be used directly to recalculate a CDN bill. Akamai'sDataStream field definitionsdistinguish between Bytes and Total bytes: the former reflects the delivered response body, while the latter corresponds to HTTP billable bytes and also covers request and response headers, request bodies, and HTTP/2 frames, excluding TCP, UDP, IP, and Ethernet overhead.
One rule that can significantly affect budgets is edge compression: when the origin provides an uncompressed object and Akamai compresses it at the edge before delivery to the user, the corresponding content is counted in Total bytes as equivalent uncompressed bytes, while Bytes reflects the compressed content actually delivered.
For an object that is 1 MB at the origin, edge compression may send only 0.3 MB, reducing transfer to the user by 70%. Under the billing definitions above, the content's billable volume cannot therefore also be reduced directly by 70%. This does not negate compression's user-experience benefits; download bytes and billing bytes simply answer different questions.
When verifying a quote, have the provider specify which report and field the GB figure comes from and whether compression occurs at the origin or at the edge. Do not export a total transfer figure from browser developer tools and treat it as all billable usage, and do not add all link overhead to the bill yourself.
Saving money requires two conditions at once: the optimization actually reduces usage defined as billable under the contract, and the charges are in a range that changes with usage. If billable usage falls from 50 TB to 40 TB, the base monthly fee at the entry rate can drop from USD 2,500 to USD 2,000; if it falls from 5 TB to 4 TB, the USD 499 minimum still applies.
Optimization plans should therefore record experience benefits, changes in billable usage, and changes in actual payment separately. Writing “higher compression ratio,” “less traffic,” and “lower bill” as the same percentage would make procurement believe cash savings exist when they do not.
A Higher Cache Hit Ratio May Save on Origin Costs
When 50 TB of content is delivered to users, they still receive that 50 TB regardless of how much comes from edge cache. A higher hit ratio can reduce origin fetches, but a 90% cache hit ratio cannot be directly interpreted as only 5 TB being billed for CDN delivery.
The benefits of cache optimization should first appear in origin egress, connection counts, and application processing. If the origin is hosted on another cloud platform, check whether its egress charges have fallen; if origin egress also has resource packages or minimum commitments, lower bytes may not immediately translate into a refund.
Also identify midgress separately—that is, related transfer within the Akamai network.Akamai's published billing termstreat it as a separate metering scope; DataStream also provides fields that distinguish internal transfer from end-user delivery. Do not mix the two and count them again as user downloads, and do not assume internal transfer is always free.
This is especially useful for multi-tier caching and origin protection: a feature may reduce origin fetches while changing internal transfer and product usage. To determine whether it saves money, compare the reduction in origin costs, changes in internal transfer, and new product charges, rather than only checking whether the hit ratio rose.
Procurement can require spending to be split into three columns: Akamai delivery and related products, origin and other cloud resources, and implementation and maintenance. Each optimization should be assigned to the relevant column. Proving that origin load fell is not enough to prove the Akamai bill fell; conversely, an unchanged CDN bill does not mean the optimization had no value.
Which Items in an Enterprise Quote Most Often Exceed the Base Traffic Price
First distinguish what is already included in the published plan from what is an additional business requirement. The channel's page lists a native console and API, standard support, free TLS certificates, and analytics capabilities. If a quote separately lists services with the same names, the additional deliverables should be explained to avoid duplicate purchases simply because the names differ.
Standard support is not the same as managed operations. Answering product questions differs from continuously modifying cache rules, maintaining protection policies, and handling business releases. Whether operations fees are worth paying depends on which responsibilities are assumed, which hours are covered, and who actually resolves issues after a response.
Quote item | What must be specified | How to decide whether to keep it |
|---|---|---|
Base delivery | Commitment volume, offset, full-tier rate, overage, and change conditions | The same charge can be recalculated from monthly traffic |
Dynamic and image optimization | Product name, enabled features, allowance, and additional metering | Addresses a real bottleneck; expand only after validating benefits |
Security and abnormal traffic handling | Protection scope, related metering, overage, and emergency response responsibilities | Covers business risks and explains cost boundaries |
Edge computing and logs | Metering units, included allowance, destination, and storage costs | Has a clear business use and can consistently justify additional usage |
Implementation and ongoing maintenance | Scope of migration, configuration, on-call, changes, and exit handover | Responsibilities are clear relative to the internal team, with no duplicate payment |
For example,the Ion product documentationlists some performance capabilities as optional features. Having an Akamai account and purchasing base delivery does not prove that all optimizations are included. Procurement should map features and prices to the specific order rather than treating the vendor's entire product catalog as a bundle.
Add-on features should not all be purchased at once either. For what should be validated for different capabilities, refer toAkamai CDN Review: Where Enterprise Website Performance Budgets Goto establish acceptance criteria. If static assets already meet requirements, any added dynamic optimization should prove that it improves dynamic business; if edge code is not in use, there is no reason to take on the corresponding commitment just because it might be used later.
Taxes, billing currency, payment processing fees, promotional validity periods, and renewal prices should be placed separately in commercial terms. When converting a USD quote into a local-currency budget, keep the exchange-rate date and the rate used to avoid mistaking currency movements for a CDN price increase. One-time discounts should not be spread into a long-term unit price in a way that obscures the restored price in the second year.
For Multi-Region Delivery, Do Not Substitute Visitor Country for Billing Region
In Akamai documentation, a Billing region is a geographic pricing region in which requests are served; it cannot simply be equated with the country of the visitor's IP address. Where regional differences exist, first obtain usage for the corresponding billing region, then apply that region's contract price.
The channel's published plan explicitly excludes delivery within mainland China and quotes it separately. Therefore, websites whose visitors are primarily in mainland China cannot use USD 499 or the table's tiered rates as a complete budget for delivery from mainland nodes. This exclusion applies to the scope of that channel's plan; it does not mean that all Akamai purchasing options exclude mainland China delivery.
Other target regions and special networks should also have their applicable scope specified in the order. Do not assume that all regions cost the same just because a “global network” is mentioned, and do not add a set of regional surcharges without supporting evidence. For separately quoted regions, obtain the corresponding rates before adding them to the budget; covering differences with a global average price would defeat the purpose of tier selection.
Another item worth examining is the Network Surcharge. DataStream provides corresponding network fields for customers subject to this type of charge, so when verifying usage, billing regions and network surcharges should be identified separately. Whether it applies, how much usage it corresponds to, and its unit price should all be found in the order or bill; it must not be automatically added to the published channel prices above.
More useful information for a quote is the regional distribution in existing billing reports, not just a global total. When the business expands into new markets, update this distribution; if regions have different rates, total bytes may stay the same while spending changes because of a different regional mix.
Regional coverage and cost scope should be verified together. You can use CdnChart'sCDN comparisonto review published performance information for candidate services, then usewebsite speed testto check how your business entry points perform in target regions. Performance data is used to judge whether delivery is worth purchasing; billable usage is still calculated under the contract and official usage reports.
If a Quote Uses 95/5 Bandwidth Billing, You Cannot Keep Multiplying Traffic by a Unit Price
If an enterprise plan is quoted in Mbps rather than GB, use a different budgeting method. Monthly traffic describes the total delivery volume but cannot determine bandwidth charges on its own: sending the same amount of data in a short burst versus spreading it evenly across the month produces different sampled bandwidth distributions.
The 95/5 method in Akamai's published terms samples bandwidth at five-minute intervals, discards the top 5% of samples, and uses the highest remaining value to determine the corresponding billable bandwidth; when regional metering applies, the relevant regions must also be handled separately. Here, 95/5 refers to a bandwidth sampling method, not the P95 metric for web latency.
Nor should it be understood as “the top 5% of traffic is entirely free.” The same document also describes SuperBurst: for contracts subject to the relevant terms, the portion within the top 5% of samples that exceeds twice the committed bandwidth may incur additional burst usage charges. Ignoring this and budgeting campaigns using only 95th-percentile bandwidth would miss another metering component.
To determine whether such a quote is suitable, you need existing bandwidth curves plus the committed Mbps, overage rates, regional aggregation method, and burst rules in the quote. Businesses with many campaigns and pronounced bandwidth spikes should ask for a recalculation using actual historical curves before comparing with traffic-based plans; do not choose based only on total TB and a lower nominal unit price.
The USD 0.05/GB above belongs to the published traffic-based plan and cannot be directly converted into a fixed Mbps price, let alone have every bandwidth clause added to that channel's traffic plan. To determine which metering a quote uses, check the order first; offerings under the same Akamai name may follow different billing paths.
Close the Quote Before Signing So First-Month Differences Can Be Identified
A quote ready for procurement should allow the payment amount to be calculated item by item along products, usage, rates, and offsets. The most effective validation is not to ask again whether there are more discounts, but to have the provider generate a cost breakdown using your most recent complete month of data.
Akamai'sCP code documentationnotes that these identifiers associate traffic with contracts and products and are used for billing and reporting. When verifying, first confirm which CP codes and businesses are covered, so you do not compare an export missing part of the usage against a bill covering all business.
List the applicable contract, products, business scope, billing period, and time zone, and confirm the conversion unit used for GB.
Obtain usage by the corresponding CP code and billing region, distinguishing end-user delivery, internal transfer, and other product metering.
Apply the selected commitment tier's rate, minimum spend, and offset order; do not mistake a full-tier rate for a tiered rate, and do not add the minimum charge twice.
Then add separately purchased services, taxes, and adjustments specified in the order, and reconcile the final amount and payment timing.
For example, at 50 TB on the entry tier, base delivery should come to USD 2,500; if the final amount is higher, it should be possible to identify which actual item caused the increase. When a difference appears, first check units, period, compression basis, CP code scope, and offsets, then check taxes and adjustments. Raw logs can help locate issues, but a simple sum must not be treated as an official bill without checking collection limitations.
The migration month should also separately list remaining charges for the old service, implementation costs for the new service, and overlapping operation expenses. A lower steady-state monthly fee for the new plan does not mean cash spending in the onboarding month will also be lower; these two budgets should be arranged separately to avoid discovering after launch that the old contract is still being paid.
For websites whose monthly usage is consistently only 1 to 5 TB and that do not need additional enterprise capabilities, the USD 499 monthly minimum and 12-month term should be priority screening criteria. For businesses approaching 75 TB or more, compare higher commitment tiers as well; at both 80 TB and 150 TB, a higher commitment may result in a lower payment.A quote ultimately worth accepting must explain base charges, off-peak commitments, actual billable bytes, and add-on items all at once. A low unit price alone, without the ability to recalculate the payment amount using your own business volume, is not enough to sign.
- Akamai CDN pricing
- Akamai traffic billing
- Akamai enterprise quote
- Akamai minimum commitment
- Akamai tiered pricing
- Akamai billing
- CDN cost calculator