THE POSSIBILITIES / 02
Built for the
ways you ship.
One reliable registry for commercial libraries, vendor SDKs, and packages that never leave your organization.
01 / USE CASE
Sell packages to customers
You built a component library, a toolkit or an SDK worth paying for. Publish it once, grant each recipient the packages they need, and keep the commercial relationship yourself.
- ↗Package-scoped download keys with expiry and revocation
- ↗Recipients install with their own read-only keys
- ↗You invoice; the platform never touches your sales
Automate access after a sale →02 / USE CASE
Distribute a vendor SDK
Ship your product's client libraries to integrators without making them public. Each integrator gets credentials that see exactly the packages you grant them.
- ↗A separate download key for each integrator
- ↗Your own registry domain, so docs point at npm.you.com
- ↗Last-used activity on each recipient key and monthly registry totals
See the available download activity →03 / USE CASE
Run your organization's private registry
Keep internal packages off the public registry and give every team and pipeline scoped credentials with the audit trail to match.
- ↗Publisher tokens narrowed by scope or package for CI
- ↗Roles, SSO and SCIM for the whole organization
- ↗Immutable versions and a full audit log for compliance
Set up a private registry →