Declared, never discovered
You name the paths. Nothing crawls a filesystem looking for things that might be config, and reads stay read-only.
Open source ยท Desktop and server
Live health, metric history, one log stream, alerts and an assistant that can actually investigate, across 31 kinds of infrastructure, from one window. It reads the configuration that governs a system as well as the metrics it reports.
One window
Every connection reports its own health on its own interval: service metrics, plus each container, job, node, index and long-running query, with its own health and numbers.
Incidents
When orders-api runs out of memory and three things that talk to it start complaining, you do not have four problems. root groups alerts from what the collectors already recorded: onset times, declared dependencies, observed changes. No model involved, so it works with no LLM configured at all.
Configuration
A Redis at 1.8 GB of a 2 GB maxmemory with noeviction is not a memory graph to keep an eye on. It is a decision that starts refusing writes in about three hours, and neither the metric nor the config file says so alone.
You name the paths. Nothing crawls a filesystem looking for things that might be config, and reads stay read-only.
Redaction sits between the file and every consumer. There is no accessor that returns an unredacted body.
The findings that matter come from rules that always fire on the same input. The assistant's own are kept apart and scored apart.
On this machine, inside a Docker container, on a server over SSH, or inside a Kubernetes pod.
Estate graph
Every connection, the containers and pods its hosts report, the outside services traces show, teams, environments and declared files, as one graph you can walk. Every link says how root knows it.
Dashboards and Explore
Paste a Grafana export and its PromQL panels run. Explore PromQL, LogQL and traces in one place, and compare any window with yesterday. Alert rules replay the last week before you save them, so you know how often they would have fired.
The assistant
It reads your monitoring data through a fixed set of tools and follows the trail: an alert leads to a snapshot, which leads to logs, which leads to a container inspect. It cites the exit code and the log line.
Connections
Each one collects what actually matters for that system: a hit rate and its evictions, a queue with nobody consuming it, an etcd near its quota while /health keeps answering true. Adding a kind is a backend-only change.
Run it
The desktop app and the server run the same collectors, rules, incident grouping and forecaster. Nothing to connect yet? Start the live demo from the first screen: a simulated shop of thirteen connections, where every twelve minutes something goes wrong.
Nothing to configure and nobody to sign in to. It reads a config file you own, holds credentials in the OS keychain and binds loopback only.
git clone https://github.com/aniketshukla1/root
cd root
npm install
npm run tauri dev
Needs Node 22, a Rust toolchain and the Tauri 2 prerequisites. No signed installers yet, so this builds from source.
Collectors run somewhere that stays up, history goes to Postgres, and the client is a browser on any device. Accounts, roles and single sign-on. It refuses to start without a token.
cd deploy
cp .env.example .env # put real values in it
docker compose up -d
open http://localhost:7777
The first person to open it claims it and becomes its administrator.
It also keeps score of itself: a Scorecard of which findings were right, which were noise, and which problems it missed.