New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: billable Add-ons #19526
Comments
hi I think you can implement it by EditionFeature https://docs.abp.io/en/abp/latest/Features |
Thx, I will re-read the docs carefully. However, as I understand it might not be possible. I might missunderstand something. Example of I what I'd like to implement: SELECT YOUR PLAN: SELECT ADD-ONS: If I would use Edition I would need to make editions for all these combinations of base plan + different sets of add-ons. Is that correct? I think additionally, maybe, could be to dynamically create editions. For example Edition_Tenant123 that is based on based edition A + 3 additional users + data encryption. But, the problem I see is what if the base edition gets new features or old ones are removed? I know many apps only have plans like: free,plus,pro,enterprise, but in my case I have lots of features that cost money to produce so the plans would be expensive if pro plan must include all of them. In the above example, ideally user could even take free base plan and add just monthly backups+encryption for a small amount some important files, but he does not need lots of storage of Edition C |
hi An The framework will only check if the tenant has a feature.
|
Alright, got it. I will double-check this approach and close or add comment soon. Do you have hints on where to look to update the billing and price per addon? I just add directly to stripe? |
hi I'm not familiar with But we do have a payment module. |
Hi @torronen, Abp provides a dynamic features system supported by value providers. To achieve the use case you mentioned, you can implement it yourself by using edition and tenant providers and no need to define a new provider. You need to use edition provider value for plan/edition and tenant value for add-on. My approach of implementing it:
|
Is there an existing issue for this?
Is your feature request related to a problem? Please describe the problem.
I am trying to sell additional add-ons, such as extra user, additional storage, feature A,b,c, but currently I am limited in creating a set of predefined plans.
Describe the solution you'd like
I would like to see an option create "add-ons" in additions to plans. The add-ons would typically allow access to a specific module. I think the only difference is selling additional user licenses. Especially the number of user seats should be a common need I believe.
In some future version the "add-on" might override or increase the limit of settings in the plan. However, I think this could be considered separately.
Additional context
No response
The text was updated successfully, but these errors were encountered: