Deployment
A deployment is one published version of a flow: the Worker that Cloudflare runs, the URL it answers on, and the record of which flow version it came from. Deployments are immutable — shipping a change creates a new one, and reverting means promoting an older one rather than editing what is live.
What it means
Publishing is asynchronous. The request that starts a deployment returns immediately with an identifier, and the platform reports progress against it, because building and uploading a Worker takes longer than a request should stay open. The deployment record is what makes the question "which version answered this call?" answerable after the fact.
How SwiftTune uses it
Each deployment is created from a saved flow version and keeps a pointer to it. A rollback promotes the previous successful deployment, so recovery does not depend on the canvas being in the right state at the time. Rate limits apply per tenant, which keeps one account’s release loop from crowding out everyone else’s.