RiceRound Cloud

The display name is "RiceRound Cloud," but the class name is RiceRoundDecryptNode, and that's the more honest description. This is the mirror image of RiceRound Publish: Publish takes your workflow, encrypts it, and files it under a template_id on riceround.online; this node takes a template_id and calls that published workflow back, handing you the resulting image. It's an API-call node in the same spirit as the platform-hosted "API nodes" pattern other ComfyUI hosts use - the difference is the thing being called was itself built and published by a RiceRound user, not a vendor's foundation model.

What it's for

Two realistic uses: verifying that something you (or someone else) published actually behaves the way it's supposed to before you point end users at the public page, or composing a published RiceRound workflow as one step inside a larger local graph - treating someone's encrypted, hosted pipeline as a black-box node the same way you'd treat any remote API. It's filed under the Output category, and per the pack's README, Output-category nodes are meant for debugging and verification rather than production graphs you go on to publish yourself - so the more likely everyday use is the first one: sanity-checking a template before you ship it.

The inputs and output that matter

• rice_template_id (STRING, no default) - the ID of the published workflow you want to invoke. This is the same identifier that comes out of a RiceRound Publish run, so you're pairing this node with a template_id someone else generated.
• seed (INT, default 0) - worth flagging as a small tell about how this pack was put together: its tooltip is the stock ComfyUI text, "The random seed used for creating the noise," copy-pasted rather than written fresh for what this field actually does here (control reproducibility of a remote call, not local sampling noise). Treat the tooltip as boilerplate, not documentation.
• input_anything (optional, wildcard type *) - accepts literally anything. This is the common ComfyUI trick for forcing execution order: wire something into it that needs to run before this node fires, and the graph will respect that dependency even though the value itself isn't used for anything semantic.
• Output: a single IMAGE, and the node is marked is_output_node, so it's meant to terminate a branch of your graph rather than feed further nodes - though nothing stops you from routing that IMAGE onward if you need to.

Installing it

Via ComfyUI Manager, search "RiceRound" and install, or by hand:

cd ComfyUI/custom_nodes
git clone https://github.com/RiceRound/ComfyUI_RiceRound

Restart ComfyUI. No dependencies or model downloads are listed in the README - this node makes a network call to RiceRound's platform rather than running inference locally, so there's nothing heavy to fetch on install.

Common issues & troubleshooting

Nothing comes back, or it hangs. Since this calls out to riceround.online rather than running locally, connectivity to that service is a prerequisite the README doesn't spell out anywhere near this node - if your machine can't reach it, expect a stall or an error rather than a clear message.

You're testing whether "encrypted" workflows are actually protected. Worth setting expectations here: a near-identical pitch from a different, unrelated pack got the community response that key-based workflow protection is trivially bypassed by anyone willing to run the graph and export it - the RiceRound author's own earlier project made essentially the same "protect and monetize your workflow" pitch. This node calling back into the platform to re-run a template doesn't change that calculus; it's how the platform intends the template to be used, not evidence of how well it's protected.

rice_template_id doesn't resolve to anything. Double-check it's a template you (or whoever shared it) actually finished publishing with RiceRound Publish - a workflow that only got as far as a local workflow.json was never uploaded, and this node has nothing on the platform side to call.