Roadmap

What is done, what is next, and the four things that must be true before a paying customer moves onto Deskspawn.

Done

A prototype on one PC.

A prototype. Everything runs on Docker on one Windows PC.

Done

The Firecracker test.

Firecracker test, done: restore to a working desktop took 1.7 to 3.0 s across five runs, and Firefox ran in 2 GB.

Next

Firecracker behind the same API.

Next: a Firecracker backend behind the same API, with the control plane moved out of the desktop.

Then

A first owned fleet.

Then: the first owned fleet, one tenant per host, TLS on the public API.

Then

Thirty days of real work.

Then: a 30-day run of BOISE AI's own agent work on that fleet.

The bar

Four things first.

No paying customer moves until four things are true: the bar for replacing today's setup is met, the 30-day run is complete, a rollback plan is written, and today's setup is still paid for.

Illustration. Solid light is done; dashed is not started.

Each stop, in detail

No dates are given past what is done. The later steps run in this order.

  1. Done

    A prototype on one PC

    A prototype. Everything runs on Docker on one Windows PC. No paying customer has ever touched it.

    • A stopped desktop keeps its home disk.
    • Clone and a soak rig for long test runs are built and merged, but not yet running on the fleet.

  2. Done 2026-09-22

    The Firecracker test

    Firecracker test, done: restore to a working desktop took 1.7 to 3.0 s across five runs, and Firefox ran in 2 GB.

    • Screenshot, pointer and keyboard were driven from the host, never from inside the desktop.
    • No kill criterion fired.
    • Getting the full desktop session running inside Firecracker is part of the next step.

    Measured on a rented test machine with a 2 GiB guest, not on the Windows PC.

  3. Next · not started

    Firecracker behind the same API

    Next: a Firecracker backend behind the same API, with the control plane moved out of the desktop.

    • Done when all 31 test suites pass against it, a test proves one tenant cannot reach another, and a person has read the isolation code.

  4. Then

    A first owned fleet

    Then: the first owned fleet, one tenant per host, TLS on the public API.

    • Done when a second person can bring the fleet back up from the docs alone.

  5. Then

    Thirty days of real work

    Then: a 30-day run of BOISE AI's own agent work on that fleet.

  6. The bar

    Four things before anyone pays

    No paying customer moves until four things are true: the bar for replacing today's setup is met, the 30-day run is complete, a rollback plan is written, and today's setup is still paid for.

Next