It's been a big month, with many new capabilities and features! You can now create Guardrails to control costs by monitoring pull requests and triggering actions when thresholds are exceeded. You can also use cost policies to scan your code repos for money saving opportunities (e.g. change gp2 to gp3 volume types) and create tasks to help engineering teams take action.

There's also Jira integration, README badges, custom reports, the ability to override the cloud region and lots of new resources.

In 2012, we built a Total Cost of Ownership (TCO) calculator for cloud. Companies could use our online calculator to design their desired cloud infrastructure, and our tool would calculate how much it would cost.

Now in 2022, 10 years later, we want to kill all cloud cost calculators ☠️

Infracost was recently named a cool vendor on Gartner’s Platform Engineering list. This is super exciting for us as a project, but also a great direction forward for engineers and our community as a whole 🎉

This month, we have a few big changes:

• Actual costs and data transfer costs are in private beta.
• See the status of all pull requests (open, merged, closed, deployed) and filter based on that to see their cost impact.
• Slice and dice for all! Export to CSV.
• Buy Infracost without talking to Hassan 😁 and public pricing.

This month we have something for everyone:

• A new usage profiles feature enabling engineers to get cost estimates based on a low, medium or high usage pattern.
• A GitHub App, so engineering managers can deploy and manage Infracost for hundreds of GitHub repos.
• A weekly reports feature for team leads and FinOps showing them the most impactful upcoming cost changes.

When it comes to cloud costs, the relationship between the engineers who are responsible for purchasing infrastructure and the team leads, managers and FinOps who are responsible for the cloud bills is broken.

It turns out the closer you are to the code, the further you are from costs.

We released a new dashboard summary table, support for team management, and introduced concepts for Repos and Projects. Upgrade to version v0.10.11 to pickup numerous bug fixes and the new features.

Two years ago we published our first blog titled Infracost - cloud costs for devs. Infracost is now used by thousands of engineers across many CI/CD systems, 3rd party integrations and even VS Code, so they can see how much their code changes will cost before resources are launched.

We released the Infracost VS Code extension, which was so popular that it hit the front page of Hacker News. That pushed Infracost to over 7,000 GitHub stars ⭐

We also released v0.10.6 that lets you customize project names, and exclude paths when running with large repos.

Back in February, we started an ambitious journey: remove our dependency on the Terraform CLI by parsing code directly! We're excited to announce Infracost v0.10, which completes that journey 🎉

Infracost is now much faster, simpler to add to CI/CD, and does not need cloud creds since a Terraform plan is not required.

In 2009 I started my PhD research to focus on the decisions that needed to be made for an organization to adopt public clouds. These included the benefits, the risks and the costs of using such systems. My aim was to create a set of vendor neutral tools that would assist decision makers during the process.

Infracost v0.9.24 is live! We've got a new Get Started guide that uses the parse HCL option, a way to run diffs between branches, direct integration with Terraform Cloud, and new resources.