OTAI Desk
Agent-Ticketansicht
kein Screenshot
Data-based comparison
OTAI Desk vs Znuny: AI Layer or OTRS Fork?
OTAI Desk vs Znuny: Python-based AI helpdesk with a front-layer model versus an established Perl LAMP OTRS fork with a .opm ecosystem.
Updated 2026-09-17 · Metrics are snapshots, not an overall ranking.
Facts side by side
The table is generated from Open ITSM Hub system and version data. Scroll horizontally on small screens to see every system.
| Property | OTAI Desk | Znuny |
|---|---|---|
| Stack | ||
| Primary Language | Python | Perl |
| Language Breakdown | ||
| Frameworks | Open Ticket AI Runtime, Docker | Znuny framework |
| Web Servers | — | Apache with mod_perl |
| Operating Systems | Linux | Linux |
| Databases | — | MySQL, MariaDB, PostgreSQL, Oracle |
| Search | RAG over internal knowledge base | Database full-text search |
| Cache | — | File system, Redis |
| Versions | ||
| Current version | — | 7.3.5 |
| Latest Release Date | — | 2026-07-22 |
| Supported Branches | — | 7.3, 6.5 LTS |
| Lts Available | — | Yes |
| Release Notes Url | — | Open source |
| Security | ||
| Security Policy Url | — | Open source |
| Advisories Url | — | Open source |
| Security Contact | — | — |
| Signed Releases | — | — |
| Sbom Available | — | — |
| Update Policy | Audit trails for AI decisions documented on the product site | Security advisories are published by the project and fixes are delivered in maintained release lines. |
| Recent Updates | — | 7.3.5 published on 2026-07-22 with security-related dependency updates |
| Community | ||
| GitHub stars | 8 | 582 |
| GitHub forks | 0 | 119 |
| GitHub issues | Open source | Open source |
| Open issues | 2 | 62 |
| Governance | Vendor-led open-source development | Vendor-led open-source development |
| Commercial Backer | Softoft | Znuny GmbH |
| Project forum | — | Open source |
| Documentation Url | Open source | Open source |
| Contribution Url | Open source | Open source |
| New issues (90 days) | — | 32 |
| Closed issues (90 days) | — | 21 |
| Issue window since | — | 2026-05-01 |
| Forum activity | — | Very active; visible daily help and discussion posts |
| Latest forum activity | — | 2026-07-29 |
| Ecosystem | ||
| Package format | pip | .opm |
| Package Repository Url | Open source | Open source |
| Migration Paths | Front layer before Zammad, Znuny, OTOBO, Jira Service Management, or Matrix42 | OTRS Community Edition, Earlier Znuny releases |
| Integration Interfaces | REST API, Email, Microsoft Teams, Chat, LDAP, Active Directory / Entra ID | Generic Interface, REST, SOAP, Email |
| Features | ||
| Built In | Ticketing, Local LLMs, RAG knowledge base search, L1 ticket deflection, AI classification, Audit trails, Microsoft Teams, Email, Chat, Backend connectors (Zammad, Znuny, OTOBO, Jira, Matrix42) | Ticketing, Process management, Generic Interface, Service catalog, Time accounting |
| Available Via Addon | Custom backend connectors | Additional ITSM and integration packages |
| Unsupported | — | — |
| Unknown | CMDB depth, Native Kubernetes operator, Classic ITIL process depth | Native Kubernetes operator |
Feature and integration matrix
| Funktion | OTAI Desk | Znuny |
|---|---|---|
| Ticketing | Integriert | Integriert |
| Local LLMs | Integriert | — |
| RAG Knowledge Base Search | Integriert | — |
| L1 Ticket Deflection | Integriert | — |
| AI Classification | Integriert | — |
| Audit Trails | Integriert | — |
| Microsoft Teams | Integriert | — |
| Integriert | — | |
| Chat | Integriert | — |
| Backend Connectors (Zammad, Znuny, OTOBO, Jira, Matrix42) | Integriert | — |
| Custom Backend Connectors | Per Add-on | — |
| Process Management | — | Integriert |
| Generic Interface | — | Integriert |
| Service Catalog | — | Integriert |
| Time Accounting | — | Integriert |
| Additional ITSM And Integration Packages | — | Per Add-on |
Interfaces side by side
The same scene per system when a screenshot exists. Missing scenes stay empty on purpose.
Znuny
Agent-Ticketansicht
Voices from operations
Curated quotes from administrators. No stars, no overall score.
Znuny
„After logging in with our existing credentials, we recognized the familiar dashboard user interface. Only the large Znuny logo (top right) shows a visual difference compared to the old OTRS CE installation. And most importantly: All our tickets (open and closed) exist, reports are still working and new ticket creation through e-mail works.“
GitHub issues and forum activity
Public activity in the main repositories and official project forums, as of 2026-09-17.
Issue-Zahlen zeigen sichtbare Entwicklungsaktivität, aber keine Produktqualität. Automatisierte Issues und unterschiedliche Arbeitsweisen der Projekte können die Werte verzerren.
OTAI Desk
GitHub-Fenster ab Nicht erhoben
- Offen
- 2
- Neu / 90 T.
- Nicht erhoben
- Geschl. / 90 T.
- Nicht erhoben
Forum
Kein dediziertes Projektforum belegt
Znuny
GitHub-Fenster ab 01.05.2026
- Offen
- 62
- Neu / 90 T.
- 32
- Geschl. / 90 T.
- 21
Forum
Very active; visible daily help and discussion posts
Letzte sichtbare Aktivität: 29.07.2026
Community and ecosystem in numbers
Stand: 2026-09-17
Einzelmetriken, keine Gesamtwertung
GitHub stars
Public stars of each main repository.
- OTAI Desk8
- Znuny582
Packages in Open ITSM Hub
Compatible packages currently listed in the hub.
- OTAI Desk0
- Znuny207
Year of first public release
Timeline context; longer bars mean a later release.
- OTAI Desk2025
- Znuny2021
OTAI Desk and Znuny belong to different traditions. Znuny is an active AGPL-licensed fork of OTRS Community Edition—Perl, LAMP architecture, .opm package ecosystem, and deep ITSM processes. OTAI Desk comes from the Python Open Ticket AI ecosystem and can run in front of Znuny as an AI layer instead of replacing it.
Origin and Deployment Model
Znuny continues the OTRS CE lineage. For teams with OTRS experience, .opm package inventory, and classic ITIL workflows, Znuny is a natural successor. The hub dataset lists Znuny with Perl, LAMP, and Generic Interface as a central integration option.
OTAI Desk is not an OTRS fork. According to the how-it-works page, it connects to Znuny and OTOBO natively via REST API and LDAP—as a backend for tickets the AI cannot resolve autonomously. Processes, packages, and agent workflows in Znuny remain intact.
Technology Overview
| Aspect | OTAI Desk | Znuny |
|---|---|---|
| Stack | Python, Docker, local LLMs, RAG | Perl, LAMP, MySQL/PostgreSQL/Oracle |
| License | LGPL-2.1 (runtime) | GNU AGPL v3.0 |
| Package format | pip (open-ticket-ai) | .opm |
| AI | core (deflection, classification) | extendable via OTAI plugins |
| Channels | chat, email, Teams | primarily email + Generic Interface |
Znuny offers historical process depth and a large addon ecosystem. OTAI Desk offers on-premise AI with audit trails—and can also use the Open Ticket AI Runtime inside Znuny as an automation engine, independent of the Desk product.
Which System Fits When?
Znuny is a better fit when:
- You are migrating from OTRS CE and want to leverage Perl/.opm know-how.
- ITIL processes, service structures, and Generic Interface are central.
- AI should be added optionally via plugins, not as an architectural core.
OTAI Desk is a better fit when:
- L1 deflection and local LLM inference are priorities.
- Znuny should remain productive—with OTAI Desk in front.
- Microsoft Teams, RAG, and fast initial responses are central.
- Compliance requires audit trails for AI decisions.
Combination Instead of Either-Or
In practice, both are not mutually exclusive: Znuny as system of record for complex ITSM cases, OTAI Desk as the entry layer for standard requests. Whether this fits your architecture depends on connector depth, ticket sync, and training effort—test both in a staging environment with real requests.
Data Status
As of September 17, 2026. Znuny version and community data from hub snapshot (July 2026); OTAI Desk as a product from 2025. Details: Znuny documentation · OTAI Desk.
Conclusion
Znuny is the established OTRS successor for classic ITSM. OTAI Desk is the AI-native alternative or complement—especially interesting when Znuny should stay. Compare both in the interactive comparison or read OTAI Desk vs. Zammad.
FAQ
Is OTAI Desk an OTRS fork like Znuny?
No. Znuny continues the OTRS CE lineage with Perl and .opm. OTAI Desk comes from the Python Open Ticket AI ecosystem and is not a fork.
It can connect Znuny as a backend: unresolved requests are passed as structured tickets. Znuny processes and packages remain intact.
Related on Open ITSM Hub
Can I use Open Ticket AI in Znuny without OTAI Desk?
Yes. The Open Ticket AI runtime is available as an automation engine for Znuny, OTOBO, and Zammad via PyPI packages—independent of the OTAI Desk product.
OTAI Desk is the full helpdesk solution with UI and channels; the runtime is middleware for classification, routing, and enrichment inside existing systems.
Related on Open ITSM Hub
Which system for OTRS migrants?
For the classic OTRS successor with .opm package inventory and ITIL depth, Znuny is the natural candidate in the hub.
OTAI Desk is relevant when AI-first and on-premise inference are priorities—either as replacement or as a layer in front of Znuny. A staging migration with real tickets delivers reliable results.
Related on Open ITSM Hub