Workers

Bring-your-own-worker (BYOW)

StatIO runs global workers by default. Deploy your own worker only when you need monitoring from inside private networks, air-gapped segments with egress, or a specific geographic location.

How it works

• The worker executes your monitors (HTTP / TCP / ICMP).

• Results are sent over outbound HTTPS to the StatIO API.

• Data is aggregated on StatIO servers and shown in dashboards.

Network requirement: outbound HTTPS to statio.net only. No inbound access required.

Want to self-host the StatIO API? Contact sales for an enterprise plan, or review pricing.

Run a worker (one-liner)

Create a worker in the UI, set its label and coordinates there, then run:

docker run -d --restart unless-stopped \
  --name statio-worker \
  -e WORKER_KEY=wk_live_paste_here \
  -v statio-worker-data:/data \
  statio/worker:latest

That’s it. The worker will automatically connect to https://statio.net.

Using an env file (recommended)

For security and automation, store secrets in an env file instead of putting them in your shell history.

# worker.env
WORKER_KEY=wk_live_paste_here

docker run -d --restart unless-stopped \
  --name statio-worker \
  --env-file ./worker.env \
  -v statio-worker-data:/data \
  statio/worker:latest

Security

• Treat WORKER_KEY like a password.

• Rotate keys regularly using “Roll key”.

• Workers initiate outbound connections only.