Why GitHub’s pricing model stinks (for us)
I love GitHub. I use it for websites, I use it for OSS, I use it for a dump of blog post code. I love the website, I love the tools, I love the apps. I love that it’s in the cloud and I can get to it from anywhere with an internet connection.
However, the pricing model stinks for us at Headspring.
GitHub prices plans based on where it considers the value to be: private repositories. Paid plans have unlimited collaborators and unlimited public repositories. The plan you pick defines how many private repositories you have. Additionally, business plans let you define unlimited teams (but still are priced based on number of private repositories:
All very reasonable prices, but unfortunately, just don’t make sense for us at Headspring. As much as I like pull requests and GitHub issues, pricing based on what is for us a very unpredictable measure (# of private repositories) completely prevents us from considering GitHub. Since we’re a consulting company, on many projects, it’s difficult to track and predict how many private repositories we have going at any given time.
Repositories aren’t our asset, our people are. We can easily predict how many employees we have, so we’d much, much rather just pay by the user. It’s the pricing model of many of our other cloud services (but not all).
Bitbucket, on the other hand, gives us 100% predictable pricing, based on users:
We get unlimited private repositories for this plan, and a very predictable monthly cost. We did a quick price comparison, but it’s really hard to compare apples to oranges here when we really can’t know how many users we have.
I see this in quite a few SaaS providers, having a rigid pricing model on only one axis. Often it’s the pricing model, and not the overall price, that dictates what services we can use. Having a flexible pricing model would allow GitHub (and other companies with similar models) to reach a broader set of companies that simply predict costs on a different measure.
I understand that a lot of teams have more predictability on repositories (and not people), and GitHub makes more sense for them. However, I don’t ever really want the decision on whether or not to create a GitHub repository (or BaseCamp project for that matter) to come down to “are we at our limit?”. I see people sitting around, and they’re easy to count.
So while we can’t use GitHub right now, I’d love to in the future if their pricing model ever matched how we can truly predict costs.