Skip to content
Bijstaan

For GLPI 11.0 · free and open source

Modular ITSM plugins built for GLPI 11.

GLPI covers core ticketing and inventory well. This suite extends it with change management, on-call alerting, vulnerability tracking, public status pages, and more. Install only the capabilities your team needs.

plugins
28
works with
GLPI 11.0
GPL-3.0 or later
Free
changes to core
None
Exposure dashboard: severity tiles, affected machines, mean time to patch, coverage fraction and confidence mixExposure dashboard: severity tiles, affected machines, mean time to patch, coverage fraction and confidence mix

Vuln — Exposure dashboard: severity tiles, affected machines, mean time to patch, coverage fraction and confidence mix

How it fits

Additions to GLPI, not a replacement for it.

Every one is a plugin you install and can uninstall again. Nothing patches GLPI, nothing swaps a core object for its own copy, and nothing asks you to run a fork.

It builds on what you already have

The plugins extend GLPI’s own tickets, changes, problems and projects rather than making their own copies. Saved searches, notifications, templates and reports keep working, and removing a plugin does not take your data with it.

Nothing new to keep patched

No extra PHP libraries to install or maintain — they use what GLPI already ships. Where one genuinely needs something outside GLPI, like a search server or an AI provider, it says so on its own page rather than in the small print.

Each one works on its own

Install only what you need. When multiple plugins are installed together, they integrate cleanly (such as known errors using typo-tolerant search or PDF exports including procedure checklists), but every plugin is fully functional by itself.

Why these exist

Six things GLPI 11 genuinely does not do.

Each one turned up while building against it. The plugin that answers it is on the right.

Start here

Eight that carry the rest.

The ones most people notice first. The other Twenty are below.

AI

Intelligence

0.7.0

AI for GLPI 11 that works with whichever provider you choose, and the features a technician actually sees on top of it.

  • One API over Anthropic, OpenAI, Gemini and Azure AI Foundry
  • You choose which entities may send anything out at all — none, until you say so
  • It looks things up in GLPI before answering, and eighteen other plugins give it more to look at

Change

Service management

0.1.0

Change enablement built on GLPI’s own changes: a risk score, a shared calendar, freeze windows, collision warnings and a recorded outcome.

  • A weighted questionnaire that turns into a risk band
  • Freeze windows, and warnings when a change is booked inside one
  • Collisions found one hop out through GLPI’s impact graph

SOP

Service management

0.2.0

Interactive procedures that find the ticket, ask only the questions that apply, and record the answers as data.

  • Fourteen kinds of step, so “was the serial recorded?” is something you can report on
  • Steps that appear only when earlier answers, the asset or an approval call for them
  • A step that is not being asked is not outstanding

Major

Service management

0.1.3

Major-incident mode for GLPI 11, and a public status page.

  • One commander, one comms owner, and an audience on every update line
  • A public title that is not the one with hostnames in it
  • One-click attachment of the duplicates, answered when it is over

Signal

Operations

0.1.0

An event and alert pipeline with on-call paging. Monitoring stays where it is.

  • Takes alerts from Alertmanager, any JSON webhook, or email
  • A reading that drifts up and down stays one alert instead of forty
  • Matches the alert to the right asset by serial, MAC, IP then hostname — and never guesses

osquery Inventory

Discovery & inventory

0.3.0

A replacement for GLPI 11’s native Inventory and Agent, built on osquery, with live queries across the fleet.

  • Speaks osquery’s own protocol, so a standard agent works unchanged
  • Assets arrive through GLPI’s own inventory pipeline, rules and all
  • A Go agent that supervises a bundled osqueryd and self-updates

Vuln

Security & identity

0.1.0

Vulnerability and patch exposure derived from the software inventory already in GLPI. No agent, no scanner, no probing.

  • Sees the laptop that is switched off, which a scan window cannot
  • Every match carries a confidence tier, and the weakest never becomes a finding
  • A review queue designed to empty — approving teaches the next hundred advisories

Search

Experience

0.1.0

Typo-tolerant search across GLPI’s records, answering as you type. It never changes who can see what.

  • “priner”, “prnter” and “printr” all find the printer ticket
  • Followups, tasks and solutions indexed with the ticket
  • Filters that build themselves out of whatever the records contain

Everything

The suite, in eight groups.

Grouped by what you are trying to get done, not by which plugin the page came from.

Service management

The work around a ticket that GLPI has no real model for: change enablement, known errors, procedures, major incidents, business services and improvement.

Discovery & inventory

What is out there, and what it costs. Endpoints through osquery, everything that answers SNMP, and the cloud accounts GLPI 11 has no model for.

Operations

The day as it happens: alerts that deduplicate and page a human, and who else has this ticket open right now.

Security & identity

Exposure derived from the inventory you already have, and a way for every entity to bring its own identity provider.

Experience

The interface a technician spends the day inside — reachable, searchable, coherent, and carrying your name rather than GLPI’s.

Documents & reporting

Everything that leaves the instance and is read by somebody who does not use it: PDFs, notification mail, service reports, calendar feeds.

Commercial

The contract, on the ticket and on the invoice. Entitlement where the work happens, billing where the money is.

Intelligence

Works with whichever AI provider you choose, and the features a technician actually sees on top of it.

Clear features, explicit boundaries.

Every plugin clearly documents its scope and requirements, making it straightforward to evaluate whether it fits your workflow before deployment.