jbauer opened 8 months ago
|
|||||
I do not have plan to provide different tiers, which is pretty hard to manage. I also checked other products and can hardly find any providing different pricing model based on user types. Some of them do provide different feature sets. For instance GitLab has premium costs for $29 per user/month, and $99 per user/month. And this price is the same for self-managed users. However OneDev's $6 per user/month is just a handful of GitLab's lowest pricing. And you can expect much stronger support from OneDev. Also if you do plan to use OneDev EE for many users, I can give a good discount based on user volume. |
|||||
Correct: GitLab has premium edition costs for $29 per user/month, and enterprise edtion costs for $99 per user/month. |
|||||
Robin Shen changed confidential 8 months ago
|
|||||
Robin Shen changed confidential 8 months ago
|
|||||
I guess user types somehow is the same as feature sets. The most common thing are people not working with code vs people working with code. It is fine if you stick to the current model, I just wanted to explore if there are any future plans that might not be provided now because OneDev needs to be updated first. How does the current pricing work if any of
has been activated? Do we manually have to keep track of the amount of users active because it affects the remaining subscription period? Imagine a company wants to use OneDev for IT but also give everyone in the company the possibility to use issues / kanban if they want. So self-registration / deletion might be active for simplicity and the company buys 5 developer seats as a minimum amount. Can remaining subscription length drop below 1 month and cause OneDev to stop working? |
|||||
@jbauer OneDev deducts one day of usage for all named users in system every day, including users added via self-registering, SSO, LDAP, but not including anonymous users. So the remaining user month will be adjusted dynamically as user is being added/removed in system. |
|||||
OneDev will not stop working even if user-months has been used out. Only that EE features are no longer available. If you distribute projects to multiple nodes, they will continue to work, only that new projects can not be distributed. |
|||||
jbauer changed state to 'Closed' 8 months ago
|
|||||
I see. Thanks for your feedback. Closing this issue for now. |
|||||
@jbauer just want to let you know that 9.2.1 adds the concept of guest users which are excluded from user month calculation and are free for EE edition. Guest users can create issues and add comments to authorized projects, but can not push code, run build or do other things modifying the system. For users created via LDAP, SSO, self sign-up, and service desk, administrator can decide whether or not to create the user as guest, to better control permissions as well as managing available user-months more predicably for EE edition. |
|||||
@robin Thanks for the information. Sounds great and should definitely help selling the EE edition if you have users that are mostly idle and only care about issues. |
|||||
@robin Just to confirm that I understand the EE pricing structure, we are only charged for developer users, not for end-users or support-related staff who would only need to create and review issue tickets? Just to be clear, by "developer user", I'm referring to a source code contributor, someone that can make commits. Am I correct in my understanding? |
|||||
@exclusionaryparticle your understanding is almost correct, except that it also charges for users able to run build. To be accurate, it charges for non-guest users. And guest users are defined here: |
Type |
Question
|
Priority |
Normal
|
Assignee | |
Labels |
No labels
|
Do you plan to provide different tiers of paid users or maybe a second model based on feature sets?
For example I have the following type of users:
So these kind of users are definitely not equal yet cost the same. Some are not even persons.