New Gitlab Product Subscription Model

I think the new tiers make some sense. Before there was no clear distinction between 4€ and 19€ feature wise – at least it seemed rather arbitrary.

Now the distinction on a quick glance over the features seems to be (rather broad, a few features skipped):

  • Premium: Project management features (ie a jira clone for better or worse) and high availability
  • Ultimate: Bad-ass security/dev(ops) features

In the longrun I am not sure if this categorizing for every small feature makes sense. Wouldn’t it make more sense to have a base user pricing (dunno 4€/month) and add feature bundles? This way you’d have broader categories and maybe a clear distinction of what is what. The feature bundles shouldn’t necessarily all depend on the user count and might have a fixed pricing.

Taking my categorization from above, for one customer I’d like “project management” & “security” features, I do not need HA (interestingly this is something many people can live without). To make the choice even harder is that I’d need to pay 99€ for every user just to get security scanning. Paying 99€ for every user even if quite a few users are only managing tickets is a hard sell. Lets be honest, not everyone in a company that has access to the “Service Desk” will even know what those features do but they are still paying for it.

I guess in the end I’d like more flexibility. Ie be able to get users with only reporter privileges at a lower price…

Not sure if that all makes sense, but I think I’d like to see a bit more flexibility for smaller companies to get ultimate features.

I’d love to hear your thoughts on my ramblings.

5 Likes