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 Integrator
Has to wire the helpdesk into a CRM, a shop and an identity provider that all predate it. Wants a documented API with rate limits, webhooks that retry, SCIM, and a sandbox. Reads a partner-contact form on an integrations page as a missing API.
OTRS
Zammad
This judge's pick
Criterion by criterion
Ticketing, queues & SLA
OTRS
Every ticket gets a unique number, classification and priority, changes are reliably stored in a ticket history, and queues, permissions, an agent dashboard, automation and workflows are all named on the product pages. What I could not find anywhere I read is an SLA target, response-time reporting, rule-based routing to teams and agents, or documented search across tickets — for a suite marketed as ITIL-aligned I expected the SLA machinery to be visible, and on these pages it is not.
Zammad
Business-hour calendars drive the escalation maths, response and solution SLAs scope to freely combinable ticket groups, and a ticket that reaches its SLA time escalates and notifies the agents who opted in — a genuine engine, with macros, triggers, text modules and full-text search all documented. Standard reporting plus deeper Elasticsearch reporting via Grafana is asserted, but we found no public information on per-agent or per-queue breakdowns, merge and split, or skills- or load-based assignment.
Channels in one queue
OTRS
The captured pages show an email server as a configured channel and an OTRS customer portal for end customers' requests and incidents, which is email plus one further channel. I found no public information on live chat, telephony, messengers or social channels landing in the same queue, so the evidence reaches exactly two channels and stops.
Zammad
Email, web form, SMS, chat and Telegram land as tickets in one structured view with the customer's history, and on the top plan Facebook and WhatsApp join them — WhatsApp with a setup guide that states prerequisites and limitations, and a chat widget that only displays when an agent has capacity. Telephony appears as a named integration with no call logging documented, we found no public information on a customer portal where requesters see their own tickets, and the channel list narrows on the lower tiers.
Knowledge base & deflection
OTRS
Knowledge management appears in the solutions and use-case lists and FAQs are mentioned, but nothing I read documents articles, draft and publish states, suggestions to agents or customers, multilingual content or deflection reporting. I cannot wire deflection expectations from a keyword in a tag cloud.
Zammad
A searchable help centre with categories, rich-text articles with attachments and embedded images, scheduled publishing, multilingual content and wiki-style linking from tickets to answers is documented, with multilingual knowledge base gated to the higher plan. We found no public information on article suggestions to customers before they submit or to agents while answering, on review dates or versioning, or on reporting that says which articles deflect — and only admins write articles unless permission is explicitly granted, so the article workflow is thin for agents.
Customer data protection
OTRS
Agent-facing limits are documented — queues and permissions, list and permission management over ticket content, and a reliable ticket history — alongside a published GDPR/Trust Center page and ISO 27001-managed infrastructure. I found no public information on a data processing agreement, product-level retention or deletion of ticket and requester data, attachment handling, redaction, or an audit log of agent access, so the product-side evidence sits at roles and permissions.
Zammad
The published privacy policy is squarely GDPR-framed: a named data protection officer in Berlin, the full rights catalogue including deletion and portability, an explicit no-sale statement, and 2FA, device management and an ISO27001-certified German data centre on the plan pages. That documentation, though, covers the vendor's own website; 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 of agent access.
Integrations & API
OTRS
This is the strong suit for my stack: twenty-plus named integrations with sync language — HubSpot for customer synchronization, GitLab for ticket mirroring, GitHub for defect sync — plus Active Directory and Azure as external agent and customer backends, SSO integration in the managed configuration, ready-to-use connectors and a REST API named on both language versions of the integrations page. But the REST API is a marketing sentence, not a specification: I found no public information on rate limits, webhooks, SCIM provisioning, a sandbox or developer documentation of any depth, and no named shop or order-system integration despite a procurement-and-ERP category.
Zammad
This is what I build against, and the foundation is unusually well documented: an API-first claim that anything the interface does the REST API does, three authentication methods including OAuth2, scope-restricted API tokens, pagination on all resources, official PHP and Ruby clients, and webhooks with HMAC signatures, custom payloads and a documented payload of tickets, articles, users, roles, organizations and groups; GitHub/GitLab integration and Slack, Teams and RocketChat use cases appear by name. We found no public information on documented rate limits, a sandbox, SSO or SCIM provisioning, or an app marketplace — the public GPL v3 source and self-hosting option soften that, but I want rate limits in writing before wiring a CRM to this.
European sovereignty
OTRS
The legal notice names EasyVista-OTRS GmbH of Oberursel, registered at the Frankfurt court, managed instances default to German hosting with USA or Canada only on request, on-premise gives complete control over system and server, and the website's own analytics run on a self-hosted Matomo. The chain underneath is thin: managed data sits on unnamed third-party provider servers, the privacy policy allows processors outside the EU for contract performance, and I found no published data processing agreement or product subprocessor list with locations.
Zammad
The chain I care about is documented German: Zammad GmbH in Berlin with a commercial register number, hosted plans on servers in German ISO27001-certified data centres, and — rare in this market — a full-feature open-source build under GPL v3 that I can download and run on my own infrastructure, with the code public and no vendor lock-in claimed. We found no public information on a data processing agreement, the data-centre provider is not named, and the subprocessor disclosure covers the marketing website — Matomo, Moosend and Vimeo in New York — rather than the hosted helpdesk service.
Pricing transparency
OTRS
I found no public prices on any page I read; the trial is contact-gated — "Want to try OTRS for free? Let us know, and we'll set up a trial instance for you" — and the homepage's How to Buy section carried no figures in the captured pages. No support lead can compute an annual invoice for an agent count from what is published here.
Zammad
Three hosted tiers are priced per agent / month — Starter v2 at 7€ capped at 5 agents, Professional v2 at 16€ with a maximum of 35, Plus v2 at 25€ with unlimited agents — each with its channel list, storage, attachment size and feature set published, VAT stated as exclusive of statutory VAT, the optional AI features metered at €0.03 per AI call, plus a 30-day free trial and a plan finder. We found no public information on minimum terms or separate telephony and messenger channel costs, so the base invoice is computable from public pages while the metered edges are not.
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.