加密组件

"Save" is doing a lot of work in that name. SaveCryptoNode (加密组件, "encryption component") is the start marker of the CryptoCat encryption pipeline, and running it once does the entire job: it strips the core of your workflow out of the JSON, uploads it to the author's server, writes out a distributable "shell" workflow, and mints ten license serial numbers. It's the node you reach for when you want to hand someone a working ComfyUI workflow without handing them your recipe.

CryptoCat is a one-pack project by RiceRound that sells a simple idea: bracket the part of your workflow you care about between two nodes, and the JSON you share no longer contains it. SaveCryptoNode opens the bracket, SaveCryptoBridgeNode closes it, and the distributed workflow automatically swaps the opener for the auto-generated DecodeCryptoNode that your customer runs with a serial number. It launched in late 2024 with a big commercial pitch - "the world's first commercial-grade workflow encryption tool" - and got a single Reddit comment in response, offering to recreate any encrypted workflow for free. More on that skepticism below.

How it works

When you queue the workflow, the node parses the whole graph (it needs the PROMPT and workflow data ComfyUI passes to every output node), finds itself and the bridge node, and collects every node between them. That middle section becomes the encrypted payload. It's written to disk, zipped, and uploaded to the CryptoCat backend at api.riceround.online - so yes, encryption and a phone-home are the same feature here. A cryptocat_<template_id>.json shell workflow is written to your output folder with the opener replaced by DecodeCryptoNode, and serial_numbers_<template_id>.txt appears next to it with ten serials.

There's no offline path in the current code. If it can't authenticate, the node returns an ExecutionBlocker and nothing else happens.

The inputs that matter

• template_id - a string that becomes the key for your workflow on the server. It defaults to a random uuid4().hex (exactly 32 hex characters), and the code hard-fails if the value isn't 32 chars. Treat it as the product ID of your workflow; the serials you mint are tied to it.
• input_anything - an optional any-type socket that's effectively a holdover in this node; the decode side is where external inputs actually get consumed.

The node has no outputs and is marked as an output node, which is why ComfyUI treats it as a run endpoint.

Install

ComfyUI Manager is the easy route - search for "ComfyUI Compression and Encryption Node" or the author's name RiceRound. Or clone it:

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

Then restart ComfyUI. The pack's requirements.txt is small - aiohttp, pyzipper, websockets - and there are no model files to download. One thing Manager won't tell you: the first run pops a login dialog. CryptoCat requires an account on the author's service; your serial numbers, keygen, and workflow storage all live behind it.

Where people get burned

• Forget the bridge. The README's warning is the top of the list: SaveCryptoNode and the bridge go head-to-toe, one at the start and one at the end. Without the bridge, the node raises "No 'SaveCryptoBridgeNode' instances found."
• Missing output connections. The README also stresses that output node connections can't be missed - the value that wires into the bridge is what your customer gets back out.
• Offline or logged out. Everything stops if api.riceround.online is unreachable. This is a cloud dependency, full stop.

The honest take

Encryption protects the workflow JSON - it cannot protect the technique. Someone with your output image and a prompt can usually reconstruct a workable equivalent, which is exactly what that one Reddit comment promised. And because this pack ships a node that uploads your workflow to a third party's server, you're trading "nobody can copy my workflow" for "the author's server has my workflow." That's a real trust calculation. If you're packaging paid workflows for customers who'll accept a serial-number/hardware-binding model, this is one of the few tools that does it; if you just wanted to tidy a workflow for sharing, ComfyUI's normal PNG-embedded workflow sharing is friendlier and there's nothing to license.