Comfyui AIUGC Host (ComfyUI-aiugc)

ComfyUIWebHost is the smallest meaningful node in the ComfyUI-aiugc pack: exactly one text field and a no-op run() method. But that one field is doing a surprising amount of work - it's the GPS coordinate that tells the shangxiaobao.com platform which ComfyUI instance should execute your workflow.

The pack (ronaldzgithub/ComfyUI-aiugc) is a fork of ComfyUI Deploy, the "Vercel for generative workflows" project, reskinned around the author's own hosted service. The mental model is the same as Comfy Deploy's: your ComfyUI install isn't just a local tool, it's a machine that a cloud dashboard can drive. You deploy a workflow from your machine to the platform, users hit a hosted app page, and behind the scenes the platform pushes each request back to a ComfyUI instance to render. The Host node is how you register that instance.

The one input

• ComfyUI 主机地址 ("ComfyUI host address") - a string, defaulting to shangxiaobao.com:7190. That's the author's own server, which is your first clue about who this is built for.

That's it. No outputs, no other options. It's a declarative marker node: when the platform's app-builder reads your workflow, it finds this node and knows where to send the job. On the runtime side, the pack's custom_routes.py exposes endpoints like /comfyui-deploy/run that receive a workflow, inject the end-user's inputs, and execute it on the host that answered.

What you'll actually hit

Two things, in order of annoyance.

The default is someone else's server. shangxiaobao.com:7190 is baked in. If you're running your own ComfyUI and you don't change it, your workflow may be pointing at a machine you don't control. If you're using the author's hosted service, sure, leave it. If you're self-hosting, put your own reachable address in there - which means your ComfyUI needs to be publicly reachable, and that opens the can of worms the community has been warning about since the "PSA: Please secure your ComfyUI instance" days: a stock ComfyUI server has an unauthenticated API, and anyone who can reach the port can execute arbitrary workflows on it. Put auth in front of it (reverse proxy, tunnel with auth, whatever) before you point a host address at it.

The node is inert by itself. On its own, on your own machine, it does literally nothing - run() is empty, there are no outputs. It only matters inside the full aiugc deploy flow, and that flow assumes you're a user of shangxiaobao.com, a platform with effectively no English documentation. The pack is also a near-dormant fork - one star, last meaningful push in late 2024, zero Reddit footprint for the pack, the platform, or the author's brand.

Installing it

No ComfyUI Manager presence worth relying on; just clone it:

cd ComfyUI/custom_nodes
git clone https://github.com/ronaldzgithub/ComfyUI-aiugc

Restart ComfyUI. Dependencies are small - aiofiles, pydantic, opencv-python, imageio-ffmpeg - no model downloads. Note the repo's README is upstream Comfy Deploy's, so don't follow its self-hosting instructions; the real install is the two lines above.

If your actual goal is "let other people run my workflows in a browser," the ecosystem has better-trodden roads - Comfy's own App Mode and Comfy Cloud, or the inference-platform integrations covered in the KB's API-node essay. ComfyUIWebHost is a glimpse at one developer's private pipeline for doing exactly that. Interesting as an artifact, and required if you're on that platform, but not a tool the broader community is rallying around.