[Argorak]

Github (SaaS) is not f(team size), it is f(projects). You can have as many users as you want and the price will stay the same, if you don't cross certain repository thresholds.

Github Enterprise is f(team size)

CircleCI is also f(usage), you can decide to have less capacity. (Although, in the case of CircleCI, more developers hopefully maps to more tests, so indirectly, it is f(team size))

[mmahemoff]

I realise some of those services aren't directly f(team size), but as a general rule of thumb, f(projects) is a proxy for f(team size).

Likewise, your CircleCI bill is going to be higher with more team members as you mention.

That's all very imprecise, it's not like there will be a direct linear relationship. But close enough compared to Mixpanel etc which scale with f(users) or f(transactions).

[Argorak]

That depends highly on your team. If I have 20 support people with access to GH, but no coding work, the cost factor is not the team size. On GH enterprise, that's another kind of math. There's certainly also projects that just run in one repos for ages (long live the monolith).

Also, with GH, I can always choose to take a project off GH and archive it. That wouldn't make sense if it were user-billed.