ComfyUI Appstore Host (ComfyUI_Appstore)

ComfyUIAppstoreHost is the config node at the heart of the ComfyUI_Appstore pack, which turns a ComfyUI workflow into a hosted web app on 画小宝 (huaxiaobao.net) that end users pay to run. This node is where the pack learns which ComfyUI it should point the platform at when you publish your workflow as an app.

The name "Host" does a lot of work, because this node doesn't host anything itself. It has exactly one input - ComfyUI 主机地址 ("ComfyUI host address"), a plain STRING that defaults to shangxiaobao.com:7930 - and no outputs. Its run method returns nothing. It's a marker: the value gets read out-of-band by the pack's connector, not passed along wires in your graph. If you wire it to something expecting data, nothing happens, and that's by design.

Here's the mechanism, from the pack's own source. When the plugin loads, __init__.py hooks into ComfyUI's HTTP server (server.PromptServer.instance), derives a unique subdomain from your machine's MAC address and the ComfyUI port, and starts a connector client that maintains a websocket to the platform backend so it can reach your instance. The Host node's value is the address the platform is told to use. The default already points at the platform's own server, so if all you want is to publish an app, leave it alone - you only change this if you're self-hosting the platform side or running a mirror.

Installing it

The README is one paragraph and a demo video, so there's no official install doc - the standard custom-node path applies. Through ComfyUI Manager, search for "ComfyUI_Appstore" and install, or:

cd ComfyUI/custom_nodes
git clone https://github.com/ronaldzgithub/ComfyUI_Appstore
# restart ComfyUI

No model files, no heavy downloads. The dependencies (aiohttp, websockets, aiohttp-cors, requests, numpy, Pillow, piexif) are mostly already present in a normal ComfyUI environment, and install.py auto-installs whatever's missing on load.

The part nobody warns you about

This is the node where you should pause and read the source before enabling anything. Its whole job is to introduce a third-party server to your ComfyUI - and the pack doesn't stop at one config string. It opens routes on ComfyUI's own server with permissive CORS, starts a connector tied to a subdomain generated from your hardware, and phones home to a mainland-China-hosted backend (the demo video sits on Aliyun's china-mainland bucket). ComfyUI's API is unauthenticated by default, and the ecosystem has a well-documented history of custom nodes that turned out to be more than they claimed - the LLMVISION infostealer arrived through exactly this install path. None of that means this pack is malicious; it means the trust decision is real and you should make it with the source open.

Practical gotchas beyond security: this is a niche, China-focused platform with essentially zero English-speaking community footprint - there are no reddit threads to consult when it breaks. And outside mainland China you can expect latency and occasional dead connections to shangxiaobao.com:7930; the connector will just sit there retrying. If that's a dealbreaker for a tiny monetization experiment, a locally-served workflow might be the saner first step.