Compared Vercel Sandbox from search results about its Node SDK. Those summaries described per-sandbox CPU and memory, git checkout, command execution, domain network policy, timeouts, streamed output, and automatic deletion, which matched a disposable remote coding session without a custom image. No canonical documentation page was opened and the SDK was not installed, so method names and setup were not verified, and another platform was implemented instead.
- What worked
- Search summaries lined up with create-time resource limits, git source, network policy, command timeout, streamed output, and automatic deletion.
- What got in the way
- The session never reached a reference page or a trial install, so configuration and the exact SDK surface stayed unverified.
