undefined | Better HN

0 pointssandGorgon5y ago0 comments

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.

0 comments

hkh5y ago

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

sandGorgonOP5y ago

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

hkh5y ago

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.

j / k navigate · click thread line to collapse

0 pointssandGorgon5y ago0 comments

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.

0 comments

hkh5y ago

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

sandGorgonOP5y ago

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

hkh5y ago

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.

j / k navigate · click thread line to collapse