Office PCs · Business plan

Keep Your PCs. Centralize Their System Disks.

Windows and Linux network boot for the PCs you already own. Each PC keeps running on its own processor, memory and graphics card, while its system disk moves into Nodekeeper distributed storage: one shared base image, a separate writable disk for every PC, snapshots and full-disk backups, all managed from one panel.

You don't have to turn every desk into a remote-desktop seat. Boot supported PCs from the network, keep each user's changes separate, and manage capacity, recovery and access in one place, across offices if you need to.

  • x86_64 PCs, BIOS or UEFI
  • Windows 10 / 11 · Debian 13 · Ubuntu 24.04
  • Network boot across locations
  • Included in Business

Business: $29 per node per month after the free first month. Card required, once per account; cancel before day 30 and you are not charged.

What changes for your office

Nine everyday problems, and how Nodekeeper handles each one.

Problem: central control seems to require VDI

Keep local computing

PCs run the operating system and applications themselves. Only the disk is central, so the desktops you already own stay useful and nothing has to be streamed to the screen.

Problem: the same OS is stored on every PC

One base image, one writable disk per PC

A template version is stored once as a read-only snapshot. Each PC gets its own copy-on-write disk, so only that PC's own changes take extra space and no two PCs write to the same disk.

Problem: every PC gets the same big drive

Allocate capacity from one pool

Disks are thin-provisioned in a central distributed storage pool with a quota per owner, so space is used as data is written. The pool grows by adding disks or hosts, not by replacing the drive in every PC. Storage management

Problem: a bad update means a reinstall

Roll back to a recovery point

Take snapshots by hand or on an hourly or daily schedule with a retention count, then roll a PC's disk back to one of them instead of rebuilding the PC.

Problem: one lost disk is one lost PC

Back up whole cloud PC disks

Back up a PC's entire system disk and restore it when you need it, alongside the website and database backups you already schedule. Full-disk backup and recovery

Problem: branch offices keep their own setup

Network boot across locations

PCs can boot from central storage across a wide-area network, so a branch office uses the same images, quotas and recovery tools as headquarters, managed from one panel.

Problem: a storage node failure stops Windows PCs

Windows iSCSI failover

The iSCSI service that serves Windows system disks supports automatic failover, so a node failure takes less manual work to recover from.

Problem: a failed PC takes the user's system with it

Continue on another PC

The system disk is not inside the PC. After a hardware failure the user logs in on another compatible PC, and Nodekeeper moves the cloud PC there and cuts off the old machine.

Problem: who may touch which PC?

Access by user group

Every permission is granted by user group. Administrators manage templates, disks and quotas; members see and manage only their own cloud PCs.

How an office PC boots, and where its disk lives

Linux and Windows take different paths to the same storage. The diagram shows the deployment as Nodekeeper builds it, and the steps are listed next to it for small screens.

How office PCs boot and where their disks live Nodekeeper panel manages a site node and a distributed storage cluster. Linux PCs map their block disk from distributed storage directly. Windows PCs boot over iSCSI from the site node, which reads the block disk from distributed storage. Every PC starts from PXE or boot media, loads signed iPXE and logs in on the NK boot screen. Nodekeeper panel (master) templates · disks · quotas · snapshots · login check · audit management + login check (NK mesh, can span offices) Distributed storage management Storage site: site node and distributed storage cluster. PCs boot from here, on the local network or across a WAN Linux office PC Debian 13 · Ubuntu 24.04 runs on its own CPU · RAM · GPU Windows office PC Windows 10 · 11 runs on its own CPU · RAM · GPU How every PC starts PXE, or USB / ISO boot media → signed iPXE → NK boot login BIOS or UEFI · Secure Boot off Site node NK node · VM or physical • network boot files • iSCSI target for Windows Distributed storage cluster Block storage pool · replicated Template v1 · v2 … read-only snapshots COW clone Disk of Linux PC (writable) Disk of Windows PC (writable) + snapshots of each disk PC disks do not use file storage Block device: Linux maps its disk directly iSCSI block boot files + login (through the site node) disk reads and writes boot and management iSCSI traffic is not encrypted: keep it on an isolated storage network.
Solid lines carry disk reads and writes. Dashed lines carry boot files and management. On a narrow screen, scroll the diagram sideways.

The boot, step by step

  1. The PC starts from the network (PXE) or from boot media (a USB stick or an ISO) and loads an iPXE build signed by Nodekeeper.
  2. Nodekeeper's signed boot system shows a login screen: the user's cloud PC password, plus a one-time code if 2FA is on. The password is checked with SRP-6a, so it is never sent over the network.
  3. Linux PCs map their own block disk straight from distributed storage and start.
  4. Windows PCs boot over iSCSI. A dedicated NK site node (VM or physical) serves iSCSI boot for Windows; Linux PCs map their block disk from distributed storage directly. Each session gets its own CHAP credentials.
  5. From then on the PC's own CPU, memory and graphics run everything. Only disk reads and writes go over the network.

Who does what

PartIts job
PXE or boot mediaStarts the PC and loads signed iPXE.
Nodekeeper boot loginChecks the user before any disk is handed out.
Site nodeServes the boot files and, for Windows, the system disk over iSCSI.
Distributed block storageHolds the template versions and every PC's own writable disk.
Distributed file storageCloud PC system disks are block devices on distributed storage; distributed file storage holds website storage and members' 'My storage'.
An office PC network-booting: boot files load, then the user logs in on the Nodekeeper boot screen.

An office PC network-booting: boot files are fetched, then the user logs in.

Cloud PC list showing the allocated size and data written for each PC.

The cloud PC list: allocated size and data actually written, side by side.

Capacity: 100 PCs with 2 TB each

An office has 100 PCs. Some people need little more than the system and a few documents, others need a lot of working space. Giving every PC a 2 TB drive doesn't let unused space flow to the people who need it. With Nodekeeper, PC disks come out of central storage, are allocated as needed and grow with the cluster. Here, 2 TB means disk storage, not memory.

Four numbers to keep apart

  1. Local disks today: 100 × 2 TB = 200 TB, mostly empty, and none of it can be shared.
  2. Allocated size: what each PC sees as its disk. Allocating 2 TB does not write 2 TB.
  3. Data actually stored: the shared base image, plus each PC's own new or changed data, plus whatever snapshots keep.
  4. Raw capacity to buy: the stored data times the number of replicas, plus room for rebuilds and growth.
Illustration with example numbers, decimal units (1 TB = 1,000 GB).
All PCs use the same base image:
  base image B            = 100 GB
  each PC's own data  Δ   = 100 GB
  number of PCs       N   = 100

Data stored today:
  D = B + N × Δ = 100 + 100 × 100 = 10,100 GB = 10.1 TB

Stored with three replicas:
  10.1 × 3 = 30.3 TB

Keeping normal use at 75 % of raw capacity:
  30.3 ÷ 0.75 = 40.4 TB

Snapshot history, extra template versions and uneven data placement add to this, and the 75 % is an example rather than a rule. Size your own deployment from a pilot group of PCs.

  • A PC's own data is more than the files people save on purpose: updates, caches and the page file count as well.
  • Snapshots keep old data and therefore take space. Their space counts against the owner's quota.
  • A new template version does not upgrade the PCs cloned from an older one.
  • Watch quotas and free cluster space, and add disks or hosts in good time.

Shared images and capacity management in Nodekeeper storage →

Recovery points, backups and failover

Updates go wrong and hardware fails. Nodekeeper gives each case its own way back.

Snapshots

  • Manual, or hourly and daily with a retention count. Scheduled snapshots stay off until you switch them on.
  • Roll a PC's disk back to a snapshot, or save a snapshot as a new disk.
  • A snapshot of the current state is taken automatically before every rollback and before a reinstall.
  • Rollback needs the PC switched off and a 2FA confirmation.

Full-disk backup

  • Back up a cloud PC's whole system disk and restore it later.
  • Backups protect against losing the cluster itself; snapshots live inside it.
  • Websites and databases are backed up with the same backup module.

Backup and recovery →

Failover

  • The Windows iSCSI service supports automatic failover.
  • Linux PCs that are already running talk to distributed storage directly.
  • Replicas keep data available when a storage disk fails.
  • A user can continue on another compatible PC.

Recovery options →

Snapshots are crash-consistent: the disk is captured as if the power had been cut at that moment, so an application that was writing may need its own recovery. Disk reads and writes need the network, so plan redundant links for the offices where it matters.

Connect Offices. Manage Storage and Recovery Together.

One Nodekeeper panel can manage several locations, and PCs can network-boot across a wide-area network.

One panel

Templates, disks, quotas and recovery for every office, connected through the NK mesh, an encrypted network between Nodekeeper nodes.

Boot across locations

A branch-office PC can boot from storage at another location. Disk traffic uses the link between the sites, so plan bandwidth and latency for it.

Same images everywhere

Publish a template version once and clone it for PCs in any office.

Access by user group

Give each office or team the group permissions it needs, and nothing more.

Multi-site networking →

What your PCs and network need

PCsx86_64 PCs, and virtual machines as terminals. Boot by PXE or from boot media (USB stick or ISO), BIOS or UEFI, with Secure Boot turned off.
WindowsWindows 10 and 11. Nodekeeper builds the template from your own licensed Windows ISO. Each network card model needs a one-time preparation step before Windows can boot from it. Install graphics drivers yourself.
LinuxDebian 13 and Ubuntu 24.04 templates, with the kernel Nodekeeper ships.
Storage networkiSCSI traffic is not encrypted, so keep it on an isolated storage network. Linux PCs map their disk directly from distributed storage.
Users and accessA cloud PC password per user (SRP-6a) plus an optional one-time code. A cloud PC runs on one PC at a time.
LicencesWindows and application licences are yours. See plan and licensing.

Questions

Is this a virtual desktop?

No. Office PCs network-boot and run the system and applications on their own hardware. Only the system disk is central. Running desktops as virtual machines is a separate path, described on the cloud PC overview.

Do I need to buy thin clients?

Not necessarily. Existing x86_64 PCs work if they can boot from the network or from a USB stick and run with Secure Boot off. Try a sample of your PC models first, as you would before any rollout.

If 100 PCs each get a 2 TB disk, do I need 200 TB of storage?

No. Allocated size is not stored data. Plan from the base image, each PC's own writes, snapshot history, replicas and headroom, as in the capacity example.

Do several people share one writable Windows disk?

No. They share a read-only template version. Every PC has its own writable disk, and a cloud PC runs on one PC at a time.

Can the PCs work without the network?

No. A PC that runs from a network disk needs the network and the storage while it runs.

Can snapshots replace backups?

No. Snapshots live in the same cluster as the disks and are for undoing changes. Use full-disk backups for the data you cannot lose.

Do you provide the PCs, servers, storage or Windows licences?

No. Nodekeeper is self-hosted management software. The PCs, servers, disks, network and the operating system and application licences are yours.

How are licences counted?

Nodekeeper is licensed per node, meaning each machine that runs Nodekeeper. Office PCs that network-boot do not run Nodekeeper. Tell us how many site nodes and storage hosts you plan and we will confirm the count before you buy.

Plan and licensing

Business
$29 per node per month (after the trial, monthly subscription)

The whole office workflow is in Business: network boot, the site node with iSCSI for Windows, distributed storage deployment and management, templates and clones, quotas, snapshots, full-disk backup and rollback, and the NK mesh between offices.

Per node means per machine that runs Nodekeeper. Tell us how many site nodes and storage hosts you plan and we will confirm the count.

After the free first month: $29 per node per month. Card required, once per account, up to 3 nodes; cancel before day 30 and you are not charged. Other billing options (yearly billing, other currencies) are on the pricing page and are not part of the trial.

Pro

Pro manages virtual machines but contains no cloud PC or distributed storage features, so it cannot run this workflow.

Enterprise

For contract terms and larger deployments, discuss your deployment with us.

Related guides: What Windows network boot is and when it fits · Shared images and writable clones: planning PC storage · Website, database and full-disk backups: which workflow

N Nodekeeper

Manage websites, office PCs and servers from one panel on your own hardware.

Support
support@host.mw WhatsApp: +817093066006

© 2026 Nodekeeper. All rights reserved.