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 Data Protection Officer
Sees a ticket archive for what it is: years of personal data customers typed themselves, including the things they should not have. Wants retention that executes, redaction, an audit of who read what, and an answer on whether vendor support can open a ticket.
OTRS
Zammad
This judge's pick
Criterion by criterion
Ticketing, queues & SLA
OTRS
Tickets carry unique ticket numbers, can be classified and prioritised, live in queues with their own permissions, and every change is reliably stored in the ticket history — a change log I want kept. Business process automation and reporting are named on the homepage. We found no public information on SLA targets, response-time reporting, escalation or search across the archive, so the evidence reaches routing and tracking, not managed workloads.
Zammad
Tickets carry states, assignment and escalation, and the SLA machinery is real: response, update and solution deadlines scoped to freely combined ticket groups, multiple business-hour calendars, and escalation notifications when a deadline is reached. Macros, text modules, templates, triggers, bulk actions, ticket history and full-text search are all documented. We found no public information on merge and split, skills- or load-based ticket assignment, or reporting broken down by agent and queue.
Channels in one queue
OTRS
The on-premises and managed documentation names an email server configuration and an OTRS customer portal for customers' requests and incidents — email plus one further channel. We found no public information on live chat, telephony, messengers or social channels arriving in one shared inbox with one history.
Zammad
Email, web form, SMS, chat, Telegram, Facebook and WhatsApp all land as tickets — WhatsApp generates a ticket per incoming message and is answered from the same interface — and the vendor describes one structured ticket view holding all communication, the customer profile and history. Telephony appears as a named integration, but we found no public information on call logging, and we found no public information on a requester-facing portal where a customer can see their own tickets.
Knowledge base & deflection
OTRS
Knowledge management appears once as a use-case label on the homepage, and the FAQs and online documentation mentioned are the vendor's own support channels, with FAQ viewing tied to an OTRS ID registration. We found no public information on a product help centre with published articles, a draft or review workflow, article suggestions, or deflection reporting.
Zammad
A help centre is positioned explicitly so customers can solve issues without opening a ticket, and the knowledge base is documented as multilingual and searchable, with categories, category-based editing rights, scheduled publishing and wiki-style links from tickets to answers. We found no public information on article suggestions to agents in replies or to customers before submitting, on versioning or review dates, or on reporting that measures deflection.
Customer data protection
OTRS
A privacy policy in German and English names an external data protection officer, grants correction, deletion, restriction, objection and portability rights and states technical and organisational measures, while the product side shows permission management, queue-level permissions and a ticket history storing every change. The retention periods actually published — ten years of email archiving, five years for business contacts, three for trial registrations — concern the vendor's own website and applicant data, not a customer's ticket archive. We found no public information on a data processing agreement, automatic retention or deletion of tickets, redaction of ticket content, an audit of which agent read what, or whether the vendor's support staff can open a customer ticket.
Zammad
The privacy policy names a data protection officer, enumerates the full set of GDPR rights, commits that data is never sold, and documents automatic deletion of inquiry and contact-form data plus statutory retention for payment data, with German ISO 27001-certified data centres, two-factor authentication, device management and role-based permissions behind it. But what is documented is the website's data lifecycle, not the ticket archive's: we found no public information on a data processing agreement for the service, retention rules per queue, redaction of ticket content, an audit log of agent access, or whether vendor support can open a hosted customer's tickets.
Integrations & API
OTRS
More than twenty named integrations are documented across fourteen categories, from identity (Active Directory, Azure) and CRM (HubSpot) to DevOps (GitHub, GitLab) and monitoring (Icinga, Checkmk, Grafana), alongside a REST API, ready-to-use connectors and SSO configuration in the managed onboarding. We found no public information on an app marketplace, documented rate limits, a sandbox or SCIM provisioning, so the API's depth rests on the availability claim alone.
Zammad
The REST/JSON API is documented as API-first — anything the interface can do the API can do — with three authentication methods, scope-restricted tokens, pagination, official PHP and Ruby clients, and webhooks since version 3.6 carrying custom JSON payloads verified by HMAC signature. Named integrations cover GitHub/GitLab and reporting via Elasticsearch and Grafana; we found no public information on an app marketplace, SSO or SCIM provisioning, rate limits, or a sandbox.
European sovereignty
OTRS
The contracting entity is a German GmbH registered in Frankfurt with a German VAT number, the managed offering stores data in Germany by default with the USA or Canada on request, an on-premises option gives complete control over system and server, and ISO 27001 is claimed for the managed infrastructure. Non-EU processors are at least named in the privacy policy with standard contractual clauses as the safeguard. The hosting runs on unnamed third-party servers, and we found no public information on a published data processing agreement, a subprocessor list with locations for the service itself, or which vendor staff can reach a managed instance.
Zammad
Zammad GmbH is the contracting entity with a Berlin address and commercial register entry, the hosted plans run on the vendor's own servers in German ISO 27001-certified data centres, and the full GPL v3 codebase is downloadable and self-hostable — an option that lets a buyer keep the archive entirely on their own infrastructure. The subprocessor names the privacy policy publishes (Matomo, Moosend, Vimeo LLC of New York) concern the vendor's website rather than the service; we found no public information on a published data processing agreement, the data-centre provider's name, or vendor support access to hosted instances.
Pricing transparency
OTRS
No price figure appears on any captured page — no per-agent rate, no tier, no 'from' price — and even the free trial is something the vendor sets up after you "let us know". A "How to Buy" navigation item points into what is evidently a sales conversation. A support lead cannot compute any part of the annual invoice from these pages.
Zammad
All three tiers are priced publicly per agent per month — Starter v2 at 7€, Professional v2 at 16€, Plus v2 at 25€ — with agent caps (5, 35, unlimited), channel lists, attachment and disk limits, support hours, prices explicitly exclusive of statutory VAT, and optional AI features metered at €0.03 per AI call. A 30-day free trial and a plan finder are offered; we found no public information on telephony or messenger costs or on minimum contract terms.
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.