Hosted naminglive today
No domain, no DNS, no dynamic IP to chase. Your network becomes you@batoncloud.org — or register the domain you already have and never take a name from us.
BatonCloud
Somewhere your agents can actually live and run 24/7.
Managed workspaces for Baton agents, plus the naming and directory that lets networks find each other. The same node model as the one on your laptop — because it is the same node model.
Baton is the open-source runtime underneath — the same one that runs on your laptop. Read how the architecture works: dev.baton.wiki
$ baton cloud register my-team
registered my-team
SHA256:9f2c1a7e…d3b4
$ baton node list
NAME LOCATION STATUS
reviewer cloud running
sandbox local running
same verbs, either column
Where this sits
Five layers, and the one row we are in.
Agent applications sit on top. Baton is the agent and network layer under them. Below that is a row of choices — where your agents actually run — and under it the harness and the model. That row is where we are, and it is a row precisely so that anyone in it can be swapped for anyone else.
APPLICATIONS
CursorCopilotWindsurfPerplexityNotionReplitn8nLangChainZapierand whatever you ship — this layer is the reason the ones below it exist
AGENT API
PROVIDER CONTRACT
RUNTIME
BatonCloudmanaged · this is what we sell
always-onsnapshotsmigrationattach
Google Cloudyour accountAWSyour accountLocal-Machineyour machine
RUNS
AGENT HARNESS
Claude CodeAnthropicCodexOpenAIOpenclawopen sourceOthersbring your own
INFERENCE API
LLM LAYER
ClaudeGeminiLlamaMistralDeepSeekQwenwhichever the harness is pointed at · any OpenAI-compatible endpoint · open weights
Read the arrow between the runtime tier and Baton carefully: it points up. A provider binds into Baton across the Provider Contract — Baton does not run on BatonCloud, and BatonCloud is not a tier of Baton. We are one cell of four in that row, every cell is the same node model, and pointing the CLI at a different one changes nothing above it.
What we run
Four things, and none of them sit in your message path.
BatonCloud helps networks find each other and gives their agents somewhere to run. Once two networks have found one another, traffic goes directly between them and this service is out of the way.
Public directorylive today
Publish and install workspace templates and skills by name. If it vanished tomorrow, networks that can already address each other keep federating. Browse it →
Managed workspaces
A node you did not have to provision, running a workspace that outlives the session. This is the part you pay for — operations, not a capability the open edition lacks.
Endpoint publication
Your address stays current without you editing DNS when an IP moves. Signed by your network's own key — we relay the record, we cannot author one.
The product
Managed cloud agent nodes.
Not a new kind of node — a Baton node that we run. A template describes the office; the node is the office; the workspace is that office once an agent is working in it, and it is still there tomorrow. Ours run in microVMs — a kernel each, not a slice of a shared one — which is a property of the host we declare, not a different kind of Baton.
2VCPU
2 GiBMEMORY
20 GBSTORAGE
1 TBTRANSFER/MO
1 GbpsBANDWIDTH
One node. 2 vCPU · 2 GiB is about a fair share of the host — it bursts higher when neighbours are idle and pauses to almost nothing when yours does. Storage is a hard 20 GB quota on SSD. 7-day backups.
MANAGED SERVICES
Managed hostsoon
a node you never provisioned, kept patched
Always-on uptimesoon
kept running 24/7, idle paused for you
One-click provisionsoon
created and configured, no setup
Managed backupsoon
snapshots taken and kept, 7 days
Reserved egresssoon
a stable outbound address we hold
Endpoint kept currentsoon
your signed address, always published
Offline inbox relaysoon
we relay while your master is down
Encrypted at rest
your keys wrapped under our KEK, never plaintext
Audit trail
every operation on your node, recorded
Hosted directory
publish and install by name, higher quota
Your agent's identity, runtime, attach, snapshots and migration are Baton itself — the same on any node, your laptop included. They are not on this list because you already have them. Everything above is what we run for you.
8VCPU
8 GiBMEMORY
80 GBSTORAGE
4 TBTRANSFER/MO
1 GbpsBANDWIDTH
Up to 4 nodes4
1234
One dedicated machine — 8 vCPU · 8 GiB · 80 GB SSD, yours alone. Allocate it into up to 4 agent nodes that run as one network — priced 25% under the same nodes bought singly.
Everything in Solo NodeAll 10 managed services, on every agent node you allocate.
Managed StudioThe agent nodes on your machine run as one managed network — discovery, endpoints and relay across them.
They bill for the time something runs. We sell a place that stays.
An agent that has to answer at 3am is idle almost all of it — and per-second pricing is the most expensive model there is for a thing that must never go away.
An agent that has to answer at 3am is idle almost all of it — and per-second pricing is the most expensive model there is for a thing that must never go away.
BATON runs without this service.
Baton is open source and Apache-2.0. The node model, the API, the CLI verbs, the node protocol and the snapshot format are the same wherever a node runs — hosting it here creates no second node model and no private Baton API. BatonCloud is one provider, and moving off it is a tested path paired with moving onto it.