Infracost helps developers and DevOps engineers get cost estimates from their IaC (Infrastructure as Code).
Here’s an example of it running:
The complexity of cloud costs keeps increasing – When we were building PlanForCloud in 2012 AWS had just hit 10,000 different pricing points for their services – now there are over 300,000.
We found existing tools fit in too late in the process and are not aimed at the people in control of the infrastructure. It’s difficult to get cost estimations when you are building and deploying your services, which often leads to bill shock and no easy way to track down these costs. So we wanted to build a CLI tool that can plug into your existing development and operations processes and bring cost visibility to the engineers.
Update 25 Nov 2020 : We have now added initial support for Google cloud.
We also want to go beyond just the baseline costs of infrastructure – data transfer costs and other usage-based costs can often be a significant portion of a cloud bill, and are also the hardest to predict and track down. If you have any ideas about the best way to handle these then please reach out to me on Twitter.
Infracost is open source, you can check it out at https://github.com/infracost/infracost.