As of 18 Nov 2026, the panel rates OTRS 2/5 and Zammad 3/5 in Customer Service & Helpdesk. Weighted by what each judge cares about, 0 of the 6 judges pick OTRS and 6 pick Zammad. OTRS scores higher on 1 of 6 criteria (European sovereignty). Zammad scores higher on 5 of 6 criteria (Channels in one queue, Knowledge base & deflection, Ticketing, queues & SLA, plus 2 more). Provenance — OTRS: EU-Made, Germany; Zammad: EU-Made, Germany. Ratings are the AI panel’s opinion, formed from public evidence: how scores are made.
The short answer
Zammad leads on ticketing core 7.0 vs 4.0, omnichannel 6.5 vs 2.3, knowledge self-service 5.7 vs 2.0 and pricing transparency 6.8 vs 0.8, with the lean 6–0 for Zammad on those criteria. Pricing is not weighted in OTRS's verdicts — the vendor publishes no prices, noted as B2B norm — while Zammad's verdict quotes Starter v2 at 7€ and Plus v2 at 25€ per agent / month. OTRS holds sovereignty at 5.2 vs 4.7, a 4–2 lean for OTRS: its data residency is listed as EU by default and hosting as self-hostable, while Zammad's residency and hosting entries are unknown, its verdict citing German ISO27001-certified data centres. Customer data protection splits 1–3 toward Zammad with 2 ties at 3.3 vs 3.7, Zammad's verdict finding no public information on a data processing agreement, retention rules or an agent-access audit log. Integrations splits 3–3 at 6.2 vs 5.5. Weighted totals span 5.2–6.3 for Zammad, 3.2–4.3 for OTRS.
Choose OTRS if
You need data residency in the EU by default plus self-hostable hosting: OTRS lists data residency as EU by default and hosting as self-hostable, while Zammad's entries for both are unknown.
Your procurement weights vendor sovereignty most: the sovereignty column leans 4 judges for OTRS against 2 for Zammad, at 5.2 vs 4.7.
You buy through quote-based B2B sales: pricing is not weighted in OTRS's verdicts, and the vendor publishes no prices, noted as B2B norm.
You read customer data protection as a near-tie: one judge leans OTRS, three lean Zammad and two tie, at 3.3 vs 3.7.
Choose Zammad if
You need a strong ticketing core: the lean is 6–0 for Zammad at 7.0 vs 4.0, with response, update and solution SLAs, per-customer business-hour calendars and escalation notifications documented in its verdict.
Your customers reach you across channels: omnichannel leans 6–0 for Zammad at 6.5 vs 2.3.
You need a self-service knowledge base: it leans 6–0 for Zammad at 5.7 vs 2.0.
You need published per-agent prices before buying: Zammad quotes Starter v2 at 7€, Professional v2 at 16€ and Plus v2 at 25€ per agent / month, and pricing transparency leans 6–0 at 6.8 vs 0.8.
Your team wants open source you can run yourself: Zammad is listed as copyleft, GPL v3 per its verdict, offered hosted or self-hosted.
Read this comparison as one judge. Each weighs the same scores by what they care about.
The Shop Operator
Handles "where is my parcel" at volume and needs the order in front of the agent without a second login. Judges omnichannel by whether WhatsApp and the shop actually land in one queue, and deflection by whether the ticket count falls in December.
OTRS
Zammad
This judge's pick
Criterion by criterion
Ticketing, queues & SLA
OTRS
Every ticket carries a unique ticket number, tickets can be classified and prioritized, and every change lands in the ticket history, with content access controlled through list and permission management. Business process automation, workflows and reporting are named as features, and queues appear in the managed setup. The captured pages do not show SLA targets, response-time reporting or search across tickets, so I cannot place this higher than solid mid-level.
Zammad
The SLA engine is genuinely documented: response, update and solution SLAs scoped to freely combinable ticket groups, business-hour calendars per customer with multiple calendars, and escalation notifications when the deadline hits, plus triggers, macros, templates, bulk actions and full-text search. We found no public information on merge and split, skills- or load-based assignment, or first-response reporting broken down by agent and queue — standard reporting is as granular as the pages get.
Channels in one queue
OTRS
The channel evidence I found is an email server configuration plus Active Directory/LDAP and a customer backend in the managed setup, and a customer portal reference for requesters' requests and incidents. We found no public information on live chat, telephony, WhatsApp or other messengers, or social channels landing in one queue, so as far as the captured pages go, the messenger traffic my shop runs never joins the ticket queue.
Zammad
WhatsApp does land in the queue: every message on the WhatsApp Business account automatically generates a ticket managed from the Zammad interface, and the chat widget only displays when an agent is online with remaining capacity. Email, web form, SMS, Telegram, Facebook and a listed telephony integration complete the picture, all feeding one structured ticket view with the customer's history. We found no public information on a customer portal where requesters see their own tickets, on call logging for telephony, or on WhatsApp consent handling.
Knowledge base & deflection
OTRS
Knowledge management appears in the use-case list, and that is the whole of the knowledge evidence. We found no public information on a help centre, article workflow, article suggestions to agents or customers, or any deflection reporting, so I cannot credit deflection the way I measure it.
Zammad
There is a genuine help centre where customers solve issues without opening a ticket, with multilingual articles, categories, full-text search, scheduled publishing and category-based editing rights granted by admins. We found no public information on article suggestions to customers before they submit or to agents while answering, on versioning or review dates, or on reporting of which articles actually deflect — so I cannot predict whether the December ticket count would fall.
Customer data protection
OTRS
There is a privacy policy with technical and organisational measures, a named data protection officer, and documented rights to correction, deletion, restriction, objection and portability, while inside the product list and permission management controls who can access content and ticket changes are stored in history. We found no public information on a data processing agreement, on deletion of a requester's ticket data, or on retention rules per queue, which caps this below the audit-ready level.
Zammad
A GDPR privacy policy listing all subject rights, a named data protection officer, a statement that data is never sold, two-factor authentication, device management and an ISO27001-certified data centre give a solid policy floor, with agent permissions and category-level rights limiting what agents can touch. We found no public information on a data processing agreement, on retention or deletion rules for the ticket archive itself, or on an audit log — the deletion statements captured concern the vendor's own contact forms, not customer tickets.
Integrations & API
OTRS
More than twenty named integrations are documented across categories — HubSpot for customer sync and ticket mirroring, GitLab, Asana, Azure DevOps, monitoring tools like Icinga and Checkmk, asset tools, plus Active Directory, Azure and SSO integration as agent and customer backends — with ready-to-use connectors and a REST API to extend anything. For a shop operator I have to note we found no shop or order system among the named integrations, and the pages give no app marketplace, rate limits or sandbox.
Zammad
API-first is claimed and documented: anything doable through the interface can be done via the REST/JSON API, with three authentication methods, official PHP and Ruby clients, scope-restricted tokens and pagination, while webhooks carry HMAC signatures with customisable JSON payloads since version 6.0 and named use cases for Teams, Slack, RocketChat and CRM. We found no public information on an app marketplace, SSO or SCIM provisioning, documented rate limits, or order context from a shop system shown inside the ticket — which is the second-login problem I care about most.
European sovereignty
OTRS
The contracting entity is a German GmbH registered in Oberursel with a Frankfurt commercial register entry, managed cloud data is stored in Germany by default, and the on-premise option keeps the archive on our own servers, which is the strongest control I can ask for. Against that, the data-centre provider behind the managed offering is unnamed, we found no public information on a data processing agreement, and the privacy policy allows processors outside the EU in contract performance.
Zammad
Zammad GmbH in Berlin with a German commercial register entry is the contracting party, the pricing pages state hosted plans run on servers in German data centres with ISO27001 certification, and GPL v3 code with a real self-hosting route means the archive can sit on my own infrastructure. We found no public information on a data processing agreement or the subprocessor chain for the hosted product.
Pricing transparency
OTRS
The captured pages give no price figure for any tier or edition; purchasing runs through a How to Buy route and the trial is arranged on request, quoted as 'Let us know, and we'll set up a trial instance for you.' A support lead cannot compute the annual invoice for their agent count from what is published here.
Zammad
All three hosted tiers are public per agent and month — Starter v2 at 7€, Professional v2 at 16€, Plus v2 at 25€ — with agent limits of 5, 35 and unlimited, channels, storage and support hours per tier, prices stated as plus statutory VAT, and the optional AI add-on priced at €0.03 per AI call, so I can compute the annual software invoice for my agent count. We found no public information on minimum contract terms, telephony or messenger costs, or pricing for the self-hosted route.
Sovereignty, side by side
Dimension
OTRS
Zammad
Legal entity
Incorporated in DE
Incorporated in DE
Hosting location
EU by default
Not determined
Hosting options
Self-hostable
Not determined
Open source
Not determined
Open source (copyleft)
Data processing agreement
Not determined
Not determined
Transfer impact assessment
Not determined
Not determined
Facts, side by side
Only facts both products carry under the same definition — anything else would not be a fair row.
As of 18 Nov 2026, the panel rates Zammad higher: 3/5 against 2/5. Weighted by what each judge cares about, 0 of the 6 judges pick OTRS and 6 pick Zammad. Which one fits depends on the criteria that matter to you; the table on this page shows both side by side, and each judge’s reading has its own page. Both were scored by the same AI bench under the same rubric, from public evidence only, as the methodology describes.
Is OTRS or Zammad European?
OTRS is European (EU-Made, Germany). Zammad is European (EU-Made, Germany). Provenance is read from each company’s own legal pages: who builds it and who owns it.
Where do OTRS and Zammad store customer data?
Per the vendors’ own pages as captured — OTRS: In the EU by default. Zammad: its pages as captured do not say.