Infracost
Shifting cloud costs left directly into CI/CD before code is merged.
Infracost shifts cloud costs left and makes FinOps proactive. It sits in the engineering workflow (CI/CD), and shows the cost impact of code changes (IaC) before the code is shipped to production. This catches costly mistakes before any money has been spent. It also checks to make sure all resources are tagged with your set tagging policy, and runs checks on the code against our FinOps policy packs, ensuring best practices are followed (e.g. GP2 volumes should be GP3). This creates a cost-aware engineering culture.
Jobs at Infracost
Active Founders
Hassan Khajeh-Hosseini
Currently working on making it easier for developers to understand how their code changes are going to affect their cloud bills before launching resources. Prior to that, founded other startups and took them through acquisitions. I like to surf, snowboard, skydive and eat! I make a vlog now and then on YouTube :)
Ali Khajeh-Hosseini
Co-founder of Infracost.io - helping engineering teams reduce their cloud costs with open source tools. I did my PhD looking at cloud costs ~10 years ago. I take my mind off work by heading into the mountains, playing football (soccer, not the other kind) and volleyball.
Alistair Scott
Co-founder of Infracost. Developer at heart. Love to ski and cook. Currently on a mission to cook a dish from every country in the world.
Hear from the founders
How did your company get started? (i.e., How did the founders meet? How did you come up with the idea? How did you decide to be a founder?)
In our first startup, we built one of the first cloud cost management products, which was later acquired and is now part of the Flexera One product. That was back in 2012. The cloud cost management space hasn’t changed in 10 years. Every company still starts from the bills, meaning they look for issues and react. With Infracost, we wanted to apply the shift left philisophy, which worked great is security to cloud costs. That’s what Infracost has become - we Shift FinOps Left into the engineering workflow.
How did you decide to apply to Y Combinator? What was your experience applying, going through the batch, and fundraising at demo day?
We applied to YC back in 2012. Back then there was 10,000 prices from AWS. Since then, cloud costs have become very complex, and we now track nearly 4 million prices from AWS, Azure and GCP. YC was fantastic back then (we interviewed with PG), and it was even better when we got accepted into the W21 batch!
How have you kept in touch with the YC community and continued to use YC resources & programs since the batch ended?
Our YC group keeps a monthly check-in going. It has been great to meetup on zoom once a month to talk about any main issues, questions, learnings that any of the companies have had.
What is the core problem you are solving? Why is this a big problem? What made you decide to work on it?
Every single cloud cost management product out there is reactive in nature. Infracost is the only FinOps product that is designed with engineers in mind, making it easy for them to ship code fast, and keep within FinOps best practices before they merge their code. Things like:* Ensuring the right cloud tags are set* Ensuring FinOps best practices are followed* Budgets are checked before money has been spent* Data is integrated into Jira with our FinOps for Jira appAll within the engineering workflow (directly in a GitHub PR, or GitLab MR).