Install guide

Install by package name. Keep your key in a local or CI secret and configure npm to send it only to this store.

Use the Node.js runtime listed by the SDK. BrightOps Memory requires Node.js 22.19 or newer.

All products are alpha and require owner approval. Join the alpha, then open My requests for your decision, license and available downloads.

1. Configure the registry

Save this in your project's .npmrc. It contains a secret reference, not your key:

@wf:registry=https://catalogue.brightops.io/npm/
@brightops:registry=https://catalogue.brightops.io/npm/
@bo:registry=https://catalogue.brightops.io/npm/
//catalogue.brightops.io/npm/:_authToken=${BRIGHTOPS_TOKEN}

Set BRIGHTOPS_TOKEN in your local secret environment or CI secret manager to the key from your license page. Never commit the key or place it in a dependency URL.

2. Install a pinned version

npm install --save-exact @wf/model-router@0.3.0-alpha.4

Use the package and available version shown on your license page. Commit the package manifest, lockfile and the token-free .npmrc. npm records an immutable archive hash and a URL without credentials.

For CI, use npm ci with the same registry secret. The README, public API types, examples and license ship inside each package.

3. Upgrade and rebuild

Install the new exact version after following its migration guide. Paid versions already acquired, including their pinned dependencies, remain downloadable for fresh builds after ordinary cancellation. Alpha downloads require current approved access. Alpha access does not create continued-use download rights.

Keep private archive backups or an internal package cache for offline builds. Package downloads need the store; the local memory SDK and installed applications do not call a licensing server at runtime.

4. Access errors

  • 401 missing_key or unknown_key: check the secret reference and registry URL.
  • 403 expired or not_entitled: select a version acquired while paid, or contact the owner about renewing alpha access.
  • 403 revoked: contact support to replace a compromised key.
  • 404: check that the version is published and covered by your license.

Included SDK dependencies do not require a second purchase. Human developer seats follow the order; automated agents and CI jobs add no seats. Read the license terms.