Skip to main content
Choose Comfy Cloud for an always-available managed ComfyUI, Comfy API for a versioned environment deployed as an endpoint, or self-hosting for infrastructure you manage.

Comfy Cloud

Run workflows without creating a Build or deployment.

Comfy API

Package models and custom nodes into a managed, autoscaling endpoint.

Self-Host

Run ComfyUI on your own hardware, rented GPUs, or containers.
All three options run API-format workflows. Choose based on whether you want Comfy to manage the environment or want to manage it yourself.

​
Deploy from the ComfyUI app

ComfyUI adds a Deploy to Comfy API entry to the Workflow actions menu of every top-level workflow. It is available in the local app, Comfy Cloud, and the Desktop app, and the entry is marked NEW in the menu.
1

Open Workflow actions

In the top bar, open the Workflow actions menu on the workflow tab.
2

Choose Deploy to Comfy API

ComfyUI activates the workflow, then opens an introduction card with a short product video and a summary of the node packs, models, and node classes the workflow uses.
3

Open the platform

Click Deploy on Platform to continue on platform.comfy.org. The Build Wizard there starts from an imported workflow JSON or a Comfy Desktop snapshot, and Build sources covers both. The card also carries a Read the docs link to the developer documentation.
4

Or hand the workflow to a coding agent

Click Build with your agent to copy a brief for the open workflow, then paste it into your coding agent.
Comfy API packages the workflow’s custom nodes, models, and Python dependencies into a reproducible build, then runs it as an autoscaling endpoint. See Comfy API for the build and deployment flow.

​
Build with your agent

Build with your agent is the alternative to building by hand. It copies a plain-text brief and runs no command. ComfyUI also downloads the workflow JSON so your agent has the file to build from. In the Desktop app it does not download a separate file: the brief points at the newest snapshot in the .launcher/snapshots directory of the Desktop install, and importing that snapshot sends its JSON to the builder the same way. The brief names the workflow’s node classes, node packs, and models, and points your agent at the current comfy skills show comfy-build recipe, which owns the comfy-cli commands, the version pins, the release cut, and how to read a failure. Your agent confirms with you before it uploads the workflow and again before the first cut. It then fixes one cause per cut, tells you the cause, the exact edit, and which build it is before every new cut, and stops after three cuts. A release is not a deployment, so the brief stops at a green release and deploying stays a separate decision.

​
Next step: run workflows against it

Once a deployment is live, see Running Workflows to call it from your application. The Comfy SDKs work against every deployment target; self-hosted instances additionally need the API Proxy to serve Comfy API v2.