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 Shop Operator
Handles "where is my parcel" at volume and needs the order in front of the agent without a second login. Judges omnichannel by whether WhatsApp and the shop actually land in one queue, and deflection by whether the ticket count falls in December.
OTRS
Znuny
This judge's pick
Criterion by criterion
Ticketing, queues & SLA
OTRS
Every ticket carries a unique ticket number, tickets can be classified and prioritized, and every change lands in the ticket history, with content access controlled through list and permission management. Business process automation, workflows and reporting are named as features, and queues appear in the managed setup. The captured pages do not show SLA targets, response-time reporting or search across tickets, so I cannot place this higher than solid mid-level.
Znuny
Queues grouped by department, service, product or country with per-queue user groups, email dispatched by queue or recipient, and SLA management for first response, update and solution time backed by working-time calendars, timezone support, escalation notifications and an escalations overview, plus splitting and merging of tickets. We found no public information on reporting of first-response and resolution time by agent or queue, skills- or load-based assignment, or macros.
Channels in one queue
OTRS
The channel evidence I found is an email server configuration plus Active Directory/LDAP and a customer backend in the managed setup, and a customer portal reference for requesters' requests and incidents. We found no public information on live chat, telephony, WhatsApp or other messengers, or social channels landing in one queue, so as far as the captured pages go, the messenger traffic my shop runs never joins the ticket queue.
Znuny
Email, a customer self-service portal where requesters view their own tickets and status, phone with CTI and customer search, and messenger and text message channels that can be added with add-ons are all documented. Messenger consent handling is not stated on any page I read, and no live chat or social channel is shown, so the WhatsApp queue is not evidenced as landing in the box out of the box.
Knowledge base & deflection
OTRS
Knowledge management appears in the use-case list, and that is the whole of the knowledge evidence. We found no public information on a help centre, article workflow, article suggestions to agents or customers, or any deflection reporting, so I cannot credit deflection the way I measure it.
Znuny
A central FAQ module stores knowledge, FAQ suggestions exist, and the knowledge database is integrated into the customer self-service portal and accessible by customers at any time. We found no public information on a searchable public help centre with categories and publishing states, multilingual or versioned articles, or reporting on which articles deflect tickets.
Customer data protection
OTRS
There is a privacy policy with technical and organisational measures, a named data protection officer, and documented rights to correction, deletion, restriction, objection and portability, while inside the product list and permission management controls who can access content and ticket changes are stored in history. We found no public information on a data processing agreement, on deletion of a requester's ticket data, or on retention rules per queue, which caps this below the audit-ready level.
Znuny
The rights-and-roles concept is thorough — seven basic permissions per queue plus extended permissions that must be switched on in system configuration — with two-factor authentication, PGP and S/MIME email encryption, and ISO/IEC 27001:2022 and SOC 2 Type 2 certification of the vendor organisations. We found no public information on a data processing agreement, retention or deletion rules, an audit log of agent access, or redaction of ticket content.
Integrations & API
OTRS
More than twenty named integrations are documented across categories — HubSpot for customer sync and ticket mirroring, GitLab, Asana, Azure DevOps, monitoring tools like Icinga and Checkmk, asset tools, plus Active Directory, Azure and SSO integration as agent and customer backends — with ready-to-use connectors and a REST API to extend anything. For a shop operator I have to note we found no shop or order system among the named integrations, and the pages give no app marketplace, rate limits or sandbox.
Znuny
Webservices over REST and SOAP are listed as available, alongside integration of identity management systems, S/MIME certificates from an LDAP and support for system monitoring tools. We found no public information on named CRM or shop integrations, webhooks, an app marketplace, or customer order data from another system shown inside the ticket.
European sovereignty
OTRS
The contracting entity is a German GmbH registered in Oberursel with a Frankfurt commercial register entry, managed cloud data is stored in Germany by default, and the on-premise option keeps the archive on our own servers, which is the strongest control I can ask for. Against that, the data-centre provider behind the managed offering is unnamed, we found no public information on a data processing agreement, and the privacy policy allows processors outside the EU in contract performance.
Znuny
The contracting entity is Znuny GmbH in Berlin with a German commercial register and VAT number, and the platform is fully self-hostable from checksummed and PGP-signed source and RPM downloads, which puts the ticket archive on the buyer's own infrastructure. The captured pages leave the managed-hosting location, the DPA and the subprocessor chain unstated, and group entities Znuny Inc. and Znuny Swiss GmbH are named without a stated seat.
Pricing transparency
OTRS
The captured pages give no price figure for any tier or edition; purchasing runs through a How to Buy route and the trial is arranged on request, quoted as 'Let us know, and we'll set up a trial instance for you.' A support lead cannot compute the annual invoice for their agent count from what is published here.
Znuny
The software itself is stated as "Free as free can be", which makes the licence cost fully public. The managed hosting with backups, updates and SLA-backed support and the professional services carry no public prices on the captured pages, so the real annual invoice for a hosted deployment is not computable from public pages alone.
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.