RETICLE_LICENSE_KEY. Activation is verified locally with Ed25519 and makes no network call, so nothing about your usage leaves your machine. Run npx @reticlehq/server license to see whether you are active, eval, missing or expired.
Premium access (how you get + activate it), what’s gated, the security/data-handling posture, and the licensing model. Integration mechanics live in platform-integration.md.
Already have a key and just need to switch it on? Activating a license key is the step-by-step version: where to set it on each platform, the editor and CI cases, how to read every status, and what to do when it does not work.
How premium access works (offline, no phone-home)
Enterprise (ee/) features ship inside the open package; they’re source-available (free for development, testing, and evaluation). A license key activates them in production. Activation is verified locally with Ed25519; nothing about your usage ever leaves your machine.
The flow, end to end:
- Buy. Contact hey@reticle.sh; we issue you a signed license key (license id, org, plan, expiry, feature set). The license id is the stable handle on your subscription: it survives a rename, and it is what a renewal continues.
-
Install. Set it on the machine running the Reticle server:
-
Verify.
reticle licenseshows your status:Every status reportscontact, so a reader who is stuck always has somebody to write to. An unlicensed status also reportsgated, what a licence unlocks in the build you are running, so the command answers “what would this buy me, and how do I get one” without anybody having to find this page first. It is derived from the features the gate actually enforces, so it names what your build will really refuse rather than a roadmap. Anactivelicence does not report it: that reader has already bought, and listing feature names at them answers nothing they asked. - Unlock. Enterprise features now run in production; without a valid key they refuse to run there (a clear error, never a silent half-feature). In eval/dev they always run free.
-
Renew. Keys carry an expiry;
reticle licensewarns before it lapses.
Procuring a license: contact hey@reticle.sh. Keys are issued offline and signed with Ed25519; the activation you run (reticle license) verifies them locally with no network call.
What’s gated (and the roadmap)
The licensing mechanism is open core (inspectable, FSL). Only the features underee/ are gated:
- Today: the activation gate + an example gated feature (audit event recording).
- Roadmap (the reliably enterprise-only set): SSO/SAML, SCIM, RBAC / team permissions, audit logs, multi-org management, verify-before-merge policy gates, and the hosted control-plane connectors. These are the things a security/compliance org pays for; the core verification engine stays free forever.
What’s premium vs free, and pricing, are business decisions for the owner; this doc describes the mechanism, not the price list.
Security & data handling
The honest one-pager a security review needs. Reticle is built so the answer to “where does our data go?” is nowhere. It runs on your machine, in your infra.
Verify it yourself: the SDK + server are source-available, so read the tree-shaking, the
127.0.0.1 bind, and the offline license verify. SECURITY.md has the disclosure process; an SBOM is available on request. SOC 2 is a GA-stage item (no Reticle-hosted data exists today to certify); the posture above is the honest current state.
Licensing model (per package)
Embedding / OEM / enterprise: hey@reticle.sh.