> ## Documentation Index
> Fetch the complete documentation index at: https://docs.runcomfy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# 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

| **RunComfy**                              | **Kubernetes**                                 | **Explanation**                                                                   |
| ----------------------------------------- | ---------------------------------------------- | --------------------------------------------------------------------------------- |
| Cloud-saved workflow version              | Container image (with tag)                     | Each workflow version is like a built image. It’s immutable and versioned.        |
| Deployment                                | Kubernetes Deployment                          | A deployment references a specific version/image to run, ensuring consistency.    |
| Deployment ID / Endpoint URL              | Deployment UID / Service endpoint              | These remain stable, even if the version/image inside is updated.                 |
| Updating workflow version in a deployment | `kubectl set image` / updating deployment spec | You update the reference to a new version without changing the deployment itself. |
| Saving a new workflow version             | Building & pushing a new container image       | Creates a new artifact, but doesn’t affect running deployments until updated.     |

***

## Visual Comparison between RunComfy Deployment vs. K8s Deployment

<img src="https://mintcdn.com/inceptionsaiinc/laEU0eA7PGXebc0k/docs-image/RunComfy_Deployment_vs_K8s_Deployment_Analogy.webp?fit=max&auto=format&n=laEU0eA7PGXebc0k&q=85&s=587e86388f9a81f408d6ee3f3d2dda30" alt="Comparison between RunComfy Deployment vs. K8s Deployment" width="1957" height="1180" data-path="docs-image/RunComfy_Deployment_vs_K8s_Deployment_Analogy.webp" />