METI · an Infobien product family
METI gathers the alarms of your monitoring tools in one place, watches applications, network and infrastructure with its own agents, cuts the noise, marks the root cause and gets it to the right team. It runs in your own data centre.
Illustrative interface · all values are sample data
01 Product family
The METI family treats the infrastructure that runs from the data centre to the field, and the process that manages it, as one subject.
IT observability and event management
Brings together the events of the monitoring products you already own, then adds APM, network monitoring, technology monitoring, discovery, topology and AI that runs locally.
Who it is forNOC and IT operations teams, network teams, SREs and developers
See the modulesVendor- and model-independent IoT / BMS data platform
Collects data from building automation, energy and field devices in hospitals and large facilities, normalises it into a shared metric dictionary, stores it and raises alarms with threshold and anomaly rules.
Who it is forFacility engineering teams, BMS integrators, contract and SLA managers
See the modulesService management
The service management product that will connect the events produced by METI and METI IoT to record, SLA and on-call processes. It is under development; its scope is given below as planned.
Who it is forService desk, incident managers, on-call teams
See the modules02 Modules
Pick a module: see what it is for, which capabilities it offers and how it looks on screen.
All your monitoring tools, one event list
Collects events, metrics and topology from different monitoring products on a schedule and shows them in a single list, in a shared language of severity and priority.
Illustrative interface · sample data
03 How it works
Data comes in from your monitoring tools, METI agents, network devices, cloud services and field protocols.
Events are translated into a shared severity language, matched with topology, and those belonging to the same failure are grouped.
The root-cause candidate is marked with a confidence percentage and its reasoning; diagnoses show the chain from symptom to evidence.
The event reaches the responsible team on its own channel, is assigned, escalated when needed and forwarded to the ticketing system.
04 Principles
Four principles shape the design of METI. Each one is documented behaviour of the product.
METI is installed in your own environment. The AI runs locally; no data is sent to any external AI service.
Root cause, diagnosis and anomaly results come with their reasoning and evidence. No decision comes out of a black box.
A metric that was not collected shows "not collected"; an unmeasured device shows "no data". Zero and unknown are kept apart.
ID numbers, cards, IBANs, emails and phone numbers are masked at the source. Secrets are stored encrypted and every action lands in the audit log.
One event list instead of ten separate screens; a handful of cases with a marked root cause instead of hundreds of alarms.
Device health, flows, routing neighbours, configuration backups and capacity forecasts in the same place.
Traces, SQL statements, errors and release impact; an answer in numbers to "where does the time go".
Building automation, energy and field devices in a single vendor-independent data model; alarms with SLA clocks.
05 Integrations
The monitoring products METI connects to, the technologies it monitors, the protocols it speaks and its notification channels.
Product and protocol names are trademarks of their respective owners.
06 Frequently asked
It does not have to. METI collects and unifies the events of the monitoring products you have; if you wish, its own APM, NMS and technology monitoring modules fill the gaps, or help you reduce the number of tools over time.
METI is installed in your environment: on Kubernetes or as systemd services. An offline image bundle is available for environments with no internet access. One installation serves one organisation.
No. The correlation and root-cause engine runs inside the installation and trains its model locally on your own event history. The optional incident assistant, too, connects only to a language model endpoint inside your organisation, and refuses an address that is not on a private network.
Event management, notification and assignment are part of the core. APM, NMS, agents and AI are separately licensed modules; you can start with what you need and add more later.
It looks at the protocol a device speaks, not its brand: MQTT, Modbus, BACnet, OPC UA, SNMP, LoRaWAN and M-Bus. Device-specific details are defined as a profile record; a new device class needs no software change.
METI ITSM is under development and is described on this site with its planned scope. Today METI offers assignment and escalation, incident records, on-call schedules and auto-assignment to the on-call person within itself, and forwards tickets to systems such as Jira and ServiceNow.
07 Contact us
Tell us which systems you monitor and what is hard today; we will show you the modules that fit, on a demo that resembles your own environment.
