cloudburn.io

What It Is

CloudBurn is an open-source cost policy engine for AWS. It is not positioned as a traditional FinOps dashboard; instead, it brings cost checks back into the engineering delivery workflow. With scan, it scans Terraform and CloudFormation in CI, Pull Requests, or release pipelines. With discover, it runs the same rules against live AWS resources to identify resource issues that are already consuming budget.

Core Capabilities and Ecosystem

Its core idea is “one rule engine, two modes”: check IaC before deployment, and check real AWS accounts after deployment. The rules listed cover services such as CloudTrail, CloudWatch, EBS, EC2, ECR, EKS, RDS, and S3—for example, EBS volumes using non-current-generation types, discouraged EC2 instance types, and S3 buckets without lifecycle configuration. scan does not require AWS credentials, making it suitable for local use and CI; discover can check across regions, but requires AWS Resource Explorer to be initialized. Output is available in table and JSON formats, making it easy to read in the terminal or integrate into internal automation. Installation options include Homebrew, npm, and npx, and the project provides links to GitHub, documentation, Roadmap, Changelog, and a Discord community.

Open Source, Pricing, and Documentation

CloudBurn is explicitly an Apache 2.0 open-source CLI. The page does not show a commercial edition, paid plans, or hosted service pricing, so it can currently be regarded as a free open-source tool. On the documentation side, the page covers installation, scanning, discovery, JSON output, and FAQ, offering enough information to get started. However, rule customization, ignore policies, least-privilege permissions, SDK language details, and enterprise support policies are not expanded on in the captured content.

Pros and Cons

The main advantage is that it shifts cost governance left, helping teams catch known waste patterns before infrastructure changes are merged. Its rules are deterministic, making them easier for engineering teams to understand and trust than black-box scores. The same rules can be used for both IaC checks and production audits, reducing policy fragmentation. The limitations are also clear: the content only shows AWS support, so it is not a multi-cloud tool; IaC support only lists Terraform and CloudFormation; and there is no visible SaaS console, team permissions, audit reporting, or SLA information.

Who It’s For and Access from China

CloudBurn is best suited to platform engineering, DevOps, SRE, and FinOps teams that already use AWS and IaC, especially organizations that want to pilot cost guardrails in a single repository first. Access from China is not disclosed in the page content. GitHub, npm, Homebrew, and AWS-related access may be affected by network quality in mainland China. If alternatives are needed, consider Infracost, AWS Cost Explorer, Vantage, CloudHealth, or building IaC policies with OPA/Conftest.