OTRS vs Zammad

OTRS

EU-Made

Sovereignty: 3 of 6 dimensions proven

Full evaluation →

Zammad

EU-Made

Sovereignty: 2 of 6 dimensions proven

Full evaluation →

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 Support Lead

Runs a team of twelve against an SLA the sales team promised. Wants routing that reflects skill, timers that warn before they breach, and reporting she can take to a quarterly review. Reads "AI-powered" as a claim to be checked against the queue on a Monday morning.

OTRS

Zammad

This judge's pick

Criterion by criterion

Ticketing, queues & SLA

OTRS

A real ticket engine is documented: every ticket gets a unique ticket number, changes are reliably stored in the ticket history, tickets can be classified and prioritized, and queues, permissions and an agent dashboard appear in the managed setup, with automation and reporting named as headline features. I found no public information on SLA targets, breach warnings, escalation or search across tickets — the timers my team lives by — so I can't take it past the middle.

Zammad

The SLA machinery is what I'd want on my wall: response, update and solution deadlines, business-hour calendars you can keep per customer, escalation notifications when the time is reached, and SLAs scoped to freely combined ticket groups — plus macros, triggers and overviews. I found no public information on warnings before a breach, merge and split, skills- or load-based assignment, or reporting broken down by agent and queue, so it stops short of the top of the scale.

Channels in one queue

OTRS

We found no public information on which customer channels — email, chat, phone, portal or messengers — land in one queue with one history. The pages we read describe tickets, integrations and hosting, but say nothing about inbound channels for requesters.

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 chat widget only appears when an agent has capacity, which I respect. Telephony is named as an integration without documented call logging, and I found no public information on a customer portal or on consent handling for the messengers.

Knowledge base & deflection

OTRS

Knowledge management appears only as a term in the use-case list on the homepage. We found no public information on articles, a help centre, publishing workflow, article suggestions or deflection reporting, so this barely registers.

Zammad

A multilingual help centre with search, category-based edit rights and scheduled publishing is documented, and the vendor states customers solve common issues without opening a ticket — deflection as an intention, not yet a number. I found no public information on article suggestions before a customer submits or while an agent answers, stale-content flags, or reporting on which articles deflect.

Customer data protection

OTRS

The privacy pages name a data protection officer, list subject rights from correction through erasure and portability, state technical and organisational measures, and set concrete retention periods for the data the vendor collects; the product pages document list and permission management over who can see content. We found no public information on a data processing agreement, on retention or deletion of ticket archives specifically, or on audit logs and redaction.

Zammad

There is a published privacy policy naming a data protection officer and the full set of GDPR rights, agent permissions with role-based limits, and two-factor authentication with device management. I found no public information on a data processing agreement, on retention or deletion rules for tickets, or on an audit log of agent access — and the deletion statements on the captured pages concern the vendor's own website inquiries rather than the helpdesk product.

Integrations & API

OTRS

Roughly twenty named connectors across monitoring, asset and inventory, DevOps, HR and customer synchronisation — HubSpot, Active Directory, Azure, GitLab and Icinga among them — plus ready-to-use connectors, a REST API described as extending anything, and SSO with an LDAP and customer backend configured in the managed setup. We found no public information on webhooks, SCIM provisioning, rate limits, a sandbox or an app marketplace, which holds it below the top band.

Zammad

"API first" is stated to mean anything doable in the interface is doable through the REST API, with three authentication methods, restricted-scope tokens, official PHP and Ruby clients, and webhooks with HMAC signatures carrying full ticket context — plus named GitHub/GitLab integration. I found no public information on an app marketplace, SSO or SCIM provisioning, documented rate limits or a sandbox, which holds it below the top of the scale.

European sovereignty

OTRS

The contracting entity is EasyVista-OTRS GmbH, registered in Oberursel with a Frankfurt commercial register entry; the managed cloud stores data on servers in Germany by default, and an on-premises option gives complete control over system and server. The privacy policy itself states processors could also be used outside the European Union, and we found no public information on a published data processing agreement or on the named hosting provider, so the chain is only partly established.

Zammad

The contracting entity is Zammad GmbH in Berlin, the hosted service is stated to run in ISO 27001-certified German data centres, and the entire codebase is open source under GPL v3 with a self-hosting route if I need the archive on my own infrastructure. The chain stops there: I found no public information on a data processing agreement or a subprocessor list with locations for the hosted service, and no data-centre provider is named.

Pricing transparency

OTRS

No price figure appears anywhere on the pages we read; the only public offer is a free trial set up on request, alongside a How to Buy link. We found no public per-agent or tier pricing, so I cannot compute an annual invoice for my twelve agents from these pages.

Zammad

Three tiers are priced per agent per month — Starter v2 at 7€, Professional v2 at 16€, Plus v2 at 25€ — with agent caps of 5, 35 and unlimited, plus storage, attachment limits, channels and support hours per tier, VAT stated as exclusive, and the optional AI features at €0.03 per AI call. What I cannot compute from the public pages: telephony or messenger costs, an annual invoice figure, or a minimum term.

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.

Fact OTRS Zammad
Integrations · Rest API REST API · yes1

captured 16 Nov 2026 · Report an error

REST · yes · JSON2

captured 16 Nov 2026 · Report an error

Legal · Address Oberursel · Zimmersmühlenweg 11 · Germany · 614403

captured 16 Nov 2026 · Report an error

10117 · Berlin · Marienstraße 18 · Germany4

captured 16 Nov 2026 · Report an error

Legal · Commercial register Amtsgericht Frankfurt am Main · HRB 143059 · commercial register B3

captured 16 Nov 2026 · Report an error

Charlottenburg · HRB 163946 B4

captured 16 Nov 2026 · Report an error

Legal · Entity Zimmersmühlenweg 11, 61440 Oberursel, Germany · OTRS GmbH5

captured 15 Sep 2026 · Report an error

Zammad GmbH · support@zammad.com · Marienstraße 18, 10117 Berlin6

captured 16 Nov 2026 · Report an error

Legal · Entity name EasyVista-OTRS GmbH3

captured 16 Nov 2026 · Report an error

Zammad GmbH4

captured 16 Nov 2026 · Report an error

Pricing · Trial yes7

captured 16 Nov 2026 · Report an error

30 · yes8

captured 16 Nov 2026 · Report an error

Product · Use cases Service Management, Security Management, Task Management, Asset Management, Technology Management, Knowledge Management, Vulnerability Management, Ticketing System, Security Incident Management, ITSM, ITIL Processes, Issue Tracking, ISO 27001, ISMS, Help Desk, Enterprise Service Management, Device Management, Customer Service Software, Corporate Security, CMDB, BPMS9

captured 16 Nov 2026 · Report an error

customer service · IT support · internal inquiries · HR10

captured 16 Nov 2026 · Report an error

Subprocessors · Matomo on-premise · web analytics · yes11

captured 1 Oct 2026 · Report an error

Matomo · no · statistische Auswertung von Besucherzugriffen6

captured 16 Nov 2026 · Report an error

Subprocessors · Vimeo Vimeo · product videos on website12

captured 16 Nov 2026 · Report an error

Vimeo LLC · eingebettete Videos6

captured 16 Nov 2026 · Report an error

Questions about OTRS and Zammad

Which is better, OTRS or Zammad?

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.