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 and version: apt (Debian/Ubuntu) or dnf (RHEL/Fedora/Rocky/Alma)?
- 02reconNATS already present? which version?
- 03reconnats-server service active? does a config exist in /etc/nats?
- 04reconis port 4222 already taken (by which process)?
- 05reconis port 8222 already taken (by which process)?
- 06reconarchitecture (x86_64 → amd64, aarch64 → arm64) for the binary
- 07actInstall nats-server (official binary)verify
- 08actWrite the config and the systemd serviceverify
- 09actEnable and startverify
- 10actNATS respondsverify
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 nats-server (official binary)Verified by
/usr/local/bin/nats-server --version - 02verifyWrite the config and the systemd serviceVerified by
/usr/local/bin/nats-server -t -c /etc/nats/nats-server.conf >/dev/null 2>&1 && echo ok - 03verifyEnable and startVerified by
systemctl is-active nats-server - 04verifyNATS respondsVerified by
curl -fsS http://127.0.0.1:8222/healthz
SEC.03
Guardrails
Non-negotiable instructions the run must respect, whatever it finds on the server.
NATS listens on 127.0.0.1: do not expose it (neither 4222 nor the 8222 monitoring) without authentication (token/nkeys) configured. Do not touch an existing /etc/nats config without a backup. Binary only from the nats-io GitHub releases.
SEC.04
Variables
What you choose before launching — the recipe fills in the rest.
| Name | Meaning |
|---|---|
| ${jetstream} | Enable JetStream (persistence) |
SEC.05
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.06
Deploy on Servor button
Maintain NATS 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.
Dark background
Light background[](https://servor.app/deploy/install-nats)SEC.07
More cache & queues recipes
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.