Znuny
EU-Made Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 2 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Znuny GmbH · www.znuny.org
Compare with OTRS → Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Znuny at a glance
- Vendor
- Znuny GmbH
- Headquarters
- Incorporated in Germany source, captured 16 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 16 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 15 Sep 2026
- Panel verdict
- The AI panel rates Znuny 2.5/5, the mean of 6 judges. Znuny is an open source ITSM and helpdesk platform, a fork of the OTRS Community Edition with guaranteed long-term support. how scores are made
- As of
- Vendor pages captured 15 Sep 2026 to 16 Nov 2026; evaluated by the panel 18 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Znuny is an open source ITSM and helpdesk platform, a fork of the OTRS Community Edition with guaranteed long-term support. Ticketing core is strongest at 6-7 — SLA management for first response, update and solution time, escalation overviews and notifications, multiple working-time calendars, ticket merge, split and watch. Knowledge and self-service sits flat at 4: a central FAQ module integrated into the customer self-service portal is documented, while we found no public information on publishing workflow, multilingual articles or deflection reporting. Customer data protection spans 2 to 4 — lower scores weigh the undocumented data processing agreement, retention rules and agent-access audit log; higher ones credit granular queue-level permissions and two-factor authentication. Integrations spread 3-5 and pricing transparency 3-5; omnichannel spans 4-6, with messenger and text-message channels arriving only as add-ons. The licence is free — "Free as free can be" — while we found no public prices for managed hosting with SLA-backed support or for professional services. Sovereignty holds at 4: a Berlin contracting entity and self-hostable delivery are evidenced; managed-hosting residency and the subprocessor chain are not.
Speaks for it
- Documented SLA management for first response, update and solution time, with escalation overviews, dedicated notifications and multiple working-time calendars.
- Granular access control with seven queue-level permissions from read-only to full access, extended per-screen permissions, two-factor authentication and PGP/S/MIME email encryption.
- The vendor organisations hold ISO/IEC 27001:2022 and SOC 2 Type 2 certification.
- Self-hostable delivery with SHA-256 checksummed, PGP-signed releases keeps the ticket archive on infrastructure the buyer controls.
- The licence is publicly free — "Free as free can be" — so the licence cost of a self-hosted deployment is computable without a sales call.
Held against it
- We found no public information on macros and triggers, skills- or load-based assignment, or first-response and resolution reporting by agent and queue.
- Messenger and text-message channels arrive only as add-ons, and we found no public information on live chat, social channels or messenger consent handling.
- We found no public information on draft-and-publish workflow, versioning, multilingual articles or reporting on which articles deflect tickets.
- We found no public information on a data processing agreement, retention or deletion rules, or an audit log of agent access.
- We found no public prices for managed hosting with backups, updates and SLA-backed support, or for Znuny Professional Services.
Best for
- You want a self-hostable, open source helpdesk to run on infrastructure you control, with an SLA engine covering first response, update and solution time.
- You are moving off the OTRS Community Edition and want a successor fork with guaranteed long-term support and continued security fixes.
- You can operate the system yourself and want the licence cost stated up front as free — "Free as free can be".
Avoid if
- Your customers reach you mainly by live chat or social channels — messenger and text-message channels are add-ons, and we found no public information on live chat or social channels.
- You must budget a vendor-run deployment from public prices alone — managed hosting with SLA-backed support and professional services carry no public prices.
- You expect maintained CRM or shop connectors ready to use — the documented integration surface is webservices over REST and SOAP plus identity-management integration.
The scores
| Criterion | Panel median |
|---|---|
| Ticketing, queues & SLA | 3.5 of 5 |
| Channels in one queue | 3 of 5 |
| Knowledge base & deflection | 2 of 5 |
| Customer data protection | 2 of 5 |
| Integrations & API | 2 of 5 |
| European sovereignty | 2 of 5 |
| Pricing transparency | 2 of 5 |
Ticketing, queues & SLA
Show reasoningHide reasoning
How this is scored
The engine: how work is routed, prioritised, escalated and measured — and whether an agent can find the ticket they need among ten thousand.
0 — Not a ticketing tool: requests stay in a shared mailbox or chat with no ticket, owner or status of their own.
3 — Tickets with assignment, a status and a conversation history, worked from a shared inbox with views or filters.
5 — Tickets routed by rules or automations to teams or agents, priorities and statuses, SLA targets or response-time reporting, and search across tickets.
8 — Business-hours-aware SLA policies per queue or customer with breach warnings and escalation, macros and triggers, merge and split, skills- or load-based assignment, and reporting on first-response and resolution time by agent and queue.
10 — The workload is managed rather than merely tracked: capacity-aware assignment, SLA per contract with reporting an account manager could show a customer, audit of every status change, and search that finds the ticket from a half-remembered phrase.
The Support Lead
The escalation and SLA side is genuinely strong for my team: first response, update and solution time SLAs, a dedicated escalation overview with notifications, and multiple working-time calendars with timezone support and agent absence handling — timers that warn before they breach. Routing is queue-based with dispatch by queue or recipient, ticket merge and split, and owner or responsible assignment; we found no public information on skills- or load-based assignment, macros and triggers, or first-response and resolution reporting by agent and queue. 3 4 6 8 9
The Agent Advocate
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. 3 4 6 8
The Data Protection Officer
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. 3 4 6 8
The Shop Operator
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. 3 4 6 8
The Integrator
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. 3 6 8 4
The Skeptic
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. 3 6 8
Channels in one queue
Show reasoningHide reasoning
How this is scored
Email, chat, phone, portal, messengers and social — judged on what actually lands in the same queue with the same history, not on how many channel logos the marketing page carries.
0 — No customer channel of its own; the product only works on tickets entered by hand or by another system.
3 — Email turned into tickets, with a web form or one further channel.
5 — Email, a web form or portal and live chat or a messenger landing as tickets in one inbox, with the customer's earlier conversations visible to the agent.
8 — The above plus telephony integration with call logging, at least one messenger (WhatsApp or similar) with its consent handling stated, social channels, and a customer portal where a requester can see their own tickets — all in one history.
10 — Channel is an implementation detail: every channel including voice and messengers writes to one conversation with one history, agents answer from one screen, and the customer can move between channels mid-issue without repeating themselves.
The Support Lead
Email, phone with CTI and a customer self-service portal where requesters can see their previous tickets and status are all documented, with messenger and text-message channels available via add-ons. We found no public information on social channels, consent handling for messengers, or a single conversation history across channels. 7 8
The Agent Advocate
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. 4 7 8
The Data Protection Officer
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. 4 7 8
The Shop Operator
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. 4 7 8
The Integrator
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. 7 8 4
The Skeptic
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. 4 7 8
Knowledge base & deflection
Show reasoningHide reasoning
How this is scored
Whether the product reduces the number of tickets as well as organising them: public help centre, article workflow, suggestions to agents and to customers.
0 — No knowledge base or self-service of any kind; the product is a ticket inbox only.
3 — A knowledge base or FAQ with articles, internal or public, that agents can link in replies.
5 — A searchable public help centre with categories and its own branding, draft and publish states, and agents able to insert or suggest an article in a reply.
8 — Article suggestions to the customer before they submit and to the agent while they answer, multilingual articles, review dates or versioning that flag stale content, and reporting on which articles deflect.
10 — Knowledge is a managed asset: gaps identified from unanswered tickets, article performance measured against ticket volume by topic, versioned content with approval, and deflection reported as a number the team can act on.
The Support Lead
A central FAQ module stores knowledge and is integrated into the customer self-service portal so customers can reach it at any time, with FAQ suggestions offered. We found no public information on article categories and own branding, draft and publish workflow, multilingual content, or reporting on which articles deflect. 8
The Agent Advocate
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. 8
The Data Protection Officer
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. 8
The Shop Operator
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. 8
The Integrator
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. 8
The Skeptic
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. 8
Customer data protection
Show reasoningHide reasoning
How this is scored
A ticket archive is personal data written by the data subject. Retention, deletion, access control, subject rights under DSGVO, and what the vendor does with attachments — judged on what the product documents it executes.
0 — The vendor's own terms state that ticket content is used for purposes beyond providing the service, or that a data processing agreement is not offered.
3 — A privacy policy and a data processing agreement (DPA) offered, with agent roles that limit what an agent can do.
5 — A DPA published or signable online, agent roles and group- or queue-level visibility, and deletion of tickets or of a requester's data documented in the help centre.
8 — Automatic retention or deletion rules per queue or data category, attachment handling stated, an audit log of agent access or changes, documented support for access and erasure requests, and redaction of ticket content.
10 — Built for a data-protection audit: retention executed and evidenced per category, field-level redaction, full audit trail, subprocessor list published, and the vendor's own support access to customer instances documented and consent-gated.
The Support Lead
The rights and roles model is granular and real — seven queue-level permissions from read-only to full access, plus extended permissions, two-factor authentication, SSL transfer and PGP or S/MIME email encryption — and the vendor organisations are certified to ISO 27001 and SOC 2. We found no public information on a data processing agreement, retention or deletion rules, an audit log of agent access, or documented support for access and erasure requests. 5 9 10
The Agent Advocate
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. 3 5 9 10
The Data Protection Officer
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. 5 9
The Shop Operator
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. 5 9 10
The Integrator
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. 5 9 3
The Skeptic
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. 5 9
Integrations & API
Show reasoningHide reasoning
How this is scored
The systems a helpdesk has to reach — CRM, shop, order management, identity — and whether the API is documented for building or gated behind a partner conversation.
0 — A closed tool with no API and no integrations; context is copied in by hand.
3 — A handful of named integrations or a connector service such as Zapier, or an API with basic documentation.
5 — Named integrations for common CRM, shop or collaboration tools, a documented REST API, and webhooks or triggers that call other systems.
8 — An app marketplace with maintained bidirectional integrations, customer context from other systems shown inside the ticket, SSO and SCIM provisioning, documented rate limits and a sandbox.
10 — A component rather than a destination: versioned API with a deprecation policy, event streaming both directions, an app framework for in-ticket extensions, and integrations the vendor maintains rather than lists.
The Support Lead
REST and SOAP webservices, identity management system integration, support for system monitoring tools and an add-on mechanism are documented, on a self-hostable open-source platform a buyer can extend directly. We found no public information on named CRM or shop connectors, webhooks or triggers calling other systems, SSO and SCIM provisioning, or documented rate limits and a sandbox. 7 9 10
The Agent Advocate
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. 6 7 9 10
The Data Protection Officer
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. 7 9 10
The Shop Operator
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. 7 9
The Integrator
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. 7 9
The Skeptic
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. 7 9 10
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where the ticket archive lives, who the contracting entity is, which subprocessors touch it, and whether vendor support can read customer data. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it. Dimensions the evidence does not establish are unknown, not non-EU.
0 — Proven non-EU on every dimension the evidence covers: non-EU vendor and contracting entity and non-EU hosting, with no EU option stated.
3 — One European element proven — an EU hosting option, an EU contracting entity or EU representative, or a published DPA — with the rest of the chain unstated.
5 — EU hosting stated as standard or selectable and an EU contracting entity or EU representative, with a DPA offered; the subprocessor chain is unstated or partly non-EU.
8 — EU or DACH hosting with a named data-centre provider, EU contracting entity, subprocessor list published with locations, and any non-EU processing named with its legal basis.
10 — Sovereign end to end and evidenced: vendor, entity, hosting and every subprocessor in the EU, certification published, and a self-hosted or private-cloud option for buyers who need the archive on their own infrastructure.
The Support Lead
The contracting entity is German and well evidenced — Znuny GmbH in Berlin with a commercial register entry and a German VAT number — and the product is self-hostable, so the ticket archive can stay on our own infrastructure; managed hosting with backups, updates and SLA-backed support is offered, but where it runs is not stated. We found no public information on a data processing agreement, a subprocessor list, or the location of the managed service's processing. 2 10
The Agent Advocate
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. 2 7 10
The Data Protection Officer
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. 2 10
The Shop Operator
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. 2 10
The Integrator
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. 2 10
The Skeptic
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. 2 10
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a support lead can compute the real annual invoice for their agent count — including the channels and features they actually need — from public pages alone.
0 — No public prices at all; every tier is a sales conversation.
3 — A public "from" price or one priced tier, per agent or flat.
5 — Per-agent prices public for the main tiers with the billing period stated and the main features per tier listed.
8 — Every tier and add-on priced publicly with per-agent maths, telephony or messenger costs and light-agent or contact limits given, billing period, minimum term and VAT treatment stated; only genuinely custom enterprise work lacks a number.
10 — Complete price computability: a calculator or table producing the annual invoice for a given agent count and channel selection, including usage-metered channels and overage.
The Support Lead
The software itself is publicly free — "Free as free can be" — so the licence cost of a self-hosted deployment is stated outright. Managed hosting with SLA-backed support and Znuny Professional Services are offered without public prices, so the real annual invoice for a managed production system is not computable from public pages alone. 1 10
The Agent Advocate
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. 1 10
The Data Protection Officer
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. 1 10
The Shop Operator
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. 1 10
The Integrator
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. 1 1 10
The Skeptic
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. 1 10
European sovereignty — proven facts
2 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity |
Incorporated in DE
unverified
Why unverified?The download page footer also names Znuny Inc. and Znuny Swiss GmbH as group entities, but no excerpt states a parent company's seat; the imprint names Znuny GmbH alone with a German commercial register as the responsible company. |
2/2 pts | 2 Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options | Self-hostable | 1/1 pts | 10 Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Znuny
Is Znuny European?
Yes. whats-best.ai classifies Znuny as EU-Made. Its vendor, Znuny GmbH, is incorporated in Germany, per the vendor’s page captured 16 Nov 2026.
Where does Znuny store data?
Not stated on the vendor’s pages as of 16 Nov 2026.
Does Znuny have a free plan?
Yes. Znuny has a free plan, per the vendor’s page captured 15 Sep 2026.
What are the best alternatives to Znuny?
As of 18 Nov 2026, the panel rates Zendesk (3.5/5), LiveAgent (3.5/5) and Intercom (3.5/5) highest among the other 35 Customer Service & Helpdesk products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Zammad (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Znuny alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 15 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Legal entity. The download page footer also names Znuny Inc. and Znuny Swiss GmbH as group entities, but no excerpt states a parent company's seat; the imprint names Znuny GmbH alone with a German commercial register as the responsible company.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 2 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- The pricing here was last read more than 30 days ago. Vendors change prices without notice; the capture date is shown with every figure. Know more? Tell us
Sources (11)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.znuny.org Checked 16 Nov 2026 +1 earlier capture: 15 Sep 2026 Details →
- 2 Imprint www.znuny.org Checked 16 Nov 2026 Details →
- 3 Ticketing, queues & SLA — found from sitemap doc.znuny.org Checked 16 Nov 2026 Details →
- 4 Channels in one queue — found from sitemap doc.znuny.org Checked 16 Nov 2026 Details →
- 5 Customer data protection — found from sitemap doc.znuny.org Checked 16 Nov 2026 Details →
- 6 Ticketing, queues & SLA — found from sitemap www.znuny.org Checked 19 Oct 2026 Details →
- 7 Channels in one queue — found from sitemap www.znuny.org Checked 19 Oct 2026 Details →
- 8 Knowledge base & deflection — found from sitemap www.znuny.org Checked 19 Oct 2026 Details →
- 9 Customer data protection — found from sitemap www.znuny.org Checked 19 Oct 2026 Details →
- 10 Self-hosting / on-premises installation docs — found from the homepage download.znuny.org Checked 16 Nov 2026 Details →
- 11 Structured-data backfill: markup only, no text or screenshot www.znuny.org Checked 8 Nov 2026 Details →