OTAI Desk
GitHub-Fenster ab Nicht erhoben
- Offen
- 2
- Neu / 90 T.
- Nicht erhoben
- Geschl. / 90 T.
- Nicht erhoben
Forum
Kein dediziertes Projektforum belegt
Data-based comparison
OTAI Desk vs OTOBO: AI Helpdesk or Docker OTRS Fork?
OTAI Desk vs OTOBO compared: AI-first Python helpdesk with front layer versus GPL-licensed Perl OTRS fork with Docker stack.
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 | OTOBO |
|---|---|---|
| Stack | ||
| Primary Language | Python | Perl |
| Language Breakdown | ||
| Frameworks | Open Ticket AI Runtime, Docker | OTOBO framework |
| Web Servers | — | Nginx, Apache with mod_perl, Gazelle |
| Operating Systems | Linux | Linux |
| Databases | — | MySQL, MariaDB, PostgreSQL |
| Search | RAG over internal knowledge base | Elasticsearch |
| Cache | — | Redis, File system |
| Versions | ||
| Current version | — | 11.1 |
| Latest Release Date | — | 2026-06-24 |
| Supported Branches | — | 11.1, 11.0, 10.1 |
| Lts Available | — | — |
| 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 reports and advisories are handled through the public GitHub security area. |
| Recent Updates | — | — |
| Community | ||
| GitHub stars | 8 | 331 |
| GitHub forks | 0 | 89 |
| GitHub issues | Open source | Open source |
| Open issues | 2 | 194 |
| Governance | Vendor-led open-source development | Vendor-led open-source development |
| Commercial Backer | Softoft | Rother OSS GmbH |
| Project forum | — | Open source |
| Documentation Url | Open source | Open source |
| Contribution Url | Open source | Open source |
| New issues (90 days) | — | 194 |
| Closed issues (90 days) | — | 208 |
| Issue window since | — | 2026-05-01 |
| Forum activity | — | Active; visible posts on the same day, especially in the German-language forum |
| Latest forum activity | — | 2026-07-30 |
| 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 OTOBO 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, Elasticsearch search, OAuth, OpenID Connect, AI assistance (beta) |
| 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 | OTOBO |
|---|---|---|
| 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 |
| Elasticsearch Search | — | Integriert |
| OAuth | — | Integriert |
| OpenID Connect | — | Integriert |
| AI Assistance (Beta) | — | Integriert |
| Additional ITSM And Integration Packages | — | Per Add-on |
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.
Community and ecosystem in numbers
Stand: 2026-09-17
Einzelmetriken, keine Gesamtwertung
GitHub stars
Public stars of each main repository.
- OTAI Desk8
- OTOBO331
Packages in Open ITSM Hub
Compatible packages currently listed in the hub.
- OTAI Desk0
- OTOBO92
Year of first public release
Timeline context; longer bars mean a later release.
- OTAI Desk2025
- OTOBO2020
OTAI Desk and OTOBO share open source—that is where the similarity ends. OTOBO is an active OTRS CE fork under GPL v3.0 with Perl, .opm packages, and Docker-oriented operations (MariaDB, Elasticsearch, Redis, Nginx). OTAI Desk is an AI-first helpdesk on the Open Ticket AI runtime (Python, local LLMs, RAG) and can run OTOBO as a backend in front of it.
Architecture and Philosophy
OTOBO modernizes the OTRS world: proven ITSM logic, container deployment, Generic Interface, and a growing .opm ecosystem. For OTRS migrants who prefer Docker as an operational path, OTOBO is an established candidate.
OTAI Desk primarily addresses L1 automation and fast initial responses. According to the product architecture, OTOBO remains untouched—OTAI Desk intercepts standard requests and hands complex cases to OTOBO via REST as structured tickets.
Technical Comparison
| Aspect | OTAI Desk | OTOBO |
|---|---|---|
| Origin | Open Ticket AI (independent) | OTRS Community Edition |
| Language | Python | Perl |
| License | LGPL-2.1 (runtime) | GNU GPL v3.0 |
| Deployment | Docker on-premise | Docker-first, also classic |
| Packages | pip / OTAI plugins | .opm |
| AI | integrated (local) | extendable via OTAI runtime |
| Database | not specified in hub | MariaDB, MySQL, PostgreSQL |
Both can be combined: OTOBO as system of record, OTAI Desk as AI entry layer. The Open Ticket AI Runtime also offers automation inside OTOBO—independent of the Desk product.
Selection Criteria
OTOBO is a better fit when:
- You are migrating from OTRS CE and want to continue ITSM processes in the Perl ecosystem.
- A Docker stack with Elasticsearch and .opm packages fits your architecture.
- AI should be added optionally via middleware.
OTAI Desk is a better fit when:
- AI-first and on-premise inference are central.
- OTOBO should remain productive—with an AI layer in front.
- Microsoft Teams, RAG deflection, and audit trails are priorities.
Data Status
As of September 17, 2026. OTOBO data from hub snapshot (July 2026); OTAI Desk from 2025. Official sources: doc.otobo.org · desk.openticketai.com.
Conclusion
OTOBO is the Docker-oriented OTRS successor for classic ITSM. OTAI Desk complements or replaces depending on the model—especially as a front layer without rip-and-replace. Related comparisons: OTOBO vs. Znuny · OTAI Desk vs. Zammad.
FAQ
Can OTAI Desk run in front of OTOBO?
According to the product site, OTAI Desk supports native connection to Znuny and OTOBO via REST API and LDAP. OTAI Desk intercepts L1 requests; complex cases go to OTOBO as tickets.
OTOBO processes, .opm packages, and agent workflows remain intact. Whether this fits your landscape requires a PoC with real requests.
Sources
Related on Open ITSM Hub
What license differences matter?
OTOBO is under GNU GPL v3.0. The Open Ticket AI runtime under LGPL-2.1. AGPL/GPL differences from LGPL have practical compliance implications for modifications and network use.
Review your organization's license requirements separately from technical architecture.
Sources
Related on Open ITSM Hub
OTOBO or OTAI Desk for AI automation?
OTOBO offers classic ITSM; AI can be added via the Open Ticket AI runtime as middleware. OTAI Desk makes AI the architectural core with UI, channels, and deflection.
For pure ticket classification in OTOBO, the runtime suffices; for L1 deflection with chat/Teams and audit dashboard, OTAI Desk is the dedicated product.
Related on Open ITSM Hub