~/ossroster.com
≡
hometoolsarticlescategoriesalternativesabout
~/tools/zammad
Zammad
tool

Zammad

Zammad is an open source helpdesk and ticketing system you can self-host — a Zendesk and Freshdesk alternative that pulls email, chat, phone, and social messages into one shared ticket queue with SLAs, a knowledge base, and full-text search.

visit website ↗ repository ↗

What is Zammad?

Zammad is a web-based, open source helpdesk and ticketing system that centralizes customer support across email, live chat, phone, and social channels into a single shared ticket queue. Built on Ruby on Rails with a Vue.js frontend, it’s a self-hostable alternative to Zendesk and Freshdesk that gives support teams SLAs, a knowledge base, and full data ownership without per-agent pricing.

What is Zammad best for?

Zammad fits support, service-desk, and IT teams that want a mature, feature-complete helpdesk they control themselves rather than renting per seat. It’s strongest when you handle inquiries across several channels at once and need SLAs, escalation rules, reporting, and a customer-facing knowledge base — the enterprise-grade features that usually sit behind higher SaaS tiers — while keeping every ticket on your own infrastructure.

What can Zammad do?

  • Omnichannel ticketing — turn email, web forms, live chat, phone calls (CTI), and social messages (Facebook, WhatsApp, Telegram) into unified tickets.
  • SLAs and escalation — define response and resolution targets, with triggers and schedulers that automate reminders and escalations.
  • Knowledge base — publish a multilingual self-service help center for customers and internal agents.
  • Full-text search — Elasticsearch-powered search across tickets, articles, and attachments.
  • Automation — triggers, macros, and text modules (canned responses) to speed up repetitive replies and routing.
  • Granular roles and permissions — organization and group-based access control for agents, customers, and admins.
  • Reporting and dashboards — track volume, response times, and agent performance.
  • Auditability — a complete history of who changed what on every ticket.

Where does Zammad fall short?

  • Heavy infrastructure footprint. Zammad runs a full stack — PostgreSQL, Redis, and Elasticsearch alongside the Rails app — so it needs meaningfully more resources than a simple PHP shared-inbox tool. Plan for around 4 GB RAM minimum, and 8 GB or more once you pass roughly 1,000 tickets a month before performance suffers.
  • Ruby stack is harder to staff. The Ruby on Rails codebase means fewer admins can debug it from the command line than a PHP tool like osTicket or FreeScout; when Elasticsearch falls over, you want someone who can read the logs.
  • Fewer prebuilt integrations than Zendesk. As an open source project, Zammad ships fewer turnkey app-marketplace connectors, so wiring it to external systems can mean more manual API work.

Is Zammad free?

Yes — the self-hosted version is free and open source under AGPL-3.0, with no per-agent fees and no seat caps. You only pay for the servers you run it on. Optional paid support subscriptions for self-hosters start at €2,999/year. A separate managed cloud (zammad.com) runs from about €7 to €25 per agent per month if you’d rather not host it yourself.

What does Zammad replace?

Zammad stands in for proprietary, per-agent helpdesk suites: Zendesk, Freshdesk, Jira Service Management, and Intercom. It covers the core ticketing, SLA, knowledge-base, and omnichannel features those tools charge for, while keeping your customer data on your own servers. If you want a lighter shared inbox instead of a full service desk, FreeScout or Chatwoot are simpler options.

FAQ

Is Zammad open source? Yes. Zammad is licensed under AGPL-3.0 and stewarded by the independent Zammad Foundation, with the full source available on GitHub.

Can I self-host Zammad for free? Yes. The self-hosted edition is completely free with unlimited agents. Paid support subscriptions and the managed cloud are optional; the software itself costs nothing to run.

Is Zammad a good Zendesk alternative? For teams wanting omnichannel ticketing, SLAs, and a knowledge base without per-seat pricing, yes. The tradeoff is that you operate the stack yourself and get fewer marketplace integrations than Zendesk’s hosted suite.

What do I need to run Zammad? A Linux server (Ubuntu, Debian, CentOS, or Docker) with PostgreSQL, Redis, and Elasticsearch. Budget around 4 GB RAM to start and 8 GB or more for busier queues.