Status: CloudBurn Platform has not launched publicly yet. This page describes how it works. Join the waitlist for a 30% founding-member discount: only waitlist members get it, and they keep the lower price for as long as they keep their plan.
An Optimization Scan checks a connected AWS account against 82 cost checks, grouped into four review areas. In the dashboard, Cost optimization has an Overview that compares the areas and one page per area. One scan refreshes all four areas from the same snapshot, so you never scan an account once per area.
Choose a review area
| Area | Checks | Review decision |
|---|---|---|
| Unused Resources | 31 | Remove, stop, pause, or release paid resources that no longer provide value |
| Resource Efficiency | 38 | Keep the resource and improve its sizing, architecture, generation, autoscaling, lifecycle, retention, or storage |
| Commitment Savings | 8 | Buy, renew, or extend Savings Plans and reservations for steady usage |
| Cost Governance | 5 | Close gaps in budgets, anomaly detection, and cost-allocation tags |
Every check is an open-source rule from the Rules documentation. Each area's page lists its checks and links each one to its rule.
Run a scan
You need a connected AWS account that passes its readiness checks, within your plan's account limit. Starter reviews Unused Resources and Resource Efficiency; Pro and Enterprise add Commitment Savings and Cost Governance. Every workspace member can run scans; owners and admins manage account connections.
- Under Cost optimization, open one of the four areas, such as Unused Resources. The Overview only reads results: when an account has no usable snapshot, it links you to Unused Resources with that account selected.
- Choose the AWS account, then choose Run optimization scan. The button shows Scan queued or Scan running until the scan finishes. If the account fails a readiness check, such as having no configured Region, the page lists what blocks the scan and links to Fix in AWS Accounts.
- Review the results when the scan completes. While a replacement scan runs, the previous successful snapshot stays visible.
Moving between the Overview and the area pages keeps the selected account and snapshot.
Inventory checks cover the connection's configured Region. Checks that read Cost Optimization Hub, AWS Budgets, Cost Explorer, or tags across Regions are account-wide. Each area shows its Evidence scope below the summary; check it before you treat a result as coverage of your whole account.
Compare areas on the Overview
The Overview shows the selected snapshot across all four areas:
- Data sources reports whether the optional AWS sources some checks read are ready (All ready or Needs setup). See Data sources and incomplete evidence.
- Findings, Checks, and Snapshot total the four areas and show whether the snapshot is Complete or Partial. A partial snapshot has a Why partial? link to the affected checks.
- One scorecard per area links to its page. It shows the findings and their change since the previous snapshot, a bar of check outcomes, and the services with the most findings. The Commitment Savings card also shows Known monthly savings.
- Where to start, Largest opportunities, Findings over time, Check outcomes over time, and Findings by service help you decide what to review first. The trend charts fill in as you build snapshot history.
Read the selected snapshot
The Snapshot selector defaults to the latest successful snapshot. Choose a timestamped entry to revisit a previous run, or Load older snapshots when more history is available.
Each area shows Findings, Checks, and a Snapshot outcome. Commitment Savings also shows Known monthly savings where financial evidence is available. An unknown amount remains unknown; it does not mean there are no savings.
| Snapshot outcome | What to do |
|---|---|
| Complete | Review the findings and individual check outcomes |
| Partial | Review the available findings and the explanation of missing evidence |
| Unavailable or Failed | Follow the evidence or error guidance; the area was not assessed, so an empty result does not mean zero findings |
Snapshots expire 90 days after they complete, and each page shows both times. Overview flags an older selection when a newer successful snapshot exists. Run a new scan when results have expired or after fixing a data-source issue.
Review checks and findings
Use the status filters to inspect Failed, Passed, or Not applicable checks, or choose All. Unknown appears when a check lacks enough evidence; a missing assessment is not a passing check.
Use the search field to search resource names and IDs, or choose a check under Checks with findings to narrow the results. Open a check to see its description and findings, then open a finding to review:
- the subject, the check that flagged it, and the remediation effort
- Financial evidence: the current cost and potential savings, in the source's currency and period, or Unknown when there is no financial evidence
- Read-only guidance for the area, with an example AWS CLI command where one is available
- Validated evidence: the data the check evaluated
Commands are examples for your review; CloudBurn does not execute them. Review the resource and its dependencies before changing anything in AWS.
Data sources and incomplete evidence
Most checks read resource configuration and metrics through the role you deployed. A few read optional AWS features that the read-only role cannot turn on for you:
| Data source | Used for | Checks that need it |
|---|---|---|
| Cost Optimization Hub | Savings Plans, Reserved Instance, and rightsizing recommendations | Six checks across Unused Resources, Resource Efficiency, and Commitment Savings |
| AWS Compute Optimizer | Rightsizing recommendations | Lambda memory in Resource Efficiency; Cost Optimization Hub also needs it for rightsizing and idle recommendations |
| AWS Cost Explorer | Cost and usage history | SageMaker Savings Plans coverage in Commitment Savings, anomaly detection in Cost Governance |
| AWS Budgets | Budget coverage | Three budget checks in Cost Governance |
| Resource Explorer aggregator index | Tags on resources in every Region | Untagged resources in Cost Governance |
A missing source affects only the checks that need it; the rest of the scan still runs. Open Data sources → Details on the Overview for each source's status, setup steps, and an AWS setup guide. After you change something in AWS, choose Check again to run a new scan. Cost Optimization Hub, Compute Optimizer, and Cost Explorer can take up to 24 hours to return data after you enable them. CloudBurn only reads budgets; it never creates them.
Export findings
From an area's Export menu, choose Matching findings to download the filtered results or All findings for the whole area. Choose Download CSV or Download Markdown. The download uses the displayed snapshot and includes up to 10,000 findings in check order; narrow the filters when an area has more. Areas that were not assessed do not offer findings exports.
Run the checks yourself
Every check runs in discovery mode in the open-source rules, so you can run them against your own account with cloudburn discover and your own AWS credentials. Platform runs the scan through the IAM role you deployed, keeps snapshot history, and lets your workspace review the results together.
What's next
| Read this | To learn |
|---|---|
| Unused Resources | Find paid resources you can remove, stop, or release |
| Connect an AWS account | Fix account readiness or add another connection |
| AWS Cost Tree | Explore the spending patterns behind a cost change |