Monitor & Manage Infrastructure

One pane over
every layer of
your estate.

MIMI is the aggregation & correlation layer for NOC teams — reading from NetBox, Prometheus and Icinga to turn a storm of signals into one incident per root cause, with AI-assisted investigations and a governed action gateway on top.

Sign in with Google Workspace Microsoft Azure AD
Fleet pulse — LON1 · NYC3 · FRA2 live
92%
healthy
Active by severity
● 2 crit● 3 warn● 4 info
CASE-2026-0912-014 · 1 root cause
3 signals correlated · Cogent upstream · failover held
local model
Reads from your systems of record NetBox Prometheus Icinga2 Grafana
What MIMI does

Correlate, investigate and act — without replacing what you run.

Every device, metric and check flows into one model. MIMI writes only to its own audit log — your inventory and monitoring stay the source of truth.

AI investigations

A local model walks the blast radius through a tool-calling loop and returns ranked causes with citations. Persistent, auditable, escalatable to a frontier model.

Discovery & onboarding

Least-privilege probes identify a new device, then the model drafts a reviewable onboarding diff — observed committed as-is, inferred flagged for edit.

Config vault & drift

Versioned config capture with running-vs-baseline drift detection, per-vendor normalization, and diffs pinned to the incident that touched them.

Action gateway

One mutation path recomputes each action's tier from blast-radius × reversibility. T1 confirms, T2 needs an admin, T3 needs two plus a ticket.

Unified overview

A live pulse band — fleet health, severity mix, activity — over a real geo map of your sites. Every widget is role-aware and rearrangeable.

Knowledge base

Resolutions promote into runbooks and known-issues that ground the model (RAG) and match new incidents against what you've already solved.

Architecture

Aggregation, not replacement.

Sources of record
NetBox — inventory & topology Prometheus — metrics Icinga2 — checks Grafana — dashboards
MIMI correlation layer
Blast-radius incident engine Local-first model + tools Tiered action gateway Append-only audit
Outcomes
One incident per root cause Approved, reversible changes Knowledge that compounds
Mode A — Standalone
MIMI owns inventory and collects metrics itself. For a small estate where nothing else is the source of truth.
Mode B — Aggregation
Reads NetBox / Prometheus / Icinga read-only, degrading to last-known-good on source failure — never a blank view.
Access & security

Locked down by default.

SSO — Google & Azure AD

OIDC sign-in with Google Workspace and Microsoft Azure AD, coexisting with local accounts.

Registration disabled

Self-registration is off by default. Accounts are provisioned by an administrator or your IdP.

Initial-admin immunity

The first account to register becomes the initial admin — permanently immune from modification by other admins.

Tiered actions (T0–T3)

Every mutation is tier-checked at one gateway; the proposer can't self-downgrade its risk.

Dual approval + windows

High-blast changes need two distinct admins, a linked ticket, and respect per-site change windows.

Append-only audit

Every attempt — including denials — is logged with actor, approver(s) and requested-vs-enforced tier.

4
Sources unified
1 row
Per root cause
T0–T3
Tiered actions
100%
Actions audited

Bring your whole estate into focus.

Sign in with your organization identity, or set up the first administrator to get started.

MIMI Monitor & Manage Infrastructure Aggregates NetBox · Prometheus · Icinga · Grafana — writes only to audit.
{{ authTitle }}
{{ authSub }}
or local account
Registration is disabled. Contact your administrator for access, or set up the first admin if none exists yet.
No administrator exists yet. The first account created becomes the initial administrator — permanently immune from modification by other admins. Self-registration then locks automatically.
or local admin
← Back to sign in
{{ loadingMsg }}
{{ doneTitle }}
{{ doneMsg }}
Enter MIMI