Change prompts. Not code.

Workspace-scoped system prompts, versioned behind named labels and injected via token binding — so a rollout is a label move, not a deploy.

A/B split traffic across two versions of a label, and roll back by moving the label if it goes badly.
One-click rollback: move the label back and the next request picks it up.
Webhooks fire on promotion, so your own systems stay in sync with what is live.

A rollout is a label move.

Prompts live in the workspace, versioned behind names like production and canary. Point the label at v4 and the next request uses it. No redeploy, no client update, no waiting for the train.

And a rollback is the same move.

Split traffic across two versions of a label, and move it back if the new one goes badly — the rollback is the same one move as the rollout. Webhooks fire on promotion so the rest of your tooling knows what is live.