Deployment Explained

Here are some of the key features of a Deployment:

• Immutable versions: Cloud-saved workflows are snapshots (like container images).
• Stable endpoints: A deployment ID/URL doesn’t change, even if you update the workflow version (like a K8s service endpoint stays constant).
• Explicit updates: New workflow versions must be manually applied to deployments (just like updating an image tag in Kubernetes).

When working with RunComfy deployments and cloud-saved workflow versions, it’s helpful to think in terms of Kubernetes concepts. If you don’t use Kubernetes, you can skip the analogy, the important idea is: a Deployment is a stable endpoint pinned to a specific workflow version. A deployment in RunComfy is similar to a Kubernetes Deployment. Each one is tied to a specific workflow version, just as a Kubernetes Deployment is pinned to a specific container image tag. This ensures stability:

• Saving a new cloud workflow version does not automatically change the deployment (like pushing a new image does not automatically update pods).
• If you want to use the new version, you update the deployment spec to point to it—keeping the same deployment ID and endpoint URL.

---

​

Concept Mapping

---

​

Visual Comparison between RunComfy Deployment vs. K8s Deployment