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 and license it per customer — the registry enforces access, you keep the commercial relationship.
- ↗Licenses with validity windows, suspension and revocation
- ↗Customers install with their own read-only npm tokens
- ↗You invoice; the platform never touches your sales
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 licensed to them.
- ↗Per-integrator products and tokens
- ↗Your own registry domain, so docs point at npm.you.com
- ↗Download metering shows who adopts what
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
