Product

One format.
Four ways to use it.

Save a ComfyUI or fine-tuning run that works — its models, custom nodes, locked dependencies and workflow — and bring it back on the next machine you rent. The console, the command-line tool and the ComfyUI panel all read and write the same open nest format, so start with whichever piece fits.

Covers ComfyUI for image & video, kohya_ss and LLaMA-Factory for fine-tunes.

renest CLILIVE Web consoleLIVE ONE FORMAT · .nest ComfyUI panelLIVE Desktop appIN DESIGN
01

Web console

Live

Your drive in the browser.

  • Every nest and version, and the files inside each one
  • Private hand-offs — revocable, never a public link
  • Free starter nests, and a restore code for every machine you rent

In the browser · nothing to install

02 $ renest pack → models · nodes · locks · workflow ✓ verified file by file

renest CLI

Live

The agent that does the moving.

  • pack · restore · verify · start — one command each
  • Checks the machine before it downloads a byte
  • Source-available, and every nest ships a plain restore.sh

uv tool install renest

03 pack

ComfyUI plugin

Live

Pack without leaving the canvas.

  • One button packs the run that just worked
  • Models, custom nodes and locked deps included
  • Same open format as the CLI

A sidebar tab in ComfyUI · on the ComfyUI Registry

04 local ⇄ pod

Desktop

In design

The cockpit on your desk.

  • Ferry big files straight from your Mac — planned
  • Works with the ComfyUI on your own machine — planned
  • Cloud keys stay in your keychain — planned

Not built yet. When there is something real to try, it will be on the blog first.

Coverage

Does it know your stack?

ADPTFrameworks

ComfyUI — image and video

kohya_ss · LLaMA-Factory — fine-tunes

Named frameworks with a dedicated adapter each.

byte-checkedModels we have actually run

SDXL · FLUX.2 klein 4B

Wan 2.2 — video

Listed only once we have run it end to end ourselves.

Where it runs

RunPod · vast.ai

Or your own Linux box with an NVIDIA GPU

Start from the official base image with one template link, or any machine — the pre-check looks at it either way.

Where it lives

Your Renest drive

Downloadable any time

Every version comes out in the open format, with the script that restores it without us.

A restore rebuilds a recipe on the new machine instead of copying a disk — which is why we cover named frameworks and do not claim “any Python environment”.

Where it lands

Three evenings this changes.

one-time01

You are delivering to a client

The render is approved. They want to run it themselves next month, on their own machine. You send one hand-off — they claim it into their own drive and bring the same files and locked dependencies back on their machine. Nothing of yours is uploaded again.

02

You are chasing the cheap card

The GPU you used last night costs double this morning, and there is a cheaper one two clouds over. You take the setup with you: the pre-check tells you whether the new card can run it before you pay for the hour, and every file is checked on the way in.

03

Someone else is picking up your work

A teammate needs the environment behind last week's output — not “roughly the same versions”, the ones that ran. They get the same files and locked dependencies, checked file by file, without asking you which node version you had.

Everything in the box

The whole list, nothing hiding.

Every line below is shipping today. If it is not here, we have not built it.

the three commandshanding work overwhen things go wronghousekeepingyour way out

Captureone command, or one button in ComfyUI, on the machine that already works
Restoreone command on whatever you rent next
Verifyevery file checked against its checksum when it comes back
Startafter a restore it prints where the output lands and starts the app for you
Hand-offpass a nest to one person privately; openly-licensed files are not uploaded again
Starter nestsclaim a run we packed and checked, free, and restore it yourself
Restore codesgive a rented machine the right to fetch one nest, not your account
Pre-checkdisk, driver, GPU generation and system libraries judged before anything downloads
Resumea cut download picks up where it stopped
Re-fetcha file that fails its check is fetched again, on its own
Dedupa file already stored is never stored twice
Trashdeleted nests can come back for a window
Downloadany version, in the open format, whenever you like
Escape hatcha plain restore.sh brings files and dependencies back with none of our code

Straight answers

What we guarantee,
and what we don't.

We guarantee

Every file, byte for byteFingerprinted when it is packed, checked when it comes back. A mismatch names the file.
The recipe, as it ranCustom nodes at the commit that ran, dependencies at the versions that resolved, the workflow you used.
Your way outAn open format, and a restore.sh that needs none of our code.

We do not

That it runs on any machineWe check instead: the machine is cleared before the download, the app is started and your workflow run once, and the result tells you what passed.
Identical renders on any cardImages depend on the hardware. In our tests the same GPU model with the same CPU brand came back pixel for pixel; a different CPU brand differed by a hair — the same hair every time.
Fragment-level dedupWe deduplicate whole files. Change one byte inside a file and the whole file counts as new.
Redistribute licensed modelsAn asset you had to accept a licence to download is never served to someone else — they fetch it from the original source with their own credentials.
Any Python environmentWe cover named frameworks with adapters. If it has no declarative config, there is no recipe to capture — only files to copy, and that is not what this is.

Every restore we publish ran on a real rented GPU, and the record — failures included — is on the Proof page. You do not have to trust the left column — you can check it.

Is it for you

Is Renest the right tool for me?

Is Renest the right tool for me?

Yes, if you have a ComfyUI, kohya_ss or LLaMA-Factory setup that already works on a rented GPU and you want it back on another machine — or in someone else's hands — without rebuilding it. No, if you're moving models between drives on one PC, moving Windows to Windows (copy the Portable folder), haven't got the setup working yet, or need a serverless deployment.

When you don't need Renest

Capture the run that finally worked.

No credit card. Claim a starter nest, restore it on a machine you rent, and see for yourself what comes back checked. When you have a run of your own worth keeping, save that too.