Skip to content

THE PLATFORM / 01

Everything your
packages deserve.

A complete path from private publish to licensed install, built around the package manager your team already uses.

01 / Publishing

Publishing

The npm CLI workflow your team already knows, hardened for commercial distribution.

  • Private namespaces

    Reserve one scope on the shared registry or run private registries; package names are unique per registry, never claimed globally.

  • Safe publishes

    Reserve, upload, finalize: retries never double-publish, fingerprints reject mismatched content, and committed versions are immutable.

  • Deprecate and unpublish

    Deprecate a version with a message or unpublish it; a tombstone keeps the version from ever coming back.

  • Dist-tags

    Point latest and your own channels at the versions your customers should get.

02 / Customers and licensing

Customers and licensing

Sell or share packages on your terms: the registry enforces what each customer may install.

  • Products

    Group packages into the products you sell, independent of npm scopes.

  • Customer licenses

    Grant a customer a product for a set period; suspend or revoke the grant without changing their registry token.

  • Customer registry tokens

    Read-only prt_ tokens for npm installs. A token can install only packages covered by that customer's current licenses.

  • Publisher registry tokens

    Separate prt_ tokens for your own npm publishing and installs, narrowed by registry, scope or package.

03 / Delivery

Delivery

Your registry looks and behaves like yours.

  • Custom domains

    Serve npm.yourcompany.com with a DNS-verified domain and managed TLS.

  • Shared registry

    Publish under your reserved scope on the platform registry and be installable by default.

  • Usage metering

    Download bandwidth is measured as egress, separate from upload bytes, so growth is visible before it is a problem.

04 / Workspace and platform

Workspace and platform

The organization around the registry.

  • Roles and SSO

    Admins, members and viewers; single sign-on by email domain, SCIM provisioning, passkeys and two-factor sign-in.

  • Audit log

    Every publish, license, token and plan change is recorded with actor and time.

  • Growth and up

    Organization API keys

    Use gsk_ keys to automate management of your organization, customers, licenses and packages through the Connect API. These keys cannot install or publish npm packages.

  • Growth and up

    Outgoing webhooks

    Package, license and customer events delivered to your endpoints with Standard Webhooks signatures.

READY WHEN YOU ARE

Your packages. Your customers. Your rules.

Start 30-day trial