As of 18 Nov 2026, the panel rates OTRS 2/5 and Znuny 2.5/5 in Customer Service & Helpdesk. Weighted by what each judge cares about, 1 of the 6 judges picks OTRS and 5 pick Znuny. OTRS scores higher on 2 of 6 criteria (Integrations & API and European sovereignty). Znuny scores higher on 3 of 6 criteria (Channels in one queue, Ticketing, queues & SLA and Knowledge base & deflection). Provenance — OTRS: EU-Made, Germany; Znuny: EU-Made, Germany. Ratings are the AI panel’s opinion, formed from public evidence: how scores are made.
The short answer
On criterion means, Znuny leads ticketing core (6.8 vs 4.0), omnichannel (5.7 vs 2.3), knowledge and self-service (4.0 vs 2.0) and pricing transparency (3.7 vs 0.8), six judges leaning Znuny on each; OTRS publishes no prices. OTRS leads integrations (5.5 vs 3.8) and sovereignty (5.2 vs 4.0), six judges leaning OTRS on each. Customer data protection is the genuine split: identical 3.3 means, two judges lean OTRS, two lean Znuny, two tie. Weighted totals run Znuny's way for the support lead (5.3 vs 3.9), agent advocate (5.4 vs 3.4), data protection officer (4.3 vs 4.2), ecommerce operator (4.5 vs 3.8) and skeptic (4.3 vs 3.2); the integrator goes to OTRS (4.3 vs 4.1). Both list legal-entity jurisdiction DE and self-hostable hosting options; OTRS's data residency attribute reads "eu default", Znuny's is unknown. The leans differ by criterion and judge, so this comparison declares no overall winner.
Choose OTRS if
Your stack depends on connecting many third-party tools — integrations is the criterion where six judges lean OTRS (5.5 vs 3.8 mean).
You weight sovereignty heaviest in the decision — six judges lean OTRS on sovereignty (5.2 vs 4.0 mean).
You need EU-default data residency on record — OTRS's data residency attribute reads 'eu default', while Znuny's data residency attribute is unknown.
An integrator leads your buying committee — the integrator's weighted total is 4.3 for OTRS vs 4.1 for Znuny.
Choose Znuny if
You need SLA management, escalation overviews and multiple working-time calendars in the ticketing core — Znuny's verdict documents these, and ticketing core leans Znuny six judges to zero (6.8 vs 4.0 mean).
Your support model must span channels — omnichannel leans Znuny six judges to zero (5.7 vs 2.3 mean).
You rely on a customer self-service FAQ portal — knowledge and self-service leans Znuny six judges to zero (4.0 vs 2.0 mean).
Published pricing decides your shortlist — pricing transparency leans Znuny six judges to zero (3.7 vs 0.8 mean); OTRS publishes no prices, and Znuny's verdict states the licence is free.
A support lead or agent advocate runs the selection — their weighted totals favor Znuny (5.3 vs 3.9, and 5.4 vs 3.4).
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
Znuny
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.
Znuny
This is a real queue engine: queues as permission objects with drill-down views, escalation management with SLAs for first response, update and solution time, multiple working-time calendars with timezone support, and merge and split. What the captured pages do not show is macros or triggers, skills- or load-based assignment, and any reporting on first-response or resolution time by agent and queue — the hundredth reply still depends on those.
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.
Znuny
Email collected from any number of mailboxes, a customer self-service portal where requesters see their own tickets and status, phone with CTI, and messenger and text channels via add-ons — all landing as tickets in one queue structure. We found no public information on live chat, social channels, or consent handling for the messenger add-ons, and nothing stating that a customer's earlier conversations are surfaced to the agent.
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.
Znuny
There is a central FAQ module, FAQ suggestions, and a knowledge database published to customers through the self-service portal at any time — self-service exists, in other words. The captured pages say nothing about categories and branding, draft and publish workflow, multilingual articles, or any reporting on which articles deflect, so knowledge here is documented as a storage place, not a managed asset.
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.
Znuny
Access control is genuinely granular: seven queue-level permissions plus extended permissions, a rights-and-roles concept, two-factor authentication, and PGP and S/MIME email encryption, with the vendor organisation ISO 27001 and SOC 2 certified. On the archive itself the pages are silent — we found no public information on retention or deletion rules, an audit log of agent access, redaction of ticket content, or a data processing agreement.
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.
Znuny
REST and SOAP webservices, identity-management integration, support for system-monitoring tools, and an add-on route for extra channels — enough wire to connect real systems, and you can self-host and extend it. We found no named CRM or shop integrations, no webhooks, no marketplace evidence, and no view of the API documentation's depth, so this sits below the level where customer context from other systems is shown inside the ticket.
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.
Znuny
Znuny GmbH in Berlin with a German commercial register and VAT number is the responsible entity, the software is self-hostable so the ticket archive can live on your own infrastructure, and the organisation holds ISO 27001 and SOC 2 certifications. Where the managed hosting actually runs, the subprocessor chain, and any DPA are not established by the captured pages, so the chain is proven at the front end only.
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.
Znuny
The software itself is "Free as free can be" — the download is public and the licence invoice for any agent count is zero, which I can compute without a sales call. But the managed hosting with backups, updates and SLA-backed support, and the professional services, carry no public figures, so a buyer wanting the hosted route cannot price it from these pages.
Sovereignty, side by side
Dimension
OTRS
Znuny
Legal entity
Incorporated in DE
Incorporated in DE
Hosting location
EU by default
Not determined
Hosting options
Self-hostable
Self-hostable
Open source
Not determined
Not determined
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
Znuny
Legal · Commercial register
Amtsgericht Frankfurt am Main · HRB 143059 · commercial register B1
As of 18 Nov 2026, the panel rates Znuny higher: 2.5/5 against 2/5. Weighted by what each judge cares about, 1 of the 6 judges picks OTRS and 5 pick Znuny. 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 Znuny European?
OTRS is European (EU-Made, Germany). Znuny 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 Znuny store customer data?
Per the vendors’ own pages as captured — OTRS: In the EU by default. Znuny: its pages as captured do not say.
Do OTRS and Znuny have a free plan?
As of 18 Nov 2026, Znuny’s own pages state a free plan; OTRS’s pages as captured do not. Each product page links the pricing page it was read from.