Available now
Open Source
For engineers running their own checks.
Free
Apache-2.0 open source
- CLI, SDK and 93 open cost rules
- IaC checks locally and in CI
- Live AWS discovery with your own credentials
- MCP server for AI assistants
CloudBurn / Open-source CLI today. Platform waitlist open.
Start with the free, open-source CLI. When your team wants it managed across AWS accounts, CloudBurn Platform runs it for you, and scan results stay in an S3 bucket in your own account.
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.
CloudBurn Platform preview with sample data.
Available today / Free and open source
Scan Terraform and CloudFormation for costly patterns before deployment. Run discovery against live AWS to find waste already in your account. Use the CLI locally or in your CI pipeline.
# Install CloudBurn
brew install towardsthecloud/tap/cloudburn
# Check infrastructure before deployment
cloudburn scan ./iac --exit-code
# Discover waste in live AWS
cloudburn discover --region us-east-1Live discovery requires AWS credentials and Resource Explorer setup. See prerequisites.
Cost estimation / Platform preview
A whole-stack estimate. One place to work.
Bring your AWS services into one estimate. Adjust regions and resource configurations, compare billing periods, and export the breakdown as CSV.
Try the free individual calculatorsCost analysis / Platform preview
See where your AWS spend went, and what changed.
Map the last 30 days of spend in a connected account by service and usage type, or by Region, and compare it with the 30 days before. Color tiles by change to spot what grew, and see the fastest-growing usage types and known waste patterns such as NAT data processing and gp2 volumes. The cost data is stored in your own results bucket.
How the AWS Cost Tree works$13.3K · 1 Sept – 30 Sept · 25 services · 62 usage types
BoxUsage:m6i.2xlarge
$1,310 · USE1
BoxUsage:c6i.4xlarge
$1,094 · USE1
SpotUsage:g5.2xlarge
$632 · USW2
BoxUsage:m6i.2xlarge
$565 · EUW1
InstanceUsage:db.r6g.2xlarge
$1,156 · USE1
Multi-AZUsage:db.r6g.large
$514 · EUW1
Aurora:StorageUsage
$284 · USW2
NatGateway-Bytes
$355 · USE1
EBS:SnapshotUsage
$345 · USE1
EBS:VolumeUsage.gp2
$250 · USE1
TimedStorage-ByteHrs
$449 · USW2
Requests-Tier1
$186 · USE1
Model-OutputTokens
$312 · USE1
Model-InputTokens
$183 · USE1
Cost estimation / Platform preview
See the cost of a change before it merges.
Bring AWS cost reports into GitHub pull requests for Terraform, CloudFormation, and AWS CDK. Review the cost change alongside the code, with assumptions and missing inputs made explicit.
How the IaC Cost Estimator works
| Resource | Current cost | New monthly cost |
|---|---|---|
| MySecondInstance | $0.00 | $133.15 (+$133.15, new) |
| MyThirdInstance | $0.00 | $66.58 (+$66.58, new) |
| firstTaskDef | $0.00 | $9.01 (+$9.01, new) |
| MyFirstInstance | $0.00 | $8.32 (+$8.32, new) |
Cost optimization / Platform preview
Find what is costing money without doing work.
Idle NAT gateways, unattached EBS volumes, RDS instances with no connections, load balancers without targets. 31 checks find what you can remove, stop, or release, and each finding shows the evidence and the monthly cost behind it.
How Unused Resources worksCost optimization / Platform preview
Make the resources you keep work harder.
Rightsize low-utilization instances, move to Graviton and gp3, schedule Redshift pauses, and catch RDS engines that are running up extended support charges. 38 checks compare what you run with what you could run, with savings where AWS or CloudBurn has the evidence.
How Resource Efficiency worksCost optimization / Platform preview
Stop paying On-Demand rates for steady workloads.
Find RDS, Redshift, and ElastiCache capacity that has run On-Demand for months without reserved coverage, Savings Plans purchases AWS recommends for your usage, and EC2 reservations about to expire. Weigh the savings before you commit.
How Commitment Savings worksCost optimization / Platform preview
Check the controls around your AWS spending.
Catch AWS Budgets that are over their limit or forecast to break it, accounts without Budgets or Cost Anomaly Detection, and resources without the tags you need to allocate spend.
How Cost Governance worksCost optimization / Platform preview
Open any finding to see the resource, the check that flagged it, the metrics behind it, and what it costs each month. Remediation commands are examples for you to review and run yourself. CloudBurn never runs them in your account.
How finding review worksFrom your terminal to every account
Connect your AWS accounts and GitHub organization once. CloudBurn Platform scans the accounts you connect with the same open-source rules and keeps the scan history, so a finding in the dashboard carries the rule name you already know from the CLI. The CloudBurn GitHub App adds cost reports to your pull requests.
Available now, for you
Waitlist open, for your team
CloudBurn Platform / How the connection works
CloudBurn Platform connects through an IAM role you deploy in your own AWS account, and scan results stay in an S3 bucket you own. CloudBurn reads the results from your bucket to draw the dashboard instead of keeping its own copy.
CloudBurn Platform
Runs the scan and draws your dashboard.
Your AWS account
IAM role
CloudBurnReadOnlyRole
You deploy it from a CloudFormation or Terraform template.
S3 results bucket
Owned by you
Every scan result is stored here, in your account.
Pricing
The open-source toolkit is free. Join the waitlist and pay 30% less on any Platform plan for as long as you keep it. Every plan starts with a 14-day free trial.
Available now
For engineers running their own checks.
Free
Apache-2.0 open source
Waitlist open
For one repository and one AWS account.
$49$34.30/month
Waitlist price, billed monthly
Waitlist open
For teams across several accounts and repositories.
$79$55.30/month
Waitlist price, billed monthly
Everything in Starter, plus:
Waitlist open
For cost review across the whole organization.
$199$139.30/month
Waitlist price, billed monthly
Everything in Pro, plus:
The open-source CLI checks Terraform and CloudFormation locally without AWS credentials, and runs live discovery with your own credentials. CloudBurn Platform connects through an IAM role you deploy in your own account from a CloudFormation or Terraform template. The role 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, where scan results are stored. CloudBurn holds no long-lived credentials.
CloudBurn Open Source is available now. Install the CLI to check Terraform and CloudFormation for costly patterns and run discovery against live AWS resources. The free, individual AWS calculators are also available on this site.
CloudBurn Platform runs the CLI's work for your team. It 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. The scans use the same open-source rules, so a finding carries the same rule name you get from the CLI.
Your scan results are already in the S3 bucket in your account. The rules the Platform runs are the open-source rules, released under the Apache-2.0 license, and you can keep running them with the CLI. The IAM role and the bucket live in your account too: delete the role with the stack or with terraform destroy whenever you want.
CloudBurn Platform is expected to open in early 2027. Waitlist members get 30% off when it launches and keep it for as long as they keep their plan. Joining does not start a trial or a paid plan. Two emails a month at most. Unsubscribe anytime.
CloudBurn Platform / Waitlist
Until then, the open-source CLI is yours to use.
30% founding-member discount
Only waitlist members get it. Join now and keep 30% off for as long as you keep your plan.
Two emails a month at most. Unsubscribe anytime. Email signup requires confirmation.
CloudBurn Platform connects through an IAM role you deploy in your own AWS account, and scan results stay in an S3 bucket you own. How the connection works.