The PC keeps doing the work with its own CPU, memory and graphics. Its system disk lives on central distributed storage, so it can be snapshotted on a schedule and rolled back to a known state. This tour uses a real physical desktop, not a VM.
| Product version | pre-release builds of 2026-10-23 and 2026-10-30, shipped in release 81fce3de6; cloud PC asset pack 20261103.1 |
|---|---|
| Terminals | a physical AMD desktop (Windows in BIOS and in UEFI mode, Debian); an office PC through a USB network adapter; Windows UEFI clones on VM terminals |
| Operating systems | Windows 10/11 (24H2) templates built from the customer’s own licensed ISO; Linux templates Debian 13 and Ubuntu 24.04 |
| Boot | PXE or boot media → signed iPXE; BIOS and UEFI; Secure Boot off |
| Data path | Windows: iSCSI from a Nodekeeper site node in the same site, per-session CHAP, on an isolated storage network. Linux: block device on distributed storage, mapped directly. |
| Result, 2026-10-30 | Windows “save as template” passed end to end in BIOS and UEFI mode; new PCs from the template completed first-boot setup, extended drive C: automatically, had network right after the first login and ran the first-boot script |
| Result, 2026-10-23 | hourly automatic snapshots of a cloud PC disk with “keep 2” — the oldest was pruned on schedule; snapshot space was measured and counted against the owner’s quota; a 2FA-confirmed rollback of a storage volume matched the snapshot checksum, and rollback was also verified on VM disks |
| Snapshot consistency | crash-consistent (no VSS, no guest agent) |
| Scale | a few terminals; no concurrent-boot or large-scale test, so no performance figures are published |
| Manual intervention | Windows needs a one-time network-card warm-up for each new NIC model and slot layout |
Read more: Office PCs and centralized storage · Cloud PCs · Distributed storage
The sandbox is invite-only and not open yet; there is no public live demo. Please do not send passwords, keys or customer data with a request.