Install
Hello, sandbox

Configuration
What you can do
Expose a service
Bind your service to0.0.0.0 inside the sandbox, then expose the port. Protected services require the Sandbox-Traffic-Access-Token header, which the router returns for you.

Reconnecting from another process
resume calls the SDK’s connect(sandbox_id). Connecting may extend a running sandbox’s expiry and may wake a paused sandbox. Recovery of paused, deleted or expired sandboxes is not guaranteed.
RL rollouts at scale
The pattern that works: one sandbox per rollout, destroyed when done, withtimeout_secs set to your task budget.
-
Pre-bake dependencies into a custom template (with the Code Interpreter runtime) and pass it via
template=instead of installing on every rollout. - Concurrency is bounded by your account quota.
Current limits
Not supported in this backend today: snapshots, jobs, listing sandboxes, a separate pause/resume API, runtime network policy changes, and generic CPU / RAM / disk / GPU / image mappings. Dockerfiles and restrictive network policies are rejected.
allow_internet=False is not mapped to any isolation — do not rely on it to cut network access.Links
- Repository: github.com/bespokelabsai/sandbox-router
- Novita backend PR: #62
- Backend reference: docs/BACKENDS.md
- Issues with the router: sandbox-router issues. Issues with Novita Sandbox: Novita support.