Installation
Choose offline or connected deployment, verify the bundle, and keep the portal out of the runtime path.
Open installation docsDocs
Customer-facing Cerberus docs should read like product guidance, not an internal landing page.
Public docs now have dedicated pages for installation, licensing, downloads, upgrades, and support. The goal is simple: customers should be able to understand the product, verify a release, and plan a rollout without needing repo access or a private handoff for every step.
Install Cerberus
Customer-facing installation guidance for offline and connected deployments.
OpenLicensing and activation
How `license.json` and `cerb1:` strings work in the portal and in Cerberus.
OpenRelease downloads and checksums
How bundles, checksums, and release notes fit into a customer-safe delivery flow.
OpenUpgrade planning
How to stage upgrades and keep self-hosted Cerberus deployments portal-independent.
OpenSupport workflow
What support covers, what a good ticket includes, and when to use the portal.
OpenLatest public release
v0.1.0
Named-user licensing, `cerb1:` support, and customer portal distribution flow.
Published 4/9/2026Licensing
Understand how the portal issues `license.json` and `cerb1:` material while Cerberus verifies it locally.
Open licensing docsDownloads and checksums
Review the legal gate, artifact verification flow, and where release notes fit before deployment.
Open download docsUpgrades and support
Plan staged upgrades, know when to open a portal case, and keep change control with your own team.
Policy index
Trust, privacy, and support boundaries should be as easy to find as the install docs.
Terms
Commercial and account terms for nyalma.com, the portal, and issued materials.
OpenPrivacy
What account, support, and security data the portal handles and why.
OpenCookie policy
Essential session cookies, browser storage, and the portal theme preference model.
OpenSupport terms
Support scope, response handling, and customer responsibilities for portal-assisted help.
Open