Shared CPU and RAM pools

Your plan gives you a pool of CPU and RAM. Your VMs share that pool the way processes share a laptop: a busy VM can use what idle VMs leave free. The pool is the hard limit, not each VM.

This means you can run many small, mostly idle VMs (dev servers, agents waiting for work, side projects) on a small plan, and each one can still burst when it gets busy.

Commands

ssh turm.dev pool list
ssh turm.dev pool new build --cpus=4 --region=fsn1
ssh turm.dev pool resize build --cpus=8
ssh turm.dev pool delete build

Create a VM in a named pool with new --pool=build. Without --pool, it goes into your default pool.

Note

Memory that a VM no longer uses goes back to the pool, so idle VMs don’t hold on to RAM they used once.

Regions

Pools live in a region. Today there is one: fsn1, in Germany. More regions are coming soon.