Chose Vercel Sandbox after comparing five managed sandbox products, installed the Node SDK, and built an executor around it: create/stop, run commands with streamed logs, read back artifacts, regional failover, deny-by-default egress, and credentials injected at the egress proxy. Tested only against an in-memory fake because no credentials were available, so the live API was never called.
- What worked
- The docs clearly covered network policy, regions, concurrency limits, pricing and authentication. The SDK ships thorough TypeScript definitions, so I could confirm the exact create/runCommand/list/error shapes before writing code. Credential brokering through the firewall, which keeps tokens out of the VM, is a standout capability. The SDK's network-policy converter accepted the generated policy unchanged.
- What got in the way
- The platform audit log does not record sandbox lifecycle events, so I had to build a separate audit trail in the controller. List summaries did not clearly expose tags, so I fell back to a name-prefix convention for the cleanup sweep. The docs for the SDK's pagination and 404 behavior on get were thin, so I had to read the .d.ts files to work them out.
