CloudCostTree reads your infrastructure-as-code — Terraform, CloudFormation, Pulumi, or a raw Terraform state file — and renders a hierarchical cost breakdown, FinOps savings recommendations, governance checks, and a what-if simulator. AWS-only by design, CLI-only by design: no hosted dashboard, no account required to see a cost tree.
$ cloudcosttree ./my-infra.tf my-infra.tf ($842.13/mo) ├── aws_instance.web (t3.medium, us-east-1) $30.37/mo ├── aws_db_instance.main (db.t3.large, Multi-AZ) $263.52/mo ├── aws_ebs_volume.data (500GB, gp3) $40.00/mo └── ... 💡 FinOps: aws_instance.web is oversized for its CPU utilization — consider t3.small ($15.18/mo, saves $15.19/mo)
No agents, no cloud account linking, no hosted dashboard. Everything runs locally against your existing IaC files.
Terraform, CloudFormation, Pulumi, Terragrunt, a raw Terraform state file, or CloudCostTree's own YAML/JSON — no cloud credentials needed to see a cost tree.
A hierarchical, per-resource breakdown of what your infrastructure will actually cost per month, before you apply anything.
Right-sizing suggestions, real Reserved Instance and Spot savings from actual usage data, and a what-if simulator for testing changes.
Run cost and tag/FinOps policy checks in your pipeline — Pro can fail a build on violation, so cost overruns never reach production. Or gate it locally with "guard", before code even reaches a PR.
Free is a generous, unlimited cost-visibility tool for local use. Pro adds CI/CD scale and the ability to actually enforce governance.
No, not for the core cost tree — it reads your Terraform, CloudFormation, or Pulumi files and computes estimates entirely on your own machine, with no cloud credentials or account link required. The optional Pro --with-usage flag calls your own read-only AWS credentials (the standard credential chain) to replace static-config guesses with real numbers; nothing about your infrastructure is ever uploaded to us.
Terraform (HCL or a terraform show -json plan), a raw Terraform state file, CloudFormation, a CDK-synthesized template, Pulumi, Terragrunt, an Atmos (Cloud Posse) stack (Pro), or CloudCostTree's own YAML/JSON.
A 0-100 number plus a letter grade (A-F) rolling up every FinOps recommendation and policy violation from a run, weighted by severity and normalized by resource count. It's on every plan — free, unlimited, no dollar figure hidden — and shows up in the console, every export format, and history save/list/compare, so a team can track whether a stack is getting healthier or worse over time the same way it already tracks cost.
No — CloudCostTree is AWS-only by design. Staying single-cloud is what lets it price real, fetched-from-AWS rates for ~84 resource types instead of guessing across providers.
Free gives you unlimited local analyses, what-if simulations, and exports, plus the top 3 FinOps recommendations and up to 1,000 CI runs a month — cost data stays informational. Pro ($14.99/mo) unlocks the full FinOps recommendation list, unlimited CI runs, real-dollar Reserved Instance and Spot savings, usage-aware right-sizing, and cost/tag policy enforcement that can fail a build on violation. See the pricing section above for the full comparison.
Yes. Cancel anytime via the customer portal link in your Paddle receipt email, or by emailing us — see the Refund & Cancellation Policy for details. Cancelling stops future billing; your Pro access continues until the end of the period you've already paid for.
Yes — cloudcosttree ci report/check/diff plus a ready-to-use GitHub Action. Free includes 1,000 CI runs a month; Pro is unlimited and can enforce cost guardrails and FinOps/tag policies, failing the build on a violation.
Yes — it's included on both Free and Pro. See the VS Code Marketplace listing.
Found a bug, or have feedback?