SEC.01
The playbook
The run starts read-only: the recon probes decide what happens next. The steps that follow are adapted to the distribution and state found — a real machine is rarely clean.
- 01recondistro (apt or dnf) and architecture (amd64/arm64)
- 02reconNetdata already installed? service active?
- 03reconexisting config directory (native or static /opt)
- 04reconport 19999 free? otherwise who holds it
- 05reconat least 512 MB of RAM and 1 GB of free disk
- 06actInstall Netdata (official kickstart, stable channel)verify
- 07actRestrict the dashboard to 127.0.0.1verify
- 08actResponds on 127.0.0.1:19999verify
SEC.02
What it verifies
Each step ships its own check. The run only moves on when the check passes, so what the recipe reports as done is what is actually on the server.
- 01verifyInstall Netdata (official kickstart, stable channel)Verified by
systemctl is-active netdata - 02verifyRestrict the dashboard to 127.0.0.1Verified by
ss -tlnH "sport = :19999" | grep -vc 127.0.0.1 - 03verifyResponds on 127.0.0.1:19999Verified by
curl -s -o /dev/null -w '%{http_code}' http://127.0.0.1:19999/api/v1/info
SEC.03
Guardrails
Non-negotiable instructions the run must respect, whatever it finds on the server.
The Netdata dashboard has no authentication: never expose it publicly, access it through an SSH tunnel or a protected reverse proxy. Do not claim the node to Netdata Cloud unless explicitly asked.
SEC.04
How a recipe runs in Servor
Servor is zero-knowledge: the platform cannot execute anything on its own. When you launch this recipe, a run reads the reconnaissance, plans the steps and asks for your approval. Each approved command is signed by your browser — with a key the server never sees — then relayed verbatim to the agent, which verifies the signature locally before executing.
search by intent — type “firewall”, get ufw
- 01Read-only reconnaissance before any change
- 02Every command signed by your browser, approved by you
- 03Each step verified before the run moves on, every run kept in the history
SEC.05
Deploy on Servor button
Maintain Netdata or a project that needs it? Put this button in your README or on your site: one click and your users install it on their own server.
SEC.06
More observability recipes
- 01node_exporterPrometheus system metrics exporter, as a systemd service.
- 02PrometheusPrometheus (metrics collection), as a local systemd service on :9090.
- 03GrafanaGrafana OSS (official repo), local on :3000, admin with a random password.
- 04Grafana LokiLoki 3.7 log aggregation via Docker, local on :3100.
- 05Grafana + Prometheus stackGrafana + Prometheus + node_exporter via Docker Compose, datasource preconfigured, all local.
Verified recipe
Run this recipe on your server
Connect a server, launch the recipe, and approve each step as Servor executes and verifies it. Free plan, no card required.