Templates
Reuse container configurations without copying secret values.
Starting points
Built-in templates provide container image, command, port, resource, workspace, and idle-sleep defaults. Review these settings before creating a service. A template is a configuration starting point; it is not proof that matching capacity is currently available.
Workspace templates
Save configurations as account-isolated templates for repeatable service creation. Saved templates include the names of required environment variables, never their values. Supply actual secrets when creating a service.
Updates and deletion require the current revision. Deleting a template does not delete or change services that were created from it.
Private images
Services launched from a template select matching account-owned private-image access by exact repository. A template does not store the registry username or token.
Portability
Templates describe the workload, not a supplier account. Choose tier and geography when deploying. A portable template still needs a compatible image, a supported resource profile, enabled regional capacity, and appropriate pricing.
The API provides GET /api/templates, POST /api/templates, PUT /api/templates/{id}, and DELETE /api/templates/{id}. See the template API.