7 ms·
> Free is for a single developer, with the purchasing decision led by that same person > Premium is for team (s) usage, with the purchasing decision led by one
by adduc 5y ago
> Free is for a single developer, with the purchasing decision led by that same person
> Premium is for team (s) usage, with the purchasing decision led by one or more Directors
Doesn't this conflict with the stewardship promise that "The open source codebase will have all the features that are essential to running a large 'forge' with public and private repositories"?
- john_cogs 5y agoThanks for the question. I shared it with @sytse and he's putting some thought into it.
- john_cogs 5y agoWhen the tiering of a feature is being evaluated, the stewardship promise (https://about.gitlab.com/company/stewardship/#promises https://about.gitlab.com/company/stewardship/#promises) will override the guidance on our pricing page (https://about.gitlab.com/company/pricing/#buyer-based-tiering-clarification https://about.gitlab.com/company/pricing/#buyer-based-tierin...). Thanks again for the question. Edit - I've created an MR to document this on our pricing model page: https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/78196 https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_request...