Sandbox Templates
Launch validated snapshot templates with inputs, volumes, previews, actions, and artifacts.
Sandbox Templates
Sandbox templates are validated workflow definitions. A template combines a repo, an openpond.yaml manifest, a validated snapshot, inputs, actions, services, volumes, and artifact rules.
Templates are not static marketing cards. They are launchable workflow snapshots that OpenPond can validate, start, fork, replay, and inspect.
What openpond.yaml declares
The manifest describes what the platform should prepare:
- runtime base or snapshot
- resources
- setup commands
- default start command
- named actions and services
- preview ports
- durable volumes
- input schema and file upload targets
- required integration leases
- artifact paths
- optional app MCP endpoint metadata
Launch behavior
When you launch a template, OpenPond validates the manifest, creates or restores the sandbox runtime, attaches volumes and leases, uploads selected files, runs setup, and starts the selected command.
If the command declares preview ports, the launch flow can open a private preview URL after the service is ready.
Fork, copy, or rebuild
- Fork a sandbox when you want to continue from an existing workspace state.
- Launch a template when you want a clean run from a validated snapshot.
- Copy a repo when you want to edit the template source itself.