GLPI services

GLPI, set up the way your team actually works.

We plan, implement, upgrade and support GLPI for IT teams and service providers. Because we work on GLPI's own code, we know where it bends and where it breaks, and we design around both.

Service desk · My queue
  • #4821Disk space low on db-prod-02In progress
  • #4822Laptop for a new joinerApproval
  • #4823VPN drops for the sales teamAssigned
  • #4824Printer offline, third floorSolved
Illustration with example data.

What we do

Everything a GLPI platform needs, from the first plan to the next upgrade.

  • Assessment and design

    We review your current GLPI or plan a new one: entities, profiles, categories, SLAs, approval flows and the asset model, written down before anything is built.

  • Implementation

    Installation on your servers or in your cloud, then configuration, rules, notifications and forms, with a working service desk early in the project.

  • Migration

    From another service desk tool or from an older GLPI. Tickets, assets, users and history are moved with checks at every step.

  • Upgrades

    Major-version upgrades rehearsed on a copy first, with every plugin checked for compatibility before the real upgrade window.

  • Integrations

    Active Directory and LDAP, single sign-on, mail collectors, the inventory agent, Zabbix, and your own systems through the GLPI API.

  • Support

    Fixes, changes and regular health checks once you are live, from the people who know your setup and the GLPI code behind it.

Where GLPI projects go wrong

Ten years of GLPI taught us where the traps are.

Most problems we are asked to fix were designed in on day one. These are the ones we see most.

  1. 01

    The trap

    Rules that fight each other

    Ticket and asset rules pile up over the years until nobody can say why a ticket landed where it did.

    What we do

    We map the rules before writing them, decide the order they run in, and test that order with real examples.

  2. 02

    The trap

    Entities designed like an org chart

    Copying the company structure into entities looks tidy on day one and makes rights painful by year two.

    What we do

    We design entities around who must see what, which keeps profiles simple as the organisation changes.

  3. 03

    The trap

    Upgrades postponed for years

    Each skipped release makes the next upgrade riskier, until the platform is stuck on an unsupported version.

    What we do

    We rehearse every upgrade on a copy, check each plugin, and then upgrade in a planned window with a way back.

  4. 04

    The trap

    Local patches to the core

    A quick change to GLPI files fixes today and quietly breaks at the next release.

    What we do

    We never edit GLPI’s own files. Changes go into plugins and configuration, and fixes the core needs are submitted to the GLPI project.

GLPI beyond IT

The same platform can run more than the IT desk.

GLPI's catalogue, approvals, SLAs and assets work just as well for other teams. We set them up so each team sees only its own work.

  • HR and people services

    Joiner, mover and leaver requests with approvals across HR, IT and facilities, from one catalogue.

  • Facilities and maintenance

    Requests for buildings and equipment, planned maintenance and the asset history behind every repair.

  • Contracts, licences and suppliers

    Renewal dates, licence counts, warranties and supplier contacts kept next to the assets they cover.

Upstream

The most active community contributor to GLPI.

When we find a bug in GLPI, the fix goes to the GLPI project for review, not into a local patch. That is how we keep learning the code, and why your platform keeps working after every upgrade.

  1. Apply form conditions on actor questions filled with a default valueMerged · #25695 · 30 Oct 2026
  2. Do not give the same index to concurrent answers of a formMerged · #26029 · 30 Oct 2026
  3. Protect the login and the directory link of users against unallowed updatesMerged · #25775 · 30 Oct 2026

FAQ

Questions we get asked

Do you work with GLPI Network or the community edition?

Both. The software is the same GLPI. GLPI Network adds the publisher’s subscription services and some plugins. We work on either, and we will tell you plainly when a paid plugin is a better choice than building something.

Can you take over a GLPI that someone else set up?

Yes. We start with a health check of the version, plugins, rules, entities, performance and data quality, and give you a prioritised list before we change anything.

How long does an implementation take?

It depends on your scope, so we only give a timeline after the assessment, never before. When your processes fit a standard ITIL model, the MarifeX Enterprise Accelerator starts you from a working service desk instead of a blank installation, which removes much of the setup work.

Our GLPI code has been customised. Can it still be upgraded?

Yes. We first find every change made to GLPI’s own files, using GLPI’s source code check where it applies and a comparison with the original release where it does not. Each change that is still needed moves into a plugin or configuration where possible, and the upgrade is rehearsed on a copy before the real window.

Will our customisations survive upgrades?

Yes, when they are built the right way. We never edit GLPI’s own files, because those edits are overwritten at the next upgrade. Customisations go into plugins and configuration. If something can only be fixed in GLPI itself, we submit the fix to the GLPI project for its maintainers to review, so it arrives in a future release for everyone.

Let's shape your GLPI.

A new service desk, a move from another tool, an upgrade or a new way of working. Start with a short call and leave with a clear plan.