I have built a Java library, which I am planning to sell. It will be used as a project's dependency and most users would use it with their build tools such as Maven, Gradle, etc. I wanted to know if somebody is already doing something similar and what selling model they followed. I am thinking:
- Per-user pricing: Based on the number of users or developers using the library. The catch is here, since it will be used as a dependency, the team can purchase a single license and several users can utilize the API.
- Project-based pricing: Based on the number of projects the library will be used in. This is probably more straight-forward in this scenario and, assuming the sale is made for 1-5 projects at a fixed cost, it is easier for the end-customer to understand how the installations work.
To me, project-based pricing seems a little more sensible and easier to understand from the user's perspective. However, I wanted to see if there are better models out there that the community uses in such scenarios.