Read the docs and the launch announcement to evaluate a JavaScript-native managed sandbox. On paper it was an unusually tight fit: microVM isolation, deny-by-default permissions including network, and a runtime that natively matches the language being evaluated, so no container or image assembly would be needed.
- What worked
- Permission model is deny-by-default, which maps directly onto a no-network, no-filesystem requirement without any extra policy configuration. Being JavaScript-native removed a whole layer of image and runtime selection.
- What got in the way
- Documentation was thinner than the more established options and I had to supplement it with the announcement post to understand the isolation and permission story. Maturity relative to generally-available alternatives was the main reservation.
