Private registry

Your packages, your rules

Publish and install private packages with LPM CLI, or with other package managers through .npmrc. When you're ready to share one, sell it on the Marketplace, add it to the Pool, or release it as Free for anyone to install.

Set up

Sign in with lpm login. If you use another package manager, run lpm setup local to add a read-only token to your project's .npmrc.

Publish

Run lpm publish. It scans the package for secrets before it uploads, and stops if it finds one.

Install

Run lpm install or npm install. LPM CLI uses your lpm login session, and npm reads the token in .npmrc.

Works with your existing tools

A scoped .npmrc routes only @lpm.dev packages to LPM. Every other package still installs from npmjs.org or the registry your .npmrc names.

Private by default

Private by default, public when you're ready

Every package starts private. Choose when and how to share: keep it internal, sell on the Marketplace, opt into the Pool for revenue sharing, or give it away as a Free package.

Only you, or your organization's members, can find, view and install a private package. You choose how to share it in the package's settings. LPM runs a security review of the latest version before the package goes public, and the choice is permanent.

Pool

Pool subscribers install it, and you earn from their installs.

Private

Only you or your organization can install it. It stays out of search.

Marketplace

Listed for sale. Anyone can find it and buy a license.

One platform

Start private, monetize later

Your internal packages and the packages you sell live on one registry. A package keeps its @lpm.dev name when it moves to the Pool or the Marketplace.

Build and iterate privately with your team. When a package is ready for the world, move it to the Marketplace to sell it directly, or to the Pool to earn from subscriptions.

Built for teams

Organizations get roles, audit logs, IP allowlists and scoped CI tokens for $10 per seat a month.

Collaborate with confidence

Limit installs of your organization's private packages, and publishes of all its packages, to the IPv4 ranges you list. Require two-factor authentication for every member.

Team roles

Members install private packages, Maintainers publish, Admins manage members and settings, and only the Owner handles billing.

CI and deploy tokens

Scope a token to read or publish, and limit it to one package or tag if you like. A trusted publisher lets GitHub Actions or GitLab CI publish with no stored token.

Audit logs

On Pro, your audit log records sign-ins, publishes, and token and settings changes. An organization's log records publishes, invitations, and member, token and settings changes. Search either one and filter it by action and date.

Required identity provider

The Owner can require every member to connect an account from one provider: GitHub, Google, GitLab, or Bitbucket. Until a member connects one, they can't open the organization's dashboard or publish its packages.

Plans at a glance

Start free, scale when you need to.

Hobby

Hobby is free, with 2 private packages and 100 MiB of storage. Publish to the Pool to earn when its subscribers install your packages.

Pro

Pro costs $10 a month for unlimited private packages and 5 GiB of storage. It adds webhooks, audit logs and Free packages that anyone can install without an account.

Organization

An Organization costs $10 per seat a month for unlimited private packages and 5 GiB of storage per seat. It adds roles, a required identity provider, an IP allowlist and shared billing.

Frequently asked questions

How do I set up my project?

Run lpm login, and LPM CLI installs @lpm.dev packages with that session. If npm, pnpm or Yarn 1 installs them too, run lpm setup local in the project to write a read-only token to its .npmrc. In CI, store a token as LPM_TOKEN. LPM CLI reads it directly, and lpm setup ci npmrc writes it to .npmrc for the other clients.

Does it work with npm, pnpm and Yarn?

npm, pnpm and Yarn 1 install @lpm.dev packages through the .npmrc that lpm setup local writes. Yarn 2 and later don't read .npmrc, and Bun can't use the registry URL in it. Only @lpm.dev packages route through LPM. Every other package still installs from npmjs.org or the registry your .npmrc names.

How many private packages can I have?

The Hobby plan includes 2 private packages with 100 MiB of storage. A package in the Pool or the Marketplace stops counting toward that limit once its first release is approved. Pro includes unlimited private packages with 5 GiB of storage, and the Organization plan includes unlimited private packages with 5 GiB of storage per seat.

Can I make a private package public later?

Yes. In the package's settings, move it to the Pool or the Marketplace, or make it Free on a paid Pro or Organization plan. LPM runs a security review of the latest version, and the package stays private until a release is approved. The choice is permanent from the moment you make it. The package can't go back to private or switch to another mode.

How do CI/CD tokens work?

Create a read or publish token in your personal or organization token settings, and limit it to one package or tag if you like. Each token expires within 90 days. Store it as LPM_TOKEN in your CI provider's secrets. An organization token stops working when the member who created it leaves the organization or loses the Admin role. A trusted publisher depends on no member. It lets GitHub Actions or GitLab CI trade the job's OIDC token for a short-lived publish token.

Publish your first private package for free

Hobby includes 2 private packages at no cost. Go Pro for unlimited private packages at $10 a month, or create an Organization at $10 per seat a month when your team grows.