Skip to content
A new technical foundation
Qisutu inherits no OTRS core files and provides an independent architecture for service desk and extensions.
Open source · Product comparison · Updated 17 August 2026
Qisutu vs. Znuny
Qisutu is the new open-source alternative for organisations that do not want to continue their service platform indefinitely on the OTRS Community code base. Instead of historical continuity, Qisutu provides a newly developed core and ten modern specialist modules.
This page also answers the common search „Znuny vs. Qisutu“.
- Independently developedNo OTRS or Znuny code base and no inherited architecture.
- Ten new specialist modulesITSM, Kim, Microsoft 365, Entra ID and monitoring work together.
- A deliberate restartMigration can clean up historical configuration instead of carrying it indefinitely.
An independent future instead of long-term OTRS continuation
Znuny continues OTRS Community Edition through LTS and current versions. Qisutu starts afresh technically and connects ticketing with a new add-on model from the outset.
Qisutu is designed for organisations that want not merely to update but to rebuild their service platform.Why Qisutu?
Why Qisutu is the stronger new choice over Znuny
Qisutu combines capabilities that would otherwise have to be distributed across different systems, add-on products or individual integrations.
More than LLM assistance
Five Kim modules separately cover product help, automatic replies, routing, process creation and verified knowledge.
Microsoft and monitoring integrated
Entra ID, Teams, calendar, SharePoint and external monitoring events become part of Qisutu work.
The Qisutu difference
What Qisutu does differently from Znuny
This comparison highlights where Qisutu takes its own broader approach through a new architecture and ten coordinated add-ons.
| Criterion | Qisutu | Difference from Znuny |
|---|---|---|
| Development lineage | Complete independent new development without an OTRS code base. |
Znuny originated in 2020 as the direct continuation of OTRS Community Edition. |
| Technical approach | New core, new interface and new add-on API. |
Znuny deliberately maintains and extends structures inherited from OTRS. |
| ITSM and CMDB | CMDB in the core; one ITSM Enterprise module connects key ITSM objects, tasks, approvals, CAB and reviews. |
With Znuny, ITSM scope depends on the version and installed packages. |
| AI | Five specialised Kim add-ons for clearly separated operational tasks. |
Znuny-LLM adds LLM support; Qisutu additionally provides its own modules for routing, processes, automatic replies and knowledge development. |
| Microsoft 365 and Entra ID | SSO and synchronisation for agents and contacts plus Teams, calendar, meetings and SharePoint inside Qisutu. |
Znuny supports Microsoft OAuth2 for email among other functions; the complete Qisutu Microsoft workspace goes substantially further. |
| Monitoring | External monitoring systems send events to Qisutu, which creates tickets and processes recovery. |
The official Znuny Prometheus exporter monitors Znuny itself and therefore covers a different use case. |
| Migration | A deliberate move to a new platform with review and cleanup of old structures. |
Znuny targets the greatest possible continuity for existing OTRS Community installations. |
| Long-term decision | Independent Qisutu architecture with a new coordinated capability portfolio. |
Znuny remains technically and historically close to the OTRS Community development lineage. |
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 Znuny now?
Qisutu was not created as a copy of Znuny. The platform was newly developed to connect ticketing with today’s ITSM, AI, Microsoft 365 and monitoring requirements.
Do more than maintain the old systemQisutu makes it possible to rebuild ticketing and service management on a new technical basis.
Five Kim capabilities instead of a general LLM linkEvery AI task has its own purpose and controllable configuration.
Complete Microsoft workspaceEntra ID, Teams, calendar, meetings and SharePoint are used within Qisutu.
Monitoring processes real operational eventsExternal incidents and recovery flow directly into ticket work.
Frequently asked questions
Questions about Qisutu and Znuny
Is Qisutu a Znuny or OTRS fork?
No. Qisutu is a completely independent new development and uses no Znuny or OTRS code base.
Do both systems offer AI features?
Yes. With five separate Kim modules for product help, replies, routing, processes and knowledge development, Qisutu goes well beyond a general LLM integration.
Why choose Qisutu instead of Znuny?
Because Qisutu combines a technical restart with a coordinated portfolio for complete ITSM, five Kim tasks, Microsoft 365, Entra ID and inbound monitoring.
Evaluate Qisutu in your own environment