Zwall treats install, secrets, and policy as separate steps. Zwall Enterprise deployment is designed to consume verified signed releases. Database schema admission is distinct from starting the Manager. Administrators can require TOTP. AI Preview drafts. Operators enforce. This page is not a SOC 2, ISO, HIPAA, or GDPR claim.
If you run infrastructure, you should ask how a Manager is allowed to start, how Agents are allowed to join, and who holds secrets. Zwall’s answer is explicit admission steps.
It is not “curl | sudo bash,” not a public key-distribution URL on the marketing site, and not a compliance certificate.
Release-bound components are admitted through protected verification and root-controlled staging. Independently stage the bundle, independently install the release verifier and a pinned trust root, then run database-only schema admission from that verified release. Starting the Manager is a later step.
Administrators authenticate with username and password; TOTP can be required. Login JSON returns token, not a session_token. Agents present Manager-issued Agent credentials, not the administrator token. Most operator APIs still require the admin role.
The Manager is intended to run unprivileged, with secrets presented by the service manager rather than ordinary unit text.
Virtualization Agents require root to load eBPF. Hosting splits unprivileged Agent and privileged pass-only loader. Least-privilege and TLS operations are operator responsibilities documented in hardening Guides — not a Zwall-issued kernel-safety certificate.
You still own: TLS certificates (Community does not automate issuance), PostgreSQL, file permissions for Hosting collectors, pin-dir and root on Virtualization hosts, and not publishing dump restore as a certified RPO/RTO.
Production secrets for JWT, database password, and default admin password are intended to stay out of ordinary YAML on Enterprise. A certified secret-custody claim is not currently published.
Community is a source build you operate. It does not use the Enterprise signed-release database admission path. That is honesty, not a downgrade insult.
| Community (Source Build) | Enterprise (Verified Release) |
|---|---|
| Source build (`go build`, example units) | Release-bound components through protected verification |
| API-driven secret rotation | Secret custody intended outside of ordinary YAML |
| TLS certificates (operator responsibility) | TLS certificates (operator responsibility) |
| Does not use signed-release admission | Uses signed-release database admission path |
You should verify releases, admit schema separately, and keep secrets out of unit text. Absence of a logo is not a hidden certification.
No. Community is a source build.
Production secrets for JWT, database password, and default admin password are intended to stay out of ordinary YAML on Enterprise. A certified secret-custody claim is not currently published.
No.
No. AI is advisory on the control plane.
No. Not the production upgrade path.
Read the deployment models or talk to an engineer about Enterprise admission.
