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 publishPRIVATE PACKAGES, YOUR RULES
Private packages.
On your terms.
Publish with npm. Grant each customer access to the packages they bought, then give them a registry token to install. Deliver from your own domain.
No card required to sign up · Works with the npm CLI
registry / overview● LIVE
ACME / PRIVATE REGISTRY
+ New packagePackages
PUBLISHED24↑ 4 this month
ACTIVE LICENSES128Across 18 customers
DOWNLOADS8.4kLast 30 days
PACKAGEVERSIONACCESS
◇ @acme/ui-kit2.4.0 Licensed
◇ @acme/sdk1.8.2 Licensed
◇ @acme/icons3.1.0 Private
$ npm publish --registry=https://npm.acme.com✓ @acme/[email protected] published
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.
Decide who gets access.
Bundle packages into products and grant each customer a license. Give them a separate read-only registry token for installs; the license controls which packages that token can access.
customer → product → packagesMake the registry yours.
Serve installs from your own verified domain with managed TLS, or start immediately on a reserved shared scope.
npm install @acme/sdk02 / CONTROL WITHOUT FRICTION
Private by default.
Open to your customers.
Commercial packages need more than a hidden tarball. Control publishing, credentials, customer access, and delivery from one workspace.
See all features