GLPI vs Jira Service Management
GLPI and Jira Service Management are both IT service management software. GLPI is open source under GPL-3.0, with 6.5k GitHub stars. Jira Service Management is a commercial product from Atlassian.
Which to pick
- Pick GLPI when
- An IT department wants a free, self-hosted helpdesk and asset register and is comfortable with a PHP application.
- Pick Jira Service Management when
- An IT or ops team whose engineers already work in Jira wants service requests linked to development work.
Side by side
IT asset management and ITIL service desk in one: inventory of computers and software, licences, contracts, tickets, changes and a knowledge base.
Atlassian's service desk for IT and business teams with request portals, incident and change management, assets and on-call.
Configuration is deep and the interface takes training; some plugins and hosted options are sold by Teclib.
Configuration sprawl is common, and Atlassian is ending on-premise Server licences.
Production-ready (both)
Self-hosted server and cloud service
Cloud service and self-hosted server
PHP, Symfony, Vue and MySQL
Not published
Open source, GPL-3.0 (strong copyleft)
Closed source, sold by Atlassian
Use inside your business is unrestricted, but anything you distribute that includes it must be released under the same license.
Closed source: you use it under the maker's terms and cannot change or resell the code.
6.5k GitHub stars
No Wikipedia article of its own
Established: started 11 years ago, latest release 12.0.1.
Not known
Other comparisons
More IT service management (ITSM) and PSA tools
Both sides were judged on 2026-11-03 from makers' descriptions, Wikipedia, READMEs and GitHub data. License, age and popularity lines are worked out directly.