ManageEngine ServiceDesk Plus vs GLPI

Start by mapping each ServiceDesk Plus edition against the modules your technicians use every week, not against a general feature comparison. Build the list from your own processes: incident and request queues, problem records, change approvals, asset records, service catalog, contracts, knowledge articles and reports. Then check which of the Standard, Professional and Enterprise editions includes each item, because module packaging is set by ManageEngine and can change between releases. Ask ManageEngine for the current module list per edition in writing, and ask which add-ons are priced separately. Do this before comparing GLPI, so the gap list reflects what your organization licenses today.

GLPI covers the core ITIL processes most service desks run, including incident, problem, change and service level management, alongside asset inventory, configuration management, knowledge base and contract management, as described in the GLPI GitHub repository. Coverage on paper is not the same as fit. Confirm how the change module handles approval steps, who can approve by role or group, and whether the approver can see linked assets and incidents before deciding, which is the practical test of impact analysis. Map your SLA and escalation rules as well. Where your ServiceDesk Plus workflows are heavily customized, expect to rebuild them in GLPI and test each one with a sample change and a sample incident before accepting the gap as closed.

Treat any gap that needs a plugin as a recurring cost and a risk, not a one-time setup. GLPI 11.0 suspends plugins when a new version is detected and requires them to be reactivated after major updates, so every upgrade needs a plugin check in the change plan. For each plugin, ask who maintains it, how often it is updated, and whether it works with the GLPI version you will run. Record every gap in one of three groups: closed by configuration, closed by plugin, or closed by a changed process. Ask Teclib' or your implementation partner to confirm each group on a test instance, and keep the results as evidence for the cutover decision.

ServiceDesk Plus is licensed per technician, so the license line grows with the number of staff who work tickets, and the reader should ask ManageEngine for current technician and asset pricing in writing for each edition under consideration. GLPI is distributed under GPL-3.0 with no license fee, so the software line for the same functions drops to zero. That does not make the platform free to run. The recurring costs move to your own budget: servers or virtual machines, database and backup storage, the staff who patch, upgrade and administer the application, and any change or integration work your processes require.

GLPI Network is optional, and it is the only paid subscription Teclib' sells on the supplied price list. According to the GLPI Network subscriptions page, the public cloud costs 19 euros per user per month and the private cloud 21 euros per user per month with a 25-user minimum. Self-hosted subscriptions range from 100 euros per month (Basic, up to 10 agents and 500 assets) to 4,500 euros per month (Enterprise), and the higher tiers include level 3 support and GLPI Network marketplace plugins. Confirm current figures on the GLPI project website before budgeting, because subscription terms change.

Support is a separate decision. Teclib' maintains GLPI and sells the subscriptions above, while independent integrators and hosting providers can also provide support under their own contracts. Ask each candidate for written scope covering response times, the versions covered, plugin support, and who handles security patches. Then compare the total over three years, including the license you would pay ManageEngine, the subscription or support you choose for GLPI, and the internal effort your team would carry.

Running GLPI after go-live is mostly a version discipline. GLPI 12.0.0 was released on October 7, 2026, and GLPI 11.0.11 on October 1, 2026, so the 11.0 line still receives maintenance releases. Decide early which line you will run, subscribe to the release notes on the GitHub releases page, and schedule a test upgrade on a copy of production each time a release affects your features. Read the GLPI 12.0.0 release notes against your current configuration, since the knowledge base was rewritten and step-up authentication now applies to certain administrative actions. Your administrators will need time to learn both changes before cutover, not after.

The documented update procedure starts with backups. Back up the database, the application files and the config directory, and make sure the glpi.key and glpicrypt.key files are included, because encrypted fields cannot be read without them. Then replace the application files, run php bin/console db:update from the GLPI root, and check the result. Since GLPI 11.0, plugins are suspended when a new version is detected and must be reactivated after major updates, so list every plugin you depend on, confirm each one has a release for the target version, and plan that reactivation step. Ask Teclib' or your integrator which plugins, if any, you need to validate first. The GLPI installation documentation is the authoritative sequence to follow.

Platform requirements change between lines, so confirm them before every upgrade rather than assuming last year's stack still works. The current README lists PHP 8.3 or later with MariaDB 10.11 or later or MySQL 8.0 or later, while the installation documentation for GLPI 11.0 lists PHP 8.2 or later with MySQL 8.0 or MariaDB 10.6. Only MySQL and MariaDB are supported. Check your operating system packages, web server configuration (the document root must point to the public directory), and PHP extensions against the exact target version, and ask your operations team to confirm whether the database server, PHP runtime and base image are still under vendor support. Include these checks in the upgrade test so a runtime change does not surface first in production.