Skip to main content

All postsGuides

Cloud Agent pricing on TOSE, and how auto-sleep keeps costs down

By TOSEPublished Updated 4 min read

A Cloud Agent's awake, asleep and waking cycle

TL;DR

Compute costs up to $0.02 per vCPU-hour and $0.01 per GiB RAM-hour, only while the agent is awake. Disk costs $0.15 per GiB-month, including while the agent is stopped or asleep. TOSE does not bill model usage. Auto-sleep (15, 30, 60 or 120 minutes) stops compute billing while keeping files and the provider sign-in.

Three separate costs

Three separate costs
CostHow it is billedPrice
Compute (CPU, RAM)Per hour, only while the agent runsUp to $0.02 per vCPU-hour and $0.01 per GiB RAM-hour
StoragePer GiB-month while the disk exists, including when stopped or asleep$0.15 per GiB-month
ModelsBilled by the provider on your API keyNot billed by TOSE

The deploy plan uses the highest compute rate to set the cost ceiling, so the figure in the plan is a maximum.

Example: the smallest Claude Code agent

With 1 vCPU and 2 GiB of RAM:

• Compute: 1 × $0.02 + 2 × $0.01 = at most $0.04 per awake hour.

• Storage: 5 GiB /workspace + 1 GiB /home/agent = 6 GiB × $0.15 = $0.90 per month.

Awake 8 hours a day, compute comes to at most about $0.32 a day. Awake around the clock, it triples. That is why auto-sleep is worth turning on.

How auto-sleep works

An agent's awake, asleep and waking cycle

In the agent's Settings tab, set Auto-sleep to Off (default), 15, 30, 60 or 120 minutes.

Auto-sleep settings
Mockup of the Settings tab with sample data.

Idle means no keystrokes or output in tmux, no running commands and no install in progress. Closing the browser tab does not count as idle, and a background build keeps the agent awake.

While the agent sleeps:

• Compute is not billed.

• Storage is still billed.

• Files and the provider sign-in are kept.

• The tmux session is lost, so do not leave unfinished work living only in tmux.

Waking the agent: only the Wake and open button on the agent page wakes it, and the wallet needs a balance. A task sent over MCP does not wake the agent; it is refused with AGENT_SLEEPING. For agents that mostly take work over MCP, consider a longer sleep delay or wake the agent before assigning work.

When the wallet runs out

• Compute stops.

• Unpaid compute is forgiven.

• Storage is still owed.

The disk is not deleted immediately, but do not leave the wallet empty for long.

Hourly cost ceiling

max_hourly_cost_cents is an optional hourly cost ceiling that can currently only be set through the API; the dashboard form does not offer it yet.

Recommendations

• Turn on 30-minute auto-sleep for every agent unless you have a specific reason not to.

• Start with a 5 GiB disk. Disks can grow but never shrink.

• Start with the smallest size and add CPU or RAM only when needed.

• Delete agents you no longer use, because a stopped agent still pays for storage.

• Commit and push often so your work stays safe in git when the agent sleeps, loses tmux or gets reinstalled on a new release. See part 4.

You have finished the series

You now know what Cloud Agents are, how to create one, delegate over MCP, receive pull requests and keep costs under control.

• Get started with creating your first Cloud Agent

• See the overview on the Cloud Agents page

Frequently asked questions

How much does the smallest Cloud Agent cost?

A Claude Code agent with 1 vCPU and 2 GiB RAM costs at most $0.04 per awake hour, plus about $0.90 per month for 6 GiB of disk (5 GiB /workspace and 1 GiB /home/agent).

Does a sleeping agent still cost money?

Compute billing stops; disk storage is still billed.

Does an MCP task wake a sleeping agent?

No. The task is refused with AGENT_SLEEPING. Only the Wake and open button on the agent page wakes the agent.