Reuse service settings
Rename a service, prepare duplicate settings, or save a portable template.
These actions help organize work and prepare another deployment. They do not allocate compute, copy workspace files, or change the source service's placement and endpoint. They require the current control-plane deployment.
Rename a service
Choose Rename on the service page. The request includes the current expectedName and the desired name. If another client has renamed the service, reread it and review the change before trying again.
A rename changes display metadata only. It does not restart compute, change the lifecycle revision, or reset the idle timer. Existing ledger entries keep their historical names; later postings use the new name. Deleting or deleted services cannot be renamed.
Duplicate settings
Choose Duplicate settings to prepare a new-service form. A draft preserves image, exact command arguments, resource profile, disk size, idle policy, and tier/location defaults.
| Included | Not copied |
|---|---|
| Image reference and command arguments | Workspace files and process state |
| GPU model, memory, count, CPU and RAM | Original volume ID |
| Workspace size and volume mode | Environment variable values |
| Required user environment names | Platform activity credentials and image-pull secrets |
Review the draft, supply required values, and explicitly create the new service when ready. Normal balance, pricing and capacity checks apply. The default new workspace is empty. If you want to reuse existing independent storage, select an eligible volume explicitly and follow its placement and attachment constraints.
Save as template
Choose Save as template on the service page. Template capture requires verified email and the current source revision, and counts toward the account's 50-template quota. A stale revision is rejected so a changed configuration is not captured silently.
The template stores portable settings and required environment names, never their secret values. Private-image access is selected from the account's repository settings at launch. Image and command text are copied exactly, so avoid putting credentials in command arguments.
Historical configuration can be read as a draft or captured as a template when the account still owns that record. This does not restore deleted files. Identical idempotent retries return the original capture result even if the source later changes.
Automate the workflow
- Service API: name, draft and template endpoints.
- CLI:
rename,draft, andtemplate-from. - Python:
rename_service,service_draft, andtemplate_from_service. - MCP: rename, draft inspection and source-based template capture.