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 Integrator
Has to wire the helpdesk into a CRM, a shop and an identity provider that all predate it. Wants a documented API with rate limits, webhooks that retry, SCIM, and a sandbox. Reads a partner-contact form on an integrations page as a missing API.
OTRS
This judge's pick
Znuny
Criterion by criterion
Ticketing, queues & SLA
OTRS
Every ticket gets a unique number, classification and priority, changes are reliably stored in a ticket history, and queues, permissions, an agent dashboard, automation and workflows are all named on the product pages. What I could not find anywhere I read is an SLA target, response-time reporting, rule-based routing to teams and agents, or documented search across tickets — for a suite marketed as ITIL-aligned I expected the SLA machinery to be visible, and on these pages it is not.
Znuny
Queues are first-class permission objects assigned to user groups with drill-down views, mail can be dispatched to a queue by recipient rule, and the escalation feature set documents SLA management for first response, update and solution time with an escalation overview, dedicated notifications and multiple working-time calendars — a business-hours-aware SLA engine, not a shared inbox. Splitting and merging tickets and ticket watch are also documented. We found no public information on skills- or load-based assignment or on first-response and resolution reporting broken down by agent and queue, which holds this below the top band.
Channels in one queue
OTRS
The captured pages show an email server as a configured channel and an OTRS customer portal for end customers' requests and incidents, which is email plus one further channel. I found no public information on live chat, telephony, messengers or social channels landing in the same queue, so the evidence reaches exactly two channels and stops.
Znuny
Email, phone with CTI and a customer self-service portal are all documented as channels, and in the portal customers can view their previous tickets and their status, so earlier conversations carry over. Messenger and text message channels arrive only via add-ons, and we found no public information on live chat, social channels, or consent handling for messengers, which keeps this clearly short of the full multi-channel band.
Knowledge base & deflection
OTRS
Knowledge management appears in the solutions and use-case lists and FAQs are mentioned, but nothing I read documents articles, draft and publish states, suggestions to agents or customers, multilingual content or deflection reporting. I cannot wire deflection expectations from a keyword in a tag cloud.
Znuny
A central FAQ module for storing knowledge is integrated into the customer self-service portal and can be accessed by customers at any time, with FAQ suggestions listed as a feature. We found no public information on draft and publish workflow, versioning or review dates, multilingual articles, or reporting on which articles deflect tickets, so this is a real knowledge base but not a managed one.
Customer data protection
OTRS
Agent-facing limits are documented — queues and permissions, list and permission management over ticket content, and a reliable ticket history — alongside a published GDPR/Trust Center page and ISO 27001-managed infrastructure. I found no public information on a data processing agreement, product-level retention or deletion of ticket and requester data, attachment handling, redaction, or an audit log of agent access, so the product-side evidence sits at roles and permissions.
Znuny
Queue-level access control is documented in depth — seven basic permissions from read-only to full access, extended permissions for screens such as close, forward and compose — alongside two-factor authentication, PGP and S/MIME encryption and a rights-and-roles concept. We found no public information on a data processing agreement, retention or deletion rules for tickets or requesters, an audit log of agent access, or redaction, so only the access-control side of this criterion is evidenced.
Integrations & API
OTRS
This is the strong suit for my stack: twenty-plus named integrations with sync language — HubSpot for customer synchronization, GitLab for ticket mirroring, GitHub for defect sync — plus Active Directory and Azure as external agent and customer backends, SSO integration in the managed configuration, ready-to-use connectors and a REST API named on both language versions of the integrations page. But the REST API is a marketing sentence, not a specification: I found no public information on rate limits, webhooks, SCIM provisioning, a sandbox or developer documentation of any depth, and no named shop or order-system integration despite a procurement-and-ERP category.
Znuny
The channels page lists webservices over REST and SOAP and the security page lists integration of identity management systems with S/MIME certificates from an LDAP, so a systems person has something to wire against. But that is a feature bullet, not a developer story: we found no public information on API documentation, rate limits, webhooks and their retry behaviour, SCIM provisioning, a sandbox, or maintained connectors for CRM or shop systems — for my CRM-and-identity wiring that is thin.
European sovereignty
OTRS
The legal notice names EasyVista-OTRS GmbH of Oberursel, registered at the Frankfurt court, managed instances default to German hosting with USA or Canada only on request, on-premise gives complete control over system and server, and the website's own analytics run on a self-hosted Matomo. The chain underneath is thin: managed data sits on unnamed third-party provider servers, the privacy policy allows processors outside the EU for contract performance, and I found no published data processing agreement or product subprocessor list with locations.
Znuny
Znuny GmbH in Berlin, with a German commercial register entry and a German VAT number, is the responsible contracting entity, and the platform is self-hostable, so the ticket archive can live on infrastructure the buyer controls; ISO/IEC 27001:2022 and SOC 2 Type 2 certification are stated for the organisations. The location of the managed hosting, a data processing agreement and the subprocessor chain are not established by the captured pages, and the group also names Znuny Inc. and Znuny Swiss GmbH without stating their seats.
Pricing transparency
OTRS
I found no public prices on any page I read; the trial is contact-gated — "Want to try OTRS for free? Let us know, and we'll set up a trial instance for you" — and the homepage's How to Buy section carried no figures in the captured pages. No support lead can compute an annual invoice for an agent count from what is published here.
Znuny
The software itself is publicly stated as free — "Free as free can be" — with the download openly available, so the licence line of a self-hosted deployment is computable at zero. We found no public information on prices for the managed hosting with SLA-backed support or for professional services, so the real annual cost of a supported deployment is a conversation rather than a calculation.
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.