Deploy
axon deploy. A stable production URL. An API key. Durable storage. No Dockerfile, no
infra config, no deployment branch. The same folder that ran in your terminal is now a
live cloud service.
A deployed agent is the same folder you ran locally, hosted as a service. The source
doesn't change. The interface does — no TUI, just the HTTP routes you defined in
server/api/, plus the built-in ones.
Axon Cloud
One command. Managed infrastructure, isolated container, durable data/, and the TUI
connects to it from anywhere you're logged in.
axon deploy
Anywhere it runs, you can reach it
Wherever the agent ends up, you drive it from the terminal you already use. :attach
binds to an agent running at a URL — a dev server on this machine, a container on your
network, a deployment:
:attach http://localhost:3010
The handshake resolves the agent's identity, its modules and tools, and its engine, then hydrates the session — so it reads exactly like a local agent. Attaching boots nothing and detaching leaves it running.
Your agent is never locked in
The agent is a folder — not a feature of our infrastructure. The same image Axon Cloud runs will run it from a mount, on any host with Docker:
docker run -v $PWD:/agent -p 8080:8080 axon/base:0.3.6
It attaches the same way, and axon bundle --image produces a
self-contained image when a mount is not available. If our hosting isn't
the best place for your agent, you can take it elsewhere — and that's deliberate. Axon
Cloud has to earn the deployment by being the easiest and best-run home for it, not by
holding your agent hostage.
Today, self-hosting is a build artifact and a container platform of your choice — first-class support, with tested provider guides and tooling, is coming. Axon Cloud is the path we've built, refined, and stand behind.