Outils
Lynx Release Channel
Choose the Lynx release channel (Production / Beta / Alpha) for your dedicated deployment
lynx_release_channel
· v19.0.1.0.0
· Premium
What this solves
Lynx Release Channel
Lets Enterprise-tier customers choose which release channel of Lynx their dedicated deployment tracks — Production (stable), Beta (release candidate), or Alpha (early access) — directly from Settings → Lynx Platform.
Pre-release modules are bundled inside the customer image (see stage-addons.py --bundle-preprod) and hidden at runtime by the lynx_license_enforcer release-channel gate. A channel change is therefore instant: it is confirmed with the Patrii licensing hub (recorded on the customer's license, signed acknowledgment), then the local module list is rescanned so pre-release apps appear in — or disappear from — the Apps installer immediately. Apps already installed are never removed by a channel change.
Channels
Production — stable builds only. The default, and the right choice for almost everyone.
Beta — release-candidate builds: upcoming features that have passed internal testing but are not yet promoted to Production.
Alpha — early-access builds including modules still under active development. For evaluation environments only.
Key Features
Settings integration — new "Release Channel" block in the Lynx Platform settings page.
Instant switching — hub-acknowledged changes take effect immediately via a module-list rescan; no deployment change needed.
Signed responses — hub responses are Ed25519-verified against the pinned issuer key, same as license validation.
Enterprise-gated — requires the release_channel license feature (included in the Lynx Enterprise plan).
Integrates With
lynx_license_enforcer — reuses the issuer endpoint resolution, database binding, and response-signature verification.
lynx_base — extends the Lynx Platform settings page.
Depends on
Try Lynx Release Channel on your team.
Free trial, no credit card. Talk to sales when you're ready.