Cloud Service

We do not charge for Baton. We charge for running your agents.

Baton is open source and Apache-2.0. Every capability is identical whether an agent runs on your laptop, your own server, or ours — so what is on this page is operations, never a feature held back. What you create here is a Cloud Agent, not a machine: you choose how it is served, we choose what it runs on, and everything it consumes is counted in Credits.

Managed Agent Runtime

Two service classes. You pay for what runs, not for what you keep.

Standard0.0005/SEC

Everyday coding, research and personal agents that stay reachable.

RESOURCES
CPU
2 vCPU
RAM
2 GiB
Storage
20 GB
Bandwidth
1 TB/mo
SERVICE LEVEL
Compute priority
standard
Memory profile
standard
Cold start
standard
Concurrent operations
standard
Scheduler priority
normal queue
Long-running jobs
best effort
Runtime rate
baseline

CPU, memory and bandwidth are ceilings a busy agent bursts to, not a reservation — an idle one falls to almost nothing. Storage is a hard quota. Metered in Credits per minute of run time: an agent that is asleep draws no runtime Credits. Rates are published before billing opens.

MANAGED SERVICES
Managed hostsoon

an agent you never provisioned, kept patched

Always-on uptimesoon

kept reachable 24/7, idle paused for you

One-click provisionsoon

created and configured, no setup

Managed backupsoon

snapshots taken and kept for you

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 agent, 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.

Early access · nothing is charged

Three things are metered

Runtime is not the whole bill, so the other two are named here rather than found on an invoice.

Managed Agent Runtime

Run time, by class. Idle draws nothing.

Intelligence

The decision plane, cloud intelligence, models, search and browser work.

Resources

Storage, network and anything we settle with an external provider for you.

One unit. Everything BatonCloud runs for you is metered in Credits. $1 = 10 Credits.

Prepaid service credits — not a token. Credits are prepaid credit toward running agents on BatonCloud. They are not transferable, not tradable, not exchangeable for cash, and are not a token or cryptocurrency.

You pay for what runs, not for what you own. There is no per-agent subscription. An idle agent draws no runtime Credits, so keeping twenty agents costs what running them costs.

The rates on the cards are indicative, and no meter is running. Final per-unit rates are published before billing opens. Today billing is off: there is no Credit balance on any BatonCloud account, no usage is being charged, and nothing on this page takes payment.

Enterprise Solution

For companies with their own compliance line.

Need more than a class?

For companies with their own compliance line.

Talk to us
  • Dedicated or self-hosted Cloud Suite
  • Custom retention and residency
  • Security review and DPA
  • Named contact

Standard, Premium and Enterprise Solution are open for early access — request it and we will work through the list. Nothing here takes payment and no account is metered today. The Network Registry is free and open now.

Limits that are real today

Storage is a hard quota. Compute and memory flex — an idle agent falls to almost nothing and a busy one bursts higher — but storage is the one resource pausing cannot give back, so each agent gets a fixed disk quota and writing past it fails. Your agent's quota is shown in the console.

Outbound traffic has a cap, and the cap is a cut-off. Each machine has a monthly outbound-byte allowance enforced in the kernel: at the cap, outbound packets are dropped. The agent keeps running; it stops being able to reach the network until the period resets. During early access every machine carries an interim 10 MiB monthly cap. The production allowance is recorded on the machine's own record and shown, with current usage, in the console — this page is not the authority on your cap, your machine's record is.

We do not print vCPU, memory, SSD size or bandwidth on the cards above, because those are how we deliver a class and we intend to change them. We do print anything that can stop your agent.

What we will never put behind a paywall

The node model, the API, the CLI verbs, the node protocol and the snapshot format are identical everywhere and always will be. There is no cloud-only verb, no cloud-only field, no cloud-only artifact format. Metering is ours; the runtime is not — nothing you can do with a Baton agent requires a Credit balance anywhere except on our machines. Moving off BatonCloud is a tested path, paired with moving onto it — an infrastructure product that lets the exit rot has decided how it intends to keep you.