GLPIZabbixMetabase

We know GLPI, Zabbix and Metabase from the inside.

For ten years our founding team has implemented, extended and supported these platforms for IT teams. Along the way we learned that the best fix is made at the source. So when something is wrong in GLPI itself, we contribute the fix to the GLPI project, and once it is accepted it reaches you and everyone else who runs GLPI.

  • Most active community contributor to GLPI
  • Ten years on these three platforms
01 DetectZabbix

Free disk space below 10% on db-prod-02

High Trigger fired at 09:41

02 ActGLPI

Incident opened and routed to the database team

Asset linked · SLA 4h · resolved in 2h 40m

03 ImproveMetabase

Mean time to resolve

3h 12m

18% faster than last month

An example of how the three platforms work together.

What we work on

Three open-source platforms. One team that knows them well.

Each one is strong on its own. Connected properly, they give you a service desk that hears about problems first and a clear view of whether things are getting better.

When they are connected

This is the part most teams never get to, and where we spend a lot of our time.

  • Zabbix to GLPI

    Alerts arrive as tickets

    A Zabbix problem opens a GLPI ticket on its own, updates arrive as follow-ups, and recovery marks it solved.

  • Zabbix to GLPI

    Less noise at the desk

    Correlation and maintenance windows stop one outage from turning into forty duplicate tickets.

  • GLPI and Zabbix to Metabase

    One set of numbers

    SLA, workload and uptime come from the same data, so the monthly review starts from facts.

Open source

When GLPI breaks, we fix it upstream.

A local patch disappears at the next upgrade. So when we find a problem in GLPI, we write the fix for the GLPI project itself and send it to the maintainers for review. Once merged, the fix reaches everyone who runs GLPI, and it stays fixed after every upgrade.

The most active community contributor to GLPI.

Every fix we contribute goes into GLPI itself, for everyone who runs it.

Extend GLPI

We build what GLPI is missing.

Ten years of GLPI projects showed us the same gaps again and again: weeks spent building ITIL from scratch, every ticket's history pieced together by hand, people who will never open a portal, technicians away from a desk, managers without numbers. So we built the missing pieces, on GLPI's own data, rights and configuration, so they survive every upgrade.

How we work

From the first call to the fifth upgrade.

Most engagements follow the same path. You can start at any step.

  1. 01

    Consult

    We look at how your team actually works today, what the platforms are doing, and where the time goes.

  2. 02

    Implement

    Implementation, migration or a clean-up of what is already there, with clear scope and a working result early.

  3. 03

    Integrate

    GLPI, Zabbix and Metabase wired together, plus your directory, email, chat and the tools you already use.

  4. 04

    Support

    Upgrades, fixes and steady improvement, by people who know the code because they contribute to it.

All services

How we think

Solve.

We start from the problem, not the product. Every engagement ends with something that works.

Collaborate.

We work alongside your team, our partners and the open-source community, and we share what we learn.

Evolve.

We keep improving: our products, our skills and the platforms we run for you, release after release.

10years on GLPI, Zabbix and Metabase

A young company with a long head start.

MarifeX is new. The people who started it are not. The founding team has spent the last ten years implementing, upgrading and fixing these three platforms for IT teams, and we started MarifeX to do that work properly and give some of it back.

Headquartered in Navi Mumbai, India. GLPI, Zabbix and Metabase run on servers and in the cloud, and so does our work. We deliver over secure access to teams across India, the Gulf and Latin America, and the engineers on your first call are the ones who do the work.

About MarifeX

Let's plan your next step together.

Starting fresh with GLPI, moving from another tool, or connecting GLPI, Zabbix and Metabase into one service operation. A short call with our engineers is the best place to begin, and you will leave with a clear way forward.