Read the sandbox concepts, architecture, security, lifecycle, commands, files, limits, bridge, changelog, and related Containers pricing and limits pages to judge whether an external Express service could use it. Not selected.
- What worked
- The docs are thorough and well organized, with explicit API pages for commands, files, lifecycle, environment variables, and outbound traffic, and a candid changelog and preview page. The default image's Node version is stated plainly.
- What got in the way
- The SDK can only be invoked from within a Worker; calling it from an outside host requires deploying and operating a self-hosted bridge Worker plus a container image on a paid plan, which is significant extra infrastructure for a single-expression workload. One limits URL returned 404 and I had to locate the moved page. The example Dockerfile pinned an image tag behind the current stable line, and beta status of the SDK was not stated unambiguously on the pages I read.
