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 Agent Advocate

Has answered tickets for six years and judges every tool by the hundredth reply, not the first. Wants search that finds the old thread, macros that save real keystrokes, and one screen rather than four tabs. Treats agent-activity dashboards as a smell.

OTRS

Zammad

This judge's pick

Criterion by criterion

Ticketing, queues & SLA

OTRS

Every ticket gets a unique ticket number, changes are reliably stored in the ticket history, and the pages list classification, prioritisation, queues and a generic business-process automation claim. I found no public information on SLA targets, escalation, macros, merge and split, or search across a large ticket base, so I cannot go higher than just past basic ticket tracking.

Zammad

Response, solution and issue-based SLAs tied to business-hour calendars — with multiple calendars for customers on different hours, escalation at breach and notifications only inside working hours — is an engine that survives contact with a Monday morning. Macros, text modules, triggers, core workflows and one structured ticket view with full-text search are documented; we found no public information on merge and split, skills- or load-based assignment, or response and resolution reporting broken down by agent and queue.

Channels in one queue

OTRS

The captured pages document an email server as part of the managed setup and a customer portal for customers' requests and incidents, which is email plus a portal. Beyond that I found no public information on live chat, telephony or messengers landing in one queue with one history.

Zammad

Email, web form, SMS, chat, Telegram, Facebook and WhatsApp are listed per plan, and the WhatsApp integration is documented to open a ticket per message and be answered from the same interface — that is the one-screen promise I judge channels by. We found no public information on a customer portal where requesters see their own tickets, on call logging behind the stated telephony integration, or on WhatsApp consent handling beyond a pointer to prerequisites and limitations.

Knowledge base & deflection

OTRS

Knowledge management appears as a term in the solutions and use-case lists, and nothing more. I found no public information on a public help centre, article workflow, suggestions to agents or customers before submission, or deflection reporting.

Zammad

A customer-facing help centre and a multilingual knowledge base with full-text search, categories, scheduled publishing and category-based editing rights are documented, and the vendor states customers solve common issues without opening a ticket — deflection as intent, though not yet as a measured number. We found no public information on article suggestions to the agent while answering or to the customer before submitting, or on reporting about which articles deflect.

Customer data protection

OTRS

There is a published privacy statement with a named data protection officer, stated subject rights including erasure and portability, and concrete deletion timelines, plus in-product permission management that can include or exclude users from content. The data processing agreement question is open on these pages, and I found no public information on product-level retention rules per queue, redaction of ticket content, or an audit log of agent access.

Zammad

The privacy policy names a data protection officer, lists the subject rights from information through deletion to portability, states that data will in no case be sold, and documents automatic deletion of contact-form data, while an ISO27001-certified data centre, 2FA, device management and individual roles sit on the trust and pricing pages. We found no public information on a data processing agreement, per-queue retention or deletion rules, an audit log of agent access, or redaction of ticket content.

Integrations & API

OTRS

Two dozen named integrations across monitoring, DevOps, asset management and CRM (HubSpot, Asana, GitLab, Checkmk, Active Directory), ready-to-use connectors, a documented REST API, and SSO integration in the managed setup. I found no public information on webhooks calling other systems, SCIM provisioning, documented rate limits or a sandbox, so it stops at a solid middle rating.

Zammad

The API is documented as API-first — anything the interface can do can be done via REST — with three authentication methods, restrictable API tokens, official PHP and Ruby clients, and webhooks since version 3.6 that POST ticket, article, user and organization payloads with optional HMAC signing; GitHub/GitLab and Elasticsearch/Grafana are named integrations. We found no public information on an app marketplace, SSO or SCIM provisioning, documented rate limits, or a sandbox.

European sovereignty

OTRS

A German contracting entity registered at the Frankfurt court, managed cloud data stored by default in Germany with optional USA or Canada regions on request, and a self-hostable on-premise option that keeps the archive on the customer's own servers. The third-party hosting provider is not named, the privacy policy allows processors outside the EU, and I found no published data processing agreement or product subprocessor list with locations.

Zammad

Zammad GmbH is registered in Berlin, the hosted service is stated to run on servers in German, ISO27001-certified data centres, and the GPL-v3 codebase is fully self-hostable, so a buyer who wants the archive on their own infrastructure has a real option. We found no public information on a data processing agreement or on the subprocessor chain for the hosted archive; the privacy policy names only website tools such as Matomo, Moosend and Vimeo.

Pricing transparency

OTRS

I found no public prices on any page captured here; the only commercial signals are a free trial instance set up on request and a How to Buy section. A support lead cannot compute the annual invoice for their agent count from these pages, so every purchase is a conversation.

Zammad

All three hosted tiers are public — Starter v2 at 7€, Professional v2 at 16€ and Plus v2 at 25€ per agent / month — with agent limits of 5, 35 and unlimited, per-tier channels, storage, attachments and support hours, prices stated as excluding statutory VAT, and the optional AI feature priced at €0.03 per AI call, so the invoice for a given agent count is computable from the pricing pages. We found no public information on minimum contract term or separate telephony costs.

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.