Create and Manage Sandboxes
Create, start, stop, restore, delete, and inspect sandbox workspaces.
Create and Manage Sandboxes
Use the Sandboxes page to create a workspace, run commands, inspect output, and control lifecycle state.
Create a sandbox
A sandbox belongs to the selected organization. When you create one, choose the source repo or template, resource size, budget, env refs, volumes, and integration leases.
After creation, OpenPond boots the sandbox, prepares the workspace, and records lifecycle logs and usage receipts.
Start, stop, restore, and delete
- Start brings a stopped sandbox back online and prepares it for commands or previews.
- Stop shuts down the runtime while preserving durable records and configured volumes.
- Archive keeps the sandbox available for later restoration without leaving it running.
- Restore brings an archived sandbox back for more work.
- Delete removes the sandbox and cleans up runtime resources. Durable volumes are kept or deleted according to their volume policy.
Files and terminal
The Files and Terminal tools let you inspect the workspace, upload or download files, run commands, and review output. Use durable volumes for state that should survive sandbox restarts or template launches.
Ports and previews
Templates declare preview ports in openpond.yaml. OpenPond opens those ports through the sandbox preview proxy. Template code should serve the app on the declared port; it should not call platform APIs to expose ports itself.
Logs and receipts
Lifecycle logs show runner setup, command execution, preview routing, and cleanup. Receipts show budget reservation, usage capture, and finalization status.
See Billing for more on budget and receipt behavior.