New Savings Proposals: approve, test and roll back cost changesLearn more Sign in|Talk to a cloud engineer
Product tourGet a demo

Find the spend behind every spike

Group your AWS and Azure bill by service, team, account or tag. Add a second grouping, compare with last month, and click any bar to see what it is made of.

Get a demoTry the interactive demo
What you're watching
  1. 1
    Add Team as a second grouping

    The last 30 days start grouped by Service. Picking Team from Add Group By restacks the same spend by owner.

  2. 2
    Try line, then stacked area

    The chart type changes but the query does not, so the headline total stays exactly where it was.

  3. 3
    Compare with a month ago

    Compare, then Month Ago, lays the previous 30 days over the bars. The headline shows the change: -1.7% vs Month Ago.

  4. 4
    Click a bar to drill in

    Clicking Sep 5 opens that day split by service, with Group by Usage type as the next step down.

Who does thisFinOps lead, or an engineering manager preparing the Monday cost reviewWhat you getThe day, team and service behind a change, found without exporting the CUR to a spreadsheet.
4cost metrics: Real, Usage, On-Demand and Amortized
3chart types: stacked bar, line and stacked area
4compare windows: a week, month, quarter or year ago
8filter operators, including “has no value”

All product scenes on this site use fictional sample data for “Lumora Retail”.

The invoice goes up and nobody can say why

Month-end questions that take a day in spreadsheets, answered from the bill itself.

Visibility

Nobody can explain a jump in the bill

What usually happens: Someone exports the CUR to a spreadsheet, pivots it for an afternoon, and the answer shows up after the next invoice.

How CloudLens resolves it: Group by service, click the Aug 20 bar, and you are looking at the checkout EKS node group that grew 48%.

Resolved
Ownership

Nobody knows which team spent it

What usually happens: Cost is split by AWS account, which rarely matches how teams are organized, so every review starts with “is that ours?”

How CloudLens resolves it: Group by Team or by your own dimensions. Unallocated spend is its own line, so gaps get fixed instead of argued about.

Resolved
Accuracy

Commitments distort the monthly bill

What usually happens: The month you buy a Savings Plan looks like a spike, and every month after it looks cheaper than it really is.

How CloudLens resolves it: Switch to Amortized cost and the fee is spread across the usage it covers, which is how unit cost should be read.

Resolved

How Ana explained a 48% jump before standup

A Monday morning at Lumora Retail, starting from a Slack alert and ending with a priced recommendation that has an owner.

ARAna RuizFinOps lead, Lumora Retail

Lumora Retail is a fictional company. The people, names and numbers are sample data.

    1
    Mon 08:40High

    Slack flags an EKS anomaly

    A High anomaly lands in #cloud-cost-alerts: Amazon EKS in prod-core is 48% above its expected range for Checkout.
    2
    Mon 08:46

    Groups the last 30 days by Service, then Team

    The stacked bar puts the extra spend in EKS, and the second grouping puts almost all of it on Checkout.
    3
    Mon 08:52

    Compares with a month ago

    The Delta view shows the increase started on Aug 20 and has not come back down. It is a new baseline, not a one-off.
    4
    Mon 09:05

    Clicks the bar to drill in

    The click adds filters for EKS and Checkout and moves the grouping one level deeper. The checkout-api node group doubled its instance hours.
    5
    Mon 09:20Shared view

    Saves the view and shares it

    She saves “Checkout EKS · daily” as a shared view and posts it in the alert thread. Priya’s team opens it exactly as Ana left it.
    6
    Tue 11:00FINOPS-218

    The fix gets an owner

    The rightsizing recommendation for the checkout-api node group is priced at $3,140/mo and tracked as FINOPS-218 in Jira.
Want to click around first?

Try the interactive Cost Explorer

Open the demo

One query behind the chart, the total and the table

Every control changes the same query, so the headline number, the chart and the table always add up to the same total.

Filter down without losing the total

Stack filters on any dimension with the operator you need, including “has no value” to find untagged spend. Then switch between Real, Usage, On-Demand and Amortized cost. Amortized spreads Savings Plan and Reserved Instance fees across the usage they cover.
  • Operators like is, is not, contains and starts with
  • “Has no value” finds unallocated spend
  • Amortized spreads SP and RI fees
What you're watching
  1. 1
    Add a second filter row

    Account is prod-core, staging is already applied. A new row starts with the Environment dimension.

  2. 2
    Exclude development

    The operator menu lists all eight operators. Choosing “is not” development and clicking Apply drops the headline and chart to match.

  3. 3
    Switch the metric to Amortized

    Savings Plan and RI fees are spread across the usage they cover, so the total reads the way commitments really cost.

Who does thisFinOps analystWhat you getProduction spend for two accounts, with commitment fees counted where they belong.

See what changed and when it started

How anomalies are detected
Compare any window with the week, month, quarter or year before it. Aligned overlays both periods, Split puts them side by side, and Delta shows only the difference for each day.
  • Aligned, Split and Delta views
  • Week, month, quarter or year ago
  • Works with every grouping
What you're watching
  1. 1
    Start in Aligned

    Both 30-day periods sit on one axis, with Month Ago dashed. The header shows each total and the -1.7% change.

  2. 2
    Switch to Split

    The two periods become side-by-side bar charts with their own totals, which is easier to read when the shapes differ.

  3. 3
    Open Delta

    Only the daily difference remains. Red bars are days that cost more than a month ago, green bars cost less.

Who does thisFinOps lead, with the engineering manager who owns the serviceWhat you getThe exact days where spend moved, so the investigation starts on the right date.

Save a view once and share it

Group by your own dimensions
A saved view keeps the grouping, filters, metric, chart type and date range. Keep it private or share it with the whole organization. Admins can pick one shared view as the page everyone lands on.
  • Private or shared with the org
  • One landing view per organization
  • Opens exactly as saved
What you're watching
  1. 1
    Save the team view

    Save view opens with the grouping, filters, metric, chart type and date range captured. The name is Checkout, monthly by team.

  2. 2
    Share it and set it as landing

    Two toggles share it with everyone at Lumora Retail and make it the page the org opens by default.

  3. 3
    Find it in the Views menu

    It is tagged Landing and Org, next to Data Platform daily by service and a private Amazon Bedrock by team view.

Who does thisFinOps lead or an org adminWhat you getEveryone at Lumora Retail opens Cost Explorer on the same Checkout view, set up once.

Built for the Monday cost review

Grouped the way you are organized

Start from teams, products and environments. Add a second grouping to see cost by team and service together.

Totals that tie out

The headline, chart and table come from one query, and Amortized cost treats commitment fees the way your invoice does.

Answers without the schema

Ask Copilot in plain English, or send someone a saved view that opens exactly as you left it.

Dimension Studio Anomalies & Budgets Copilot Interactive demo

Cost Explorer questions

AWS Cost and Usage Reports (CUR 2.0) and Azure Cost Management exports. Both land in the same explorer, so you can group and filter across clouds.

Real cost is what was billed on each day. Amortized cost spreads upfront and recurring Savings Plan or Reserved Instance fees across the usage they cover, which is how most teams want to read unit cost.

Yes. Add a second group-by, for example Team and Service, and click any bar to filter to it and move to the next grouping.

You choose. Keep it private or share it with your whole organization. Admins can set one shared view as the landing view.

Ready to see CloudLens in action?

Connect a read-only AWS role or Azure service principal. We'll walk you through your bill, your security graph and the first things worth fixing.