Skip to content
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 · GitHubQisutu comparisons 2026
Qisutu vs. Jira
This comparison concerns Jira Service Management, Atlassian’s service desk and ITSM product. Qisutu focuses on control over deployment, an open core and individually installed extensions.
Comparison from Qisutu’s perspective · Updated: 20 September 2026
Our assessment
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 CollectionThe differences in detail
| Topic | Qisutu | Jira Service Management |
|---|---|---|
| Self-hosting | A self-hostable AGPL core. Your organisation controls the installation, updates and infrastructure.Qisutu · GitHub | Jira Service Management Data Center is scheduled to reach end of life on 28 March 2029. Atlassian describes exceptions for certain existing customers.Atlassian · Data Center |
| Costs and CMDB | CMDB in the core and no per-agent core licence fees. Infrastructure, support and external services remain cost factors.Qisutu · GitHub · Qisutu · CMDB | Cloud subscriptions depend on agent count and plan. Assets includes plan-specific object allowances; additional objects may incur charges.Atlassian · Service Collection |
| ITSM and extensions | ITSM Enterprise provides changes, CAB, releases and post-incident reviews. Availability adds outage calculations, risks and resilience tests.Qisutu ITSM Enterprise · Qisutu ITSM Availability | ITSM, Assets, automation and AI services are organised through Atlassian’s Service Collection; capabilities and allowances depend on the plan.Atlassian · Service Collection |
Why consider Qisutu
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.
Already in the 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 · CMDBTicket work and automation
Agent and customer portals, queues, services, SLAs, triggers, scheduled tasks, reports and a REST API are part of the core.
Qisutu · GitHubRelevant Qisutu add-ons
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.
Qisutu ITSM Availability
Complete reactive and proactive Availability Management for Qisutu ITSM Enterprise with outages, metrics, risks, plans, and resilience tests.
Kim – Processes
A naturally written instruction becomes an editable BPMN process template for structured, email-driven service workflows.
Kim Microsoft 365
Calendars, Teams, and SharePoint are available inside Qisutu under each agent's personal Microsoft permissions.
Qisutu Monitoring
Qisutu Monitoring receives authenticated problem and recovery events, correlates duplicates, and automatically creates or updates tickets.
Entra ID – Agents
Secure agent sign-in through Microsoft Entra ID with automatic creation and updating of Qisutu accounts.
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.