The Rundown AI homepage

Independent tool overview

Comfy Deploy at a glance

Comfy Deploy is a cloud and open-source platform for sharing ComfyUI environments, testing workflows on GPUs and exposing versioned workflows as application APIs.

Visit the official Comfy Deploy site ↗
Comfy Deploy product preview
Tool type
ComfyUI cloud workspace and deployment platform
Deployment target
Authenticated REST APIs on cloud GPUs
Team access
Shared environments, workflows and simplified playgrounds
Source license
GPL-3.0 for the open-source platform
Hosted model
Pay as you go
Last reviewed
August 30, 2026

Overview

What Comfy Deploy is

Comfy Deploy packages ComfyUI workflows for team use and production applications. A developer can import a workflow JSON, reproduce its nodes and models in a cloud machine, expose selected inputs, test it in a managed ComfyUI workspace and deploy a version behind an authenticated API. Non-technical teammates can use simplified playgrounds without editing the underlying node graph.

The project changed direction in 2025: its founders open-sourced the full frontend and backend under GPL-3.0 while continuing to offer the hosted pay-as-you-go service and support existing customers. That makes Comfy Deploy both a usable hosted product and a self-hosting foundation, but teams should evaluate the maintenance model, deployment ownership and migration risk rather than treating it like a conventional fast-growing SaaS platform.

Use cases

Who Comfy Deploy is best for

The strongest fit depends on the job you need the product to complete, not the size of its feature list.

ComfyUI application backends

Turn a proven node graph into an endpoint that a website, internal tool or product can call.

Creative teams

Share models, custom nodes and tested workflows while giving non-builders a simpler playground.

Staging and production versions

Attach separate workflow versions to staging and production deployments before promoting a change.

Variable GPU workloads

Select different cloud GPUs for image, video and other workflows instead of maintaining one fixed machine.

Teams needing source access

Self-host or inspect the full platform when managed SaaS alone does not meet ownership requirements.

Capabilities

Core Comfy Deploy features

1

Workflow import

Imports a ComfyUI workflow JSON and detects the custom nodes needed for a compatible environment.

2

Cloud ComfyUI workspace

Runs ComfyUI in a browser-backed workspace for editing and testing on cloud machines.

3

Private model storage

Keeps downloaded models available to the workspace and its shared workflow environments.

4

Custom nodes and models

Supports team-specific ComfyUI dependencies rather than limiting users to a small fixed catalog.

5

Exposed workflow inputs

Marks selected node values as external inputs for API calls and simplified playgrounds.

6

Versioned deployments

Connects a workflow version and machine to staging or production deployment slots.

7

Run API

Queues authenticated runs, retrieves status and cancels work through the current V2 endpoints.

8

Webhooks

Sends run updates to an application instead of requiring constant status polling.

9

GPU selection

The hosted product advertises autoscaling choices ranging from T4-class hardware through high-memory accelerators.

10

Open-source platform

Publishes the application stack for teams willing to operate the service and its dependencies themselves.

Process

How the Comfy Deploy workflow works

  1. Step 1

    Stabilize locally

    Test the ComfyUI graph, pin model files and record exact custom-node versions before moving it to deployment.

  2. Step 2

    Import the workflow

    Upload the workflow JSON, select or create a machine and resolve any ambiguous custom-node detections.

  3. Step 3

    Build the environment

    Choose a GPU, ComfyUI version, custom nodes and private model files that reproduce local behavior.

  4. Step 4

    Expose a narrow contract

    Make only the intended parameters external and define allowed sizes, types, defaults and validation in the calling application.

  5. Step 5

    Test staging

    Exercise expected, malformed and concurrent requests while recording latency, failure rate and cost per successful output.

  6. Step 6

    Deploy and monitor

    Promote a fixed version to production, consume V2 status or webhooks and retain a rollback path when nodes or models change.

Cost

Comfy Deploy pricing and free plan

Comfy Deploy offers a hosted pay-as-you-go path and a GPL-licensed self-hosted codebase. The public site no longer presents a stable numeric GPU rate card, so teams should check current per-machine rates inside the hosted account before estimating production cost. Self-hosting removes the platform license fee but not infrastructure or operations cost.

Hosted pay as you go

Usage-based

Managed workspace and API deployment billed for selected cloud resources.

  • No sales call required for the pay-as-you-go path
  • Confirm GPU, storage and concurrency rates in the account
  • Cost depends on run time, machine and workload

Self-hosted

$0 software license

Run the GPL-3.0 platform code in infrastructure controlled by your team.

  • Cloud, database, storage, authentication and operations costs are separate
  • Requires engineering ownership
  • Review GPL obligations with counsel for your distribution model

Existing and enterprise arrangements

Contact Comfy Deploy

Support and commercial arrangements for established or higher-touch deployments.

  • Scope and service commitments should be documented
  • Ask about support horizon and response times
  • Validate private output and resource requirements

Pricing checked . Check current pricing at the source ↗

Assessment

Comfy Deploy strengths and limitations

Where it stands out

  • Purpose-built bridge from editable ComfyUI graphs to callable APIs
  • Shared environments reduce node and model drift across a creative team
  • Staging and production slots support safer workflow promotion
  • Simplified playgrounds let teammates use workflows without understanding every node
  • Hosted and self-hosted paths offer different control and operations tradeoffs
  • Source access reduces dependence on an opaque proprietary control plane
  • API supports queueing, status, cancellation and webhooks
  • GPU choice can match lightweight image jobs or memory-heavy video graphs

What to consider

  • The founders have publicly shifted focus while promising continued service, so new customers should evaluate the long-term maintenance and support model
  • Self-hosting the full stack requires significant infrastructure, security and operations work
  • The public site does not expose a durable numeric hosted-price table for independent cost planning
  • ComfyUI workflows can break when custom nodes, model filenames, dependencies or ComfyUI versions change
  • Import detection still requires human review when node names conflict or models are missing
  • The current V2 API uses a different base URL and endpoint shape from V1
  • Official migration notes say the Python and Ruby SDKs are not actively maintained
  • The documented RunPod worker image is not actively maintained
  • Cold starts, model downloads and large output uploads can dominate latency
  • GPU autoscaling does not remove the need for concurrency limits, timeouts, retries and idempotency in the calling application
  • User-provided workflows and nodes expand the supply-chain and code-execution attack surface
  • The GPL-3.0 license and the licenses of individual models and nodes must be evaluated separately
  • Production teams need independent output moderation, rights checks and retention controls

Compare

Comfy Deploy alternatives

The right alternative depends on the specific output, workflow, controls and budget your project requires.

Coding

Replicate

A more model-centric hosted API platform with broad public model packaging and usage-based inference.

Explore Replicate

Coding

Together AI

Better suited to deploying and serving mainstream open models without centering the workflow on ComfyUI graphs.

Explore Together AI

Content Creator

Krea

A managed creative suite for teams that want visual generation and editing without operating ComfyUI infrastructure.

Explore Krea

Content Creator

Runway Creative

A higher-level managed creative platform when polished image and video tools matter more than custom node-graph deployment.

Explore Runway Creative

Questions

Comfy Deploy FAQs

What is Comfy Deploy?

Comfy Deploy is a team workspace and deployment layer for ComfyUI. It imports workflows, reproduces their nodes and models on cloud machines and exposes selected versions as authenticated APIs or simplified playgrounds.

Is Comfy Deploy still active?

Yes. Its site, hosted console and current V2 documentation remain available. The founders also open-sourced the full platform and said the hosted service would remain online and supported while they explored other ideas.

Is Comfy Deploy open source?

Yes. The full platform repository is published under GPL-3.0. Self-hosters still need to provision and operate databases, storage, authentication, queues and GPU execution.

How much does Comfy Deploy cost?

The hosted service uses pay-as-you-go cloud-resource pricing, but a current numeric GPU rate card was not published on the public marketing pages reviewed. Check the account's rates for your GPU, storage and concurrency. The open-source software has no license fee, but infrastructure and engineering are separate costs.

Can I deploy any ComfyUI workflow?

It is designed for custom nodes and models, but deployability depends on compatible code, available model files, licenses, VRAM and a reproducible environment. Test the exact graph rather than assuming every local workflow will import cleanly.

What is the current API base URL?

The V2 documentation lists https://api.comfydeploy.com/api. Older integrations using the www.comfydeploy.com API base and legacy run endpoints should follow the V2 migration guide.

Does it support staging?

Yes. The deployment documentation describes production and staging slots, each tied to a specific workflow version and machine.

What should I test before production?

Pin dependencies, test malformed and concurrent requests, measure cold starts and cost, validate webhook retries, scan custom-node code, check model licenses and keep a known-good deployment available for rollback.

Bottom line

Our Comfy Deploy verdict

Comfy Deploy remains useful when the hard problem is operationalizing a custom ComfyUI graph for a team or application. The hosted path can save substantial setup time, while the open-source release provides control. New deployments should proceed with clear eyes about the project's transition, current API generation and the maintenance burden hidden inside custom-node environments.

Visit Comfy Deploy website ↗
The Rundown University

AI training for the future of work.

Get access to all our AI courses, hundreds of real-world AI use cases, live expert-led workshops, an exclusive network of AI early adopters, and more.

AI Courses

Get unlimited access to all of our current & upcoming industry-specific AI courses for the duration of your subscription.

Daily Guides

To keep up with the rapid pace of AI, our team publishes AI implementation guides daily. Our library contains 300+ practical use cases to automate real-world work.

Workshops

Join weekly, live, interactive sessions with industry leaders who are at the forefront of AI for hands-on implementation guidance and exclusive insights.

Community

Network with an exclusive community of AI-first professionals who are working smarter with AI. Learn how early adopters are using AI in their work and businesses.