Beta Briefing
PayDevs provides a private registry for JavaScript packages - keeping your project open source with a closed package. Users with a dependency to your package now have to pay for the convenience of downloading the compiled package - by paying a flat rate of $1 per month for private users and $150 for corporate users to access the entire registry.
To keep things fair and simple, we make monthly payouts based on the number of users (i.e. not downloads) that we count for your library. We provide and operate the network of closed registries for your package and handle the monetization as a service - without any cost for you!
How can you help?
During the Beta we need help understanding different publishing processes maintainer have, what features you would additionally need, and test the technical system. If you want to help please:
- Register and confirm your email adresses
- Login to our NPM registry (e.g.,
npm set registry https://npm.paydevs.com/ && npm login) - Publish a new version of your package (e.g.,
npm publish --registry https://npm.paydevs.com/) - Unpublish your new version (e.g.,
npm unpublish --registry https://npm.paydevs.com/) - Logoff from PayDevs - or you might use npm.paydevs.com unintentionally (e.g.,
npm set registry https://registry.npmjs.org && npm login). However, you can always stay with paydevs and test it more - we have an uplink to npmjs.org so every package in npmjs.org is also available in our registry.
We would also be very interested to hear if you have a special publishing process that goes beyond "npm publish", and if publishing to another registry would change or disrupt your CI/CD workflow - and why.
What's in it for you?
As an early adopter, you can help shape and optimize the system and be among the first to participate in the payouts during the public beta. As for the potential income, you can look at our calculations in the Maintainer Introduction.