Skip to content
CMDB linked to tickets
Custom CI types, fields, relationships, history and CSV import profiles. Devices and other configuration items can be linked directly to tickets.
Qisutu · CMDBQisutu comparisons 2026
Qisutu vs. OTOBO
Both systems support open-source self-hosting. The key difference lies in the configuration and extension model your team uses every day.
Comparison from Qisutu’s perspective · Updated: 20 September 2026
Our assessment
Extensive flexibility can mean excessive configuration work
OTOBO is actively developed and offers extensive functionality. Its process model of activities, dialogs, transitions and transition actions can still feel cumbersome to new administrators. Kim – Processes starts with the business instruction and produces a workflow that remains editable.
OTOBO · Process Management · OTOBO · GitHubThe differences in detail
| Topic | Qisutu | OTOBO |
|---|---|---|
| Creating processes | Kim – Processes turns natural-language instructions into editable BPMN templates with decisions, parallel branches and configurable steps.Kim – Processes | The documented designer combines activities, activity dialogs, transitions and transition actions. These elements are configured and deployed.OTOBO · Process Management |
| CMDB and extensions | CMDB in the core. ITSM Enterprise and Availability add specialised processes; the add-on API provides separate extension points.Qisutu · CMDB · Qisutu · Add-on API | OTOBO describes an ITSM extension with CMDB and manages additional functionality through packages.OTOBO · GitHub |
| Technical development | An independently built system using Perl/CGI, Template Toolkit, MariaDB/MySQL and its own versioned add-on API.Qisutu · GitHub · Qisutu · Add-on API | OTOBO is an actively developed fork of OTRS Community Edition. Its established structure provides continuity and existing expertise.OTOBO · GitHub |
Why consider Qisutu
Qisutu suits teams building service processes around their own CMDB, AI-assisted process templates and focused modules in a shared working environment.
Already in the Qisutu core
Administration through forms
Separate LDAP/AD profiles for agents and customers, with field mapping and connection testing. OAuth2 for Microsoft and Google mailboxes and TOTP two-factor sign-in are also included.
Qisutu · LDAP · Qisutu · GitHubDedicated extension API
The versioned add-on API provides events, REST routes and UI insertion points. Extensions are managed as separate ZIP modules.
Qisutu · Add-on APIRelevant Qisutu add-ons
Kim – Processes
A naturally written instruction becomes an editable BPMN process template for structured, email-driven service workflows.
Kim FeedMe
FeedMe captures reviewed knowledge from resolved tickets and free-form entries and makes it semantically available for new replies.
Kim Microsoft 365
Calendars, Teams, and SharePoint are available inside Qisutu under each agent's personal Microsoft permissions.
Qisutu ExtraFiles
ExtraFiles provides internal notes and documents for customers and contacts. The same information is accessible from their tickets; read and edit permissions follow ticket access.
ITSM, Availability, Kim and Microsoft 365 are separate add-ons. Availability requires ITSM Enterprise; FeedMe requires its service and Qdrant. Kim functions need the designated API access; Microsoft 365 needs Entra configuration and connectivity to Microsoft.
See Qisutu in your daily work
Let us show you the functions that matter to your team.
Basis and sources
Core claims are based on reviewed GitHub commit 0933c3d dated 17 September 2026. Add-on capabilities come from the respective module descriptions; ExtraFiles was also checked against its current package. Statements about effort and usability are our assessment of the documented workflows.