CloudBurn
Get automatic AWS cost estimates in your pull requests. Prevent expensive infrastructure mistakes before deploying to production.
About
CloudBurn is for teams using Terraform or AWS CDK who want to prevent expensive infrastructure mistakes before they reach production. Most teams discover AWS cost problems weeks later on their bill, after the infrastructure is already running and the money is spent. CloudBurn changes this by showing AWS costs during code review, when changes are easy to make. Here's how it works: 1. A developer opens a pull request with infrastructure changes (Terraform or AWS CDK). 2. CloudBurn automatically analyzes the changes using real-time AWS pricing. 3. A cost report appears in your PR, showing exactly what each change will cost per month. 4. Your team discusses costs during code review and adjusts before deployment. What you get: - Automatic cost analysis on every infrastructure PR - Real-time AWS pricing for your specific region - Resource-level breakdown showing old vs. new monthly costs Stop optimizing reactively. Catch costly decisions during code review when they're easy to fix.
Key Features
Automatic PR Cost Reports
Automatically analyzes Terraform plans or AWS CDK diffs and posts a detailed cost report as a comment on every pull request.
Real-time AWS Pricing by Region
Uses the official AWS Pricing API to calculate accurate, region-specific monthly costs for each resource change.
Resource-level Cost Breakdown
Shows per-resource old vs. new monthly costs and an overall monthly delta so reviewers can see exactly which changes drive cost increases.
GitHub Actions Integration
Easy setup via GitHub Marketplace and GitHub Actions — capture cdk diff or terraform plan output and send it to CloudBurn for instant analysis.
Shift-left FinOps Workflow
Embed cost visibility into code review so teams can discuss and reduce cost impact before deployment, preventing surprise bills.
How to Use CloudBurn
1. Install CloudBurn from the GitHub Marketplace and grant access to the repositories where you manage AWS infrastructure. 2. Add the matching GitHub Action to your repository workflow (Terraform Plan PR commenter or AWS CDK Diff PR commenter) so plan/diff output is captured. 3. Open a pull request with infrastructure changes; the action will send the diff/plan to CloudBurn for analysis. 4. Review the cost report CloudBurn posts in the PR (per-resource breakdown and overall monthly delta), then adjust resources or configuration before merging.