Infracost
Shows you the dollar cost of an infrastructure change before you merge it — posts a cost estimate right on the pull request, the same way a code reviewer leaves a comment, so surprise cloud bills get caught before deployment instead of after.
🔗 Visit Infracost
Description
Cloud bills are famously easy to blow up by accident: someone bumps an instance size, adds a new database, or forgets to set an auto-scaling limit, and nobody notices until the invoice arrives weeks later. Infracost catches that at the moment it's easiest to fix — the pull request — the same way a spell-checker flags a typo before you hit publish, rather than after.
Infracost is an open-source (Apache 2.0) CLI that reads your Terraform, CloudFormation, CDK, or Terragrunt code and estimates the cost of the change across AWS, Azure, and GCP, covering usage-based pricing for over 1,100 resource types. It posts a before/after cost diff as a pull request comment, plugs into IDEs (VS Code, JetBrains, Neovim, Zed, Cursor) and AI coding agents (Claude, Cursor) for real-time estimates while writing code, and can enforce FinOps policies (tagging rules, budget guardrails) automatically. The free CLI covers individual and core use; Infracost Cloud is the paid layer for team dashboards, centralized policy management, and multi-repo visibility.
💬 Our review
The short version: Infracost is close to the default answer for 'catch cloud cost surprises before they happen' — the CLI is free, well-adopted (12.5k+ GitHub stars), and does the one thing (cost diffs on PRs) reliably; the paid Cloud tier is worth it once you have more than a couple of repos to watch.
What makes it stand out isn't novelty — cost-diff-on-PR is a well-understood idea — it's coverage and integration depth: 1,100+ resource types across three major clouds, plus IDE and AI-agent integration means the estimate shows up while you're writing the Terraform, not just after you open a PR. That earlier feedback loop is where the real value is; catching an oversized instance type in your editor beats catching it in a PR comment, which beats catching it on next month's invoice.
The honest limits: it's an estimate, not a bill — accuracy depends on how current the underlying cloud pricing data is, and usage-based resources (data transfer, autoscaling) are inherently approximate. The free CLI alone is enough for a solo developer or single repo; the real governance features (centralized policy, multi-repo dashboards) sit behind the paid Infracost Cloud tier, whose pricing isn't published up front. For a team already writing Terraform, there's little reason not to add the free CLI to CI; the Cloud upgrade is a 'when you feel the pain of doing this across repos manually' decision, not a day-one one.
💰 Pricing
📊 Global score
🤖 AI-enriched data
CLI open source (licence Apache 2.0) gratuite pour usage individuel ; Infracost Cloud payant pour dashboard équipe, gouvernance multi-repo (tarifs non publics, plans équipe à partir d'environ 50 $/mois selon les sources).
Pros
CLI gratuite et open source (Apache 2.0), très adoptée (12.5k+ étoiles GitHub)
Couvre 1100+ types de ressources sur AWS, Azure et GCP
Estimation dès l'IDE et via agents IA (Claude, Cursor), pas seulement en pull request
Policy FinOps automatisable (règles de tagging, garde-fous de budget)
Cons
Le dashboard d'équipe et la gouvernance multi-repo sont payants (Infracost Cloud), tarifs non publiés clairement
Estimation de coût, pas une facture réelle — reste indicative selon la précision des prix cloud utilisés
Valeur surtout marginale pour un seul développeur sur un seul repo ; l'intérêt grandit avec l'échelle