GOOD TO KNOW / 03
Questions,
answered.
Everything you need to know about the registry, your trial, and how customer access works.
FREQUENTLY ASKED
The details,
up front.
Looking for the specifics? The features and pricing pages go deeper.
What is a private npm registry?
A registry that serves packages only to the credentials you allow. npm, pnpm and yarn work with it out of the box — it is the same protocol, pointed at your registry.
Shared or private registry — what is the difference?
Every publisher can reserve one scope on the platform's shared registry (npm install @your-scope/pkg). Private registries are separate namespaces with their own names, served from your own verified domain.
How does the 30-day trial work?
Sign up and your organization gets 30 days on the Growth plan — no card required. You can create packages, products, licenses and customers right away. Publishing package versions needs a card on file; you are still not billed before the trial ends.
What happens when the trial ends?
Nothing is deleted and everything stays readable and exportable. Creating and publishing pause until you choose a plan.
What do the plans limit?
Plans cap packages, customer licenses that have not been revoked, private registries, seats and storage. An expired license still counts until you revoke it; revoking it frees a slot. Each plan also includes a monthly bandwidth egress allowance measured in GB. At 80% and 100% we email organization admins about upgrade options; downloads continue and there is no automatic overage charge. Upload traffic does not count toward egress. Tokens are not billed as licenses.
Do you bill my customers?
No. Your customers are your records: you sell and invoice them however you like. The platform only enforces their licenses at install time.
Is a customer license a key?
No. A license is a grant from one of your products to a customer. You give that customer a separate read-only registry token (prt_) for npm installs. The token works only for packages covered by their current licenses. You can change or revoke a license without replacing the token.
Which keys manage my organization?
Organization API keys (gsk_) call the Connect management API for your tenant, including permitted customer and license operations. They are available from Growth up and cannot authenticate npm installs or publishes. Registry tokens (prt_) authenticate npm publishing or installs on every plan; they cannot call the management API. Webhooks also start on Growth.
Can I change plans later?
Yes, upgrades are self-service at any time. Limits are enforced when you create, never retroactively.