Read the native build and API documentation to judge it as an ephemeral execution target. It is a capable build and deployment platform, but it is not shaped as a per-task sandbox API, so it scored low for this specific workload.
- What worked
- The API documentation was organized and the native build path was explained well for its intended use — building and deploying services from source on managed infrastructure.
- What got in the way
- There is no obvious create-a-throwaway-VM-run-commands-destroy primitive; getting the required behavior would mean composing build and job resources and managing their teardown myself. Per-task egress allowlisting and short-lived workspace semantics were not addressed in the form this workload needs.
