Comparison of Znuny and OTOBO Ticket Systems

Znuny and OTOBO are forks of the now-discontinued OTRS Community Edition and have evolved into independent open-source ticket systems. Both solutions are among the best-known OTRS forks and offer numerous features for the efficient management of customer support requests. Nevertheless, they differ in several key aspects. In the following Znuny vs OTOBO comparison, we highlight similarities and differences – from the range of functions, Docker support, and REST API to artificial intelligence (AI), installation, and demo options.

OTOBO: A Modern Open-Source Ticket System

OTOBO is based on OTRS 6 and extends it with modern features and an improved user experience. It is a web-based helpdesk system for managing customer requests. The main features of OTOBO include:

Modern Customer Portal: Completely redesigned, user-friendly interface for end users, also optimized for mobile devices.
Optimized Forms: Simplified ticket creation through configurable forms and input fields.
Advanced Security Features: e.g., password policies, brute-force protection, two-factor authentication (2FA), and fine-grained access rights.
Easy Migration from OTRS: Integrated migration scripts enable a smooth transition from an OTRS 6 installation to OTOBO.
Elasticsearch Live Search: Faster and more precise search results through the integration of Elasticsearch for full-text search.
Integration with OpenStreetMap: Geographical data can be displayed directly in the ticket (useful, for example, for location-based tickets).
Flexible Escalation Options: Advanced escalation rules for better control in escalation management.
GDPR Support: Functions for compliance with GDPR (e.g., anonymizing tickets) are integrated.
Improved Performance: Revised codebase and caching (Redis) lead to faster response times.
AI-Powered Ticket Classification: An optional AI plugin is available that uses machine learning to automatically categorize tickets and assign priorities.

Znuny: The Evolutionary Successor to OTRS

Znuny is the direct continuation of the OTRS project by the community (maintained by Znuny GmbH) and focuses on long-term stability and compatibility, supplemented by selected innovations. The outstanding features and characteristics of Znuny include:

Continuous Development: Znuny receives regular updates with bug fixes and new features. For example, newer versions have added features such as appointment filtering in the calendar, OAuth2 support for external services (Invoker), user mentions (@-mentions in ticket notes), and text snippets.
Security and Compliance Options: Support for nested LDAP groups for rights assignment, improved S/MIME handling (key management), and further security updates ensure a secure system.
Flexible Customizability: Through a package system and the GenericInterface web services, Znuny can be extensively extended and integrated into other systems. Filter options and ACLs allow for individual configuration of the interface and processes.
Audit Compliance: All ticket changes are logged completely, ensuring that changes and actions are traceable at all times (important, for example, for auditable processes).
ITIL Components Available: Znuny offers optional add-ons such as the ITSM module (including CMDB for asset management) and FAQ module as free extensions to provide a range of functions similar to the former OTRS::ITSM suite.
Strong Community Support: As the official community fork of OTRS, Znuny has an active forum and community contributions. Many formerly paid OTRS features have been continued in Znuny by the community.

Versions and Current Developments

Both projects have continuously evolved since the split from OTRS and regularly release new versions:

OTOBO Version 10 (first released in 2020) forms the basis of the current OTOBO installation. This version introduced the modernized web interface and numerous improvements mentioned above. Since then, regular patch releases (e.g., 10.0.17, 10.0.18, etc.) have been published, providing bug fixes and minor features. OTOBO Version 11 has already been announced for the future, which is expected to bring further optimizations and new features (Softoft has published preliminary information on this). The OTOBO developers (Rother OSS GmbH) value an innovative roadmap – for example, an AI integration was provided early on as an optional module.
Znuny adopted the OTRS 6 codebase and initially maintained it as Znuny 6 (including Znuny LTS 6.5, a long-term support version for companies that prioritize maximum stability). In March 2023, Znuny 7.0 was released, representing a significant step forward: the customer interface was 70% redesigned (Welcome Znuny 7) to be more modern and user-friendly, while the agent interface was carefully modernized but kept intentionally familiar (Welcome Znuny 7). Currently (early 2025), Znuny 7.1 is the stable main version, and Znuny 7.2 is already planned for Q3 2025 (Roadmap). Znuny 7 also brings technical modernizations “under the hood” intended to facilitate future adjustments and extensions (Welcome Znuny 7). Important to mention: Znuny 7.x are feature releases and require active maintenance by the user, while Znuny LTS 6.5 continues to receive security updates until at least the end of 2025 (Roadmap). Thus, Znuny offers both a conservative LTS track and a progressive release track.

Comparison of Functionalities

Below is a tabular comparison of important features of OTOBO and Znuny:

Feature	OTOBO	Znuny
Basis	Fork of OTRS Community Edition 6	Fork of OTRS Community Edition 6
Developer	Rother OSS GmbH (initiator and main developer)	Znuny GmbH (led by former OTRS community developers)
License	100% Open Source (GNU GPL v3) – no proprietary modules	100% Open Source (GNU GPL v3) – fully freely available
Docker Support	Yes – official Docker images and Docker-Compose templates for a fast installation are available	No official images (installation classically on Linux server or via unofficial community Docker containers)
Customer Portal	Completely redesigned customer portal (modern UI, responsive design, intuitive operation)	Customer portal from OTRS 6 with improvements; partially redesigned in Znuny 7, but not developed from scratch like in OTOBO
Elasticsearch	Integrated with advanced configuration options (complex index configuration, live search)	Integrated as an optional search engine with standard functions from OTRS (indexing of basic ticket fields)
OAuth2 for Email	Yes – supports OAuth2 for IMAP/POP3 since OTOBO 10.0.11 (e.g., for Office 365 without insecure Basic Auth)	Currently limited – direct OAuth2 support for email accounts is expected in Znuny 7.2 via the Microsoft Graph API (Roadmap) (workarounds necessary until then)
Migration Tools	Migration from OTRS 6 to OTOBO is supported (scripts and instructions available)	Migration from OTRS 6 to Znuny seamlessly possible; taking over an existing OTOBO database to Znuny has also been successfully performed by the community (with conversion steps)
Community	Active community, forum, and regular contributions (still smaller than Znuny, but steadily growing)	Very active community with official forum (community.znuny.org) and many extensions by users
Security Updates	Regular security patches by the developers (Rother OSS) and community contributions	Regular security patches and bugfix releases (Znuny GmbH provides updates promptly, especially for LTS versions)

Further Functions

Function	OTOBO	Znuny
Workflow/Process Management	Yes – comprehensive support (incl. graphical process designer for workflows)	Yes – basic support (process management from OTRS 6, functional but less comfortable)
ITIL/ITSM Components	Yes – ITSM modules (change management, configuration management/CMDB, etc.) are integrated or available as packages	Yes – ITSM (incl. CMDB) available as a free add-on (ported and installable for Znuny 7) (Welcome Znuny 7)
Reporting & Analytics	Extensive statistics and reports via integrated statistics module, additional graphical evaluations possible via add-on	Standard statistics module from OTRS with predefined reports (expandable via community add-ons)
API Support	Yes – REST API and SOAP web services (Generic Interface) for integration with third-party systems, incl. extended endpoints in OTOBO 10	Yes – REST and SOAP API (GenericInterface) analogous to OTRS, fully compatible; extensions possible via additional web service packages
SLA Management	Yes – comprehensive SLA and service management (contracts, response/solution times per service definable)	Yes – SLA management analogous to OTRS (definition of service times and escalations per queue/service possible)
Multi-Channel Support	Yes – email, web portal, phone tickets, chat (via add-on), and much more.	Yes – email, web portal, phone. (Chat or social media via third-party add-ons)
Mobile Access	Partially – customer frontend is responsive; agent UI optimized for desktop, mobile use via browser possible with limitations	Partially – similar to OTOBO: customer portal in Znuny 7 responsive; agent interface primarily designed for desktop
Integration of External Tools	Yes – numerous integrations (e.g., calendar sync, CRM connection, chatbots) available; flexible connection via REST/SOAP	Yes – integrations via GenericInterface (REST/SOAP) and community add-ons (e.g., for monitoring tools, CMDB import, etc.)
Paid Features	None – all features are open-source (community-driven; support and hosting potentially chargeable via service providers)	None – Znuny is fully open-source; professional support optionally available via Znuny GmbH or partners

(Table: Differences and similarities between OTOBO and Znuny)

Docker Support in Znuny and OTOBO

An important aspect when choosing a ticket system is deployment and installation. Here, the approaches of the two forks differ significantly regarding Docker:

OTOBO provides a Docker environment out-of-the-box. Official Docker images are available, and using Docker-Compose, a complete OTOBO system (web server, database, Redis cache, Elasticsearch, etc.) can be installed and started within a very short time. This significantly simplifies testing and production deployments, as dependencies are preconfigured. The OTOBO documentation offers a dedicated section for installation with Docker and lists the containers (e.g., otobo_web_1, otobo_db_1, otobo_elastic_1, etc.) used for operation. Through this comprehensive Docker integration, OTOBO is ready for use very quickly, and updates can also be carried out easily in container environments.

Znuny, on the other hand, does not provide official Docker images. The preferred installation method for Znuny is the classic installation on a Linux server (Debian/Ubuntu, Red Hat, CentOS, etc.) via package manager or source code installation. Although unofficial Docker containers from the community exist (e.g., on Docker Hub from third-party providers), these are not maintained by the Znuny project itself. Admins who want to use Znuny via containers can fall back on these community projects but should note that official support focuses on traditional installations. For Znuny, this means a bit more manual effort during setup, but in return, full control over the server environment. Many Znuny users appreciate the classic installation because it is based on the OTRS deployment. Nevertheless, the call for official Docker images has become louder in the Znuny community – perhaps a change could come here in the future, but as of now, OTOBO clearly scores points.

REST API and Integrations

Both Znuny and OTOBO offer powerful interfaces for integration into existing system landscapes. Via the GenericInterface, REST and SOAP web services can be defined to, for example, create tickets externally, retrieve them, or perform other actions.

In OTOBO, the REST API has been further improved and expanded. The OTOBO documentation describes in detail how various automations can be implemented via REST. Typical use cases are the connection of CRM systems, automatic ticket creation from forms, or integration with chatbots. OTOBO offers some pre-built endpoints out-of-the-box, and custom endpoints can be added via configuration. OAuth2 authentication for API access can also be configured to ensure secure integrations.

Znuny relies on proven compatibility when it comes to the API. All web service interfaces known from OTRS function identically in Znuny. As a result, companies that already had integrations based on the OTRS API can switch to Znuny seamlessly without having to adjust their interfaces. The Znuny REST API also allows CRUD operations on tickets, users, articles, etc. Web services (REST/SOAP) can be set up via the admin interface with mapping configurations. Differences from OTOBO arise less in the functionality of the API itself – both systems support similar use cases – and more in the documentation and further development: OTOBO documents the REST API extensively in its own manual and might potentially offer extended API functions in the future, while Znuny focuses on keeping the existing interfaces stable and backward compatible. In practice, the “Znuny REST API” and “OTOBO REST API” are equally capable – the choice of system is influenced here more by other factors than by the API.

Artificial Intelligence in the Ticket System

An exciting distinguishing feature is the use of artificial intelligence (AI) to support the ticket process. Here, OTOBO set accents early on, while Znuny remains (still) reserved:

OTOBO offers an optional AI module for ticket classification. This plugin (also called OTOBO AI) uses machine learning algorithms to automatically analyze incoming tickets and suggest categories and priorities. For example, it can recognize which queue or topic is likely based on the subject and content and pre-fill the ticket accordingly. The AI module runs in a separate Docker container and communicates with the OTOBO core via an interface. The advantages of this solution are accelerated response times and relief for support staff during the pre-qualification of requests. The artificial intelligence in OTOBO is still in its infancy but is already showing clear efficiency gains in pilot projects. Furthermore, the community is experimenting with chatbot integration and NLP tools in the OTOBO context.

Znuny currently has no integrated AI function. Topics such as automatic categorization or AI-supported response suggestions are not officially covered by Znuny (as of 2025). However, one can extend Znuny with AI by connecting external AI services – for example, tickets can be sent to an external machine learning service via the REST API, and its evaluations can be returned. This, however, requires individual customizing. The Znuny community does have the topic “AI in Znuny” on its radar, but the project’s focus is more on stability and core functions. Companies that want to benefit from AI immediately tend to choose OTOBO or implement their own solutions for Znuny. It remains to be seen whether future Znuny versions will integrate AI features directly, but currently, OTOBO is clearly ahead in terms of artificial intelligence in the ticket system.

Installation and Demo Availability

Both ticket systems are open-source and can be installed freely. The installation of Znuny and OTOBO follows classic OTRS principles, but OTOBO has opened up additional paths that make getting started easier:

Znuny Installation: Znuny is typically installed on a Linux server. Official packages (RPM/DEB) and instructions exist for common distributions, and the installation involves setting up Perl modules, web server (Apache/Nginx), and a database (MySQL/MariaDB or PostgreSQL). Znuny provides tutorials and the well-known OTRS Installer-Bash for this purpose. Since Znuny corresponds to OTRS 6, administrators with OTRS experience can perform the installation very familiarly. There is no official port for Windows – Znuny is aimed at server operation under Linux/Unix. Help with the Znuny installation can be found in abundance in the official documentation and the community forum.
OTOBO Installation: OTOBO can also be installed manually on Linux (similar to Znuny, with Apache/Perl/etc.). However, the developers recommend the Docker-based installation, which drastically simplifies the process. With provided Docker-Compose files, OTOBO can be pulled up in minutes, including all components. This reduces misconfigurations and facilitates updates. Alternatively, Rother OSS also provides a package repository for Ubuntu, so that installation and updating can be done via apt. Overall, the initial installation in “Znuny vs OTOBO” tends to be completed faster with OTOBO thanks to Docker, while Znuny follows more traditional setup steps. Both systems require similar prerequisites (Perl 5, database, web server); differences lie more in the provided installation paths.

As for demo availability, there are also differences: A Znuny demo for direct testing is not publicly offered by the project itself – interested parties must install Znuny independently or use one of the unofficial demo containers. OTOBO, on the other hand, can be tested easily: either use the Docker installation locally, or contact service providers like Softoft, who offer a hosted OTOBO demo. A form is available on the official OTOBO website to request a personal demo. This allows potential users to experience OTOBO’s interface and functions live in advance without having to install it themselves. In summary: those looking for an environment to try out quickly will find it easier with OTOBO, while with Znuny, one should be prepared to perform a short installation – which, with some Docker experience, can also be done very quickly.

Areas of Application and Advantages

Both systems are suitable for a variety of areas of application in service management. Znuny and OTOBO are successfully used for IT support/helpdesk, customer service hotlines, internal ITIL processes (incident/problem/change management), facility management, and many other scenarios. Due to the common OTRS root, both serve a similar purpose, but depending on the requirements, one or the other system may offer advantages:

Znuny plays to its strengths primarily where stability, long-term support, and continuity are required. Companies that have worked with OTRS for a long time appreciate the familiar environment in Znuny and the assurance of long-term security updates (especially with the LTS version). Furthermore, a large pool of community modules exists around Znuny, enabling special industry solutions. The learning curve for OTRS-experienced administrators and agents is minimal – one feels at home immediately.
OTOBO scores in environments that prioritize modern features and user-friendliness. The new customer portal and the fresh UI elements are well-received by end users. Features like Elastic search or integrated AI increase efficiency in the support process. Thanks to Docker, OTOBO can be quickly scaled in cloud environments or duplicated for testing purposes. OTOBO is often chosen by organizations that take a more innovative path and are not afraid to use a slightly younger fork with smaller (but agile) developer teams.

Ultimately, the decision Znuny vs. OTOBO depends on the specific requirements, the existing infrastructure, and the strategic goals of the company. Both solutions are free of charge and open-source, so there is no license risk – it comes down to which priorities are set (stability vs. innovation, familiarity vs. modern UI, etc.).

Conclusion

Znuny and OTOBO share common roots in the OTRS Community Edition but continue to develop in partially different directions. OTOBO impresses with a modern user interface, additional features (e.g., AI module), and convenient deployment via Docker. Znuny focuses on reliability and strong community support – it integrates innovations carefully and ensures long-term maintenance of the OTRS heritage. There is no clear “winner”: both ticket systems are among the best open-source solutions on the market. The choice between them ultimately depends on the individual needs and preferences of the user. It is recommended to try both – if possible – in a demo or test environment to find out which solution is most suitable for your own company. In any case, one benefits from the flexibility and know-how of the OTRS community, which lives on in both projects.

Sources

Znuny Website: Official website of the Znuny project with downloads, documentation, and blog.
OTOBO Website: Official website of OTOBO (project page of Rother OSS GmbH) with feature descriptions and announcements of new versions.
Znuny Roadmap & Blog: Announcements regarding Znuny 7 (e.g., UI redesign, planned OAuth2 support) on znuny.org.
OTOBO Documentation: Online documentation on otobo-docs.softoft.de (including Docker installation and REST API, as well as AI plugin).
Community Forums: Exchange of experience on Znuny and OTOBO in forums (community.znuny.org, OTOBO Forum) – e.g., reports on migration from OTOBO to Znuny, or use of Docker for OTRS forks.