The ComfyUI APIthat doesn't break in production.
Pin your exact build so ComfyUI updates can't touch it. Route across GPU providers so vendor downtime can't either. Your endpoint stays live.
Takes 30 seconds · No credit card
ComfyUI is graduating to production. Runflow is the managed route.
The graphs that used to live on a single creator's desktop are now powering real products: on-model try-on, headshot pipelines, ad creative at scale. The choice teams face is the same one we faced at BetterPic: stitch together Docker, Redis, Modal, S3, and a queue, or pick a managed route. Runflow is the managed route, with output observability on every call and pay-per-second-of-use pricing so an idle graph costs you nothing.
One ComfyUI graph. One production endpoint.
Mark your inputs, mark your outputs, and push with the Deploy node. Runflow handles hosting, auth, scaling, and the API surface so you ship without leaving ComfyUI.
A full Runflow pipeline: Input, Output, and Deploy nodes wired into ComfyUI.
One workflow team. 87% gross margin.
Runflow is built by the team behind BetterPic, running AI image infrastructure in production since 2023. When BetterPic moved headshot generation to Runflow, margins went from 40% to 87% on 100K+ jobs a month, with zero dedicated infra hires. The stack you're deploying on is the same one.
ComfyUI is a tool. Runflow is what makes your workflow shippable.
Output observability ships day one. Active controls (auto-retries and quality loops) come after launch. Everything else is the floor we start from.
Output observability
Every generation gets scored and logged (identity, framing, artifacts) so you can see where a workflow drifts before your customers do. Think Google Analytics for your outputs.
Pinned to your build
We pin the exact ComfyUI commit, custom node commits, and model hashes you ship with. Upstream churn never touches your workflow. The next ComfyUI update won't break a thing.
Multi-provider GPU routing
If a GPU provider degrades or goes down, we swap to another in seconds. Your workflow stays up while everyone else's API status page lights up red.
ComfyUI-native deploy
Drop the Runflow Deploy node into your graph, mark inputs, ship. No Dockerfiles, no Python envs, no GPU config.
Active auto-retries
Low-score outputs re-run automatically, so your customer never sees the bad one. Shipping after launch.
Typed REST API per workflow
Every deploy auto-generates a typed REST endpoint with inputs matching your graph parameters. Call it from any language, hand a spec to your frontend.
Quality loops
Iterate on a prompt until the output passes your quality threshold, no custom code. Shipping after launch.
Cached models + custom nodes
Popular checkpoints and community nodes stay warm on GPU. Your workflow is seconds from the first call.
Version history
Every workflow update is versioned. Roll back to any previous version in one click and keep full history across your team.
Dev → staging → prod
Promote workflows across environments with the controls your team already expects. Test on staging before pushing to production, no surprises in live traffic.
Pay per second of active use
We only charge while your graph is computing. No idle GPU, no reserved instance, no monthly commit. Scale to zero when nobody's calling.
Per-second GPU pricing. Scale to zero when nobody's calling.
Pick the GPU that fits your workflow. Pay only while your graph is computing. No idle instances, no monthly commit, no reserved hours.
No monthly commits · No reserved instances · Billed per second, not per hour
Comfy Cloud, self-host, or Runflow. Three paths, same goal.
Comfy Cloud is the browser-based playground from the ComfyUI team. Great for iterating, but you can't turn a workflow into a production API from it. Self-hosting on RunPod means Dockerfiles and cold starts. Runflow is the managed route from your local ComfyUI: drop in our Deploy node and your graph becomes a typed API, with output observability on every call.
Based on each platform's public site as of April 2026. "Soon" means post-launch on Runflow's roadmap.
Publish your workflow.
Earn on every run.
Once you're shipping APIs, publish workflows to the Runflow marketplace and join the Founding 100. Here's what comes with a seat.
- 10% net rev-share on every runYou publish, we host. Every time someone runs your workflow, you earn. Locked for your first 3 months.
- Active client matching · 133 open bountiesWe mapped 133 vertical workflows with paying B2B demand. Bid on the list, we make the introduction when a customer asks for it.
- $10 free credits on signupNo card, no commitment. Enough to deploy and test a workflow end-to-end before you publish.
- Numbered Founding Builder badgeA collector badge 001–100 on your marketplace profile, with priority placement and early access to new features.
A numbered collector badge. You get yours when you're accepted — 001 through 100, assigned in order. The example here is 007.
100 seats total · Locked-in terms.
Questions, answered.
Do I have to leave ComfyUI to use this?
No, that's the whole point. You install the Runflow custom node, paste your API key, and keep building the way you already build. When you're ready, your graph becomes a live endpoint your product can call.
When do I get access?
We launch early access on May 18. We'll email install instructions, your API key, and $10 in launch credits the moment your spot is live, plus an invite into the Builder Program, where published workflows earn 10% rev-share. Sign up now; early-access spots fill first.
What ComfyUI workflows do you support?
Standard ComfyUI JSON exports. Most core and popular community nodes are supported. If your workflow uses something exotic, reach out after signup and we'll confirm support.
Is my workflow private?
Yes. Your workflow stays yours. We deploy it as a private API endpoint that only you can call. We don't resell it, share it, or train on it.
What if my workflow uses custom models or LoRAs?
Most public models on Hugging Face and Civitai are supported. If you depend on a private model, you can upload it from your Runflow dashboard.
Do I need to pay anything?
No. Launch credits cover your initial usage. After that, Runflow uses simple per-call pricing. No subscriptions, no minimums.
What if the platform isn't ready on May 18?
May 18 is the target and we're tracking it. If anything slips, your spot and launch credits carry over, you don't lose anything. We'd rather ship a working platform than a rushed one, and you'd rather call a working API.
Can my workflow combine local GPU models with external paid APIs (Claude, Gemini, etc.)?
Yes. A Runflow custom node wraps the external API call. Your workflow runs locally on GPU as normal, only that one node round-trips through us to hit the external model. The third-party API key stays on our side, never on the GPU host or in the workflow file, and the cost of the external call gets metered into the per-run price your customer pays. The managed wrapper ships in a release after May 18. If your workflow already handles its own external API key, that path works on launch day.
Why won't my workflow break on the next ComfyUI update?
When you submit a workflow, we pin the exact ComfyUI version commit, the custom node commits, and the model hashes you built it with. Upstream churn doesn't touch the pinned environment. Public custom nodes get pulled from the original repo and pinned to the commit. Private custom nodes upload once into your tenant container. Models are matched by hash to our pre-cached pool, instant if we have it, one upload if we don't.
How do you protect my custom LoRAs and trained models?
Clear split between internal and external. Everything internal (LoRAs, model weights, the node graph, your configuration) is tenant-isolated and encrypted at rest, processed inside our workers, never exposed outside that boundary. End users only pass runtime inputs like prompt, reference image, or brand asset. They see the input form and the output, never the LoRA, the weights, or the workflow internals.
We already run ComfyUI centrally on our own AWS. What does Runflow add?
Centralised compute is the easy half. Centralised workflow development is the hard half. Self-hosting means your engineers spend real time on EC2 sizing, driver and kernel upkeep, subnets, security groups, and ComfyUI sigterm-killing itself without auto-restart. With Runflow: open your workflow, add 4 nodes, click deploy, get an API endpoint. Our smart router across GPU providers means a single provider hitting capacity doesn't take you down.
Stay in ComfyUI. Ship on May 18.
Join before launch and we'll load $10 in credits into your account on day one, plus an invite to the Builder Program: 10% rev-share on every run, for workflows you publish.
Takes 30 seconds · No credit card