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…
Happy June! It’s time for another Infracost update, but before that, we’ve got some exciting news: we’ve got a booth at the FinOpsX conference in San Diego next week. My co-founder (and brother!), Hassan, posted some great pics from last year’s conference, let us know if you/your team is going to be there 🥳 Enterprise Data…
Happy May! As the sun gears up for its annual performance upgrade (it’s still cold in Scotland) and temperatures start to climb, it’s time for another Infracost update – let’s dive in. Usage Costs We’ve redesigned Infracost pull request comments to differentiate Baseline costs and Usage costs: Large enterprises have thousands of code repos, so…
Happy spring equinox! In the past few months, we’ve been heads-down, making major improvements to the Infracost CLI, Infracost Cloud, and our CI/CD integrations to support large enterprises with thousands of code repos and complex workflows. Faster and Deeper Code Parser Infracost is now used by over 3,000 companies 🚀 Large enterprises have repos with…
In 2023, cloud cost complexity kept increasing, and many new cloud cost management tools were launched. We also saw existing players launch new features and capabilities to help their customers reduce cloud costs, improve their cloud budget, and eliminate cloud waste. The cloud providers released new capabilities, AWS Cost Explorer released a whole set of new features…
Launching the new FinOps policy checker Today, we’re very excited to announce a new FinOps policies capability for Infracost Cloud. You can now check for FinOps best practices directly in engineering workflows before infrastructure code has been deployed. This has many benefits: Helping engineers with FinOps Pop quiz: which of the 46 out of the…
We released major improvements to the tagging policies feature to simplify identifying and fixing tagging issues. We also re-designed the Infracost report emails to summarize key changes across your repos. The CLI also got many bug fixes and big performance improvements. Log in to Infracost Cloud or upgrade to CLI version v0.10.29 to use the new features. Tagging policy…
New feature announcement: FinOps tags can now be checked directly in the engineering workflow in CI/CD, before anything goes to production, by shifting them left. Both the key and value can be verified. If the tagging policy has not been followed, the engineer will be notified and the code pull request can be blocked until…