← backNot built yet.
Netric is in early development. There is no docs site, no pricing page, and no changelog feed yet — the landing page is about as much product as exists in public. Here’s what the roadmap looks like so you know where this is going.
roadmap · 8 phases
- p0bootstrap
repo, ci/cd, vercel, supabase, brand system, env isolation, per-project identity. complete 2026-04-10.
done - p1thin vertical slice
one cisco device → polled by an on-prem collector → encrypted config → posted to web api → decrypted → snapshot → diff → drift event → visible in dashboard. no ai yet. this marketing page is part of phase 1.
in progress - p2claude drift analysis
claude-written drift summaries with severity, likely cause, and suggested remediation, pinned inline to specific diff hunks. the ai annotation cards on the landing page are a preview of the phase 2 output shape.
planned - p2.5hardened sensor node appliance
a signed minimal debian 12 image shipped as ova (esxi), vhdx (hyper-v), and qcow2 (proxmox). first-boot pairing via rfc 8628 device-authorization-grant tui — zero ssh, zero config editing, type a six-digit code into the dashboard.
planned - p4psa dispatch
webhooks into ninjaone, connectwise, and autotask. when a drift event lands with a critical severity, a ticket gets created in the msp’s psa without anyone touching anything.
planned - p5snmp metrics + anomaly detection
time-series telemetry with pg_partman range partitioning, baseline anomaly detection on interface, cpu, memory, and latency counters. "why is the network slow" answered in plain english.
planned - p6client reports
scheduled pdf reports per site — monthly drift summary, top offenders, ai-written executive tl;dr. the thing the msp forwards to the customer at month end.
planned - p7+netric reach
thousandeyes-caliber synthetic monitoring with a channel islands agent moat. answers the "whose fault is it" question by correlating probe failures across agents and shared network paths.
planned