Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Launch HN: Infracost (YC W21) – open-source cloud cost estimator

news.ycombinator.com

Post reply on HN
Print view View original

11–20 of 56 posts

Re: Launch HN: Infracost (YC W21) – open-source cloud cost estimator

#11

Post by hkh »

sandGorgon wrote: post #10

this is very cool! pricing will be key here - you need to figure out some per-repo, per-pull request pricing.

Yea, we will have to strike a balance so we don't contribute to the cost complexity too! haha

We talked about if we should approach it with user-based pricing, or usage-based pricing. Do you think usage based pricing would be preferred here? Or should we keep it in a way that users can run it as many times as they like?

Our current thinking is buyer-based open core with per user pricing, maybe like SYNK.

Re: Launch HN: Infracost (YC W21) – open-source cloud cost estimator

#12

Post by aliscott »

zegl wrote: post #9

Congratulations on the launch! Keeping track of our AWS costs and attributing those costs to each team was a huge pain at my previous job, a tool like this would have come in real handy then.

Thanks! Yeah we think that making the costs visible to engineers will help remove the pain here. We're seeing some big companies like Netflix, Slack and Segment implement dev-focussed approaches to cost-management and think this will become more of a standard in the future.

Re: Launch HN: Infracost (YC W21) – open-source cloud cost estimator

#13

Post by sandGorgon »

hkh wrote: post #11
sandGorgon wrote: post #10

this is very cool! pricing will be key here - you need to figure out some per-repo, per-pull request pricing.

Yea, we will have to strike a balance so we don't contribute to the cost complexity too! haha We talked about if we should approach it with user-based pricing, or usage-based pricing. Do you think usage based pricing would be preferred here? Or should we keep it in a way that users can run it as many times as they like? Our current thinking is buyer-based open core with per user pricing, maybe like SYNK.

per-user is tricky. I can have a super duper complex terraform repo with just 1 user and a 10 liner repo with 5 people.

you should do a "build minutes" kind of pricing. or the number of times i triggered a re-run.

From your perspective, it can only be better than per-user, since the number of commits will be minimally proportional to the number of users.

Re: Launch HN: Infracost (YC W21) – open-source cloud cost estimator

#14

Post by tim775 »

This makes a lot of sense. I've been telling people building something in the cloud is like trying to get healthcare: You can't make good decisions up front because it's impossible to figure what something will cost and somebody else ends up paying the bill anyway.

Re: Launch HN: Infracost (YC W21) – open-source cloud cost estimator

#15

Post by hkh »

sandGorgon wrote: post #13
hkh wrote: post #11

Earlier quoted context omitted.

Yea, we will have to strike a balance so we don't contribute to the cost complexity too! haha We talked about if we should approach it with user-based pricing, or usage-based pricing. Do you think usage based pricing would be preferred here? Or should we keep it in a way that users can run it as many times as they like? Our current thinking is buyer-based open core with per user pricing, maybe like SYNK.

per-user is tricky. I can have a super duper complex terraform repo with just 1 user and a 10 liner repo with 5 people. you should do a "build minutes" kind of pricing. or the number of times i triggered a re-run. From your perspective, it can only be better than per-user, since the number of commits will be minimally proportional to the number of users.

Good point. I wonder as the world goes more towards serveless, if users will slowly become used to per call (or maybe per comment, or as you say per re-run) pricing

Re: Launch HN: Infracost (YC W21) – open-source cloud cost estimator

#18

Post by akh »

tim775 wrote: post #14

This makes a lot of sense. I've been telling people building something in the cloud is like trying to get healthcare: You can't make good decisions up front because it's impossible to figure what something will cost and somebody else ends up paying the bill anyway.

And getting cloud-bill shock is like going to emergency department :D
Post reply on HN