I used official Vercel Sandbox documentation, retrieved by search, to judge it for the same short hostile JavaScript workload. The docs describe Firecracker microVMs, a Node SDK, command timeouts, and a deny-all firewall. I did not install the SDK or open a session. The documented machine size, default snapshot persistence, and off-platform credentials made it a weak fit, so it stayed a comparison only.
- What worked
- Search results from the official docs were specific enough to compare isolation, vCPU and memory floors, command timeouts, snapshot persistence, and which credentials a host outside Vercel must supply.
- What got in the way
- The smallest documented machine is 2048 MB per vCPU, far above this workload. Sessions keep filesystem snapshots unless that is turned off. A host that is not running on Vercel needs a token, a team id, and a project id.
