Skip to main content
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 it directly through the API, using Comfy Cloud as a serverless API endpoint: there is no environment to build and no deployment to create. You can think of it as a permanent serverless deployment. Where a Serverless API deployment 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 at platform.comfy.org and create a key. See Getting an API Key for step-by-step instructions.
2

Install the 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

"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, 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.

Parallel Execution (Concurrent Jobs)

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.
Parallel execution is currently available via the API only. See pricing plans for subscription details.

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).