Version metadata
Version: community-v1
Effective: April 15, 2026
Change level: Material. New acceptance can be required for affected flows.
Community terms
Community terms for self-serve Cerberus access.
Community access is for evaluation, labs, and smaller self-hosted teams. It provides portal access, installer delivery, and license retrieval without paid support or managed-service obligations.
Community scope
Community is intended for evaluation, proof-of-concept work, and smaller internal rollouts of self-hosted Cerberus.
- Community includes portal access, release downloads, and signed license retrieval
- Community limits remain part of the issued entitlement and can change only through a new issued license or commercial upgrade
No bundled support
Community does not include a paid support response target.
- documentation and public release materials are available to Community users
- hands-on troubleshooting, response targets, and escalation depend on a paid support add-on or commercial agreement
Self-hosted responsibility
The customer remains responsible for validation, approval, deployment, and operation of Cerberus in its own environment.
- validate bundles and checksums before rollout
- test changes in a controlled environment before production where feasible
- maintain backups, rollback plans, and change approval for impacted systems
No managed service commitment
Community access does not turn Nyalma into the operator of the customer's environment.
- Community does not create a hosted control plane dependency for running Cerberus
- Community does not include guaranteed uptime, response targets, or environment-specific implementation work
Upgrade path
Customers that need higher limits, support commitments, or tailored commercial terms should move to a paid plan.
- Professional adds higher packaging limits and a cleaner commercial path
- Enterprise stays available for custom terms, rollout help, and larger estates