Skip to main content
The orchestrator that manages your container.

​
What is the Fleet Agent?

The Fleet Agent is a service running on dedicated servers. It’s responsible for the entire lifecycle of user containers — from spinning them up to freezing them when idle to destroying them when no longer needed. It also manages the networking layer: DNS records and reverse proxy routes.

​
API endpoints

The Fleet Agent exposes a simple REST API, authenticated with a shared cluster secret:
MethodEndpointDescription
POST/spawnClone template, start container, configure networking
POST/freezeSuspend container processes, preserve state
POST/restoreResume frozen container, reconnect services
POST/killDestroy container, clean up DNS and proxy routes

​
Spawn flow

When a user starts a new session:
1

Clone template

The fleet clones the template image to create a new container using copy-on-write.
2

Configure the container

CPU, RAM, and storage limits are set based on the user’s plan.
3

Inject credentials

The user’s AI provider API key, channel credentials, and integration configs are written into the container.
4

Start the container

The container boots. ZeroClaw starts automatically.
5

Set up networking

A DNS record is created and a reverse proxy route is added for HTTPS termination.
6

Health check

The fleet polls the ZeroClaw gateway inside the container until it responds, confirming the assistant is ready.

​
Freeze and restore

Freezing a container is like hibernating a laptop — all processes are suspended in place, but the container uses zero CPU and minimal RAM. The key benefit: messaging bridges don’t need to re-authenticate. WhatsApp sessions, Signal connections, and other stateful processes resume exactly where they left off.

​
DNS management

Each container gets a unique hostname for WebSocket connections from the browser:
  • When a container is spawned, a DNS record is created
  • When a container is killed, the record is deleted

​
Reverse proxy

The reverse proxy handles:
  • TLS termination — Automatic HTTPS certificates
  • Request routing — Routes requests from the container’s hostname to its internal IP
  • WebSocket support — Upgrades HTTP connections for real-time communication
Routes are added and removed dynamically as containers are created and destroyed.

​
Server infrastructure

The Fleet Agent runs on dedicated servers in European data centers with:
  • High CPU count for running multiple containers
  • Fast NVMe storage for copy-on-write cloning
  • Direct internet connectivity

​
Scaling

Each server runs one Fleet Agent managing containers on that machine. Scaling is done by adding more servers. The public API routes users to the appropriate server based on region and capacity.