Installation docs

Install Cerberus with a predictable path for offline and connected deployments.

Nyalma helps you obtain the bundle, release notes, and license material. Your running Cerberus deployment should still operate as a self-hosted system that does not depend on the portal for day-to-day validation.

1. Choose the deployment shape

Use offline mode when your environment should not rely on live portal connectivity.
Use connected mode when you want portal convenience features such as Entra-backed sign-in.
Both models still rely on signed license material rather than runtime phone-home checks.

2. Verify what you downloaded

Download the installer bundle and its matching checksum from the public delivery flow.
Read the release notes before rollout so version-specific changes are visible to operators.
Record the version and checksum you approved in your own change process.

3. Keep first-run expectations clear

Portal-assisted steps are limited to public docs, downloads, account access, and license retrieval.
Local configuration, rollout approval, backups, and recovery plans remain your responsibility.
Use staging or another controlled environment before production where feasible.

4. Know when to leave the docs

Use the portal for license retrieval, release access, and customer support threads.
Use the public support path for enterprise planning or support add-on requests.
Keep change approval for firewalls, identity systems, and network integrations with your own team.

Review download terms Licensing docs Support paths