What Infracost Does
Cloud cost surprises happen when infrastructure decisions are made without cost visibility. Infracost eliminates these surprises by injecting cost feedback directly into the developer workflow — the pull request where infrastructure decisions are actually made. This review evaluates whether Infracost delivers actionable cost intelligence or just adds noise to your PR process.
Core Experience and Resource Coverage
The core experience is straightforward and effective. Configure Infracost in your CI pipeline, and every PR that modifies Terraform files gets an automated comment showing: monthly cost before the change, monthly cost after, the diff, and a breakdown by resource. The comment is formatted clearly with expandable sections for detailed resource-level costs. Reviewers can see cost implications without leaving the PR — no separate dashboard or tool switching required.
Resource coverage is impressively broad. Infracost calculates costs for over 1,000 AWS, Azure, and GCP resource types using each provider's pricing API. This covers compute (EC2, VMs, GKE), storage (S3, Azure Blob, GCS), databases (RDS, Cloud SQL, Cosmos DB), networking (load balancers, NAT gateways, data transfer), and serverless (Lambda, Cloud Functions). The accuracy is high for standard resources — pricing matches what you would calculate manually from provider pricing pages.
Usage Estimation and GitOps Integration
Usage-based cost estimation addresses the tricky resources where cost depends on consumption rather than configuration. For resources like S3 requests, Lambda invocations, or data transfer, Infracost accepts a usage file (infracost-usage.yml) where you specify expected usage patterns. This transforms Infracost from a configuration-based calculator into a realistic cost estimator. Without usage data, these resources show the base cost without consumption charges.
The Atlantis integration is particularly elegant for teams using GitOps Terraform workflows. Infracost hooks into the Atlantis plan-comment workflow, adding cost information alongside the plan output. The team sees what will change and what it will cost in the same PR comment. This integration makes Infracost essentially invisible — cost visibility becomes part of the natural workflow without any extra steps.
CLI and Dashboard
The CLI tool runs locally for quick cost checks during development. Run infracost diff before pushing changes to preview cost impact without waiting for CI. The breakdown command shows the full cost of your current Terraform configuration. For developers who want cost awareness during development rather than only at PR time, the CLI provides immediate feedback.
The cloud dashboard adds team-level visibility. It tracks cost trends across repositories, teams, and time periods. Alerts notify when a PR would push costs above configured thresholds. For FinOps teams that need organizational cost oversight, the dashboard aggregates what individual PR comments cannot — the cumulative cost trajectory of infrastructure decisions across the entire engineering organization.
Cost Governance and Limitations
Policy enforcement enables cost governance without manual review of every PR. Configure cost thresholds that trigger warnings or block PRs — for example, requiring approval for changes that increase monthly costs by more than $500. Combined with Terraform plan approval workflows, this creates a cost-aware deployment pipeline where expensive changes get appropriate scrutiny.
The main limitation is that Infracost estimates costs from Terraform configuration, not actual consumption. Resources that scale dynamically (auto-scaling groups, serverless functions) will show estimates that may differ from reality. Infracost is excellent for predictable infrastructure but less precise for consumption-heavy architectures. It complements rather than replaces actual cloud billing analysis.
The Bottom Line
Infracost is essential infrastructure for any team managing cloud costs through Terraform. The PR integration shifts cost awareness to the point of decision, the CLI enables local cost-conscious development, and the dashboard provides organizational visibility. At 12.4K+ stars and Apache 2.0 license with enterprise adoption at JPMorgan Chase and BMW, the tool is mature and trustworthy. If your team uses Terraform and cares about cloud costs, Infracost should be in your CI pipeline.