npm registry
Private npm packages, with the npm client you already use.
At a glance
- Clients
- npm, pnpm, yarn
- Setup
- Nothing to create; one registry per organization
What it does
- Nothing to set up
- The registry exists from the moment your organization does. Point your scope at it and publish.
- Dist-tags and visibility
- Manage dist-tags such as
latestandnext, change a package’s description, or make a package public. - Tokens for people and CI
- People at a terminal get a token valid for 12 hours. CI publishes with an access key you can set to expire and revoke.
- Access by policy
- Who may install or publish is an IAM policy, like everything else in your organization.
Command line
Get a token for the npm client, then publish as usual.
$ dcloud npm tokens create
$ npm publish Price
As of 19 November 2026
| What | Price | Unit |
|---|---|---|
| npm package storage † | €0.00632 | per GB-month |
† Charged after notice: metered today and shown in the console with what it would cost. It appears on invoices from a date we announce in advance, never retroactively.
Documentation
Related: Container registry, Actions, Code.