About CloudBurn
CloudBurn came out of real AWS cleanup work.
I'm Danny Steenman, and I build CloudBurn. In my AWS work, the same expensive decisions kept showing up in Terraform, CloudFormation, and live accounts, and teams usually found them on the bill.
CloudBurn turns those patterns into rules you can read and run where the work happens: in CI before you deploy, and against live AWS with cloudburn discover after. When a team wants that run for them across its AWS accounts, CloudBurn Platform does it.
Danny Steenman
Founder & Cloud Engineer
Has over a decade of experience designing, building, and operating large-scale, distributed systems on AWS Cloud.
Why it's open source
You should be able to read a rule before you trust its finding.
A cost finding asks you to delete, resize, or re-architect something. I wouldn't act on one without knowing how it was made, so I don't ask you to. The CLI, SDK, and rules are free under the Apache-2.0 license, and they run in your own environment. CloudBurn Platform scans with the same rules, so every finding in the dashboard carries a rule name you can look up in the source.
Why your data stays in your account
Connecting an AWS account should be a decision you can check.
So CloudBurn Platform asks for as little standing trust as I could design for. You deploy an IAM role in your own account from a CloudFormation or Terraform template. It uses the AWS managed ReadOnlyAccess policy, which can read your resources and the data they hold, plus write access to one S3 bucket you own. Scan results are written to that bucket, and CloudBurn reads them from there to draw your dashboard. CloudBurn holds no long-lived credentials, and removing the role ends its access.
How CloudBurn works
One set of AWS cost rules, run before and after you deploy.
CloudBurn runs the same readable rules in two places. Run them on your infrastructure code to stop an expensive change before it merges, then run them against your AWS account to find what is already wasting money.
What it changes for your team
Developers see the cost of a change in the pull request, while it is still easy to change.
Platform teams get checks they can read, tune, and explain to the rest of the organization.
Years of AWS cost reviews become checks that run on every change.
Readable rules
Every finding traces back to a rule
Each check is a plain rule you can open in the source: what it looks for, the threshold it uses, and what to do about it. The same input gives the same result on every run.
Before deploy
Catch costly changes in the pull request
Run cloudburn scan in CI against Terraform and CloudFormation. A costly pattern gets flagged during code review, while changing it is still a one-line fix instead of a migration.
After deploy
Find the waste that is already running
Run cloudburn discover against your live AWS account. The same rule engine checks deployed resources for idle NAT gateways, unattached EBS volumes, and other spend that does no work.
Start small
Try it on one repo for free
Install the open-source CLI with brew or npm, read the rules, and add it to one pipeline. The output works in the terminal, in CI logs, and as JSON when you want to automate around it.
CloudBurn Platform / Waitlist open
When your team wants the CLI run for it, the Platform runs it.
CloudBurn Platform adds shared workspaces, unused-resource scans of the AWS accounts you connect with scan history, the AWS Simple Pricing Calculator, and pull-request cost reports through the CloudBurn GitHub App. Every finding traces back to a rule you can open.
View the roadmapJoin the CloudBurn Platform waitlist.
Waitlist members get 30% off when CloudBurn Platform launches in early 2027, and keep it for as long as they keep their plan.
Two emails a month at most. Unsubscribe anytime. Email signup requires confirmation. Privacy policy.
Hands-on help
Need someone to work on your AWS bill with you?
Some teams need more than findings: a person to review the architecture, plan the changes, and set up FinOps practices with them. That is the work I do at Towards the Cloud, my AWS consultancy. If your team needs hands-on AWS cost optimization or FinOps consulting beyond what CloudBurn Platform does, start there.
AWS cost optimization at Towards the Cloud