One measured case · 9 October 2026
This page is the full record behind the case on the home page. It is one run that we carried out and measured ourselves: the same account packed the nest and restored it, so nothing was handed to anyone. It is not a rate, and it says nothing about machines we did not use.
| Packed on | Restored on | |
|---|---|---|
| Cloud | RunPod | Vast.ai |
| GPU | RTX A5000 | RTX 3090 — the same GPU generation |
| Where | CA-MTL-1, Canada | Ukraine |
| Date | 7 October 2026 | 9 October 2026 |
| renest tool | 0.1.20 (pre-release build) | 0.1.21 (as published on PyPI) |
The result holds for this pairing of tool versions only. This page reports that pairing and no other.
Anima Standard, a community ComfyUI image workflow published on Civitai. The nest held 14 files, 5.67 GB in all: 3 model files, the ComfyUI code, 5 custom-node packs the workflow uses (ComfyUI-Easy-Use, ComfyUI-Image-Saver, ComfyUI-Impact-Pack, ComfyUI-KJNodes, ComfyUI-Lora-Manager), the dependency lock, and the workflow itself. The 164 Python packages in the lock were reinstalled at the packed versions, not copied.
| Stage | Time | What the restore said |
|---|---|---|
| S0 checking this machine | 27 s | machine checked; 2 notices, nothing was held back |
| S1 downloading | 76 s | 13 downloaded, 1 already here |
| S2 putting files in place | 52 s | All 5 files check out, 6 code folders in place, lockfile back where it belongs |
| S3 installing dependencies | 293 s | Python environment ready (python 3.11.16) |
| S4 starting up | 25 s | The app started and is answering |
| S5 test render | 48 s | Re-ran the packed recipe and it produced 1 image in 48s |
| Door to door | 536 s | The restore reported it as 8 min 56 s; exit code 0. |
The first stage printed machine check: warn. Behind it: 14 checks passed, 1 check could not be answered, and there were 2 notices — a GPU driver version different from the packing machine's; a CPU with fewer instruction sets than the packing machine's. The restore went ahead: nothing was held back.
Door to door is the restore command, from its start to its last line; renting and booting the machine and installing the tool are not in it. Starting the rented machine took another 352 s, before the restore began. The stages do not add up to the door-to-door figure exactly: the rest is the time between them.
✓ Re-ran the packed recipe and it produced 1 image in 48s A separate check, not the product, re-read 5 nest files + 1 dependency lock on the restored machine and compared each one byte for byte with the nest: 6 files compared, 0 differed. It could not re-compare 7 items — the code archives are unpacked and removed during a restore, and the workflow recipe is stored without a fixed path — so for those the only check is the product's own, on the way in.
The restore's last stage ran the packed workflow and produced 1 image. The separate check then started the app itself and ran the workflow again on the same machine: the second image was the same file as the first. The image was not compared with the one made on the packing machine; across different machines we compare files, not images.
Each environment we offer is a run we packed after it produced output. Take one and restore it on a machine you rent; the restore prints the same stage lines you see above.