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 Skeptic
Counts the channel logos on the marketing page, then asks which of them share one queue and one history. Reads for the tier where SLA policies begin, what a "light agent" may actually do, and whether the AI summariser is included or metered.
OTRS
Zammad
This judge's pick
Criterion by criterion
Ticketing, queues & SLA
OTRS
Tickets carry a unique ID, can be classified and prioritized, and every change is stored in the ticket history; business process automation and workflows are stated at marketing-page level, and queues, permissions and an agent dashboard appear in the managed setup list. I read for where the SLA policies begin and found none: no SLA targets, escalation rules or response-time reporting on any captured page, and reporting is a single word on the homepage.
Zammad
The SLA machinery is well documented: response, update and solution deadlines, business-hour calendars with multiple calendars per customer, escalation notifications, and SLAs scoped to freely combinable ticket groups, alongside macros, triggers, automation rules and full-text search. SLAs first appear in the Professional feature list rather than the entry tier, and we found no public information on merge and split, skills- or load-based assignment, or reporting broken down by agent and queue.
Channels in one queue
OTRS
Counting the channels that actually write into the queue: the managed setup configures an email server, and that is the one channel the captured pages document. The integration directory lists DevOps, monitoring and asset tools rather than chat, telephony or messenger connectors, so we found no public information on anything beyond email landing in one history.
Zammad
WhatsApp explicitly generates tickets answered from the same interface, and email, web form, SMS, chat and Telegram are listed — though Facebook and WhatsApp arrive only on the top plan. Telephony appears as a named integration with no call-logging detail on the captured pages, and we found no public information on messenger consent handling or a portal where requesters see their own tickets.
Knowledge base & deflection
OTRS
Knowledge management appears as a word in the use-case list and content can be made accessible or excluded through list and permission management — an internal content store at most. We found no public information on a searchable public help centre, article workflow, suggestions to customers or agents, or deflection reporting; the FAQs mentioned belong to the vendor's own download and support portal.
Zammad
A searchable knowledge base with categories, scheduled publishing, wiki-style linking and multilingual articles — though multilinguality is on the top plan while the mid plan is monolingual, and authoring is gated to admins by default. We found no public information on article suggestions before submission or while an agent answers, on draft and publish states, or on reporting of which articles deflect, even though the help centre is said to let customers solve issues without opening a ticket.
Customer data protection
OTRS
The privacy policy, data-protection officer and subject-rights text govern the vendor's own website and marketing data, and the retention periods given — six months for applicant data, ten years of email archiving for tax law — likewise concern the vendor, not a customer's ticket archive. Product-side there are queues and permission management; we found no public information on a data processing agreement, documented ticket deletion, retention rules per queue, or an audit log of agent access.
Zammad
A German GDPR privacy policy names a data protection officer, lists the full set of subject rights, and the product documents role-based permissions down to knowledge-base authoring. We found no public information on a data processing agreement, per-queue retention, audit logs, redaction or attachment handling; the documented automatic deletion covers inquiries sent to the vendor's own website rather than ticket data inside a customer's instance.
Integrations & API
OTRS
A long named catalogue — HubSpot, Asana, GitLab, GitHub, Azure DevOps, monitoring and asset systems, Active Directory and Azure backends — across fourteen categories, plus a REST API named on the marketing page and SSO integration in the managed setup. But the pages show pairing blurbs, not a maintained marketplace, and we found no public information on documented rate limits, a sandbox, SCIM provisioning or webhooks.
Zammad
An API-first REST/JSON API with three authentication methods, restrictable tokens, official PHP and Ruby clients and pagination, plus webhooks with HMAC signatures, custom payloads and stated use cases including Teams, Slack and CRM. GitHub/GitLab integration and Grafana reporting sit on the top plan, and we found no public information on an app marketplace, SSO or SCIM provisioning, documented rate limits or a sandbox.
European sovereignty
OTRS
The contracting entity is German — EasyVista-OTRS GmbH in Oberursel, registered in Frankfurt — managed instances store data in Germany by default, and an on-premise option gives complete control over system and server. The servers belong to an unnamed third-party provider, the privacy policy reserves the use of processors outside the European Union, and we found no public information on a data processing agreement or a published list of subprocessors for the product itself.
Zammad
Zammad GmbH in Berlin is the contracting entity, hosted plans run on servers in German data centres described as ISO27001-certified, and the GPL v3 codebase can be downloaded and self-hosted entirely. We found no public information on a data processing agreement or on which subprocessors touch the hosted ticket archive; the published subprocessors (Matomo, Moosend, Vimeo) concern the vendor's website.
Pricing transparency
OTRS
We found no price figure on any captured page — not a per-agent price, a tier or an add-on — and the only pricing-adjacent items are a "How to Buy" link and a trial the vendor sets up after you "let us know". A support lead cannot compute any part of the annual invoice from these pages.
Zammad
All three tiers are priced per agent per month with feature and channel matrices, agent caps, storage and attachment limits, VAT stated as excluded, and the AI summariser explicitly metered at €0.03 per AI call rather than included. We found no public information on telephony or messenger costs, a minimum term, or differences between monthly and annual billing.
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.