OTRS vs Znuny

OTRS

EU-Made

Sovereignty: 3 of 6 dimensions proven

Full evaluation →

Znuny

EU-Made

Sovereignty: 2 of 6 dimensions proven

Full evaluation →

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 Skeptic

Counts the channel logos on the marketing page, then asks which of them share one queue and one history. Reads for the tier where SLA policies begin, what a "light agent" may actually do, and whether the AI summariser is included or metered.

OTRS

Znuny

This judge's pick

Criterion by criterion

Ticketing, queues & SLA

OTRS

Tickets carry a unique ID, can be classified and prioritized, and every change is stored in the ticket history; business process automation and workflows are stated at marketing-page level, and queues, permissions and an agent dashboard appear in the managed setup list. I read for where the SLA policies begin and found none: no SLA targets, escalation rules or response-time reporting on any captured page, and reporting is a single word on the homepage.

Znuny

SLA management for first response, update and solution time sits in the documented core, alongside an escalation overview, dedicated escalation notifications, multiple working-time calendars and timezone support — and tickets can be merged, split and watched. What holds it below the top band: assignment is queue- and group-based, and we found no public information on macros and triggers, skills- or load-based assignment, or first-response and resolution reporting by agent and queue.

Channels in one queue

OTRS

Counting the channels that actually write into the queue: the managed setup configures an email server, and that is the one channel the captured pages document. The integration directory lists DevOps, monitoring and asset tools rather than chat, telephony or messenger connectors, so we found no public information on anything beyond email landing in one history.

Znuny

Email is collected from any number of accounts into queues by rules, and the customer portal lets requesters create tickets and view their own previous ones with status; phone is listed with CTI and customer search, but the captured pages do not state that calls land as tickets in the same queue. Messenger and text-message channels exist only as add-ons, and we found no public information on live chat, social channels, consent handling, or one shared history across all channels.

Knowledge base & deflection

OTRS

Knowledge management appears as a word in the use-case list and content can be made accessible or excluded through list and permission management — an internal content store at most. We found no public information on a searchable public help centre, article workflow, suggestions to customers or agents, or deflection reporting; the FAQs mentioned belong to the vendor's own download and support portal.

Znuny

A central FAQ module is documented for storing knowledge, integrated into the customer self-service portal so customers can reach it at any time, and FAQ suggestions are named as a feature with no stated direction. We found no public information on article categories and own branding, draft-and-publish workflow, versioning or review dates, multilingual articles, or reporting on which articles deflect tickets.

Customer data protection

OTRS

The privacy policy, data-protection officer and subject-rights text govern the vendor's own website and marketing data, and the retention periods given — six months for applicant data, ten years of email archiving for tax law — likewise concern the vendor, not a customer's ticket archive. Product-side there are queues and permission management; we found no public information on a data processing agreement, documented ticket deletion, retention rules per queue, or an audit log of agent access.

Znuny

The access model is genuinely granular: seven queue-level permissions from read-only to full access, extended per-screen permissions, and a rights-and-roles concept with two-factor authentication, encrypted transfer and PGP/S-MIME email protection. What a data-protection conversation turns on is undocumented on these pages — we found no public information on a data processing agreement, retention or deletion rules, an audit log of agent access, redaction of ticket content, or attachment handling.

Integrations & API

OTRS

A long named catalogue — HubSpot, Asana, GitLab, GitHub, Azure DevOps, monitoring and asset systems, Active Directory and Azure backends — across fourteen categories, plus a REST API named on the marketing page and SSO integration in the managed setup. But the pages show pairing blurbs, not a maintained marketplace, and we found no public information on documented rate limits, a sandbox, SCIM provisioning or webhooks.

Znuny

Webservices over REST and SOAP are listed as a product feature, identity management integration and OAuth2 or Microsoft Graph mailbox authentication are documented, and the pitch is 'Self-host, extend, integrate'. We found no public information on named CRM or shop integrations, webhooks, an app marketplace, single sign-on or SCIM provisioning, or documented rate limits and a sandbox.

European sovereignty

OTRS

The contracting entity is German — EasyVista-OTRS GmbH in Oberursel, registered in Frankfurt — managed instances store data in Germany by default, and an on-premise option gives complete control over system and server. The servers belong to an unnamed third-party provider, the privacy policy reserves the use of processors outside the European Union, and we found no public information on a data processing agreement or a published list of subprocessors for the product itself.

Znuny

A German contracting entity is proven in the imprint — Znuny GmbH, Berlin, commercial register Charlottenburg — and the software is self-hostable, so a buyer can keep the ticket archive on EU infrastructure of their own choosing; the organisations also hold ISO/IEC 27001:2022 and SOC 2 Type 2 certifications. The chain around that is unstated: we found no public information on a data processing agreement, subprocessor locations, or where the managed hosting runs, and the download page's footer names Znuny Inc. and Znuny Swiss GmbH as group entities with no stated seats.

Pricing transparency

OTRS

We found no price figure on any captured page — not a per-agent price, a tier or an add-on — and the only pricing-adjacent items are a "How to Buy" link and a trial the vendor sets up after you "let us know". A support lead cannot compute any part of the annual invoice from these pages.

Znuny

The core product has one public, unambiguous price — 'Free as free can be', downloaded as self-hosted source and signed packages. The commercial side is where a support lead cannot compute an invoice: managed hosting with backups, updates and SLA-backed support, and professional services, carry no published figures on the captured pages, and the term for either is not stated.

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

captured 16 Nov 2026 · Report an error

HRB 139852 B · Charlottenburg2

captured 16 Nov 2026 · Report an error

Legal · Entity Zimmersmühlenweg 11, 61440 Oberursel, Germany · OTRS GmbH3

captured 15 Sep 2026 · Report an error

Znuny GmbH4

captured 19 Oct 2026 · Report an error

Questions about OTRS and Znuny

Which is better, OTRS or Znuny?

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.