Private Registry

Your Packages, Your Rules

Publish private packages with npm, yarn, or pnpm. Free to start. When you're ready to monetize, move packages to the Pool or Marketplace without changing platforms.

Setup

Run lpm setup to configure your project. It creates the .npmrc for you automatically.

Publish

Run lpm publish to push your package to the registry. Version management works just like npm.

Install

Run lpm install or npm install. Authentication is handled transparently behind the scenes.

Works With Your Existing Tools

No new tooling to learn. LPM is a drop-in private registry for your npm workflow.

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, or opt into the Pool for revenue sharing.

Distribution modes give you full control. Private packages are hidden from search and accessible only to your team. When you're ready to monetize, switch to Marketplace or Pool with a single setting.

Pool

Available via Pool subscription. Earn revenue from installs.

Private

Accessible only to you. Not visible in search.

Marketplace

Listed for sale. Anyone can discover and purchase access.

One Platform

Start Private, Monetize Later

LPM is the only registry where your internal packages and commercial packages live side by side.

Build and iterate privately with your team. When a package is ready for the world, move it to the Marketplace for direct sales or the Pool for subscription-based revenue, without migrating to a different platform.

Built for Teams

RBAC, audit logs, SSO, and scoped CI tokens. The controls your team needs without the enterprise price tag.

Collaborate With Confidence

Fine-grained access control, audit trails, and secure CI/CD integration. Everything your team needs to ship internal packages safely.

Team Roles

Owner, Admin, Maintainer, and Developer roles with granular permissions for every action.

CI/Deploy Tokens

Machine-owned tokens scoped to read or publish. They survive employee turnover.

Audit Logs

Full history of publishes, installs, invitations, and setting changes for compliance.

SSO Integration

Enforce login via GitHub or Google Workspace. One less password to manage.

Plans at a Glance

Start free, scale when you need to.

Hobby

Free: 2 private packages, 100 MB storage. Publish to the Pool and start earning immediately.

Pro

$7/mo. Unlimited private packages, 5 GB storage. Plus webhooks, analytics, and audit logs.

Organization

$7/seat/mo. Unlimited private packages, 5 GB storage per seat. RBAC, service accounts, and unified billing.

Frequently Asked Questions

How do I set up my project?

Run lpm setup in your project directory. It creates a .npmrc file pointing to the LPM registry. For CI/CD, set the LPM_TOKEN environment variable in your pipeline.

Does it work with npm, yarn, and pnpm?

Yes. LPM is fully npm-compatible. The .npmrc configuration works with npm, yarn, and pnpm out of the box. No custom tooling required.

How many private packages can I have?

The Hobby plan includes 2 private packages with 100 MB of storage. Pro and Organization plans include unlimited private packages with 5 GB of storage.

Can I make a private package public later?

Yes, you can move a private package to Pool or Marketplace distribution at any time. However, this change is permanent. Once a package leaves private mode, it cannot be switched back.

How do CI/CD tokens work?

Generate scoped tokens from your dashboard with read-only or publish permissions. Organization tokens are machine-owned, so they survive employee turnover. Add them as environment variables in your CI platform.

Your internal packages deserve a real registry.

Start free with 2 private packages. Upgrade to Pro ($7/mo) or create an Organization ($7/seat) when your team grows.