LPM.dev Registry and Pro
What LPM.dev Registry adds to LPM CLI: private packages, Pool and Marketplace distribution, Free vs Pro limits, and hosted platform features.
lpm is the LPM CLI command. LPM.dev Registry is the hosted registry and platform layer behind the @lpm.dev/* scope.
LPM CLI is registry-agnostic. It installs npm packages from npm, honors private registries in .npmrc, and only routes @lpm.dev/* packages through LPM.dev Registry by default. Use LPM.dev Registry when you want hosted private packages, Swift packages, Pool distribution, Marketplace sales, or the cloud-backed developer platform features.
What LPM.dev Registry adds
lpm login
lpm publishPublishing to LPM.dev Registry 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 accepted upload receives baseline Registry processing:
- Archive, manifest, and package-configuration validation.
- Quality scoring for JavaScript and Swift packages.
- OSV vulnerability scanning where dependency data is available.
- Dependency and access checks for the package's selected distribution mode.
Pool and Marketplace versions also enter public publication review. Their new versions remain pending while LPM.dev Registry performs the public-only AI review, reviews any bundled Agent Skills, and prepares public package metadata. Private versions do not wait for that public review and remain available only to authorized users.
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 Registry 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% |
| Firewall for public npm packages | - | Included |
| Local env storage | 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 |
| Concurrent tunnels | 1 | 3 |
| Included tunnel requests | 20,000/UTC month | 100,000/billing period |
| Account-wide tunnel rate | 4,000/min | 20,000/min |
| Per visitor IP within the account | 600/min | 600/min |
| Tunnel requests beyond allowance | Hard stop | $1/100,000, proportional |
| Claimed tunnel domains | - | 3 |
| Tunnel auth | - | Included |
| Webhooks, analytics, audit logs | - | Included |
Pro tunnel overage is enabled by default. Turn it off from the personal tunnel dashboard when you prefer a hard stop at 100,000 requests. There is no retroactive billing; paid usage follows the active Stripe subscription period.
Organizations use separate org billing: $8 per seat, unlimited private packages, 5 GB package storage per seat, 25 GB remote cache per seat, 10 concurrent tunnels, and 10 claimed tunnel domains. When a tunnel usage period is first opened, each billed Stripe seat in that snapshot adds 100,000 included requests and 20,000 requests/minute to the organization account for the rest of the period. Organization overage uses the same proportional $1/100,000 rate and default-on toggle.
Tunnel request limits are account-wide. Three Pro tunnels share one 100,000-request allowance; the allowance is not multiplied by the number of tunnels or domains. See Tunneling for exactly what counts.
The Pool
The Pool is LPM.dev Registry'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.dev Registry 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 CLI routes npm, private registries, and LPM.dev Registry.
lpm publish- publish JavaScript and Swift packages.lpm pool- view Pool revenue stats from the CLI.- Environment variables and secrets - 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.