Servers Overview

Servers are first-class resources in Reoclo’s BYOS model. Any Linux host with an IP can be onboarded, including instances from Hetzner, AWS, and DigitalOcean, as well as bare metal or home lab systems. Reoclo does not rely on provider SDK integrations, so operational behavior stays consistent across infrastructure vendors.

Each server uses a single connection type: SSH for direct key-based access or RUNNER for agent-based access over persistent WebSocket. SSH is a good fit when inbound administration is available; Runner is optimized for firewalled, NATed, or zero-inbound networks where an outbound connection from the host is easier to manage.

Server lifecycle is explicit and operationally meaningful: PROVISIONING during initial checks, ACTIVE when healthy, UNREACHABLE after repeated failures, and DECOMMISSIONED when retired. Reoclo updates status automatically through health checks and connection telemetry so deployment decisions reflect real host availability.