Skip to content
privatenpmREGISTRY
Start free trial
Menu

PRIVATE PACKAGES, YOUR RULES

Private packages.
Shared on your terms.

Publish packages for your own teams and CI, or deliver libraries and SDKs to customers. Give each person or pipeline access to exactly the packages they need.

Start 30-day trial Publish your first package

No card required · Publish up to 3 packages with 10 GB storage during your trial

Prefer a walkthrough? Book an engineer demo →

acme / registry INTERACTIVE DEMO
Try the registry flowSimulated · click to try
p/◫▤◈⚙
ACME / PRIVATE REGISTRY

Packages

SIMULATION

NEW PACKAGE 01 / 04

@acme/

Private namespace · npm compatible

RELEASE PIPELINE 02 / 04

◇
@acme/ui-kitPackage ready for a release
v2.4.0
Local packagenpm registryPublished

DOWNLOAD ACCESS 03 / 04

N
Northstar LabsRecipient download key
✓
Allowed package◇ @acme/ui-kitOnly this package can be installed

RECIPIENT INSTALL 04 / 04

◇@acme/ui-kit2.4.0 · private
Download keyExact accessnpm install
MICRO DEMO · 4 STEPS

SEE IT IN ONE MINUTE

The whole workflow,
start to finish.

Publish with npm, give each recipient a key for exactly the right packages, serve installs from your own domain, release from CI without stored secrets, and see every install in the audit log.

A one-minute narrated tour of PrivateNPM. Narration: From npm publish, to exact access. Point your scope at your own registry, and publish with the npm you already know; every version is immutable the moment it lands. Give each customer, team, or pipeline a read-only download key, for exactly the packages they need, and revoke it whenever you like. They install with npm, pnpm, or Yarn, as usual; anything you didn't grant stays out of reach. Serve every install from your own domain: point a CNAME at our edge, and we verify it and keep the certificate fresh. Publishing from CI? Trusted publishing trades a signed OIDC token for a fifteen-minute key, with no long-lived secrets to leak. Every publish, install, and key change is on record, so you always know who shipped what, and who installed it. One registry for npm, PyPI, and Files. PrivateNPM: start your thirty-day trial today.

FOR INTERNAL TEAMS

Keep company packages inside your organization.

Give developers and CI scoped credentials for the packages they need. Manage team access and see who published or installed each version.

Explore team distribution

FOR PACKAGE SELLERS

Deliver private libraries to customers.

Give each customer a read-only key for the packages they bought. Change or revoke access when needed; keep your own sales and billing relationship.

Explore customer delivery

BUILT AROUND THE TOOLS YOU ALREADY USE

npmpnpmyarnCI/CD

01 / THE WORKFLOW

From publish to permission,
all in one place.

Your packages stay private while the people you choose get a familiar install experience.

01 — PUBLISH

Use your existing npm workflow.

Publish immutable versions with the CLI your team already knows. Safe retries keep each release exactly where it belongs.

npm publish
02 — GRANT ACCESS

Choose the packages.

Create a read-only download key for each recipient and select the exact packages they may install.

recipient → download key → packages
03 — DELIVER

Make the registry yours.

Serve installs from your own verified domain with managed TLS, or start immediately on a reserved shared scope.

npm install @acme/sdk

02 / CONTROL WITHOUT FRICTION

Private by default.
Ready to share.

Commercial packages need more than a hidden tarball. Control publishing, credentials, recipient access, and delivery from one workspace.

See all features
01Private namespacesKeep every package where it belongs↗02Download keysEnforce access at install time↗03Your registry domainGive recipients a familiar home↗04Audit and usageSee who published and installed↗

BUILT FOR REAL DISTRIBUTION

One registry.
Many ways to ship.

Sell a component library. Deliver an SDK to integrators. Keep internal packages inside your organization. Each can install through the package manager they already use.

Explore use cases

LEARN THE WORKFLOW

Set up private packages with confidence.

Start with how a private npm registry works, then publish your first private package. Connect developer machines with the .npmrc authentication guide and release from CI with npm trusted publishing.

Choosing how to host? Compare self-hosted and managed npm registries, or browse all guides.

From the blog: test a private package as a recipient.

Need a quick check? Try the free registry developer tools to check authentication, lockfile hosts and clean installs.