Comfy Cloud

Use Comfy Cloud as an always-available managed deployment for running workflows via API

Comfy Cloud is a stateful, interactive, fully managed version of ComfyUI. You build and run workflows in the browser as you would on a local install, while Comfy manages the models, the GPUs, and everything in between. You can also call Comfy Cloud through the API. Comfy Cloud provides a managed endpoint, so there is no environment to build and no deployment to create.

Unlike a serverless deployment, which serves one pinned environment that you build and release, Comfy Cloud serves a full, managed ComfyUI that is always on.

See the Comfy Cloud introduction if you are new to it. This section covers using the Comfy Cloud API as a developer.

Quickstart

Comfy Cloud works with the Comfy SDKs out of the box: the base URL defaults to Comfy Cloud, so all you need is an API key and a workflow. API access requires a paid Comfy Cloud subscription; the free tier does not include it.

1. Create an API key

   Log in to the Developer Platform and create a key. See Getting an API Key for step-by-step instructions.

2. Install the SDK

   Python

   pip install comfy-sdk
   
3. Export a workflow in API format

   Build and test a workflow in the Cloud editor, then save it with File → Export Workflow (API) as workflow_api.json. See Workflow API Format.

4. Run it

   Python

   from comfy_sdk import Comfy
   
   client = Comfy(api_key="comfyui-...")  # Comfy Cloud is the default target
   
   wf = client.workflows.from_file("workflow_api.json")
   
   job = client.run(wf)
   for output in job.get_outputs("9"):
       output.to_file(output.name)
   

   "9" is the ID of the output node in your workflow file. See the SDK guide for inputs, progress events, and error handling.

See Running Workflows for how the same code moves between Comfy Cloud, serverless deployments, and self-hosted deployments.

Credits and Usage

API requests draw from the same monthly credit allocation as the Comfy Cloud web UI. There is no separate API credit pool. Each tier’s included credits, top-up options, and per-workflow runtime caps apply to API jobs in exactly the same way as UI jobs. See the pricing page for the monthly credit amounts on each tier. If you run out of credits mid-month, top-ups can be purchased from your account dashboard.

Concurrency Limits

Running multiple jobs in parallel is only supported when you submit workflows through the API. API users can submit multiple workflows concurrently without waiting for previous jobs to complete. Submission returns as soon as the job is accepted, so you can keep several in flight. The dispatcher runs them in parallel up to your subscription tier’s limit; check platform.comfy.org for your current concurrency.

Jobs submitted beyond your concurrency limit queue normally and execute automatically as slots free up. If the queue itself is full, the SDKs retry for you within a bounded budget before raising QueueFull.

The Comfy Cloud UI does not support running more than one job per person. Workflows queued in the editor run one at a time, in order. Only API submissions run in parallel. See pricing plans for subscription details.

On Team and Enterprise plans, concurrency is per member: everyone in the workspace has their own concurrency limit, so one member’s running jobs never block another’s.

Existing v1 integrations

The deprecated v1 Cloud API also runs against Comfy Cloud. Use it only for existing integrations or for Cloud capabilities that Comfy API v2 does not expose yet. Runnable examples are in the Cloud API Reference (deprecated).