History

How experience led to a new open-source alternative

Learn how Qisutu originated and how experience with real help desk and support processes continues to shape its development.

Qisutu symbol as an abstract interpretation of cuneiform

Experience from Real-World Operations

A new ticket system begins with the people doing the work

Years of developing, introducing, and supporting service processes provide a clear view of what agents, administrators, customers, and process owners actually need. Clear ticket views, understandable responsibilities, and short paths through the system matter just as much as flexible configuration, automation, and reliable email processing.

Qisutu grew out of this experience. Its starting point was the daily work of help desk and service desk teams: accepting requests, assigning them correctly, working together, meeting binding targets, and documenting every decision transparently.

This perspective shapes the entire platform. Features should make complex service processes manageable without burdening the people using the system with avoidable complexity.

More Choice in the Open-Source Market

A new alternative to OTOBO, Znuny, Zammad, and other ticket systems

Organizations have different requirements for usability, capabilities, integration, and operations. Qisutu expands the available choice with a new open-source ticket system that combines professional ticket management, modern administration, and self-determined operation.

Whether Qisutu, OTOBO, Znuny, Zammad, or another solution is the right choice depends on the actual processes involved. Qisutu is designed for organizations that want clear workspaces, extensive configuration, open interfaces, and control over their data and infrastructure.

Designed from the Ground Up

A ticketing core for today’s help desk and service processes

Ticket management, email processing, customer portal, queues, groups, and permissions form the operational center. Automation, service levels, calendars, dynamic fields, forms, checklists, and notifications turn those foundations into reliable workflows.

Knowledge base, CMDB, reports, time accounting, REST API, and add-ons extend Qisutu beyond the classic ticketing core. Every area follows the same objective: present information clearly, keep work steps transparent, and make controlled adaptation possible.

Community as a Guiding Principle

The name Qisutu represents openness and collaboration

Qisutu refers to qissûtu, a possible Akkadian rendering of the term “community.” The name expresses a central idea of the project: service emerges from shared knowledge, clear responsibility, and reliable collaboration.

The Qisutu symbol is an abstract interpretation of cuneiform. Its wedge-shaped elements combine origin, structure, and movement into a distinctive mark—a visual bridge between early written culture and modern digital communication.

Open and Self-Determined

Open source as freedom in operation and development

Qisutu is published under the AGPL-3.0-or-later license. Organizations can run the system themselves, adapt it to their requirements, and integrate it into existing environments. Professional services are also available for implementation, migration, support, hosting, and custom extensions.

Qisutu therefore combines the openness of an open-source project with the standards expected of a professional help desk and service desk system.

Openness Source code, architecture, and ongoing development remain transparent.
Community Service is understood as structured collaboration.
Clarity The interface supports the task, not the complexity.
Independence Operations, data, and product development remain under your control.