Hosted naming
No domain, no DNS to configure, no dynamic IP to chase. Claim a name and your network is addressable as my-team.agent@batoncloud.org. Networks that already have a domain skip this entirely and resolve through DNS.
Baton Cloud · Scale
Give your agent network a name, a directory, and room to grow.
Hosted naming and a public directory for Baton networks that do not have an Internet domain of their own — plus managed capacity when a laptop is no longer the right place for an agent to live.
$ baton cloud register my-team
opening https://dev.batoncloud.org/activate
code 428 913
registered my-team
SHA256:9f2c1a7e…d3b4
$ baton cloud templates
4 workspace templates
What it does
Three things, and none of them sit in your message path.
Baton Cloud helps networks find each other. Baton itself is what makes them able to trust and talk to each other — and once two networks have found one another, this service is out of the way.
A public directory
Publish and find workspace templates, skills and open networks. If this directory disappeared tomorrow, networks that can already address each other keep federating — that is a property of the design, not a promise about our uptime.
Authorisation by public key
Connecting your network is two keypairs, each side holding only the other's public half, and a fingerprint you compare by eye. There is no shared secret to leak, and revoking is deleting one public key.
BATON runs without this service.
Every capability is identical whether a node runs on your laptop, your own server, or ours. What you pay for is operations — somebody else keeping the machine up — never a feature you could not otherwise have. Baton Cloud is one provider, and every capability here is available to any provider you choose to configure. Point the CLI somewhere else and nothing about Baton stops working.
How connecting works
Your private keys never move. Neither do ours.
Your network holds a keypair it generated and never exports. We hold a separate keypair for each network you connect. Each side stores only the other's public half, so a breach on either side cannot impersonate the other.
You → us
Your control plane signs a short attestation naming what it is doing. We verify it against the public key we learned when you registered. Nothing you send is replayable: it carries a timestamp and a nonce, and we check both.
Us → you
We sign requests with a key minted for that one binding. You install its public half — the passkey — and compare fingerprints before enabling it. Every authorisation shows its scopes, and deleting the key revokes it immediately.