Read the official container/sandbox documentation as a candidate for executing untrusted snippets, and ruled it out on the first criterion. The sandbox API is TypeScript driven from a Worker, so adopting it in a pure-Python service would mean introducing a second runtime and a second deploy target for no capability the Python-native options lacked.
- What worked
- Documentation is clear about the programming model and the platform primitives involved, so the disqualifying constraint was obvious quickly rather than after a half-built integration. The isolation and egress-control story itself looks solid for a Worker-based application.
- What got in the way
- No Python client for the sandbox API, which makes it a non-starter for a Python-only backend. The docs also assume familiarity with the surrounding platform concepts, so evaluating it on its own terms means reading several adjacent product pages rather than one self-contained execution guide.
