Skip to content
A deliberate technical restart
Qisutu does not inherit the OTRS code and configuration structure; it models service work on a new platform.
Open source · Product comparison · Updated 17 August 2026
Qisutu vs. OTOBO
Qisutu is the new open-source alternative for organisations that do not want to build once again on a continuation of the OTRS architecture. Its newly developed core combines modern ticket work with ten modular add-ons for ITSM, AI, Microsoft 365, Entra ID and monitoring.
This page also answers the common search „OTOBO vs. Qisutu“.
- No OTRS code baseQisutu is a completely independent new development.
- New add-on modelTen specialist modules extend the core without modifying its files.
- Modern integrationKim, Microsoft 365, Entra ID and monitoring are part of the new Qisutu portfolio.
A new platform instead of another OTRS continuation
OTOBO originated as a fork of the former free OTRS version. Qisutu was independently developed from scratch and uses neither that code base nor its accumulated technical structure.
Qisutu enables a genuine technical restart without giving up professional service management.Why Qisutu?
Why Qisutu is the stronger new choice over OTOBO
Qisutu combines capabilities that would otherwise have to be distributed across different systems, add-on products or individual integrations.
New capabilities designed together
ITSM, Kim, Microsoft 365, Entra ID and monitoring were built for the shared Qisutu add-on API.
Migration as controlled cleanup
Moving to Qisutu is an opportunity to review old queues, fields, permissions and processes and migrate only what is still needed.
The Qisutu difference
What Qisutu does differently from OTOBO
This comparison highlights where Qisutu takes its own broader approach through a new architecture and ten coordinated add-ons.
| Criterion | Qisutu | Difference from OTOBO |
|---|---|---|
| Development lineage | Complete independent new development without an OTRS code base. |
OTOBO originated in 2019 as a fork of the former free OTRS version and continues that lineage. |
| Architecture choice | New core, new interface and a dedicated add-on API for Qisutu specialist modules. |
OTOBO continues to develop the technical and administrative concepts inherited from OTRS. |
| ITSM | CMDB in the core and one coherent ITSM Enterprise module for Incident, Major Incident, Problem, Known Error, Change, Release, CAB and reviews. |
OTOBO provides ITSM through its OTRS-derived platform and additional packages. |
| AI | Five specialised Kim add-ons for product help, replies, routing, processes and verified knowledge development. |
A comparable coherent portfolio of five task-specific AI modules is not part of the OTOBO product information reviewed. |
| Microsoft 365 and Entra ID | Agent and contact SSO plus calendar, Teams, meetings, SharePoint and semantic document search directly inside Qisutu. |
OTOBO can connect external systems; Qisutu provides the described Microsoft 365 workspace as a coordinated add-on portfolio. |
| Monitoring | Ready-made connectors receive incidents, correlate duplicates, create tickets and process recovery events. |
With OTOBO, an equivalent monitoring connection depends on the selected package or an individual integration project. |
| Migration from OTRS 6 | A planned platform move with the opportunity to clean up historical configuration before migration. |
Because of its origin, OTOBO targets the most direct possible continuation of existing OTRS 6 structures. |
| Licence and operation | AGPL-3.0-or-later, self-hosted or managed hosting, including openly licensed Qisutu add-ons. |
OTOBO is also open source and self-hostable; the central difference is new development versus continuation. |
The Qisutu profile
What Qisutu brings as a new platform
Qisutu combines its newly developed core with ten independent add-ons. The system can therefore grow step by step from ticketing into a broad service workspace.
Independent new development
Qisutu is not a fork of OTRS, OTOBO, Znuny or Zammad. Its architecture, interface and add-on API were built from scratch.
Ten modular add-ons
ITSM Enterprise, Monitoring, Microsoft 365, two Entra ID modules and five specialised Kim extensions can be added selectively.
Kim in several roles
Product help, automatic customer replies, business-aware routing, process creation and knowledge development are separate and controllable capabilities.
Microsoft 365 in the service desk
Personal calendars, Teams, meetings, SharePoint files and semantic document search are available directly in the agent interface.
Coherent ITSM domain model
Incident, Major Incident, Problem, Known Error, Change, Release, CAB and Post-Incident Review use tickets, services, SLAs and the CMDB.
Monitoring becomes ticket work
Events from Checkmk, Zabbix, Icinga 2, Nagios, PRTG and Prometheus are authenticated, correlated and followed through to recovery.
The Qisutu advantage
Why choose Qisutu instead of OTOBO now?
Qisutu was not created as a copy of OTOBO. The platform was newly developed to connect ticketing with today’s ITSM, AI, Microsoft 365 and monitoring requirements.
No renewed dependency on the old OTRS lineageQisutu creates an independent technical foundation for the years ahead.
AI is already divided into concrete processesReplies, routing, process creation, knowledge and product help can be controlled separately.
Microsoft 365 becomes part of agent workTeams, calendar, meetings and SharePoint are available directly in the service desk.
ITSM and monitoring connect to the ticket coreService records and technical incidents are not limited to loose external integrations.
Frequently asked questions
Questions about Qisutu and OTOBO
Is Qisutu a fork of OTOBO or OTRS?
No. Qisutu is a completely independent new development and uses no OTRS or OTOBO code base.
Are Qisutu and OTOBO open source?
Yes. Qisutu is released under AGPL-3.0-or-later, while OTOBO is distributed under the GNU GPL.
Why choose Qisutu instead of OTOBO?
Qisutu offers a genuine technical restart combined with a new modular portfolio for ITSM, five Kim capabilities, Microsoft 365, Entra ID and monitoring.
Evaluate Qisutu in your own environment