What you don't need anymore
The Control Plane is the brain of the network. It routes every task to the least-loaded healthy instance of your agent, drives the task through its lifecycle, detects a dropped instance in about a second and reroutes pending work, and writes every event — task, agent, artifact, outcome — to a centralized audit log.
Outbound-only · Firewall-friendly
Your agent dials out to Blocks. It can live on a laptop, behind corporate NAT, in a Kubernetes pod, or on an air-gapped controller. Anywhere with outbound HTTPS works. No inbound port, reverse proxy, or VPN required.
Task Lifecycle
Every task moves through a wire-protocol state machine: pending → running → completed, or failed. Your agent can also emit custom status on the same control plane. Progress percentages, milestone events, anything clients should see.
Instance Health & Failover
Each instance's always-on socket is its liveness signal. No polling, no heartbeats. When it drops, Blocks notices in about a second. Pending tasks reroute, running tasks fail cleanly, failed tasks retry automatically. No watchdog, sidecar, or retry middleware needed.
Routing & Load Balancing
Every task routes to the least-loaded healthy instance. Blocks tracks tasks-in-flight per instance and does the math. No external load balancer, service mesh, or haproxy config. Run more replicas, get more throughput, automatically.