Comparisons anchored on GLPI, the GPL ITSM and asset management suite maintained by Teclib'.
Asset-centric ITSM or customer-facing helpdesk: GLPI's ITIL processes and native inventory against Zammad's omnichannel ticketing on PostgreSQL and Elasticsearch, with a verdict by whether the desk serves internal IT or external customers.
Two open-source ITSM suites with a CMDB: GLPI with built-in agent inventory and Teclib' subscriptions against Combodo's iTop and its agent-tiered editions, judged by CMDB depth, change management, discovery and the vendor support each offers.
Whether a self-hosted GLPI service desk can run on the free community release or needs a Teclib' GLPI Network subscription: what Basic, Standard, Advanced and Enterprise add in level 3 support, Network-only plugins and instance counts, and how agent and asset caps set the tier.
Whether to run GLPI on Teclib's GLPI Network Cloud or on your own servers: public versus private cloud pricing, availability, RPO and RTO commitments, backup retention, LDAP and VPN limits on cloud instances, data reversibility, and the infrastructure work self-hosting keeps in house.
Full ITSM with inventory against focused IT asset management: GLPI versus AGPL-3.0 Snipe-IT. Compares asset, license and consumable tracking, helpdesk scope, LDAP and SAML login, APIs, hosting requirements and when teams run both.
An ITSM suite against a lightweight ticket system: GLPI and GPL-2.0 osTicket compared on ticketing, asset and change management, authentication plugins, editions and support, hosting stack and which fits an IT team versus a customer support desk.
The CMDB question inside GLPI vs iTop: iTop's fully customizable CMDB data model and impact analysis against GLPI's asset-centric inventory fed by the GLPI Agent, and which one fits change and impact management versus asset tracking.
GLPI against Znuny, the OTRS Community Edition fork: an asset and ITIL suite with native inventory versus a mature ticketing engine for service desks, with license, database support, LTS lines and who sells support for each.
How to feed GLPI with hardware and software inventory: the native GLPI Agent available since GLPI 10, plus the GLPI Inventory plugin for network discovery, against keeping an OCS Inventory NG server synchronized through the ocsinventoryng plugin.
Running GLPI from the official Docker images, rebuilt weekly with auto-install and volume layout, against installing the release archive on your own PHP and web server stack, including how cron, plugins and scaling work in each.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.