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 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
Znuny
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.
Znuny
Queues as permission objects, mail dispatch by rule, owner and responsible assignment, priorities, merge and split, and SLA management for first response, update and solution time with escalation overviews, escalation notifications and multiple working-time calendars are all documented. We found no public information on macros and triggers, skills- or load-based assignment, or reporting of response and resolution times 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.
Znuny
Email collection from any number of accounts across IMAP, POP3 and Microsoft Graph, phone with CTI, a customer self-service portal where requesters see their own tickets, and messenger and text channels via add-ons are all documented as part of the ticket system. We found no public information on call logging detail, messenger consent handling, or social channels, so this sits between the documented channel set and a fully unified, consent-documented one.
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.
Znuny
A central FAQ module is documented, integrated into the customer self-service portal so customers can reach it at any time, with FAQ suggestions and a customer survey module. We found no public information on article draft and publish states, multilingual articles, review dates or versioning, or reporting on which content deflects tickets.
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.
Znuny
A granular rights and roles model is documented — seven basic queue permissions plus extended per-action permissions, queue-level visibility, two-factor authentication, and PGP and S/MIME encryption of email — which genuinely limits what an agent can see and do. As data protection officer I must record that we found no public information on retention or deletion rules, an audit log of who read or changed a ticket, redaction of ticket content, attachment handling, or a data processing agreement, and no statement on whether vendor support can open a customer instance.
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.
Znuny
REST and SOAP web services, integration of identity management systems, and a self-host, extend, integrate posture with PGP-signed and checksum-verified releases are documented. We found no public information on named CRM or shop integrations, an app marketplace, webhooks, or SSO and SCIM provisioning.
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.
Znuny
Znuny GmbH of Berlin is evidenced as the responsible contracting entity with a German commercial register entry and VAT number, and the software can be self-hosted — which as this buyer I weigh heavily, since it puts the archive on infrastructure the operator controls, with signed releases. Data residency of the managed offering, the subprocessor chain and a data processing agreement remain unknown in the captured pages, and there is no statement on whether vendor support can read customer 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.
Znuny
The self-hosted software is publicly stated as free — "Free as free can be" — with signed downloads available. Managed hosting with backups, updates and SLA-backed support and professional services are offered, but we found no public prices for them, so a support lead cannot compute those invoices from the captured 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.