Hacker News Reader

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.

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

its already normal right ? Github Pipelines or CI/CD bill this way. Actually the best example of this abstraction was Heroku with its "dynos".

Yea! Very true. and exactly as you say, CI/CD is going that way as well and we fit in there, so it would make sense for our pricing to fit that.

Reply on news.ycombinator.com