OTRS Forks and Zammad Compared: Five Systems for 2026

The decision for an IT service management system (ITSM) or helpdesk is more complex for technical decision-makers today than it was before the end of the original OTRS Community Edition in 2021. Organizations face the choice of continuing their familiar Perl-based architecture with one of the active forks such as Znuny or OTOBO, adopting newer projects like O-Fork, or making a technological paradigm shift with Zammad. This comparison analyzes the five systems based on their architecture, security strategies, and operational requirements for 2026.

Technological Foundations: Perl Continuity vs. Ruby Modernity

The technological basis forms the most distinct difference in this comparison field. Four of the five systems examined (Znuny, OTOBO, O-Fork, and OTRS Community Edition) are based on Perl and continue the tradition of the classic OTRS framework. These systems typically use the LAMP stack (Linux, Apache, MySQL/MariaDB/PostgreSQL, Perl).

Znuny relies on the proven Znuny framework in version 7.3 and requires at least Perl 5.24. It supports a wide range of databases, including MariaDB, PostgreSQL, and Oracle. OTOBO also uses Perl, but deviates in infrastructure by pursuing a Docker-first strategy and integrating components such as the Gazelle web server and Redis for caching. O-Fork (version 12.0.3) stays true to the classic structure, but features a distinct trait in database support: it explicitly lists MySQL in versions earlier than 8.0 and Oracle from 10g onward as compatible.

In contrast, Zammad is based on Ruby on Rails and Vue.js. Zammad officially supports PostgreSQL; Redis 6 or newer is used for real-time communication. According to documentation, Elasticsearch is optional but strongly recommended for search and reporting. OTOBO integrates Elasticsearch and Redis in its documented Docker stack, while Znuny and the OTRS Community Edition use database full-text search in their captured standard configurations.

Security Management and Release Cycles

For administrators, the reliability of security updates is a primary criterion. As of the data snapshot on 2026-07-30, varying levels of governance maturity are visible:

• Zammad: Follows a strict policy with numbered security advisories. Versions 7.1.1 and 7.0.3 were released simultaneously on 2026-06-25 to patch vulnerabilities (Source: Zammad Advisories).
• Znuny: Regularly publishes patches for the current feature line (7.3.5 on 2026-07-22) as well as for the long-term support branch (LTS 6.5). Security announcements are coordinated centrally (Source: Znuny Security Advisories).
• OTOBO: Provides the GitHub security infrastructure for notifications and advisories. Version 11.1 was released on 2026-06-24 and includes OAuth token management and OpenID Connect, among other features.
• O-Fork: The public repository has existed since October 2025; version 12.0.3 was released in June 2026. A dedicated published security policy or security contact is not documented in the captured data snapshot.
• OTRS Community Edition (Centuran): This system is in a maintenance mode. The last documented release, 6.0.41, dates from 2024-12-09. It primarily serves to maintain existing installations based on the OTRS 6 codebase.

Extensibility and the Package Ecosystem

A key factor for flexibility is the availability of add-on modules. The OTRS forks use the .opm format (OTRS Package Manager). In the current hub dataset, Znuny is assigned 115 packages and OTRS Community Edition 111 packages. These figures describe the catalog inventory, not automatically compatibility with every current version.

OTOBO is assigned 53 packages; Elasticsearch is part of its captured stack. Zammad uses its own .szpm package format and lists 54 packages. In addition, Zammad documents REST, GraphQL, and webhooks as integration interfaces.

Artificial intelligence integration is also relevant for future planning. Zammad introduced AI-powered ticket summaries with version 7.0. OTOBO introduces AI support "Rotobo" in beta status with version 11.1.

Operational Consequences: Deployment and Migration

The effort required for operations varies depending on the chosen infrastructure strategy.

OTOBO and Zammad document Docker Compose as their deployment method. Zammad also offers packages for common Linux distributions. Znuny can be operated via Linux packages, source installation, or Docker; the classic Apache/Perl architecture is preserved.

During migrations within the OTRS family, code history and the .opm package format remain as commonalities; the actual compatibility of custom packages, templates, and database adjustments must still be tested. Switching to Zammad is not an in-place upgrade: processes, integrations, and data transfer require a dedicated migration plan.

Which System Fits Whom?

Choosing the right system depends on available expertise and functional focus areas:

• Znuny belongs in your consideration set if LTS 6.5, Oracle support, the Generic Interface, and a large inventory of assigned .opm packages are relevant.
• OTOBO belongs in your consideration set if OTRS logic is to be combined with a documented Docker Compose stack, Elasticsearch, Redis, and OpenID Connect.
• Zammad belongs in your consideration set if multi-channel ticketing, Ruby on Rails, Vue.js, PostgreSQL, and REST/GraphQL interfaces match your target architecture.
• OTRS Community Edition (Centuran) is primarily relevant for teams that continue to maintain an existing OTRS 6-based installation and consciously accept the maintenance status.
• O-Fork should be evaluated if its AGPL license, classic Apache/Perl architecture, and database support fit your inventory; the still small public project and community footprint is a distinct evaluation criterion in this case.

Data Status and Limitations of the Comparison

This comparison is based on the specifications and publications of the projects as of 2026-07-30. Because open source projects develop dynamically, current release notes and security advisories should be checked directly in the repositories before making a final decision. In particular, the compatibility of third-party packages in .opm format can vary between the different forks.

For a detailed comparison of individual functions, please use the interactive comparison table, where you can place the systems directly side by side.