[kyptin]

Nice! I see your guide here: http://taprun.com/pricing/ . I'll check it out, thanks!

I think the Github vs. Bitbucket question is a proxy that I can easily translate into my scenario. So in that case, what are the relevant factors?

[arghbleargh]

It would definitely help if you said more about what your product is. But generally speaking, from the customer's perspective, you should charge for the thing that the customer can predict better up-front, so that it's easier for them to assess your value proposition. You might want to take into account your own costs as well, if applicable.

The interesting thing about Github vs. Bitbucket is that both usage patterns can make sense depending on the project and user. For individuals, you might have a lot of repositories for small projects that end up abandoned after a while. For teams, it might make more sense to have a flexible headcount.

[kyptin]

Ah, very good point, to consider what is easier for the customer to predict. I had not considered that. Thank you!