Things to know
Last updated 17 November 2026
A Volume is a disk for one Machine at a time, in one region, billed while it exists. This page gathers the rules that decide how you use one; how its data is kept is on How Volumes work.
One Machine, one region
A Volume is bound to at most one Machine, and a Machine has at most 1 Volume. No two Machines share one, read-only or otherwise: to reach the same files from several programs, keep them in a database or run the programs on one Machine. A Volume’s region is fixed when you create it, it binds only a Machine of that region, and it never moves to another region.
Its states
| State | What it means |
|---|---|
available | No Machine has it. You can bind it to a Machine of its region, or delete it. |
bound | A Machine has it and gets it at its next wake; that Machine is asleep, or awake without it. |
attached | The Machine that has it is awake with it mounted. |
deleting | It is being deleted, and its data is being destroyed. This cannot be undone. |
tonbo volume show (GET /v1/volumes/{name}) gives a Volume’s state and its Machine.
Changes apply at the next wake
Binding a Volume to a Machine, removing it with --no-volume, or changing its path takes effect at the Machine’s next wake; a Machine awake now keeps what it woke with until it sleeps (see Deploy a change).
Moving it to another Machine
A Volume moves from one Machine to another of its region in one write, and only while the Machine that has it is asleep; the Machine it moves to may be awake, and gets it at its next wake (see Move a Volume). A Volume that is a Machine’s whole disk moves only to a Machine on the same image, and not while a Rebuild it waits for is still to be applied; it never becomes a Volume mounted at a path (see Keep a Machine’s whole disk).
Deleting a Volume
A Volume cannot be deleted while a Machine has it. Remove it from the Machine first, with tonbo machine update <machine> --no-volume; if the Machine is awake, the Volume is free once it sleeps. Deleting a Volume deletes its data for good: Tonbo destroys its key first, then its stored copies, and nothing can bring it back. Its name is free at once. Deleting your account deletes its Volumes too.
Deleting its Machine
Deleting a Machine keeps its Volume, unbound and billed until you delete it, unless the Volume was made for that Machine, as the console makes the disk of a Machine it creates: such a Volume is deleted with its Machine. Say which you want to be sure: tonbo machine delete <machine> --keep-volume or --delete-volume (delete_volume=false or true on DELETE /v1/machines/{name}). A Machine deleted because its delete-after time passed leaves its Volume unbound and kept, even one made for it.
What it costs
A Volume is billed $0.05 per GiB-month for its live bytes: the compressed blocks its latest state references, not the size you give it. A Volume is billed while it exists, attached or not, until you delete it. The writes that record its blocks count as Streams usage (see Metering and holds).
How large, and how many
- 1 to 100 GiB, fixed when you create it, and billed for the bytes it holds, not its size.
- At most 1 per Machine and 25 per account, each in one region and attached only to a Machine there.
- Until an account buys credit it holds one Volume, in any region, of at most 10 GiB, or 100 GiB once it has a card. Bought credit lifts both. A create past either answers
payment_required. - No snapshots, backups or resizing, and no Volume shared between Machines.
What a Volume does not do
- It keeps no earlier versions: there are no copies you can go back to, no clones and no backups, so it does not protect your files against your own deletes and overwrites. To keep a copy of something, copy it off the Machine yourself, or keep it in a database you can export (see Backups).
- It does not grow or shrink: its size stays what you gave it.
- It cannot be browsed or read without its Machine: you reach its files through the Machine that has it.
- It is not shared, and it does not move between regions (see One Machine, one region).
When you need several programs to read the same records, or a write to be safe off the server the moment you answer, use a database (see Keep data on a Volume or in a database). What to do about each refusal is on Troubleshooting.
Encryption
Tonbo encrypts a Volume’s data on the server and in storage, with a key that belongs to the Volume alone and is destroyed when the Volume is deleted (see Data protection).