Zwall
Talk to an Engineer
Talk to an Engineer
Documentation
Docs Home › Editions › Community

Community

Zwall Community

CommunityStatus: SUPPORTED as a first-class open-source edition — not a deprecated Enterprise trialAudience: Community operators and evaluators

Purpose

Describe what Community is, what it includes, and what it must not be documented as.

Concept

Community is the AGPL-3.0-only licensed edition. One Manager, at most three registered Agents. Install is source-first (go build, ebpf/make, web npm build) plus optional scripts/setup.sh.

What Community includes (verified)

  • Manager with /api/v1, console, PostgreSQL
  • Virtualization Agent (enforcement) — not Hosting observation
  • zwallctl without license, update/upgrade campaigns, local-tracker
  • secret-rotate [jwt|db|all] live API rotation (this is not the Enterprise command)
  • Health probes /health, /health/live, /health/ready
  • Rules, blocks, GeoIP, brute-force, notifications (in-process)
  • Community uninstall script

What Community does not include (verified by absent handlers/routes)

  • Hosting Agent, privileged loader, hosting profile
  • AI Preview HTTP group
  • License HTTP group and zwallctl license
  • Cloudflare HTTP group and unblock-portal HTTP group (Enterprise V1 router only)
  • GET /api/v1/dashboard/ebpf-health handler
  • Product ACME
  • Enterprise database admission / zwall-release verifier

Edition differences operators miss

  • Fourth Agent → 403 COMMUNITY_AGENT_LIMIT_REACHED on register, web create, and pre-register:
{
  "success": false,
  "error": "COMMUNITY_AGENT_LIMIT_REACHED",
  "code": "COMMUNITY_AGENT_LIMIT_REACHED",
  "message": "ZWall Community supports up to 3 agents",
  "limit": 3,
  "current_agents": 3
}
  • Logout uses AdminAuth() (Enterprise logout is unauthenticated at the gin layer)
  • Login cookie policy: Community does not implement the Enterprise “Secure HTTPS session required” gate the same way; still use TLS in production
  • Dashboard stats: Community omits several Enterprise keys; total_rules / active_rules may be zero in the Community handler
  • No GET /api/v1/dashboard/ebpf-health handler
  • Default zwallctl example URL http://localhost:8080 vs Manager example 8443 (both editions)

Common misconceptions

  • “Community is Enterprise with a time bomb.” No.
  • “Hosting observation is in Community.” No.
  • “Cloudflare sync is in the Community router.” No.