Loading video...

Video Failed to Load

Go Home

Comfy Router is live One API for frontier image, video, 3D, and audio models. Same model string. Same arguments. No new SDK, no new key, no redeploy. What Comfy Router gives you: → Explicit routing. You name the provider, we call that provider. It's down? The request fails there....

7,420,417 views • 3 days ago •via X (Twitter)

34 Comments

ComfyUI's profile picture
ComfyUI3 days ago

Get Your API Key today:

ComfyUI's profile picture
ComfyUI3 days ago

Learn more with the blog:

Robin Huang's profile picture
Robin Huang3 days ago

Great work team!!

Yoland Yan's profile picture
Yoland Yan3 days ago

LFG!

Maximus's profile picture
Maximus3 days ago

Finally

Tara Ding's profile picture
Tara Ding3 days ago

Congratulations!!!

Bohan's profile picture
Bohan3 days ago

Sick!

TongTong C's profile picture
TongTong C3 days ago

🔥🔥🔥

Atul Kumar's profile picture
Atul Kumar3 days ago

The biggest win here is consistency. One workflow across image, video, 3D, and audio means teams can focus on building products instead of maintaining integrations.

Ethan Kurzweil's profile picture
Ethan Kurzweil3 days ago

Sweet! 🎡

mathurah's profile picture
mathurah3 days ago

ahh this is going to be such a game changer! congrats to the team on the launch :)

Carl Wheatley's profile picture
Carl Wheatley3 days ago

Great launch!!!

Will Phillips's profile picture
Will Phillips3 days ago

Epic! Feel like Router is the word of the quarter 🚀

TongTong C's profile picture
TongTong C3 days ago

finally

Shun Ito's profile picture
Shun Ito3 days ago

congrats for the launch!!

Grace's profile picture
Grace3 days ago

This is a major upgrade LFG!

Sponko's profile picture
Sponko3 days ago

😮‍💨

Aaliya's profile picture
Aaliya3 days ago

The “finding out who did it” line fits nicely with the Beast Mode theme while keeping the CX message clear.

Olivia Li's profile picture
Olivia Li3 days ago

Let’s go!!

Orestis Lykos's profile picture
Orestis Lykos3 days ago

fal all the way down!

Rob Muresan's profile picture
Rob Muresan3 days ago

DAMN!

rob - comfyui's profile picture
rob - comfyui3 days ago

Very important things happening

Hasanuzzaman Khan's profile picture
Hasanuzzaman Khan3 days ago

Batch workflows are going to save teams a surprising amount of time.

Ian Lim's profile picture
Ian Lim3 days ago

Huge 🔥

Annette Sung's profile picture
Annette Sung3 days ago

lit

Ashley Nicole's profile picture
Ashley Nicole3 days ago

AI tooling is maturing—observability is finally becoming part of the conversation.

Arish Ai's profile picture
Arish Ai3 days ago

The multimodal ecosystem is getting crowded—having one workflow across providers makes a lot of sense.

David Kwon's profile picture
David Kwon3 days ago

Let's go! Great job @yoland_yan and team

David Marco💡's profile picture
David Marco💡3 days ago

Less glue code. More building. That's the kind of tradeoff every engineering team wants.

Tiger's profile picture
Tiger3 days ago

Hyped!

AlphaEcho's profile picture
AlphaEcho3 days ago

This is the kind of infrastructure launch developers actually appreciate less integration work, more shipping.

joao fig's profile picture
joao fig3 days ago

@yoland_yan killing it 🔥

Arnez Ai's profile picture
Arnez Ai3 days ago

Production-ready details like request IDs and retries are what make platforms stick.

Alishba's profile picture
Alishba3 days ago

This feels like infrastructure built for builders, not just demos.

Related Videos

HERMES AGENT VS OPENCLAW. a local ai onboarding flow test. a 3.9gb bonsai served on localhost, both agents upstream and latest, i point each one at the endpoint and watch which one even finds it. > hermes opens a provider menu, thirty plus options, local servers sitting right there next to the cloud ones, i hand it 127.0.0.1:8899, it verifies the endpoint, one model visible, auto-detects the model by name, bonsai-27b-q1_0, reads the context length straight off the server, saves it, and starts reasoning and firing real tool calls on my local model. no key. no friction. > openclaw has no menu. it goes hunting for a codex login, an openai key, finds none because there are none, prints no models available three times, defaults to openai/gpt-5.5, a cloud model it cannot reach, and dead ends on run auth login --provider openai. read that back. it asked me for an openai key. to run a model already running on my own machine. it never once looked at localhost. to be fair, openclaw can run local if you hand wire endpoint yourself. what it will not do is find the model already sitting on your box. hermes agent found it in one line. now the part i owe you. the auto-detect that just won, the model name read, the .gguf strip, the context length probe off the server, that is my code, it is in hermes agent main right now, authorship preserved, #2051 and #4218. the wizard fix that stops an agent from silently routing you to someone else's creds, the exact trap openclaw still falls into, mine too, #4210. i contribute to hermes agent, i told you that going in. one agent is built to talk to whatever you are running, the other is built to talk to a cloud api, so one found my model and ran it and the other asked me to log into openai. onboarding flow of both, mapped, below.

Sudo su

23,816 views • 2 months ago

Production traffic is not uniform. You get a few requests that need your best model, but most are simple questions and lookups you can solve with cheaper, faster models. The most expensive mistake you can make today is sending every request to your strongest model. You need routing. Period. This is the simplest trick to improve the architecture of whatever you are building. Please, don't implement routing yourself. You don't have to. I'm currently working with TrueFoundry's Auto Routing. It reads each request, classifies it as simple, medium, or complex, and sends it to the model assigned to that tier. You have two choices: 1. Send every request to the free heuristic classifier to score signals such as technical vocabulary, code, prompt length, and multi-step reasoning. 2. Send the request to an LLM classifier when its difficulty requires a more nuanced judgment. The beauty of using routing is that nothing changes in your code. You still call a single endpoint model, but routing works behind the scenes to pair every request with the best possible model. TrueFoundry ran several experiments with two different setups: 1. Send every request to Claude Opus 2. Send every request to a router with Haiku, Sonnet, and Opus The first experiment ran 550 deterministically graded academic prompts through every setup. Auto Routing was 69% cheaper while retaining 98% of the baseline quality. The second experiment ran three production-shaped workloads through every setup, using user chats, developer chats, and long agent tasks. Auto Routing was 80% cheaper. Thanks to the TrueFoundry team for partnering with me on this post.

Santiago

15,543 views • 15 days ago