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, make it Free for anyone to install, add it to Pool, or sell it through the Marketplace. Free, Pool, and Marketplace are permanent choices.
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.
Free, 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 |
| Free | Anyone, without an account | Open packages you publish with Pro or organization coverage |
| 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. Free, Pool, and Marketplace are explicit per-package choices, permanent once made. See LPM.dev package distribution for review, requirements, and what each mode allows.
Free vs Pro
| Capability | Free | Pro |
|---|---|---|
| Price | $0 | $10/mo |
| Private packages | 2 | Unlimited |
| Package storage | 100 MiB | 5 GiB |
| Package storage beyond that | Publishing stops. The tarballs of packages whose sales pass $50 do not count. | $0.20/GiB a month, rounded up to a whole GiB. Publishing past it waits while billing is not active. |
| 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 GiB |
| Remote cache uploads and cache hits | - | 4,000 and 50,000/day |
| Remote task cache beyond 25 GiB | - | Optional overage: $0.20 per GiB kept 30 days, up to a cap you set |
| Tunnels | - | Included |
| Concurrent tunnels | - | 3 |
| Included tunnel requests | - | 100,000/billing period |
| Account-wide tunnel rate | - | 20,000/min |
| Per visitor IP within the account | - | 600/min |
| Tunnel requests beyond allowance | - | $1/100,000, proportional |
| Claimed tunnel domains | - | 3 |
| Tunnel auth | - | Included |
| Webhooks, analytics, audit logs | - | Included |
Remote cache overage is off by default. You can turn it on and set its cap on the billing page. See Remote task cache.
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.
If a Pro payment fails, Pro continues to work for nine days while Stripe tries the payment again. During this time, tunnel overage is off, so tunnels stop at the included requests. If the payment does not succeed in the nine days, the account moves to Hobby. The relay then refuses tunnels, and LPM.dev Registry releases your claimed tunnel domains. If you pay the subscription later, Pro returns, but the released domains do not. To pay, update the payment method in billing settings.
Organizations use separate org billing at $10 per seat. Each seat includes unlimited private packages, 5 GiB package storage, and 25 GiB remote cache with 4,000 uploads and 50,000 cache hits a day. Package storage past the organization's total is billed at $0.20/GiB a month, rounded up to a whole GiB. See Remote cache for every request limit. The organization shares a limit of 3 concurrent tunnels and 3 claimed tunnel domains across all members and base domains. Additional seats do not increase these two limits. Members connect organization tunnels through the claimed domains of the organization, with or without a personal Pro plan.
Each billed Stripe seat adds 100,000 included tunnel requests and 20,000 requests/minute to the organization account. The seat count is fixed when the tunnel usage period opens and applies for the rest of that 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 number of tunnels or domains does not multiply the allowance. 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 - public URLs, claimed domains, auth, and webhook capture.
- lpm.dev pricing - current billing and plan details.
- The Pool - the full Pool model.