Volumes
Last updated 17 November 2026
A Volume is a disk of your account that one Machine mounts. Your program sees an ordinary ext4 filesystem, from any language, and finds its files where it left them after every sleep and wake, and after the Machine wakes on another server.
What to keep on it
Every wake starts your program fresh: memory, processes and files on the Machine’s own disks are gone (see What comes back). A Volume is where files last: an agent’s working tree, a project and its dependencies, tools you installed, a cache worth keeping warm, an application’s data directory. Mount it at a path, or make it the Machine’s whole disk so that everything you change on the Machine lasts.
A Volume or a database
Keep files on a Volume, and keep records that must not be lost, or that other programs read too, in a Tonbo database. A Machine can have both.
| A Volume | A database the Machine binds | |
|---|---|---|
| What it holds | Files on an ext4 filesystem, from any language | SQLite tables, from Node.js |
| Who reaches it | The one Machine it is bound to | The Machine, and any other program of yours that opens it by name; one writer at a time |
| Where a write is kept | On the disk of the server the Machine runs on, and copied to the region’s storage (see Data guarantees) | In three zones of the region, durable once synced() resolves (see When a commit is durable) |
| Size | 1 to 100 GiB, fixed when you create it | Up to the database limits |
How it relates to a Machine
A Volume belongs to your account, not to a Machine. You create it in a region, then bind it to one Machine of that region, at a path or as its whole disk; the Machine gets it at its next wake. While the Machine is awake the Volume is attached to it, and while the Machine sleeps you can move the Volume to another Machine of the region. Deleting the Machine keeps the Volume, unless it was made for that Machine (see Deleting its Machine). You create, list and delete Volumes with tonbo volume or the API, as on Manage Machines.
Tonbo encrypts a Volume’s data on the server and in storage, with a key of its own (see Data protection).
What Tonbo promises
What a write to a Volume survives, a crash, the loss of its server or zone, or a sleep, is Tonbo’s promise on Data guarantees. How Volumes work explains the design behind it.
Use a Volume
- Keep data on a Volume or in a databaseCreate a Volume, mount it at a path, and choose between it and a database.
- Keep a Machine’s whole diskMake a Volume the Machine’s disk, so installed packages last too, and change its image with a Rebuild.
Learn more
- How Volumes workWhy its data is on its server’s disk and copied to the region’s storage, what that means for your program, and why a wake elsewhere reads slower at first.
- Things to knowOne Machine and one region, moving and deleting, what it costs, how large it can be, and what it does not do.
- PerformanceWhat each shape lets it read and write.
- Troubleshooting: VolumesEach refusal and surprise, and what to do.
- Management API: VolumesEvery Volume operation, field and refusal.
The tonbo volume commands are in the CLI reference.