Isolation guarantees
Last updated 2 November 2026
Machines are not open yet. These pages describe Machines as they will open; until then, a create answers region_not_offered (422), “Machines are not offered in any region yet.”
Rely on your Machine being sealed off: no other Machine can read it or starve it, and it cannot reach Tonbo’s own systems.
- Each Machine runs in a virtual machine of its own, with its own Linux kernel.
- No other Machine can read its memory or its disks, while it runs or after it sleeps.
- It cannot reach Tonbo’s hosts, Tonbo’s internal networks or the cloud metadata service, except its own database and name lookups, which Tonbo serves it.
- Its CPU, memory, disk and network are bounded, so it cannot starve other Machines, and a host never promises more memory than it has.
- The token that opens its database is kept only in memory, for one wake.
- What it uses is measured from outside it, where it cannot change the count.
What is not claimed
- Protection from hardware side channels beyond what the host’s kernel already provides.
- Protection from an unknown flaw in that kernel.
- Staying up when its host is lost; its database survives that.
The exact claims
Tonbo’s isolation claims, word for word, and how each is enforced are on Isolation claims.