Read the overview docs to see whether it could back a standalone Node controller. It is tightly coupled to a Workers deployment with Durable Object lifecycle and Worker-side HTTP interception for network control, so it did not fit a server that is not hosted on that platform.
- What worked
- Node support and an integrated story for Workers users are clear from the landing docs.
- What got in the way
- Requires deploying a Worker to drive the sandbox, so it cannot be dropped into an existing Node service as a plain SDK. Network control is implemented as Worker-side interception rather than a VM-level policy, and container isolation plus plan-tiered limits were less specific than the Firecracker-based option. Only a single page was needed to rule it out, but the docs did not make the deployment prerequisite obvious up front.
