Unblended cost
Unblended cost is AWS cost as billed: each line priced at the rate actually charged for it, on the day the charge occurs. Upfront commitment fees appear in full on the day you pay them and discounts can show as separate lines, which makes unblended cost the view that matches the invoice.
In plain English
Think of your card statement: every charge on the day it happened, at the price you paid. A year of gym membership shows up once, in full, on the day you signed. Unblended cost is that statement view of your cloud bill.
Formula and worked example
Unblended cost = unblended rate × usage amount
- Unblended rate
- = the rate AWS charged for that line
| A typical day of AWS cost, unblended | $3,200 |
|---|---|
| Upfront Savings Plan fee, charged on 15 January | $12,000 |
| 15 January, unblended | $15,200 |
One day looks almost five times as expensive as any other. Amortized cost spreads the same fee at about $33 a day for a year, which is what each day of usage actually consumed.
Why unblended cost matters
Unblended cost is the number that reconciles with the AWS invoice, so it is the starting point for finance: cash planning, accruals and checking the bill. It is also how AWS Cost Explorer shows cost by default, and the column most Cost and Usage Report queries start from.
What it is not good at is showing what usage cost over time. A commitment bought today makes today look expensive and the rest of the term look cheap, so for trends, showback and unit economics, use amortized cost alongside it.
Common mistakes
- Summing Savings Plan lines without the negations. In the Cost and Usage Report, usage covered by a Savings Plan shows its on-demand price as unblended cost, offset by a separate SavingsPlanNegation line. Leave the negation lines out and covered usage looks as if it was billed at on-demand prices.
- Ignoring discount lines. Grouped by charge type, unblended cost lists discounts as their own lines. AWS's net unblended cost subtracts them; use it when you need the after-discount figure.
- Reading spikes as usage changes. A jump on one day is often a purchase, such as an upfront commitment fee, a support charge or a Marketplace subscription, not a change in usage. Check the charge type before chasing it.
- Comparing clouds on different bases. Azure calls this view actual cost, and Google Cloud's billing export shows cost before credits with the credits alongside. Compare like with like.
Where to find it in AWS, Azure and Google Cloud
| Cloud | What it is called | Where to find it |
|---|---|---|
 AWS | Unblended cost | Cost Explorer's default view (Advanced options → Unblended costs). In CUR 2.0: line_item_unblended_cost (unblended rate × usage amount), with line_item_net_unblended_cost for the after-discount figure. |
 Azure | Actual cost | Cost Management → Cost analysis, Actual cost view: usage and purchases as billed, with reservation and savings plan purchases shown in full when they are charged. |
 Google Cloud | Cost before credits | Cloud Billing export to BigQuery: the cost column is usage at the price charged, before credits. Credits such as committed use and sustained use discounts are listed separately, so net cost is cost plus credits. |
How CloudYali helps
CloudYali shows AWS cost as billed (unblended) across its cost views, so totals reconcile with your AWS invoice; Financial Commitments switches to amortized commitment cost. The docs explain how each provider's cost is counted.
Related terms
Billing & cost types
Amortized cost
Amortized cost spreads each commitment fee across the period it covers, so a one-year Reserved Instance or Savings Plan paid up front shows up as a share of the fee every day of the term instead of one large charge on the day you buy it.
Billing & cost types
Blended cost
Blended cost is AWS cost priced at a blended rate: the average of the Reserved Instance and on-demand rates that accounts in an AWS Organization paid for the same usage. It spreads the benefit of reservations evenly across accounts, so it rarely matches what any one account was actually charged.
Billing & cost types
Cost and Usage Report (CUR)
The Cost and Usage Report (CUR) is AWS's most detailed billing dataset: every charge, down to the hour and the resource, with its usage, rates, discounts and commitment details, delivered as files to an S3 bucket you own. CUR 2.0, created through AWS Data Exports, has a fixed set of columns.
Commitments & rates
Savings Plan (SP)
A Savings Plan is an AWS or Azure commitment to spend a fixed amount per hour on eligible compute for one or three years. Usage up to that amount is billed at lower rates, and the discount follows your usage across instance sizes and, with the most flexible plans, instance families and regions.
Commitments & rates
Reserved Instance (RI)
A Reserved Instance (RI) is a one- or three-year commitment to a specific kind of capacity, such as an EC2 instance type in a region or an RDS database, in exchange for a lower hourly price. It's a billing discount, not a server, and you pay for every hour of the term whether the capacity runs or not.
Frequently asked questions
What is the difference between unblended and amortized cost?
Unblended cost shows each charge on the day it happens, including upfront commitment fees in full. Amortized cost spreads those fees across the period they cover. Over the term they add up to the same amount.
What is net unblended cost?
Unblended cost after the discounts AWS lists as separate lines, such as negotiated or volume discounts. In CUR 2.0 it's line_item_net_unblended_cost: what you actually pay for the line.
Why does unblended cost spike on some days?
Usually because of a purchase: an all-upfront or partial-upfront commitment, a support fee or a Marketplace charge lands in full on the day it is billed. Switch to amortized cost to see whether usage actually changed.
