Fixed menus versus configurable machines
Boat, Sandboxer, Lizard and boxd sell four or three fixed shapes. Sprites sells one: 8 vCPU and 100 GB, with memory assigned automatically. E2B, Vercel, Runtime and Morph let you choose resources within bounds; Blaxel sizes CPU from memory, and InstaBox sells fixed vCPU/RAM pairs by plan.
The difference matters most when your workload is lopsided. A browser agent needs memory more than cores; a compiler needs the reverse. On a fixed menu you buy the nearest shape and pay for what you do not use.
Disk is part of the shape, or it is not
Boat attaches 51 GB to its smallest three sizes and 111 or 251 GB to the larger ones. boxd gives every machine 100 GB and does not let you choose. Vercel gives 64 GB of ephemeral NVMe. E2B includes 10 GiB on Hobby and 20 GiB on Pro, and asks you to contact support beyond that.
Where disk is a separate meter, the capacity you see is not the storage you pay for: Vercel's drives bill on logical used size, and boxd's disk bills on bytes written.
Regions and hardware
Vercel is the outlier with 19 regions. E2B and Blaxel list four, Sandboxer and Lizard two, Agent 37 three, and Runtime one. Boat and boxd are EU-only; InstaBox publishes no region selector and its terms say the United States. Sprites does not let you choose a region: placement is automatic near you, according to a community answer.
No provider in this set publishes a GPU for sandboxes. Several say so explicitly: E2B, Boat, Lizard and Sprites. ARM is not offered either, and only Runtime, Sandboxer, Morph and Vercel document nested virtualisation or /dev/kvm. Morph publishes no region or GPU statement at all.