A Rust kernel
The kernel manages memory, schedules work and controls access to devices. It establishes the boundaries between the machine and its applications.
Hardware & process isolationAn independent desktop operating system
A new view.
From the kernel up.
A Rust foundation. A JavaScript interface. CasementOS brings them together in a desktop operating system built from the ground up.
The desktop, taking shape
Actual capture · Running in QEMU
This capture shows the system running in a virtual machine. Physical bring-up has begun on two test machines, but it is not hardware qualification. View full resolution
Built as one system
From the machine
to the interface.
CasementOS runs its own kernel and desktop. JavaScript powers the interface directly, with no Linux, Node.js or browser underneath.
JavaScript, protected
QuickJS-ng runs JavaScript inside protected processes. Applications use explicitly granted capabilities to communicate with the system.
JavaScript in userspaceReact, rendered natively
A custom React renderer describes the interface. A native rasterizer draws its windows, text and controls directly to the display framebuffer.
UI without a browserHardwareRust kernelProtected JavaScriptDesktop
Development status
Working today.
Building toward tomorrow.
Progress is measured in running code and repeatable tests. Emulator results and physical hardware results are tracked separately.
Working in QEMU
A running desktop
- Rust kernel and protected JavaScript execution
- System UI shell and separate Clock app
- Persistent files and settings under
/home, with a Files text editor - DHCP configuration and network status (no application network access yet)
These are development capabilities, not a claim of complete hardware or application support.
Underway
Physical bring-up
- The desktop has been observed booting from a USB stick on an Intel NUC and a Dell Latitude (owner-reported bring-up, not qualification)
- Validating USB input, USB-stick documents, restart and shutdown, and the wired network path on the NUC
- Investigating laptop power-button and lid events, which do not work yet
- Designing a bounded document broker for a separate text editor, and staging HTTPS support; neither is available to applications yet
Physical results are early and partly unfiled. No hardware is qualified or supported.
Ahead
A system ready to use
- Qualified hardware drivers and device support, including USB hubs
- Application HTTPS and network access, a separate document editor, and display and audio qualification
- Installation, signed updates and recovery
- Long-running reliability and release testing
There is no public installer or announced release date.
Last updated
Development journal
Notes from the build.
Small milestones, what we learned, and what comes next.
A desktop running. Hardware bring-up begun.
CasementOS now boots into its own desktop in QEMU, with a System UI shell and Clock running in separate protected processes. Files and settings persist, and the desktop can report the network configuration supplied by DHCP.
Since then the desktop has also been observed on two physical machines, an Intel NUC and a Dell Latitude, booted from a USB stick. These are early bring-up observations, not qualification. The NUC is the machine for the next milestone, a reliable document workflow, and laptop power-button and lid events still need work. Qualifying devices and reliability will take further testing.
This site will follow that progress with actual captures and updates from development. The screenshot above is from the QEMU build.
A few early questions
Before you ask.
Can I install CasementOS today?
There is no public installer yet. CasementOS is an active development project, with most validation in QEMU and early physical bring-up under way.
What hardware is supported?
No hardware is qualified yet. The desktop has been observed on an Intel NUC and a Dell Latitude during bring-up, and the NUC is the reference machine for the next milestone. Device-specific and reliability testing must finish before a supported configuration is announced.
Does it run websites or existing desktop apps?
The JavaScript interface uses a custom native renderer, not a browser engine. Browser APIs and compatibility with existing Windows or Linux applications are not currently provided.
When will it be available?
No release date has been announced. Hardware qualification, installation, recovery and reliability testing still need to be completed before a release is ready. Progress will be shared here.