Create a private npm registry

Choose a registry namespace

Open Registry → Registries. Reserve your one scope on the shared registry if names such as @acme/sdk fit your distribution. The shared host is registry.privatenpm.com. If you need your own package namespace or unscoped names, create a private registry with a display name and hostname instead. Private registries use verified custom domains.

Prepare publishing

1. On the registry card, choose Manage keys → New publisher key. Choose the actions your release process needs, then copy the reveal-once secret into your CI secret store.
2. Set the package's name to your reserved scope, for example @acme/sdk, and route that scope to the registry in .npmrc.
3. Publish a version and confirm the package appears under Registry → Packages.

During a trial, publishing versions requires a payment method on file; the trial is not billed before its end. The publishing walkthrough covers the npm command and key setup.

Prepare installs

In that registry's Manage keys page, create a separate read-only download key for each recipient. Grant selected packages, one owned scope, or all packages in that registry. Copy its secret when issued and send it through a secure channel with the customer .npmrc instructions. You can later edit access, rotate, or revoke a key without republishing.