All comparisonsQisutu comparisons 2026

Qisutu comparisons 2026

Qisutu comparisons 2026

This comparison considers the current public Qisutu code and the published add-ons. The assessments below show where Qisutu offers advantages for your service desk.

Comparison from Qisutu’s perspective · Updated: 20 September 2026

Features, control and operational effort matter

Qisutu vs. Zammad

Additional integrations can make a service desk unnecessarily cumbersome

Zammad offers a modern helpdesk interface, automation and AI. Its documented CMDB integration adds i-doit, however. Teams organising inventory, changes and availability together need to consider the entire system landscape. For this use case, we see Qisutu’s own CMDB and integrated ITSM add-ons as the more direct route.

Zammad · i-doit · Zammad · API / n8n · Zammad · AI

Qisutu is particularly relevant when ticket handling, your own CMDB, formal ITSM processes and reusable solution knowledge should work together in one service environment.

Open full comparison

Qisutu vs. Jira

Plans, quotas and a cloud transition make planning harder

Jira Service Management is powerful. Agent-based plans, Assets allowances and the announced Data Center end of life can nevertheless complicate planning. For organisations wanting to keep running their own service desk, we consider Qisutu the more suitable foundation.

Atlassian · Data Center · Atlassian · Service Collection

If you want an open service desk on your own servers, a built-in CMDB and clear module choices without per-agent core licence fees, compare Qisutu directly with the Jira plan you need.

Open full comparison

Qisutu vs. OTOBO

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 · GitHub

Qisutu suits teams building service processes around their own CMDB, AI-assisted process templates and focused modules in a shared working environment.

Open full comparison

Qisutu vs. Znuny

Established configuration practices can make getting started harder

Znuny maintains both LTS and current release lines. Its documented directory integration uses Perl configuration and coordinated backend keys. For administrators without OTRS experience, we consider Qisutu’s configuration forms with connection testing more accessible.

Znuny · User Backends · Znuny · Process Management · Znuny · LTS

Consider Qisutu when your team wants to rely less on established configuration files and build administration, its own CMDB and new specialist modules together.

Open full comparison

Qisutu vs. OTRS

Multiple configuration layers can make daily work harder

OTRS provides an extensive service management platform with CMDB, knowledge and processes. Its combination of process components, system configuration and vendor services requires familiarisation. For teams preferring a self-controlled foundation with focused modules, we see Qisutu as a straightforward approach.

OTRS · Process Management · OTRS · System Registration · OTRS · Administration

Qisutu is an attractive option if you want to inspect the code, run your own installation and extend the service desk with clearly defined ITSM, knowledge and integration modules.

Open full comparison

Already in the Qisutu core

Qisutu core

Control your deployment

AGPL-3.0-or-later and self-hosting. The Qisutu core has no per-agent licence fee; operations, support and external services require their own budget.

Qisutu · GitHub
Qisutu core

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 · CMDB
Qisutu core

Forms and knowledge

Customer forms and embeddable web forms with a target queue and custom fields. The knowledge base provides revisions and inserts FAQ content into replies.

Qisutu · Forms · Qisutu · FAQ
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 · GitHub
Qisutu core

Traceable time accounting

Billable and non-billable time with activity types. Corrections create a cancellation with a reason and a linked replacement entry.

Qisutu · Time accounting
Qisutu core

Dedicated 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 API
Qisutu core

Ticket work and automation

Agent and customer portals, queues, services, SLAs, triggers, scheduled tasks, reports and a REST API are part of the core.

Qisutu · GitHub

Relevant Qisutu add-ons

Add-on

Qisutu ITSM Enterprise

Extends Qisutu with end-to-end IT service management for incidents, major incidents, problems, known errors, changes, releases, and post-incident reviews.

Add-on

Qisutu ITSM Availability

Complete reactive and proactive Availability Management for Qisutu ITSM Enterprise with outages, metrics, risks, plans, and resilience tests.

Add-on

Kim – Automatic Routing

Kim classifies new email tickets and assigns them exclusively to queues and priorities approved by an administrator.

Add-on

Kim – Automatic AI Reply

New tickets created from incoming customer emails automatically receive a professional acknowledgement in the appropriate language.

Add-on

Kim – Processes

A naturally written instruction becomes an editable BPMN process template for structured, email-driven service workflows.

Add-on

Kim FeedMe

FeedMe captures reviewed knowledge from resolved tickets and free-form entries and makes it semantically available for new replies.

Add-on

Kim Chat

A globally available AI chat assists agents with general questions independently of the ticket currently open.

Add-on

Entra ID – Agents

Secure agent sign-in through Microsoft Entra ID with automatic creation and updating of Qisutu accounts.

Add-on

Entra ID – Customer Users

Customer users sign in to the customer portal through Entra ID and can be imported and updated automatically.

Add-on

Kim Microsoft 365

Calendars, Teams, and SharePoint are available inside Qisutu under each agent's personal Microsoft permissions.

Add-on

Qisutu Monitoring

Qisutu Monitoring receives authenticated problem and recovery events, correlates duplicates, and automatically creates or updates tickets.

Add-on

Qisutu Survey

Configurable customer satisfaction surveys are sent automatically after a ticket is closed and answered on a public token-protected survey page.

Add-on

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.

Demo / Quote

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.

Code on GitHub · Relevant Qisutu add-ons