The Omarchy Robots Manual

Chapter 10

Security

A robot sits on a lab network, often next to other people’s machines. The defaults are strict and there is little to configure.

validate checks the SSH and firewall settings on every run, so a hand edit that weakens them shows up as a FAIL.

Opening a port

Only when you need it, in robot.nix:

networking.firewall.allowedTCPPorts = [ 8080 ];

When S2 runs on another machine (an edge server, a cloud host), the link between the runtime and S2 carries goals, decisions and execution summaries. The OS secures it, not the runtime: omarchy.robot.s2Link puts it in a WireGuard tunnel, and the runtime adds no TLS of its own.

omarchy.robot.s2Link = {
  enable = true;
  address = "10.77.0.1";                        # the robot, inside the tunnel
  privateKeyFile = "/var/lib/omarchy-s2-link/private.key";
  peer = {
    address = "10.77.0.2";                      # S2's machine, inside the tunnel
    publicKey = "base64 public key of S2's machine";
    endpoint = "edge.lab:51820";
  };
};

What is not here yet

No secure boot, no disk encryption, no automatic updates. Releases are source only: you build every system yourself from pinned inputs, so what runs on the robot is what flake.lock says.