Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
Self-host GLPI
updated Nov 2026deployed by usprices checked · Jul 2026Install verified on Ubuntu 26.04 · Nov 2026 · how we test
We earn commissions when you shop through the links below. Full disclosure →
IT asset management and service desk software written in PHP. It keeps an inventory of computers, network equipment, software, licences and contracts, and runs an ITIL-style helpdesk with tickets, problems, changes, service levels and a knowledge base. Assets can be filled in by inventory agents that report to the server, and a plugin marketplace extends it. It stores everything in MySQL or MariaDB. The official Docker image runs Apache and PHP as a non-root user and installs the database schema on first start when it is given the database credentials; the cron worker runs inside the same container.
Pick GLPI when you need one system for both the asset inventory and the helpdesk: computers, network gear, software and licences with their relations and contracts, plus ITIL-style tickets, problems and changes that link back to those assets. Inventory agents can report machines in automatically, and a plugin marketplace covers the rest. It is GPL-3.0 (the repository's licence file is the GPLv3 text), PHP with MySQL or MariaDB. Our snippet adapts the glpi-project/docker-images compose example, pins `glpi/glpi:12.0.1` (the current release, 2026-10-28) and `mysql:8.4.13` instead of `latest` and the unpinned `mysql`, generates the database password into `.env`, and adds a database healthcheck so GLPI does not start before MySQL accepts connections. We chose the 12.0 line over 11.0.12: both were released on 2026-10-28 with the same list of security fixes, and the project's security policy supports both lines. Choose 11.0 only if a plugin you need has no build for 12 yet, because GLPI plugins declare the versions they accept. GLPI 12 needs MariaDB 10.11 or MySQL 8.0 or newer. Look elsewhere if you only want a small ticket queue: GLPI is a large application with many menus, and a lighter shared-inbox helpdesk is easier to run.
What you need
Any VPS with at least 1024 MB of RAM
A domain you control — most self-hosted setups need HTTPS in front of them
GLPI's README, the docker-images README and the 12.0.1 release notes flag these before you rely on it:
non-negotiableThe installer creates four accounts: glpi (administrator), tech, normal and post-only, with the passwords glpi, tech, normal and postonly. Anyone who can reach port 8080 can sign in with them until you change the passwords or disable the three you do not use, so do that on first login. After sign-in, GLPI's home page warns administrators about any of these accounts still on its default password.
non-negotiable12.0.1 is a security release. Its notes list a critical external authentication bypass and several high-severity XSS and privilege escalation fixes, so do not stay on 12.0.0, and keep to patch releases of the line you pick. The image README says the project rebuilds the latest release of each supported line weekly for OS and PHP patches without changing GLPI code.
non-negotiableThe database password lives in .env and in GLPI's configuration inside the glpi_data volume (/var/glpi, which holds config, files and the marketplace directory). Back up both that volume and the db_data volume together; a restored GLPI volume with a different database password will not connect.
non-negotiableAuto-install and auto-update run only when all five GLPI_DB_* variables are set. The image then applies database schema updates on restart (GLPI_SKIP_AUTOUPDATE=true turns that off), so take a database backup before changing the image tag, and do not move between the 11.0 and 12.0 lines without reading the upgrade notes.
non-negotiableThe compose example uses a random MySQL root password that exists only in the database container's first-start log. Our snippet keeps that; to run database:enable_timezones you must first grant glpi access to mysql.time_zone_name as the image README describes, which needs that root password from docker compose logs db.
non-negotiableThe container serves plain HTTP on port 80 (published as 8080 here). Put TLS in front of it before the helpdesk is reachable from outside, because ticket content and sign-ins cross the wire.