noc

noc connects only where you point it: the endpoint you save below is stored in this browser and queried straight from it — what that does and does not promise is explained under the panel.

noc is a self-prioritizing, always-on board for the metrics you already collect. Point it at a Prometheus-compatible endpoint you run — Prometheus, Thanos, Mimir, Cortex, VictoriaMetrics, GreptimeDB — and it scores every series client-side, reallocating panel size, color, and focus toward whatever's behaving unusually right now. It's a display and sharing surface, not an investigation tool and not an alerting system: it decides what deserves your eyes, it never pages anyone.

noc is in active development. What's wired up so far is the connection check above, a single panel you can point at any query, and the board itself — which lives on its own page. It builds itself from whatever your endpoint reports and then reorders and resizes itself from what it scores. Once an endpoint is saved the board polls it on a fixed interval and keeps scoring; when a poll fails it stops presenting what's on screen as a current reading.

noc has no accounts and no server of its own: boards live in your browser, and every query goes straight from your browser to the endpoint you configure — nocternal never sees it. That's a narrower promise than the redaction tools make, on purpose: their connect-src 'none' is something your browser enforces, and you can confirm it in DevTools in five seconds. noc's policy has to stay open enough to reach wherever you point it, so it can't prove the same thing by itself — open your Network tab and check for yourself that every request goes to the endpoint you configured, nothing else. And noc doesn't change where your data already lives: point it at your own infrastructure and it stays there; point it at someone else's cloud, and it left your network before noc ever entered the picture.