Cerberus delivery surface
Nyalma is where customers learn what Cerberus does, download the installer, read the docs, retrieve licenses, and request support. Running Cerberus deployments stay offline-first and keep validating issued license material locally.
Why teams care
Offline-first
Nyalma handles public docs, release delivery, support entry, and license distribution while deployed Cerberus environments keep verifying issued material locally.
Customer clarity
The public site should answer what Cerberus is, who it is for, how offline deployments work, and where support or enterprise conversations start.
Clean commercial path
Community and Professional both expose real Cerberus behavior. The upgrade path comes from named-user and team limits, commercial packaging, and optional support.
Public docs
Customer-facing installation guidance for offline and connected deployments.
OpenHow `license.json` and `cerb1:` strings work in the portal and in Cerberus.
OpenHow bundles, checksums, and release notes fit into a customer-safe delivery flow.
OpenHow to stage upgrades and keep self-hosted Cerberus deployments portal-independent.
OpenWhat support covers, what a good ticket includes, and when to use the portal.
OpenTrust layer
Customers should be able to review terms, privacy, cookie behavior, and support boundaries before they ever request a download or hand over deployment details.
Commercial and account terms for nyalma.com, the portal, and issued materials.
OpenWhat account, support, and security data the portal handles and why.
OpenEssential session cookies, browser storage, and the portal theme preference model.
OpenSupport scope, response handling, and customer responsibilities for portal-assisted help.
Open