Deployments
Pin specific versions to dev, staging, and prod environment slots — promote prompts through environments without code changes.
Environment slots
Each prompt and chain has three deployment slots: dev, staging, and prod. A slot pins one specific version to that environment. Promoting a prompt is just pointing the next slot at a version — no code deploy required.
1
Deploy to dev
From the History/Versions tab, deploy a version to the dev slot and test it.
2
Promote to staging
When it looks good, deploy the same version to staging.
3
Ship to prod
Promote to prod — your live API traffic now uses this version.
How the API resolves a version
When you call the inference API, the versionfield selects which slot to use:
Sensible fallbacks
Prompts that never used slots still work:
live/prod falls back to the active version. For chains, the fallback is the latest committed version.