SERVOR
Server operationsMonitoringAI copilotRecipesPricingBlogDocsAgent source
Open consoleSign in

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.

  1. 01recondistro and version: apt (Debian/Ubuntu) or dnf (RHEL/Fedora/Rocky/Alma)?
  2. 02reconDocker Engine + compose plugin present? (otherwise the docker step installs them)
  3. 03reconKafka already deployed (container, /opt/kafka/compose.yaml)? healthy → skip
  4. 04recondoes a Kafka data volume already exist? never delete it
  5. 05reconis port 9092 already taken (by which process)?
  6. 06reconat least 2 GB of RAM and a few GB of free disk?
  7. 07actInstall Docker Engine (only if missing)verify
  8. 08actWrite /opt/kafka/compose.yaml (KRaft, single node)verify
  9. 09actRun Kafka (KRaft)verify
  10. 10actThe broker 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.

  1. 01Install Docker Engine (only if missing)Verified bydocker compose version && systemctl is-active docker
  2. 02Write /opt/kafka/compose.yaml (KRaft, single node)Verified bydocker compose -f /opt/kafka/compose.yaml config -q && echo ok
  3. 03Run Kafka (KRaft)Verified bydocker inspect -f "{{.State.Status}}" kafka
  4. 04The broker respondsVerified bydocker exec kafka /opt/kafka/bin/kafka-topics.sh --bootstrap-server localhost:9092 --list >/dev/null 2>&1 && echo ok

SEC.03

Guardrails

Non-negotiable instructions the run must respect, whatever it finds on the server.

Minimum 2 GB of RAM. Broker bound to 127.0.0.1 in PLAINTEXT: do not expose it publicly (remote access = dedicated listener + SASL/TLS, outside this recipe). Never delete the kafka-data volume and do not change the CLUSTER_ID of an existing deployment.

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.

recipe — fail2ban_setup150+ in catalogue
security4 steps · low risk · idempotentrun
reconsshd present? ufw active? existing jails?✓
actinstall fail2ban · write default jails✓
actenable service · restart sshd (safe)✓
verifytest ban 60s · jails active · sshd alive✓

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
Server operationsAI copilotRead the blog

SEC.05

Deploy on Servor button

Maintain Apache Kafka 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.

Deploy on ServorDark background
Deploy on ServorLight background
[![Deploy on Servor](https://servor.app/badges/deploy-on-servor.svg)](https://servor.app/deploy/install-kafka)

SEC.06

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.

Start for freeBack to the catalogue