LPM.dev and Pro
What lpm.dev adds to the CLI: private packages, Pool and Marketplace distribution, Free vs Pro limits, and hosted platform features.
lpm is the CLI. lpm.dev is the hosted registry and platform layer behind the @lpm.dev/* scope.
The CLI is registry-agnostic. It installs npm packages from npm, honors private registries in .npmrc, and only routes @lpm.dev/* packages through lpm.dev by default. Use lpm.dev when you want hosted private packages, Swift packages, Pool distribution, Marketplace sales, or the cloud-backed developer platform features.
What lpm.dev adds
lpm login
lpm publishPublishing to lpm.dev creates a private package by default. From there, you can keep it private for yourself or your team, switch it to Pool, or sell it through the Marketplace.
Every publish goes through registry-side checks:
- Quality scoring for JavaScript, Swift, and XCFramework packages.
- OSV vulnerability scanning.
- AI security and quality analysis.
- Generated package metadata, API docs, and AI-readable package context.
- Access control for private, Pool, and Marketplace installs.
Distribution modes
| Mode | Who can install | Best fit |
|---|---|---|
| Private | You, or members of the owning organization | Internal packages, paid-client work, early versions |
| Pool | Pool subscribers | Broadly useful packages that should earn from real usage |
| Marketplace | License owners | Commercial packages where you set the price |
All lpm.dev packages start private. Pool and Marketplace are explicit per-package choices.
Free vs Pro
| Capability | Free | Pro |
|---|---|---|
| Price | $0 | $8/mo |
| Private packages | 2 | Unlimited |
| Package storage | 100 MB | 5 GB |
| Marketplace platform fee | 15% | 10% |
| Local env vault | Included | Included |
| Cloud env sync | - | Included |
| Platform env push and OIDC CI pulls | - | Included |
| Remote task cache | - | 25 GB |
| Ephemeral tunnel URLs | Included, 1-hour sessions | Included |
| Claimed tunnel domains | - | 3 |
| Tunnel auth | - | Included |
| Webhooks, analytics, audit logs | - | Included |
Organizations use separate org billing: $8 per seat, unlimited private packages, 5 GB package storage per seat, 25 GB remote cache per seat, and 10 claimed tunnel domains.
The Pool
The Pool is LPM's usage-based funding model for packages that should be broadly available but still economically sustainable. Subscribers pay one flat monthly fee for access to Pool packages. LPM distributes the author share to the packages those subscribers actually install, then follows the dependency tree with depth weighting, so maintainers of low-level transitive dependencies can earn when real projects depend on their work.
That matters more in the AI era: packages are increasingly discovered and installed by tools, agents, and automated workflows, not by humans clicking donation links. The Pool moves funding closer to the place where value is actually used: the install graph. It is not a complete answer to open source funding, but it is a more structural one than donations, sponsorship buttons, or one-off marketplace sales alone.
Pool access is separate from Pro. Pro unlocks creator and platform features. Pool is a $12/mo subscription that unlocks access to Pool packages and funds authors through usage-based revenue sharing.
Marketplace
Marketplace packages are for direct sales. You set the price, buyers receive a license, and only license owners can install the package. Free publishers pay a 15% platform fee; Pro and Org publishers pay 10%.
Use Marketplace for commercial or proprietary packages. Use Pool when the package benefits from broad access and usage-based revenue.
See also
- Registries - how LPM routes npm, private registries, and lpm.dev.
lpm publish- publish JavaScript, Swift, and XCFramework packages.lpm pool- view Pool revenue stats from the CLI.- Secrets vault - local secrets, cloud sync, and platform pushes.
- Tunneling - ephemeral URLs, claimed domains, auth, and webhook capture.
- lpm.dev pricing - current billing and plan details.
- The Pool - the full Pool model.