Zammad vs Chatwoot

Corporate login is where the two products diverge most, and the tier you buy from Chatwoot decides the answer. Zammad's third-party login covers SAML, OpenID Connect, Microsoft, Google, GitHub and GitLab, among other providers, as documented in the Zammad third-party applications guide. Chatwoot's self-hosted Community Edition does not include SSO. SSO with SAML appears in the Enterprise Edition, which is priced per agent per month on Chatwoot's self-hosted plans page, so a team that needs SAML sign-in should budget for that tier before it compares any other feature. Confirm whether the Chatwoot Enterprise license covers SAML only or also includes other directory features your identity team expects.

Extensibility also differs in kind. Zammad offers an API for data import and other integrations, and its migration documentation says systems without a built-in migrator can be imported through that API or through custom development from Zammad. Chatwoot's README lists integrations with Slack, Dialogflow, Shopify, Google Translate and Linear, which are prebuilt connections rather than a general extension path. If your helpdesk must talk to an internal ticketing system or CRM that none of these covers, price the API work or custom development into the plan with each vendor, and ask who maintains that code after go-live.

Before you commit, confirm directory group mapping and user provisioning with each vendor, not only single sign-on. Ask whether group membership from your identity provider can set Zammad roles or Chatwoot team and role assignments automatically, whether users are created and removed through SCIM or only on first login, and how deprovisioning is handled when someone leaves. These behaviors are not settled by a login feature list, so test them in a staging instance with a pilot group of users and your own identity provider.

The running cost of both platforms is set mostly by infrastructure, staff time and, on paid tiers, per-agent or per-year fees, and the largest variable is conversation volume. Chatwoot's requirements page recommends at least 4 CPU cores and 4 GB of RAM for up to 10,000 conversations a day, and 8 cores and 8 GB for up to 20,000, plus at least 1 GB of swap, with Sidekiq able to use more than 1 GB on a very active server. Zammad's sizing depends more on agent count, attachment volume and search needs. Its documentation makes Elasticsearch optional but strongly recommended, because it drives faster search, reporting and attachment content search, and Memcached is needed for multi-instance deployments such as containers or cluster nodes. Ask your team to estimate peak daily conversations or tickets and attachment storage before you size either stack, and confirm the Elasticsearch and Memcached footprint with Zammad rather than assuming a single-node install.

Separate one-time setup from recurring costs. One-time costs include installation, configuration of channels and identity sign-in, migration from your current helpdesk, and any custom integration work. Recurring costs include the infrastructure bill, staff time for upgrades, backups, monitoring and security patches, and, for Chatwoot, the per-agent fees on Premium Support ($19 per agent per month) or Enterprise Edition ($99 per agent per month) as listed on its self-hosted plans page. Zammad's self-hosted support plans are priced per year at 2,999, 5,999 and 9,999 euros for the Business, Enterprise and Corporation tiers, and the pricing page states that self-hosted customers handle updates, backups and availability themselves. That means the staff line is often the largest recurring cost on Zammad, while Chatwoot's larger recurring fee sits in its paid per-agent tiers.

When you request a quote from any vendor or implementation partner, ask for the price per agent and the total for your actual agent count, the currency, and whether it is billed monthly or annually. Confirm which support tier covers version upgrades and security patch application, whether backups or high availability are included, and what response times apply. For Chatwoot, confirm whether SSO with SAML and SLA policies are in the tier you need, since the plans page places them in Enterprise Edition. For Zammad, confirm which of the Business, Enterprise or Corporation support plans fits your team and whether the Elasticsearch and Memcached components are in scope. Ask DeployOpen or any partner to write the staff hours for upgrades and restores into the scope, because those hours recur every release cycle.

Rollouts slip most often at channel onboarding, not at installation. For Zammad, the email routing work is the long pole: inbound addresses, sender rules and the outbound notification path all need testing with real mail before agents depend on the queue. Search and reporting are the second risk. Zammad's documentation describes Elasticsearch as optional but strongly recommended for faster search, reporting and attachment content search, so plan for it as a sizing and operations task rather than an afterthought. Ask your implementation partner or the vendor to confirm how the search index is rebuilt after a restore, because teams often discover this only after a failed test.

On the Chatwoot side, channel onboarding is more approval-driven. Each social channel, such as Facebook, Instagram, WhatsApp or Telegram, depends on app registration and review by the platform owner, and the widget placement on your site needs a change window with your web team. Your schedule should assume those external steps can take longer than the technical setup. Before you pick a host, confirm the operating system support with Chatwoot. Its deployment requirements list Ubuntu 20.04 as the only officially supported Linux distribution, which may conflict with your standard build. Also check that your image can supply Ruby 3.2 or later and Node.js 20.x, since those versions often need pinning on a hardened base. Staff training and multi-instance design are the quieter sources of delay. Zammad agents work from a ticket queue, so supervisors must define states, groups and escalation rules before go-live. Chatwoot agents work from a conversation list with private notes and auto-assignment, so the same people need different habits and different metrics. If you run Zammad across several application nodes, plan Memcached as a shared cache, since Zammad's documentation says multi-instance deployments need it while single installations can use the file system cache. Scope, deliverables and timelines for this work should be agreed in writing before the engagement starts, with each item named and assigned.