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.
Cost Governance checks the controls around your spending rather than individual resources: whether the account has AWS Budgets and Cost Anomaly Detection, whether a budget is over its limit or forecast to break it, and which resources lack the tags you use to allocate spend. It is one of four areas of a Cost Optimization scan, and the same scan refreshes all four. Open Cost Governance under Cost optimization, choose an AWS account, and run a scan or review its latest snapshot; Run a scan covers plans, readiness, and snapshot history.
What it checks
Cost Governance runs 5 checks, all account-wide.
| Check | Rule | Evidence scope |
|---|---|---|
| AWS Budgets Missing | CLDBRN-AWS-COSTGUARDRAILS-1 | Account-wide |
| Cost Anomaly Detection Missing | CLDBRN-AWS-COSTGUARDRAILS-2 | Account-wide |
| AWS Budget Limit Exceeded | CLDBRN-AWS-COSTGUARDRAILS-3 | Account-wide |
| AWS Budget Forecasted Breach | CLDBRN-AWS-COSTGUARDRAILS-4 | Account-wide |
| AWS Resource Untagged | CLDBRN-AWS-TAGGING-1 | Account-wide |
The three budget checks read AWS Budgets, Cost Anomaly Detection Missing reads AWS Cost Explorer, and AWS Resource Untagged reads tags through the Resource Explorer aggregator index so it covers every Region you index. When a source is not set up, its checks report missing evidence and the rest run as usual. See data sources.
Review the findings
The findings table uses governance labels: Scope names the account, budget, or resource; Governance check names the check; and Evidence source names where the evidence came from. Account and budget findings show their Region as Global; untagged-resource findings show the resource's own Region.
A finding's guidance is labelled Read-only: Governance guidance. CloudBurn only reads your budgets and tags; it never creates budgets, anomaly monitors, or tags.
Exports include each resource's tags. An account with many untagged resources can exceed the 10,000-finding export limit, so filter by check or search before you export. See Export findings.
Run it yourself
Every check above is an open-source rule that runs in discovery mode, so you can run it against your own account with cloudburn discover. Platform runs the same rules through the role you deployed and keeps snapshot history for your workspace.
What's next
| Read this | To learn |
|---|---|
| Cost Optimization | Set up the data sources these checks read |
| AWS Cost Tree | Explore spend by service, usage type, and Region |
| Rules documentation | How each check decides and how to fix it |