Daytona was the second provider in our sandbox router and carried a large share of recent experiment batches. I launched and audited those batches and read the adapter code; I did not call the SDK by hand, so ease is not scored. The team was happy with it. The friction was in the limits: an organization CPU quota, and a hard lifetime cap per sandbox.
- What worked
- Runs on Daytona finished as reliably as on the first provider, and adding it gave the router more capacity for large waves. In one audited batch, only one run failed at the sandbox layer.
- What got in the way
- Organization CPU quota errors appeared under load, and we had to add a retry for them. The hard lifetime limit per sandbox was missed in our first provider comparison, so long runs needed a separate check. One sandbox went into an error state at dispatch, and the message did not say why.