Skip to main content

Deploying to Production

This tutorial covers taking a Waxell agent from your laptop to production. Waxell hosts the execution infrastructure — workers, queues, storage, and isolation — so going to production is a push, a choice of execution tier, and monitoring.

Push the agent​

Point the CLI at your production tenant and push. Use a named profile so you never push to the wrong tenant:

wax -p prod whoami             # confirm the tenant before you push
wax -p prod push --dry-run     # validate the manifest or agent file
wax -p prod push               # publish (auto-discovers waxell.yaml)
wax -p prod agents info my-agent

Versions are immutable: bump version: on every re-push. To change which pushed version is served:

wax -p prod agents promote my-agent --version 1.2.0    # flip the default to an existing version
wax -p prod agents rollback my-agent --version 1.1.0   # snapshot an older version as a new one
wax -p prod agents pause my-agent                      # stop accepting new runs
wax -p prod agents activate my-agent                   # resume

Choose an execution tier​

Agents run on shared workers by default. For per-execution isolation or custom dependencies, see Execution Tiers:

  • Shared — the default; nothing to configure.
  • Warm slot — selected by your tenant's sensitivity tier or reserved capacity.
  • Self-contained — declare a dependencies: block in waxell.yaml and the platform builds the agent its own container on push.

For a self-contained agent, check the build:

wax -p prod agents builds my-agent

Monitor runs​

wax -p prod runs list --agent my-agent     # recent runs
wax -p prod runs watch --agent my-agent    # stream new runs as they start
wax -p prod runs show <run_id> --spans     # one run, with its span tree
wax -p prod runs tail <run_id>             # follow a run until it finishes

Monitoring​

Monitor agents via the dashboard:

  • Execution metrics: Success rate, latency, throughput
  • Token usage: LLM token consumption
  • Error tracking: Failed executions and causes
  • Audit logs: All agent actions

Next Steps​