The Ecosystem Has No Economic Layer
Maintainers Earn Nothing
The developer behind Masonry (the layout engine Pinterest was built on) had to start an entire company just to earn from his own code. Donation buttons didn't work. Most open source developers still earn nothing.
Burnout Leads to Backdoors
The xz backdoor happened because an unpaid, burned-out maintainer was pressured into handing over access. Open source maintainers build critical infrastructure with zero financial return. That's not sustainable.
No Standard Way to Sell Code
Developers try Flattr, PayPal, Patreon, custom licensing portals. Buyers deal with confusing install flows. There's no npm install for paid packages. Until now.
For Package Authors
Turn real-world usage into passive monthly income.
Sustainable Dependencies
Open source is a tree of dependencies. LPM ensures that the people who build the "invisible" libraries your favorite packages rely on also get paid. When you install a package, your monthly share is distributed down the dependency chain using Depth Multipliers. This ensures that the entire stack not just the top-level package is financially sustainable.
Depth 0 earns 100%, Depth 1 earns 70%, Depth 2 earns 49%, and Depth 3 earns 34%. This rewards packages people intentionally install while still compensating foundational libraries.
Your Users. Your Revenue.
Each subscriber's $9.60 stays within their own dependency tree. If they use your code, you get paid - period.
In the 'Global Pro-Rata' model, niche tools are ignored in favor of superstars. LPM flips the script: your share of a subscriber's monthly fee is calculated purely on their local installs. This ensures that essential, deep-stack libraries are rewarded for the value they provide to their actual users, not their global download count.
Built-In Fair Play
Same-Owner Weighting
Dependencies owned by the same author receive 30% weight. Revenue goes to packages people actually depend on, not self-referencing trees.
Real Usage Only
Packages need at least 2 unique installers before they earn Pool weight. No gaming with fake installs.
Depth Limit
Dependency tracking stops at depth 4. Deep nesting doesn't mean more revenue.
For Subscribers
One subscription. Unlimited packages. Fairer distribution.
Unlimited Installs, One Flat Fee
Subscribe once for $12/month and install any package that has opted into the Pool. No checkout flows, no license keys, no friction.
Unlimited Access
Install as many Pool packages as you need. No limits, no overage charges.
Same Workflow
Just run lpm install like normal. Pool access is transparent.
Every Package, One Price
No per-package purchases. Your subscription covers the entire Pool. Every package, every update.
Fund Real Work
Every install you run sends revenue directly to the developer who built it. Not charity. Compensation.
Frequently Asked Questions
Is opting into the Pool permanent?
Yes. Once a package is set to Pool distribution, it cannot be changed back to private or marketplace. This ensures subscribers can rely on long-term access.
When do authors get paid?
Revenue is calculated monthly and paid out on the 5th of the following month, with a minimum payout threshold of $10.00. Earnings below the threshold roll over to the next period.
How is Pool different from the Marketplace?
Marketplace packages are sold individually with per-seat licensing and one-time or recurring purchases. Pool packages are accessed via a single monthly subscription. Marketplace gives authors full pricing control; Pool provides passive income from aggregate usage.
What happens if I subscribe but don't install anything?
Your $9.60 author share is distributed equally among all Pool packages, ensuring authors still benefit even from inactive subscribers.
Can organizations subscribe to the Pool?
Yes. Organizations pay $12/month per seat. Each org member gets unlimited Pool access, and the revenue distribution works the same way as personal subscriptions.
Why can't authors switch a package back to Private after joining the Pool?
Because your subscribers depend on it. Once a package is in the Pool, existing consumers have added it to their projects. Switching back would break their builds. The lock is a trust guarantee: subscribers can rely on every Pool package staying available.
