KIX vs Znuny: CMDB Platform or Classic OTRS Successor?

KIX and Znuny share OTRS origins, but by 2026 they are no longer interchangeable drop-in successors. KIX 18 is documented as an independent service management platform featuring a Perl backend and TypeScript frontend, placing its focus on tickets plus assets/CMDB. Znuny remains a Perl framework with a classic LAMP path, an LTS branch, and a public .opm package directory. For administrators, the choice comes down to the operating model, asset depth, and whether existing OTRS packages remain relevant.

Origins and Product Line

Both systems are recorded in the hub as active forks or successors of the OTRS Community Edition. Znuny is maintained by Znuny GmbH as a continuation of the Community Edition, featuring a public GitHub repository and documented closeness to OTRS 6 installations. KIX originated historically as KIX4OTRS; its current public line is KIX 18, provided by KIX Service Software GmbH. Shared origins do not mean that user interfaces, internal APIs, or extensions have remained identical.

For a migration from OTRS 6, Znuny is the more conservative audit path via the documented update scripts of the LTS and 7.x branches. KIX 18 is described as a rewrite; existing OTRS customizations must be re-evaluated there rather than assumed to be 1:1 upgrades.

Stack and Operations

Znuny documents Linux packages, source installations, and Docker on a LAMP stack (Apache/mod_perl, MySQL/MariaDB/PostgreSQL, optional Oracle). Search runs via the database by default, with Redis provided as a cache.

KIX 18 is publicly delivered as a Docker on-premise setup (repository kix-on-premise). The dataset lists MySQL/MariaDB and Redis; PostgreSQL 15 is announced in the release notes for 18.37 as a target for a later version, not as an already occupied standard. A native Kubernetes operator is listed as unknown for both systems.

Teams wanting to run a single Linux VM without container orchestration will find the classic path more concisely documented in Znuny. Those who accept Docker as standard operations and expect asset objects in the same product will want to evaluate KIX 18 against their internal operational requirements.

Features: CMDB vs. Package Ecosystem

In the hub dataset, the following are integrated for KIX: ticketing, CMDB/assets, FAQ, reports, and organizations/contacts. Service contracts and news are marked as KIX Pro features, meaning they are not part of the free starting line.

Znuny lists ticketing, process management, Generic Interface, service catalog, and time accounting as integrated; additional ITSM and integration packages reside in the add-on ecosystem. The public package directory is addons.znuny.com. No comparable public .opm repository is stored in the dataset for KIX 18.

Those who need a CMDB in the core product must evaluate Znuny via packages and custom modeling. Those who require .opm compatibility and Generic Interface (REST/SOAP) will find a denser, more traceable package situation with Znuny.

Community, Releases, and Evidence

Znuny 7.3.5 (2026-07-22) and the 6.5 LTS branch are documented in the dataset, including security advisories under znuny.org. As of July 30, 2026, the main repository shows 582 stars, 62 open issues, and a very active forum.

KIX 18.37 (2026-04-28) is documented as a stabilization release. The public on-premise repository has 24 stars; issue activity over 90 days has not been comparably collected. A security policy URL is missing from the dataset and remains unknown. Exchange takes place primarily in the KIX Forum.

Star counts and forum activity do not replace a quality assessment. They merely show where operational knowledge can be looked up publicly.

Which System Fits Whom?

KIX is worth evaluating if:

• Asset and CMDB objects should reside in the core product rather than as an optional package.
• Docker on-premise fits your intended operational workflow.
• A REST API and a vendor-managed service management product are top priorities.

Znuny is worth evaluating if:

• An OTRS-CE-leaning Perl/LAMP environment and a documented LTS branch are required.
• Generic Interface, .opm packages, and Oracle support are relevant.
• Public issue and forum activity should be leveraged for self-hosting.

Data Status and Limitations

This comparison uses the structured system data from the Open ITSM Hub (Znuny status as of 2026-07-30, KIX status as of 2026-08-26). Unknown fields—such as a Kubernetes operator or a KIX security policy—are left blank. A staging migration with real assets, permissions, and interfaces remains the reliable next step.

The live table on this page and the interactive overview display individual criteria without an aggregate score.