Hi all, Hassan here - one of the founders of Infracost.
Infracost sits in Github / GitLab etc, and when an engineer makes a infrastructure code change, we show them how much the code will cost to run on cloud before they merge it. It also shows them how they can optimize their code for costs.
Cloud costs are very unfair in the way they are priced - we track prices from AWS, Azure and GCP, and from these three we track 4 million price points!! Why do we expect engineers will just know the cost of cloud resources? We need tools!
Would love your feedback, that's the only way we can keep building in the right direction. <3
This is good - I just signed up and tried it out. I liked that I could take a picture and draw on the picture to highlight something to the team! It's like loom but for physical work environments like workshops!
hahaha love it - it'll keep evolving, and get more interesting for sure. I just think back to Dev and Ops, and how it went from a culture to a job title; testing was another one.
Hi, I think the key issue with both the Azure policy, and the Amazon services is that they only work after a pull request has been merged. Then the build fails, and the engineer has to come back to their code, make a new Pull Request and then send it again, till it passes.
That's the feedback we got from users, so with Infracost, the Pull Request itself tells the engineer what needs to be done, along with exact code line numbers etc before going any further, so everything is fixed within the same pull request. Also, it works across all cloud providers, so FinOps can set central tags in a uniform manner no matter where the engineers are launching resources.
Vantage is awesome - I've talked with Ben (their CEO) a few times. There are a lot of tools that start from the cloud bills, and give you visibility of everything (Vantage, Cloudability, Cloud Health Tech, Flexera etc) - all of these tools are reactive in nature as they start from the cloud bills. Infracost sits where your code sits, and therefore it can be proactive; before anything is launched and costs money, it'll tell you how much it is going to cost. So if you have a budget of $1K, and you try to launch a 24xl instance, it'll tell you that you budget will be blown, before you've launched the resource. Making it all proactive.
Bingo - so Infracost will tell you before you launch anything how much it'll cost. Now scale that to a few thousand developers across a large company, and it's very impactful.
Backfilling tags works, but the issue is if Terraform isn't updated, it causes drift - it's much better to fix it at the root, so that's what Infracost helps with
Yep, for sure! It's on the roadmap. We are friends with the folks at Pulumi too. Love what they are building, so hopefully we will get some bandwidth and add support. And Cloud Formation too. Azure ARM ... haha there is a lot more to build :)
Wonder how long until we get our first request to add support for this to infracost https://github.com/infracost/infracost? At least the price list looks a lot simpler than AWS / Azure / GCP - more like UpCloud! Though honestly, if it starts to work, I'm sure the number of prices/services will grow exponentially.
reply