Release tracker
The road to WillowOS 1.0
WillowOS has been in the works since late 2025. Here is everything built so far, what's left before the first public release, and how far along it is.
321 of 1000 sprints complete
- Foundation 133
- Release plan 188 of 867
- 679 sprints left
- Launch date to be announced
- Updated November 16, 2026
Built so far
Planning begins: a private, secure desktop OS written from scratch in Rust.
Coding begins.
A fully working hybrid kernel written in Rust, booted by a patched open-source Rust bootloader, with memory management, scheduler, system calls, file system, desktop and first apps.
Desktop hardening: input, search, shortcuts, clipboard and text editing.
Real programs run in user mode, and files persist to disk.
The WillowOS file system, TCP and TLS 1.3 networking, a firewall and VPN, disk encryption, the installer, signed updates with rollback, USB, power and sleep, multi-core scheduling, a built-in database, and the Settings, Files, Editor and Terminal apps.
Groundwork for running Linux apps, secure connections moved toward their own service, and a full security audit with fixes.
The sprint plan to 1.0 begins: the new desktop design, security reviews, clean-room driver tools, and the work tracked below.
Stages
- Now
Build
Finish the desktop, apps, security and app compatibility.
- Next
Alpha
Testers install on their own PCs. Their reports drive hardware support, and fixes ship automatically.
- Then
Beta
A wider test shortly before launch.
- Date to be announced
Release
Version 1.0 passes every release check on tested hardware.
Alpha, beta and launch dates will be announced when they're scheduled. Waitlist members hear first.
Release plan by area
Foundation, finished before the sprint plan
-
Kernel core: boot, memory, scheduler and system calls
Done17 of 17 complete100%
-
Desktop basics: input, search, shortcuts and text editing
Done10 of 10 complete100%
-
Networking, secure connections, firewall and VPN
Done5 of 5 complete100%
-
Hardware support: disks, USB, power and audio
Done17 of 17 complete100%
-
File system, disk encryption, installer and updates
Done16 of 16 complete100%
-
Settings, timeline, tags, backup and stability
Done23 of 23 complete100%
-
The desktop and apps moved to user mode, plus the built-in apps
Done24 of 24 complete100%
-
Platform: Linux app groundwork, multi-core, database and crash recovery
Done21 of 21 complete100%
The sprint plan to 1.0
-
Desktop and the WillowOS look
In progress29 of 64 complete45%
-
Security and privacy
In progress25 of 136 complete18%
-
Windows and Linux apps, and the web browser
In progress3 of 26 complete12%
-
Games, Steam and the app store
In progress1 of 42 complete2%
-
Widgets and living wallpapers
In progress6 of 26 complete23%
-
Core system: speed, stability, networking and storage
In progress68 of 240 complete28%
-
Built-in apps
In progress36 of 182 complete20%
-
Graphics drivers for Intel, AMD and NVIDIA
In progress1 of 13 complete8%
-
Backup and recovery
In progress0 of 24 complete0%
-
Hardware: Wi-Fi, Bluetooth, Ethernet, audio, USB
In progress7 of 57 complete12%
-
Installer, updates and alpha testing
In progress12 of 58 complete21%
Releases
Now: Preview 10 · Day one: keys, the USB stick, one password, updates
1 point · 1 card · Nov 16 – Dec 13
Points finished so far, added up week by week (Monday to Sunday). A hollow dot is a week still running. No plan has been set for this release yet.
| Version | Name | Cards | Points |
|---|---|---|---|
| Preview 1 | First bootFeb 23 – Apr 5 | 11 | 35 |
| Preview 2 | Real programsJun 8 – Jun 21 | 3 | 13 |
| Preview 3 | Hardware, network and storageJun 29 – Jul 5 | 17 | 73 |
| Preview 4 | The Ring-3 desktopJul 6 – Jul 26 | 57 | 165 |
| Preview 5 | Linux apps and hardeningJul 27 – Sep 13 | 8 | 26 |
| Preview 6 | Sprint ladder and the groups desktopSep 14 – Sep 27 | 17 | 55 |
| Preview 7 | Security review and driver kitSep 28 – Oct 4 | 26 | 88 |
| Preview 8 | The WillowOS lookOct 5 – Oct 18 | 45 | 137 |
| Preview 9 | Solid foundationOct 19 – Nov 15 | 100 | 205 |
| Preview 10 | Day one: keys, the USB stick, one password, updatesNov 16 – Dec 13 · now | 1 | 1 |
| Preview 11 | Online on real laptops; Linux windowsDec 14 – Jan 10, 2027 | – | – |
| Preview 12 | Alpha: Secure Boot, the Windows installer, graphics, the browserdates to be announced | – | – |
| Preview 13 | Games and Windows appsdates to be announced | – | – |
| Preview 14 | Rewind, Leaf and living beside Windowsdates to be announced | – | – |
| Preview 15 | Everyday apps and the finished lookdates to be announced | – | – |
| Preview 16 | Store, Mail and Calendar, the screen reader in every appdates to be announced | – | – |
| Preview 17 | Widgets, Grove and a Leaf that actsdates to be announced | – | – |
| Preview 18 | Every core, every screen, private searchdates to be announced | – | – |
| Preview 19 | Any shape, never crash, instant ondates to be announced | – | – |
| 1.0 RC | Release candidatedates to be announced | – | – |
A card counts toward the release it was finished in. Points show size: small 1, medium 3, large 5. 1 finished card has no size yet and counts as 0 points.
Recently completed
- The Terminal and Files keep the names and paths you type out of their logs
- Program output can't fake the Terminal's prompt marks or turn off paste warnings
- Pasted and dropped file paths reach the Terminal's shell safely quoted
- An app that asks before closing can always be closed
- Typed keys and file names never reach the serial port
- Terminal: Ctrl+C stops a command even with text selected, paste reaches Find, and closing asks first
- Dragging a window to a corner never crashes the desktop
- A moved Terminal session's saved screen is read safely
- The dock grows with the text size
- Terminal: a command stopped with Ctrl+C reads Stopped, not Failed
Up next
- Release tagging and notes
- Release hardening checklist
Also planned
-
Grove social network
Planned0 of 12 complete0%
Grove isn't required for 1.0 and is tracked separately. Foundation counts the work finished before the sprint plan began on September 17, 2026, measured in sprint-sized pieces. Sprints vary in size, so the bar isn't a time estimate, and new sprints are added as testing turns up work.