Blog

Most security scanners treat infrastructure-as-code like any other codebase: pattern matching, regex rules, surface-level checks. But infrastructure code isn’t like application code. Variables reference other variables. Modules pull in external dependencies. A single Terraform code block might expand into dozens of cloud resources, after evaluation, across different environments. We’ve spent years building deep parsing for…

Here’s something we keep seeing: an engineer grabs Terraform code from their last project, makes a few tweaks, and ships. The code works. The infrastructure deploys. Everyone moves on. Six months later, finance asks why the cloud bill spiked. The culprit? That “working” code used a database version that’s now in extended support. Or storage…

When engineers choose AWS CDK, they’re making a bet on unification. One language for their application code and their infrastructure. TypeScript all the way down, or Python from Lambda to load balancer. It’s an elegant proposition. But until now, that choice came with a trade-off: the cost visibility that Terraform teams take for granted simply…

AWS Cloud Spend and AWS Budgets allow AWS users to monitor cloud spend after it’s already been deployed. This presents issues for engineering teams that are steeped in AWS CloudFormation — do they optimize after deployment and slow engineering teams down, or simply accept cloud waste? Now, organizations that rely on CloudFormation can proactively reduce cloud costs before each…

Large enterprises struggle to scale FinOps governance. With tens of thousands of applications spread across business units, product families, and thousands of engineers, cost issues are scattered across code repos; making it nearly impossible to see the full picture. Today we’re introducing Issue Explorer – enterprise reporting that gives FinOps and business leaders clear visibility into where…

A key question at this year’s FinOpsX conference was: what does “AI for FinOps” really mean? Today, we’re answering that with the general availability of AutoFix pull requests for GitHub. Infracost doesn’t just prevent new cost issues anymore, it now opens AI-powered pull requests to fix existing ones. Engineers can remediate issues 10x faster and at scale,…

Since launching Infracost in 2021, we’ve been pulled by engineers who all want to Shift FinOps Left. Today, we’re taking a major leap forward. We’re announcing five powerful new features designed to help engineers proactively find and fix cloud cost issues, including bringing rightsizing recommendations into the workflow. These features lay the foundation for a new…

Happy New Year 🎉 We’re excited to kick off 2025 with the latest Infracost updates!  New Graviton policies for EC2, ECS and Lambda Last year, many enterprises used Infracost’s Graviton policies for RDS, ElastiCache, and OpenSearch to achieve significant cost savings. Migrating these managed AWS services to Graviton proved to be low-effort and low-risk, thanks to AWS’…

With autumn in full swing, we’re excited to bring you the latest Infracost updates! If you are attending the FinOps X conference in Barcelona, stop by the Infracost booth to grab a pair of Infracost socks and see what Shifting FinOps Left actually looks like in a live demo. Introducing Issue Explorer We wrote a…

Happy August! Summer may be in full swing, but our team has been hard at work in between recharging on vacations. I’m excited to announce the release of major product updates all focused on helping enterprises with FinOps tagging 🏷️ API for ServiceNow integration Large enterprises are familiar with this FinOps challenge: cloud resources need…

Happy July! We’re excited to share a key insight from the recent FinOpsX conference: FinOps has shifted left 🚀 This approach, which we’ve championed since 2021, integrates cloud costs and best practices into the development workflow before deployment. Our new ebook explains how shifting left saves engineering time and prevents cost overruns—check it out! Improved Pull Request…