☁️BizyAir KSampler

If you've used ComfyUI for more than a day you already know this node. Same seed, same steps, same cfg, same giant sampler and scheduler dropdowns. The twist with BizyAir KSampler is that none of the actual denoising happens on your machine. You hit run, the request goes to SiliconFlow's servers, and the finished latent comes back over the wire. That's the entire pitch of the BizyAir pack: nodes that behave like their stock ComfyUI equivalents but don't need your GPU, your VRAM, or a multi-gigabyte checkpoint sitting on your disk.

That convenience comes with a wiring catch you'll hit immediately. This isn't a drop-in replacement for the regular KSampler in an existing workflow, because it doesn't accept a regular MODEL. It wants BIZYAIR_MODEL, BIZYAIR_CONDITIONING and so on, BizyAir's own typed sockets that only come out of BizyAir's own loader and encoder nodes. That's not an accident or a bug, it's how the pack keeps a whole subgraph routed to the cloud coherently: mix a local checkpoint loader into a BizyAir sampling chain and you'll just get a type-mismatch error at the socket, not a working hybrid workflow.

What you actually set

The inputs are the exact same six knobs you already know from the stock node: seed, steps (1-50, default 20), cfg (default 8), sampler_name and scheduler (44 samplers, 9 schedulers, the full stock ComfyUI lineup), and denoise (0-1, default 1 for a full generation, lower for img2img-style partial denoising). Plug in positive/negative conditioning and a latent_image, and the node hands back a LATENT you send to a decoder same as always.

One thing worth flagging before you build around this: steps caps at 50 here. If your workflow needs more than that, per the schema this basic node simply won't take it, that's what BizyAir KSampler (Advanced) is for, which raises the ceiling to 10,000 and adds start/end-step splitting for multi-pass pipelines.

On sampler choice itself, the same rules apply here as anywhere else: what you should pick depends entirely on the model's architecture, not habit. DPM++ 2M Karras is still the right call for SD 1.5/SDXL-family checkpoints, but it's a genuine failure mode, not just a suboptimal one, on flow-matching architectures (Flux, Z-Image, and friends), where Euler-family samplers on a conservative scheduler like beta or simple do far better. If the model card tells you what to use, use that first.

Installing it

Easiest path is ComfyUI Manager: search "BizyAir" (the pack shows up as "☁️BizyAir Nodes"), hit install, restart. Manually it's the usual custom-node clone:

cd ComfyUI/custom_nodes && git clone https://github.com/siliconflow/BizyAir.git

Restart ComfyUI after either method. The part that trips people up isn't the node install, it's the account: BizyAir needs an API key before anything will actually execute, and the README is blunt about it, set it on first use via the "click to login" prompt. Registration goes through SiliconFlow and involves phone-number verification; more than one person on r/comfyui has reported getting stuck there without a Chinese number, so budget time for that step if you're outside China.

Common issues

The one worth knowing about before you even go looking for this node: ComfyUI Manager occasionally auto-installs BizyAir on its own when resolving an unrelated missing-node error, particularly on older shared workflows (pre-February 2025) where node-to-pack inference guesses wrong. People have posted "security alert" threads assuming a foreign node quietly appearing in their custom_nodes folder is malware. It isn't, it's a real product from a real company (SiliconFlow), but if you didn't ask for it and don't want it, it's safe to remove: ComfyUI Manager's uninstall, or just delete the folder from custom_nodes and restart.

Beyond that, the failure modes are what you'd expect from any API-backed node: a run that just sits there or errors out almost always traces back to a missing or invalid API key, not a workflow problem. And if you get a type error at the model socket, it means something upstream is a stock ComfyUI loader instead of a BizyAir one, not a bug in this node.