No. Baton is open source and Apache-2.0 — the node model, the API, the CLI verbs and the snapshot format are the same wherever a node runs. With this service entirely unreachable every local capability keeps working; only public directory browsing degrades.

Operations, never capability. Three things draw Credits: your agents' run time, the intelligence they call on (the decision plane, cloud intelligence, models, search, browser) and the resources they use (storage, network, anything we settle with an outside provider for you). Your agent's identity, runtime, attach, snapshots and migration are Baton itself — the same on any node, your laptop included — so they are not on the price list.

No. Credits are prepaid service credits — credit toward running agents on BatonCloud, at $1 = 10 Credits. They are not transferable, not tradable, not exchangeable for cash, and they are not a token or a cryptocurrency. They exist so that runtime, intelligence and resources — which have nothing in common cost-wise — can be read as one number instead of six meters. Nothing is metered today: there is no balance on any account and no code that keeps one.

An agent we run and keep reachable, in a microVM of its own — a kernel each, not a slice of a shared one. You choose how it is served, not what it runs on: Standard for everyday coding, research and personal agents, Premium for heavy coding, browser work, builds and long-running jobs. Underneath it is an ordinary Baton node — there is no second node model here, which is what makes moving one off us a tested path rather than a rewrite.

CPU and memory are ceilings. Standard is 2 vCPU · 4 GB Workspace, Premium 4 vCPU · 8 GB Workspace. A busy agent bursts up to its class ceiling, not past it; an idle one falls to almost nothing. Storage and outbound traffic: to be announced. Their allowances are not set yet and will be published before billing opens.

No. This service is not in the message path. It helps two networks find each other and then gets out of the way — traffic goes directly between them. We hold public keys, a signed endpoint record, and whatever you publish to the directory.

We are in early access. The flow is built, but checkout is off and nothing is charged today — provisioning a Cloud Agent is not shipped yet, and we do not sell what does not run. Join the waitlist to get in line; you will be first when it opens.

Networks that can already address each other keep federating. A registry outage is a discovery outage — it cannot break connections that already exist, and it cannot let anyone impersonate your network, because your identity is a keypair we do not hold half of.