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. VS Code extension The Infracost VS Code extension shows cost…
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. Infracost v0.10…
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…
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. Super-fast CLI We updated the Get Started guide to use the new parse HCL option. This option received very positive community feedback as it enables the CLI…
Infracost v0.9.21 is live! We added support for cost policies into the CLI and pull request comments, added many more resources, and updated the Jenkins and CircleCI integrations to support the latest features. Catch mistakes & budget-breaking changes in CI We added native support for cost policies into the CLI and pull request comments. DevOps and FinOps teams can…
Cost policy checks are now reported directly inside pull request comments! Native integration with Open Policy Agent simplifies writing policies that are checked before resources are launched. I love shipping fast! And to ship fast, as engineers we usually automate things: The key benefit of these guardrails is that they fit into my workflow and tell me something…
Infracost v0.9.19 is live! We’re experimenting with parsing HCL (we need your help), partnered with GitLab, improved Bitbucket support, published a Windows Chocolatey package, and added many new resources… Parsing HCL Imagine you could add Infracost to repo README files, get cost estimates for Terraform modules before using them in your projects, and even see cost estimates in Visual Studio…
Infracost v0.9.17 is live! There’s a new Atlantis integration, native Azure DevOps extension, cost policies with Open Policy Agent, Sentinel and more. New Atlantis integration The new Infracost Atlantis integration enables you to: Follow our migration guide if you used the old bash-based integration. New Azure DevOps extension The new Infracost Azure DevOps extension is live in the Azure Marketplace! These JavaScript tasks…
Summary: Infracost v0.9.16 is live! You can now share cost estimates with colleagues, managers and with your external clients. We have also released our new composable GitLab CI template, and 10 new AWS/Azure/Google resources. Upgrade now! Share cost estimates There are a few use cases in which sharing cost estimates with others is really helpful: sharing an estimate…
Summary: we’re excited to announce Infracost v0.9.14 and our new composable GitHub Actions 🎉 This release also includes new GitHub comment and Slack message output formats, 6 new AWS/Azure/Google resources, a summary table in PR comments, improved CLI output, and faster runs. We recommend everyone to upgrade! How did we get here? It’s a bit noisy! We’d…
We released Infracost v0.9.12 recently, you can upgrade to use these features. This release includes many bug fixes and we have made Infracost a lot faster to run! Improved CLI output We’ve simplified the output for AWS S3 and CloudFront. Previously these resources had over 50 lines of output due to their complicated pricing models. We now…
We released Infracost v0.9.9 recently, you can upgrade to use these features. Fetch usage from CloudWatch When it comes to estimates for resources where the cost fully depends on usage (e.g. AWS S3 or Lambda), we have a usage file, in which users can define how much of those resources they will use. This requires you to manually…