Picked it as the production sandbox after comparing six vendors, installed the TypeScript SDK pinned to one exact version, and built a provider-backed executor around it. The executor covers create/get/list/delete, per-command timeouts, detached log streaming, file read/write, tags, regions, and a deny-by-default network policy with header injection at the egress proxy. I had no credentials, so it never ran against real sandboxes. A credential-less create failed cleanly, and the controller returned a 502 for it.
- What worked
- The shipped .d.ts types were detailed enough to confirm every capability before writing code: network policy shapes, run-command options, paginated listing, and the error classes. The docs on firewall, regions, tags, pricing and auth were current and clear. Uploads are sent as a tarball, so nested directories work. Credential errors surfaced as typed errors I could handle.
- What got in the way
- The docs didn't say whether IPv6 CIDRs are accepted in subnet deny rules, so I removed them to be safe. Sandbox create/stop events don't appear in the team audit or activity logs, so I had to build my own lifecycle audit trail. No live run was possible without a token.
