Project updates, architecture notes, and milestones.
Status updates from Open Nexus — what shipped in the NEURON microkernel, the Rust userspace and the RISC-V desktop, and what is coming next.
View All Tags
In June, we ended with a promise: the screen is on — now we teach it to think.
Our own language. A shell. A launcher that feels like home.
Six weeks later, all three exist. And a few things we didn't promise, because we didn't yet know we'd need them.
In March, we showed you a kernel that could explain itself.
Today, it can show itself.
Three months ago, NEURON was an argument. A set of papers. A microkernel you could measure, but not see. There was nothing on the screen — because there was no screen.
At first, an OS feels like progress.
Things compile. Services start.
You can point at features and say, “Look—momentum.”
Then the truth shows up:
Most “working” systems are simply lucky systems.
They work until contention shows up. Until timing shifts. Until a second core enters the room.
So we changed the objective.
Not “add more features.”
Not “move faster.”
Replace luck with proof.
When I first started Open Nexus, I took the pragmatic path:
build on Redox's proven microkernel, focus on the UI layer, ship faster.
It worked. We had a login screen, a launcher, a control center.
The foundation felt solid. Redox was Rust-native, microkernel-based, open source.
What could go wrong?
When we first introduced Open Nexus, it was only an idea — an alternative to fragmented ecosystems, built on Rust and a Redox microkernel.
Today, that idea has taken shape. The foundation of the project is no longer abstract; it is code, libraries, and a working environment.