What you need
2 projectsCommercial useMaintainedSetupCost
- Commercial use
- Yes
- MIT. Commercial use, modification and closed-source use are all allowed; keep the copyright notice. The exception is the code under the enterprise/ directory of the repository, which has its own Enterprise license: production use requires a paid subscription for the right number of seats. See the caveat below.
- Maintained
- Active
- Last push on 2026-10-13. The repository is not archived.
- Setup
- Easy
- There is an official install script, documented for Ubuntu 24.04: download it and run one install command. If you want a domain, point its A record at the server first and the script sets up Nginx and a Let’s Encrypt certificate. Docker Compose also works: download the official .env and compose templates, change the Postgres and Redis passwords, prepare the database and start. You bring your own SMTP server for notification emails.
- Cost
- Paid tiers
- The Community edition is free. The docs list a minimum of 2 cores, 4 GB of RAM and a 20 GB SSD, and recommend 4 or more cores, 8 GB or more and 50 GB or more for production, plus PostgreSQL 12 or later and Redis 6 or later. For paid features on your own server, the prices in October 2026 are $19 per agent a month for Premium Support and $99 per agent a month for Enterprise. If you would rather not self-host, the official cloud has a free plan for up to 2 agents and paid plans at $19, $39 and $99 per agent a month.
- What to watch out for
- The self-hosted pricing page lists what the Community edition leaves out: Captain AI, voice calls, custom branding, agent capacity, roles and permissions, SSO / SAML and SLA policies. The first five come with Premium Support; SSO and SLAs need Enterprise. The code for these sits in the enterprise/ directory of the repository under the Enterprise license. To run only the MIT-licensed part, the docs say to switch to the Docker image tags ending in -ce.
- Commercial use
- Conditions
- AGPL-3.0. Running it unmodified adds no obligations. If you change the code and let customers or staff use it over a network, you must offer those users your modified source. The README states that the code is owned by the Zammad Foundation, which is independent of the commercial provider Zammad GmbH.
- Maintained
- Active
- Last push on 2026-10-13. The repository is not archived.
- Setup
- Moderate
- You can install from packages (CentOS / RHEL 9 and 10, Debian 11 to 13, Ubuntu 22.04 to 26.04, openSUSE Leap / SLES 15 and 16), or use Docker Compose or Kubernetes. It needs PostgreSQL 15 or newer and Redis 7 or newer; the package install sets both up automatically. Docker Compose needs at least 4 GB of RAM, and you first raise the host’s vm.max_map_count to 262144 so Elasticsearch runs properly.
- Cost
- Moderate
- The software is free. The stated minimum is 2 cores and 6 GB of RAM, plus 4 GB if Elasticsearch runs on the same server; the example for up to 40 agents is 6 cores and 6 GB, plus 6 GB for Elasticsearch. The docs make no disk recommendation. If you would rather not self-host, the hosted plans in October 2026, billed annually and excluding VAT, are €7 per agent a month (up to 5 agents), €16 (up to 35) and €25 (unlimited).
- What to watch out for
- The docs call Elasticsearch “optional but strongly recommended”: Zammad runs without it, but search is slower and very limited, and features such as reports and searching inside email attachments rely on it. When you self-host, updates, backups and availability are yours; official support contracts for self-hosted installs start at €2,999 a year excluding VAT. If you deploy with Docker, support covers only the Zammad application, not Docker itself.
Your industry is not here?
Tell me the industry and what you need solved. I will look at it next.