
Lock the exact models, custom nodes, dependencies, and workflow behind a run that actually worked. Free up local SSD space without fear — bring missing models and red nodes back anytime, or revive your environment on a cloud GPU in minutes.
One active workflow slot included free for a full week. Safe local SSD cleanup. No card needed.
ComfyUI on Windows, macOS and Linux · Cloud restore verified on Linux + NVIDIA (RunPod, Vast.ai)
Check compatibility & limits →
The run it came from
The models inside
All logos, trademarks and registered trademarks are property of their respective owners.
Three steps
The render finally works. One command records what made it work — the models, the custom nodes, the exact locked versions, the workflow — so the machine underneath becomes disposable again. If a package can't be installed on another machine, the pack says so and marks the nest.
Your first active workflow sits in your drive free for a full week — or permanently on a paid plan. Nothing is running, nothing bills by the hour, and a file you have already stored is never stored twice.
One command on whatever you rent next. Every file is checked byte for byte on the way in and the dependencies are reinstalled at the versions you packed. Then it starts the app, runs the packed workflow once and tells you what passed, what didn't, and where the output is. Where it stands today: the files come back, checked.
One measured case · 9 October 2026
Restore, step by step · seconds
✓ Re-ran the packed recipe and it produced 1 image in 48s One measured run, by us. Renting and booting the machine are not in the time.
See the full record →What travels with your workflow
Restoring for yourself brings back every stored file, each one checked.
output/ temp/ input/ user/ No licence from the author, so it does not travel in a hand-off: the recipient's restore names it and its source, fetches it from there and checks it against the nest.
Two ways to start
Claim a starter nest — a hand-off from Renest — and restore it on a machine you rent.
FLUX.2 Klein 4B
Z-Image-Turbo
Wan 2.2 TI2V 5BGet the run working first — then save it in one click from the ComfyUI sidebar panel (Windows, macOS, Linux) or with the CLI. Your first active workflow sits in your drive free for a full week.
$ uv tool install --upgrade renest$ renest pack --dir ./run --workflow workflow-api.json --out ./nests --dest hosted
Where the promise stops
Source-available tool · Open format
The format spec and the escape hatch are Apache-2.0; the renest tool's source is public, but the tool is not open-source software. Nothing about a nest depends on us still being here — your work is never hostage to us.
Every nest ships one. It brings back the files and the locked dependencies with zero Renest code.
bash restore.sh Point it at your nest and a target folder. It leans on curl · jq · sha256sum · tar · uv — and nothing else. escape hatch
Hand-off
A hand-off is a private link: they claim the nest into their own drive and restore it on their own machine. A file whose licence doesn't let you pass it on does not travel: their restore names it and where it comes from, fetches it from its original source and checks it against the nest.
A hand-off is an unguessable private link, single-use by default. You choose how many people can claim it — up to a limit set by your plan — and how long it lives. It stops the moment the claims run out, the clock runs out, or you revoke it.
Not just "no gallery": the preview page is never indexed by search engines. It shows a summary — name, size, how many files, dates — never the file names, never an image. Nothing for a stranger to stumble into — or a crawler to find.
Claiming copies the nest into their drive without consuming yours.
Pole to pole · ~71,000 km a year
The Arctic tern makes the longest migration on Earth — pole to pole and back, every year. A nest travels the same way: packed once where the run lives, kept in storage while nothing runs, and rebuilt file for file on the next pod you rent.




One global network
A nest comes down from your drive onto whichever machine you rent — RunPod, vast.ai or your own — every file checked byte for byte.
North America · South America · Europe · South Asia · Southeast Asia · East Asia · Oceania
FAQ
A pod's container disk is wiped when it stops, and the custom nodes, their Python packages and downloaded models go with it. A network volume keeps the files inside one region of one provider; a nest keeps the files and a reinstallable record of the environment, and comes back on any machine you rent, every file checked.
If you always come back to the same region and the same kind of machine, you may not. A volume keeps files, not a working environment: the Python packages and system libraries a custom node needs are built for one machine and often break on the next one. A nest reinstalls them for the machine you landed on.
Yes — each keeps a different layer. A Manager snapshot records which node repositories and commits you had and clones them again; it doesn't carry models. A Docker image freezes the system and Python layers, and gets huge with models baked in. A nest keeps the files themselves, the exact package versions to reinstall, and the system libraries the run loaded.
Not necessarily, and we don't promise it. The same GPU model with the same CPU brand gives the same image; other hardware gives small, consistent differences. What we guarantee is the files.
A Linux machine with an NVIDIA GPU, and the renest command-line tool. The quickest start is the official base image — one template link on RunPod or vast.ai. Any other machine works too: the restore checks it before anything downloads and refuses a pairing that cannot work.
It prints where the output is, the workflow file, and the command that starts the app: renest start --dir ./run --listen 0.0.0.0. Open that port in your provider's panel and use your ComfyUI in the browser as usual.
Yes, with a hand-off: an unguessable private link you send yourself — nothing is ever listed publicly. They preview what's inside, claim it into their own drive and restore it on a machine of their own. Receiving works on the free plan; sending needs a paid plan.
They stay yours. The format is open (Apache-2.0) and every nest carries a plain restore.sh that brings its files and dependencies back from storage with ordinary tools and no Renest code. You can also download any version, any time.
Save your first active workflow to your drive free for a full week — or test how fast an environment revives with a verified setup. Free, no card.