⊙ overview.html
⊙ platform.html
1,284 endpoints monitored Talk to us
imhub status --all

ITSM for IT teams that actually run prod.

Monitoring, incidents, patching, and asset management in one workspace built like the tools you already use. Keyboard-first, scripted, audit-ready.

Book a walkthrough Read the platform docs
imhub@acme:~ — ssh imhub.it-maintenance-hub.com
monitoring/status.json

Live across every customer estate.

Independently monitored components, real-time status, 90 days of bars.

API gateway ● operational

api.imhub.network
p50 · 38msuptime · 99.99%

Ingest pipeline ● operational

ingest.imhub.network
5.2M ev/minuptime · 99.97%

Web console ● operational

app.imhub.network
p50 · 124msuptime · 99.99%

Patch service ● degraded

patch.imhub.network
partial slowdownuptime · 99.91%

module/monitoring.imhub

Monitoring built for the alerts you actually want.

Synthetic checks, log-based alerts, and metric anomaly detection in one place. Routed by your on-call calendar, escalated by your runbook, silenced when the upstream is the cause.

  • HTTP, DNS, TCP, gRPC, mailflow synthetic checks
  • Log alerts via Loki, ES, or syslog
  • Metric anomalies via streaming z-score and seasonal models
  • Alert grouping that survives a noisy upstream
monitor.yaml imhub config validate
1# acme-prod-db slow query monitor 2monitor: 3 name: "prod-db slow query" 4 type: metric 5 expr: avg_over_time(query_p95_ms[5m]) 6 threshold: > 450 7 severity: P2 8 runbook: "runbooks/db-slow.md" 9 notify: 10 - oncall(team="db") 11 - slack("#prod-db")

module/incidents.imhub

Incidents with a runbook attached.

Every incident gets a structured timeline, an attached runbook, and a post-mortem template that fills itself in from the incident's own data.

  • Slack & Teams two-way bridges
  • Runbook-as-code, versioned in your repo
  • Auto-generated timeline from monitor and pager events
  • Post-mortem drafts that pull the data they need
incident.json INC-2284
1{ 2 "id": "INC-2284", 3 "severity": "P2", 4 "service": "acme-prod-db", 5 "status": "acked", 6 "opened_at": "2026-04-28T03:42:14Z", 7 "runbook": "runbooks/db-slow.md", 8 "oncall": "db@acme", 9 "channel": "#inc-2284" 10}

module/patching.imhub

Patch what you can, defer what you must.

Patching campaigns scoped by tag, target, and risk. Full audit trail of what shipped where. CVE catalog with our own severity assessment for your stack.

  • Linux, Windows, macOS, ESXi, Kubernetes
  • Maintenance window scheduling per asset class
  • CVE catalog with stack-specific severity
  • Audit-ready evidence pack on demand
patch-campaign.imhub $ imhub patch apply
1$ imhub patch apply --tag prod --cve CVE-2026-0241 2 3scope: 412 endpoints (tag=prod) 4maintenance: window-prod-2 (Sun 02:00-04:00 UTC) 5action: apt upgrade openssl --target=fixed 6rollback plan: snapshot before, verify, revert if hash drift 7 8[ok] 412/412 endpoints patched 9[ok] evidence pack written: ./patches/2026-04-28/

Run prod with fewer 3am pages.

Talk to a real engineer about your stack. We'll come prepared, having read your published architecture.

Book a walkthrough