Zammad vs Chatwoot
Both are alternatives to Freshdesk. Here's how they stack up — verified facts, no spin.
Also searched as Chatwoot vs Zammad — same comparison, one verdict.
Zammad and Chatwoot are closely matched on ownership (90 vs 84) — this one comes down to pricing and to which trade-offs below you can live with.
Zammad
TOP PICKA full-featured, AGPL-licensed help desk with ticketing, a knowledge base, and multi-channel inboxes.
Zammad is a mature, actively-developed open-source help desk covering email, chat, and social ticketing, SLAs, a customer-facing knowledge base, and text modules/macros — the closest like-for-like replacement for Freshdesk's core ticketing product. It's built in Ruby on Rails with an Elasticsearch-backed search index and ships an official Docker Compose stack, so a self-hosted install is a well-trodden path rather than a science project.
Chatwoot
An open-core omnichannel inbox strongest at live chat, WhatsApp, and social messaging.
Chatwoot unifies live chat, WhatsApp, Instagram, Facebook, Telegram, SMS, and email into one team inbox, with a Captain AI layer for FAQ-driven auto-replies on paid tiers. Chatwoot ships as an 'open core' project: the community edition (the whole visible codebase outside one folder) is MIT-licensed and free to self-host with no seat limit, while a smaller set of enterprise features (SSO/SAML, agent capacity management, custom branding, SLA policies) live in a separate 'enterprise/' directory under Chatwoot's own proprietary license and require a paid subscription even when self-hosted.
Side by side
10 points of comparison, every one read from a verified field. Green marks the side that wins a row outright. A dash means we do not hold that fact — never that it is zero.
| Zammad | Chatwoot | |
|---|---|---|
| Sovereignty ScoreOur transparent 0–100 composite for data ownership and exit cost. | 90 | 84 |
| Open source | Yes | Yes |
| Self-hostable | Yes | Yes |
| Local-first data | Yes | Yes |
| License | AGPL-3.0 | MIT (core); enterprise/ directory is a separate proprietary license, verified directly against chatwoot/chatwoot's own LICENSE file |
| Pricing | Free to self-host with unlimited agents; optional managed cloud plans start around €19/agent/month and Zammad also sells paid support contracts for self-hosted installs. | Community edition free to self-host, unlimited agents. Self-hosted paid tiers: Premium Support $19/agent/month (Captain AI, voice, branding, roles/permissions) and Enterprise $99/agent/month (adds SSO/SAML, SLA). Cloud-hosted plans start at $19/agent/month (Startups tier). |
| RAM to run it wellThe figure that actually matters, not the vendor's minimum. | 16 GB for a single-server install. The vendor's floor is 6 GB for Zammad plus 4 GB for Elasticsearch, and the usual VPS size above that is 16 GB. You can fit it on 8 GB by capping the Elasticsearch heap, which Zammad itself calls a less-than-ideal fix. | 4 GB plus 1 GB of swap is enough for a small team. Sidekiq alone can use more than 1 GB on a busy server, and 8 GB is the vendor's figure for 20,000 conversations a day. |
| Realistic running costWhat the box costs each month if you run it yourself. | $48–96/mo for a 10-agent instance on a 16 GB VPS with Elasticsearch on the same box; $24–48/mo on 8 GB with a capped Elasticsearch heap | $24–48/mo for a 10-agent instance on a 4–8 GB VPS (Chatwoot asks for 4 cores, which most hosts only sell with 8 GB), plus object storage if attachments move off the box |
| Setup timeHonest first-install estimate, not the marketing quickstart. | 2–3 hours with Docker Compose, including the Elasticsearch host setting; email channels and triggers take longer | An hour with Docker Compose. Each channel after that (email, WhatsApp, social) is its own setup. |
| Ongoing maintenanceThe part nobody budgets for. | Regular Zammad releases pulled with git pull and docker compose, PostgreSQL major-version bumps (15 or newer is now required), Elasticsearch upgrades followed by a search-index rebuild, and backups that follow the Docker-specific procedure. Zammad does not support problems that are specific to Docker. | Pull new images and run `rails db:chatwoot_prepare` on every update, and step very old installs through intermediate tags. Set WEB_CONCURRENCY yourself: the docs leave it out, so Puma runs a single process unless you change it. |
Zammad is Macrostack's recommended Freshdesk alternative, so it's our pick here.
Weighing both against staying on Freshdesk? Is Freshdesk free? What it actually costs →
Zammad
Strengths
- +Full AGPL-3.0 open-source core — no enterprise-only feature split
- +No per-agent limit when self-hosted; unlimited tickets and mailboxes, so team growth never triggers a new bill tier
- +Mature product: multi-channel (email, chat, Twitter/Facebook, telephony via CTI), SLAs, and a real knowledge base out of the box
- +Official Docker Compose and package installers make self-hosting straightforward
Trade-offs
- −Elasticsearch is a required dependency for full-text search, adding real memory/operational overhead versus a lighter stack
- −No built-in generative AI agent as of this writing — nothing directly equivalent to Freddy AI Copilot's inline reply drafting
- −Smaller third-party app marketplace than Freshdesk's connector catalog
Chatwoot
Strengths
- +MIT-licensed core is genuinely open source, not source-available — you can audit, fork, and modify it freely
- +Best-in-class channel coverage for chat-first support: WhatsApp, Instagram DM, Telegram, SMS, and live chat widget out of the box, broader than Freshdesk's native channel set on lower tiers
- +Very active project (multiple releases a month) with a large community and strong docs
- +Self-hosting the community edition is completely free with no agent-count restriction
Trade-offs
- −SSO/SAML, SLA policies, and agent capacity management sit behind a paid license even when self-hosted — not a full feature set for free
- −Captain AI (the auto-resolution layer, Chatwoot's rough equivalent of Freddy AI Agent) is a paid add-on, not part of the free community edition
- −Less oriented toward classic long-form ticket workflows than Freshdesk or Zammad; strongest for chat-style support
Which one fits you
The trade-offs above, turned into a decision. Find the line that describes your team.
Choose Zammad
if a lower exit cost matters more to you than any single feature, and full AGPL-3.0 open-source core — no enterprise-only feature split.
Choose Chatwoot
if mIT-licensed core is genuinely open source, not source-available — you can audit, fork, and modify it freely.
Neither, yet
if both carry a real cost you should weigh first — elasticsearch is a required dependency for full-text search, adding real memory/operational overhead versus a lighter stack, and sSO/SAML, SLA policies, and agent capacity management sit behind a paid license even when self-hosted — not a full feature set for free. If either of those is a dealbreaker for your team, the shortlist is wrong rather than the choice.
What it takes to run these yourself
Real requirements and honest running costs, not the vendor quickstart.
Self-hosting Zammad
16 GB for a single-server install. The vendor's floor is 6 GB for Zammad plus 4 GB for Elasticsearch, and the usual VPS size above that is 16 GB. You can fit it on 8 GB by capping the Elasticsearch heap, which Zammad itself calls a less-than-ideal fix. RAM · 2–3 hours with Docker Compose, including the Elasticsearch host setting; email channels and triggers take longer
$48–96/mo for a 10-agent instance on a 16 GB VPS with Elasticsearch on the same box; $24–48/mo on 8 GB with a capped Elasticsearch heap
Self-hosting Chatwoot
4 GB plus 1 GB of swap is enough for a small team. Sidekiq alone can use more than 1 GB on a busy server, and 8 GB is the vendor's figure for 20,000 conversations a day. RAM · An hour with Docker Compose. Each channel after that (email, WhatsApp, social) is its own setup.
$24–48/mo for a 10-agent instance on a 4–8 GB VPS (Chatwoot asks for 4 cores, which most hosts only sell with 8 GB), plus object storage if attachments move off the box
Zammad vs Chatwoot — common questions
Is Zammad a better fit than Chatwoot for help desk & customer support?
It depends on what you are optimising for, and the honest split is this: Zammad scores 90 to Chatwoot's 84 on data ownership and exit cost, so it is the safer choice if you care about being able to leave. Chatwoot earns its place on a different axis — mIT-licensed core is genuinely open source, not source-available — you can audit, fork, and modify it freely. Neither is a wrong answer for every team; the table above is the actual comparison.
What happens if we want to switch later?
Zammad keeps its data local or in open formats, so leaving is an export rather than a negotiation. Chatwoot is still self-hostable, so the files stay on your server either way — but it is not local-first by design, so check what its export produces before you rely on it.
Can I self-host Zammad or Chatwoot?
Both can be self-hosted. The difference is what it costs you in time rather than whether it is possible — see the setup and maintenance rows above.
Are Zammad and Chatwoot both alternatives to Freshdesk?
Yes — both appear in our Freshdesk comparison, which is why they are worth putting side by side. People usually arrive here already having decided to move off Freshdesk and now choosing between the two replacements, which is a narrower and much easier question.
More Freshdesk head-to-heads
Related alternative guides
Facts verified 2026-07-11. Licenses and pricing change — spotted something out of date? That's a correction we want.