Skip to main content
A worker is a long-running Python process. Run it anywhere that can reach AIR over HTTPS and the private systems used by its tools.

Container example

Configure runtime values through your deployment system:

Kubernetes secret reference

Operational checklist

  • Pin the SDK version and test upgrades before rollout.
  • Give staging and production separate worker keys.
  • Give the worker’s database identity the minimum required permissions.
  • Let the process receive SIGTERM; the CLI stops claiming work and closes its connections.
  • Start with one staging replica and scale after observing tool latency and throughput.
  • Rotate a key by deploying the new value, confirming reconnection, and revoking the old key.
  • Monitor registration, task failure, lease loss, and downstream timeouts.
Do not put real credentials in a Dockerfile, image layer, committed .env file, or Kubernetes manifest. Sync them from a managed vault at runtime.