Compare / Zammad vs GLPI

Zammad vs GLPI

Pick GLPI if you want assets and an ITIL desk (the published ServiceNow/Freshservice/JSM stack). Pick Zammad if the job is email tickets (already on /best/helpdesk).

Facts checked 21 Oct 2026. License, language, and GitHub activity come from the catalog or the project's own repo. "Not in the catalog row" means the public catalog dump does not store that number.

Zammad in the catalog GLPI in the catalog Start on Railway

How they compare

ZammadGLPI
LicenseAGPL-3.0 (catalog) sourceGPL-3.0 (catalog) source
LanguageRuby (catalog) PHP (catalog)
GitHub activity6,025 stars in the catalog source6,485 stars in the catalog source
Self-hostEmail-first ticket desk. Rails plus Postgres/Elasticsearch as documented. Published as /stacks/glpi-itsm. PHP plus MariaDB. Assets and an ITIL portal.
Best forTickets, not a CMDB. Assets plus a service desk.

Self-hosting and resource needs

GLPI is on /stacks/glpi-itsm. Zammad is zammad/zammad and already compared with Chatwoot — /compare/chatwoot-vs-zammad. iTop is the other CMDB — /compare/glpi-vs-itop. Jira Software stays on /replace/jira.

FAQ

Is this Jira?
Jira Software is /replace/jira. This pair is Jira Service Management — tickets and a portal.
Chatwoot or Zammad?
Chatwoot is the shared inbox — /compare/chatwoot-vs-zammad.
Are these free?
Zammad is AGPL-3.0. GLPI is GPL-3.0. You pay hosting.
How do I deploy GLPI?
Open /stacks/glpi-itsm. Persist the database. Import one asset list or one queue.

Related pages

Stack of the Week

Get one stack a week that replaces a SaaS bill.

Sponsor this page