KIX vs Zammad: Technical ITSM or Modern Helpdesk?

KIX and Zammad address different operational needs, even though both present themselves as open ticketing systems. Zammad is an independent Ruby on Rails helpdesk with a Vue.js interface, REST/GraphQL, and an optional, strongly recommended Elasticsearch setup. KIX 18 is a service management system that evolved from the OTRS lineage, featuring a Perl backend, TypeScript frontend, and integrated CMDB. This does not result in a single overall winner, but it does yield clear exclusion criteria for administrators.

Two Product Philosophies

Zammad launched in 2016 as an independent open-source helpdesk (AGPL) maintained by Zammad GmbH. Channels, agent UX, and search take center stage, while CMDB depth is marked as unknown in the dataset. Migrations from OTRS, Zendesk, and Freshdesk are listed as paths rather than guarantees of process parity.

KIX continues the OTRS/KIX4OTRS lineage, currently as KIX 18 (18.37 from April 28, 2026). Its documented focus is on tickets plus assets. Service contracts and news belong to KIX Pro according to the documentation, not the free base line.

If you are looking for a "modern helpdesk," evaluate Zammad first against channel and UX requirements. If you are looking for "technical ITSM with inventory," evaluate KIX first against its asset model.

Stack and Operations

Zammad: Ruby on Rails, PostgreSQL, Vue.js, Nginx, Redis for real-time features, and Elasticsearch as an optional but strongly recommended search engine. Deployment options include Linux packages, Docker Compose, and source code. Kubernetes support is unconfirmed; while a community Helm chart exists outside of the mandatory hub field, it is not counted here as a product feature.

KIX 18: Perl backend, TypeScript frontend, Docker on-premise, MySQL/MariaDB, and Redis. Elasticsearch is not documented. Backup documentation is missing from the dataset.

Both systems are container-ready. The differences lie in the runtime (Ruby vs. Perl/Node frontend), database requirements, and whether you plan to operate Elasticsearch.

Features and Interfaces

Zammad integrates ticketing, knowledge base, REST, GraphQL, webhooks, full-text search, time tracking, SAML, OpenID Connect, and AI ticket summaries. WhatsApp and social channels are described in the product line's release notes, while the hub feature list remains limited to structured fields.

KIX integrates ticketing, CMDB/assets, FAQ, reports, and organizations. The documented interface is REST. GraphQL, webhooks, and native messenger channels are not included in the dataset for KIX and remain unknown.

For multi-channel support and a searchable knowledge base, Zammad has the stronger documented footprint. For asset relationships tied to tickets, KIX has the stronger documented footprint.

Community and Transparency

Zammad: approximately 5,800 repository stars, public security policy and advisory directory, contact at security@zammad.com, and a very active forum. As of July 30, 2026.

KIX: public on-premise repository with 24 stars, forum for releases, and no documented security policy URL. As of August 26, 2026.

Zammad's issue counts should not be interpreted as a quality disadvantage for KIX, as projects manage visibility differently. For self-hosting, what matters is where security updates can be tracked.

Which System Fits Whom?

KIX is worth considering if:

• Technical services, assets, and CMDB objects need to reside in the same system.
• A Docker on-premise setup and the AGPL license model fit your operational requirements.
• Helpdesk channels beyond email and tickets are of secondary importance.

Zammad is worth considering if:

• Agent UX, search performance, and multiple communication channels are top priorities.
• Ruby, PostgreSQL, and Elasticsearch are part of your target stack.
• Public security advisories and a large community knowledge base are required.

Both paths require a test migration: Zammad overwrites a fresh instance during imports, and KIX 18 does not automatically carry over OTRS customizations.

Data Status and Limitations

Unknown CMDB depth for Zammad and unknown channel breadth for KIX are not filled in. Screenshots and quotes on the comparison pages currently focus primarily on Zammad and Znuny; missing KIX media does not imply any rating judgment.

Use the table on this page and the interactive overview to evaluate criteria individually rather than expecting a single overall score.