Hello,
I plan to release my plugin in the EAP channel(free available) in the near future. Within the next year the plan is to convert the plugin to a paid plugin and monetize it. Are there any points to consider when releasing to the EAP channel so that a later conversion to a paid plugin works without problems?
How would the conversion generally take place?
As I understand it, I would add special parameters such as Product Code( How to add required parameters for paid plugins | JetBrains Marketplace Documentation) at this point to convert the plugin.
Would it also be possible to release the plugin as a paid plugin now, which is freely available since it was released in the EAP channel?
Hello,
If you’re planning to monetize your plugin in the future, I recommend publishing it under an Organization vendor type. This is a required step for all paid authors, so it makes sense to start with it from the beginning.
Additionally, clearly state in your documentation (which you can add as custom pages to your plugin) or on the plugin page itself that the plugin is currently free but may become paid in the future. This should help set expectations early and avoids confusion for your users.
It’s also a good idea to think about an end-user agreement in advance to prevent any copyright issues. You might even consider releasing the plugin under a closed license from the start if monetization is your long-term goal.
As for the conversion process:
Hope this helps!
Thanks a lot - that definitely helps 
I was thinking to use an end user agreement from the beginning. I don’t know a lot about the difference between EULA and closed licenses - will have to do some research about that. Is it recommended to use a closed license when selling plugins on the marketplace?
I’d say using a closed license is pretty common when selling plugins on the marketplace. But we also have some plugins that are open-source, so both options are possible.
Oh ok - I think that was a misunderstanding. My plugin will definitely be closed source from the beginning. I was just confused about the difference between a closed source license and an EULA.
Anyway I did some research and checked also how other plugins handle that issue and seems like a lot of paid plugins use the Standard EULA Jetbrains(End User License Agreement - EULA | JetBrains Marketplace Documentation) and adapt it to their need. I think I will also go this way.
Did I miss something, or would this be a sufficient way to go forward with this topic?
1 Like
Yes, using a EULA should be sufficient. I don’t have anything further to add here!
1 Like