Windows compute / Amazon WorkSpaces Personal alternative

Amazon WorkSpaces Personal alternative for portable agents

WorkSpaces Personal provides a returning desktop with root and user volumes. AutoStop can preserve applications and data on eligible configurations, while other configurations stop without hibernating. This is a persistent desktop service with bundle and licensing terms, not one generic per-agent VM tariff.

Start buildingCompare capabilities ↓

Reviewed 2026-10-19 · Published by the Sandbox0 team

When Amazon WorkSpaces Personal fits

Choose WorkSpaces Personal for managed remote desktops, native Windows applications and user access integrated with AWS desktop infrastructure. Confirm OS, protocol, bundle and hibernation requirements for the actual users.

When to consider Sandbox0

Consider Sandbox0 for compatible Linux agents needing automatic online whole-RootFS growth and supported paused files. Retain Windows-native desktop tasks and required user/identity services separately.

Capabilities

Amazon WorkSpaces Personal and Sandbox0: what persists?

Feature comparison with documentation and verification status
Environment and runtime lifetimeAmazon WorkSpaces PersonalAlwaysOn and AutoStop have different desktop and billing lifecycles. Eligible AutoStop restores memory; unsupported configurations stop without retaining unsaved execution state.View evidence ↗Sandbox0ttl and hard_ttl default to 0 (disabled). Configure idle pause and deletion policies for the same persistent sandbox identity; an idle running sandbox still accrues compute charges.Read documentation →
Persistent filesAmazon WorkSpaces PersonalRoot and user volumes retain installed desktop and user data; lifecycle, rebuild and deletion choices must be managed separately.View evidence ↗Sandbox0The writable RootFS survives successful checkpoints, including software, system configuration, dependencies, and user data.Read documentation →
Whole RootFSAmazon WorkSpaces PersonalThe managed desktop has a retained root/system volume as well as its user volume.View evidence ↗Sandbox0Persistence extends beyond /workspace to paths such as /usr/local, /etc, and /home. Runtime tmpfs and virtual filesystems are excluded.Read documentation →
Release compute, keep stateAmazon WorkSpaces PersonalEligible AutoStop desktops hibernate and resume; unsupported configurations stop without preserving unsaved execution state.View evidence ↗Sandbox0Pause compute between tasks; resume on available capacity. Default resume starts fresh processes from the saved filesystem.Read documentation →
Memory and process stateAmazon WorkSpaces PersonalHibernation-capable WorkSpaces save open programs/document state to the root volume, with explicit configuration exclusions.View evidence ↗Sandbox0Experimental memory checkpoints can preserve compatible process state. Use memory: true on both pause and resume on a compatible deployment. A filesystem checkpoint alone does not preserve running processes.Read documentation →

Online RootFS growth

On growth-enabled images, Sandbox0 automatically expands the writable RootFS as free space runs low, within a configured sparse logical ceiling up to 64 TiB. Agent processes keep running. Growth is enabled in the qualified Cloud region; confirm activation for other regions. Existing images and snapshots retain their captured storage geometry. The ceiling is logical capacity, not preallocated host disk.

WorkSpaces Personal already retains system and user volumes and can preserve RAM on eligible AutoStop configurations. Volume growth is explicit and requires a reboot, unlike integrated automatic online low-space RootFS growth for compatible Linux agents.

Files while compute is paused

Sandbox0's Files API reads persistent files without resuming compute. Filesystem-only pauses also permit edits; retained-memory pauses are read-only and reject mutations with 409. SSH, SFTP, file watching, and runtime-only mounts require running compute.

Saved desktop state and retained volumes are meaningful persistence. The cited service does not expose a native arbitrary file API across a paused desktop’s whole system filesystem; desktop protocols or storage tooling have separate access requirements.

See paused file operations →

AutoStop can retain RAM, with important exclusions

On hibernation-capable WorkSpaces, AutoStop saves desktop state to the root volume and restores open documents/programs on login. Some GPU/large compute types and specific Windows/nested-virtualization configurations do not support hibernation. Save essential work to disk rather than assuming every AutoStop desktop restores unsaved memory.

Source 1 ↗

AutoStop still has a monthly base fee

AlwaysOn uses a fixed monthly desktop price. AutoStop combines a monthly base amount with hourly desktop usage and waits for disconnection/its idle period before stopping. The root/user bundle and license choice affect the quote; a stopped AutoStop desktop is not a zero-total-cost desktop.

Source 1 ↗Source 2 ↗

Volume enlargement is explicit and needs a reboot

WorkSpaces documents growing root and user volumes within supported groups, up to 2,000 GB each. The operation extends the guest partition and requires rebooting for the change to take effect. This retains installed-system data but differs from low-space-triggered growth while an agent continues executing.

Source 1 ↗

Pricing

Compare billing models, then price your workload

CPU allocation, memory, billing minimums, disk, plan fees, and supported workload differ. These meters are not equal-performance machine quotes. Confirm region, resource units, and included allowances before estimating a total.

Amazon WorkSpaces Personal

Pricing reviewed 2026-10-19

Published Oregon Windows Standard example
$44 per WorkSpace-month
AWS pricing illustration: 175 GB root/100 GB user; confirm current regional bundle and licensing.
Rate source ↗
AutoStop desktop
Monthly base fee + hourly active usage
The fixed base remains even when compute usage stops; do not substitute the page’s separate Ubuntu example as a Windows rate.
Rate source ↗
Storage, licensing and supporting resources
Match the selected bundle and current quote
Personal and nonpersistent Pools are different products with different meters.
Rate source ↗

The $44 Windows amount is the cited US West (Oregon) worked example, not a universal live order quote. Include root/user capacity, OS/license eligibility, usage mode, IP/network and other selected resources. Do not mix WorkSpaces Pools RDS/user fees or a Linux Power example into a Personal Windows quote.

Check current Amazon WorkSpaces Personal pricing ↗

Sandbox0

$0.015/GiB-hour compute (billed by the second at approximately $0.000004167/GiB-second), plus $0.02/GiB-month of retained incremental RootFS and memory checkpoint data. Shared base images and platform recovery retention are excluded; paused sandboxes accrue storage charges only.

Compute / GiB-hour
$0.015
Retained data / GiB-month
$0.02
Paused compute
$0.00

A 4 GiB agent, 100 running hours

$6.00 compute

4 GiB × 100 hours, billed by the second. Keeping 20 GiB of billable incremental data for a full billing month adds $0.40. CPU is derived from memory by the platform; choose a tier that fits your workload.

Understand storage billing →

Before migrating from Amazon WorkSpaces Personal

  1. Inventory Personal bundle, root/user volumes, OS/protocol, AlwaysOn/AutoStop, hibernation exclusions and native desktop dependencies.
  2. Export required portable files and rebuild Linux-compatible agent stages while retaining Windows desktop and identity requirements.
  3. Test state coverage, unsaved-process requirements, growth, paused files and combined desktop base/usage, storage, networking and Linux runtime costs.

Common questions

Is Sandbox0 a drop-in Amazon WorkSpaces Personal replacement?

Evaluate API compatibility and product scope. These products serve different core workflows, so a change may require a different architecture.

Does keeping files also keep a running agent?

Filesystem state and volatile process state are separate. Sandbox0 requires explicit compatible memory checkpoints to preserve running processes; its default filesystem resume starts fresh processes.

Sources and review scope

The Boat team's Battleships directory is the discovery source. References below describe the product and plan discussed on this page. Check current availability, regional terms and billing units before migrating. Where the cited material does not establish a capability or price, the comparison identifies that uncertainty.

Battleships research record ↗docs.aws.amazon.com/workspaces/latest/adminguide/running-mode.html ↗aws.amazon.com/workspaces/desktop-as-a-service/pricing/ ↗docs.aws.amazon.com/workspaces/latest/adminguide/modify-workspaces.html ↗Sandbox0 RootFS capacity →

Related comparisons

AWS EC2 Windows Server vs Sandbox0 →Azure Windows Virtual Machines vs Sandbox0 →Daytona Windows VM Sandboxes vs Sandbox0 →Google Compute Engine Windows Server vs Sandbox0 →Vultr Cloud Compute Windows Server vs Sandbox0 →Windows 365 Business / Enterprise Cloud PC vs Sandbox0 →