erXos
a microkernel OS in Erlang based on Genera/Plan 9/QNX ideas
Get picks like this daily. Today's launch numbers, the top launches, AI and tech news, and a daily opportunity pick, straight to your inbox.
Want to reach these readers? Sponsor an issue.
What if every Erlang process were an operating-system process? With as much system code and drivers written in Erlang itself. This is something I was pondering for a while, and finally was able to prototype thanks to AI coding agents.erXos is a capability-based microkernel OS in Erlang: drivers, filesystems, and the network stack are all supervised Erlang processes, same as any app.The kernel itself is Fiasco, in C++, slightly modified for erXos needs. This is an OS I wanted for a long time: an Erlang machine where every BEAM process is a process visible to the OS and scheduler, not something bolted on top.You can try it right now with nothing to install: there is an emulator on the website that boots the whole OS in the browser ARM64 emulator. At the rc prompt, try `ps`, `top`, `ping` or `erl` and write any kind of erlang code. There's a Pi 4 SD image and a QEMU image too. The goal is to build an ultra-reliable microkernel OS with hot code loading and both system and BEAM-based isolation. The latter is one thing that would allow you to run millions of processes on the system, something that would be prohibitive on a microkernel alone due to the context switch overhead. Capabilities keep every component least-privileged, supervision keeps the machine running when drivers or subsystems crash, and hot code loading would let you fix a broken driver without reboot.The secondary goal is to keep as much of a UNIX face as possible. Too many novel OSes change things for no particular reason that makes them hard to use. erXos tries to preserve as many existing UNIX/FreeBSD concepts as much as possible to remove the learning curve.What works today:- Boots in the browser/v64, in QEMU, and on a Raspberry Pi 4 from an SD card- A real shell (plan9 rc) with job control, pipes, `ps`, `grep`. It feels like UNIX on the surface- Erlang versions of basic UNIX apps.- Drivers written in Erlang: UART, virtio, SD card, Ethernet (GENET), display- A pure Erlang EROFS filesystem for root images- A TCP/IP stack in Erlang based on FreeBSD network stack and verified for correctness against it- Domains: every app runs as its own address space or Erlang node, isolated from others- Plan 9 namespaces and 9P everywhere; windows are files like RIO and 9P is a file protocol between OS servers- Supervision end to end: if a driver fails, its supervisor resets the device and restarts itI also have 2 demo apps built on app sdk: a full-screen kiosk app with live crypto quotes and clock and, of course Doom, which ships on the Pi 4 card image (type `doom`).What's coming:- Raspberry Pi 5 support- Full display on the Pi- WIFI- Bluetooth- POSIX-lite for C programs, so existing code can run as a domain- Performance, debugging and tracing features.The code is all available under the BSD license.Would love to hear all and any feedback!
HN · launched Nov 19, 2026 · 7 upvotes (top 58%) · 0 views
Niche: experimental and embedded operating systems · 156 launches, 11 in the last 7 days ▼ -15% · Explore this niche →
Category and tags
- Horizontal
- Dev tools
- Developer
- Not AI
- Hobby / open-source project
Visit website ↗ Source listing ↗
More like this: all 156 launches in experimental and embedded operating systems →
Could you build this?
No An operating system with a capability-based microkernel, device drivers, and filesystems is systems programming at a deep level. Vibe coding can help prototype, but a real OS needs kernel, hardware, and security expertise that the builder would have to supply.
What it would actually take: Building a real version means a microkernel that enforces capabilities and isolation, plus drivers for real hardware, filesystems, networking, and a boot path. The Erlang layer sits on top of that kernel. The hard parts are correctness and security of the kernel, hardware enablement, and the performance of process-per-driver isolation. This requires experienced OS and low-level systems engineers, and testing on real hardware.
Discussion
3 comments analyzed.
Concerns raised: unclear whether any process can reach arbitrary sites, unclear protection against malware exfiltration and remote commands, unknown per-process or per-profile control
Feature requests: page showing how each malware type is prevented, per-site network access capabilities
Competitors
Other products that read as similar to this one : 199 launches clear the similarity bar, closest 8 shown.
Attention rank: #124 of 200 (itself plus its competitors, highest first, normalized so YC and Product Hunt are compared fairly).
Launched 383 days after the earliest competitor.
- Crazierl · hn · 2026-03-29 · 72 upvotes · similarity 0.60
- Anos · hn · 2026-04-04 · 115 upvotes · similarity 0.47
- Micron: a high performance C++23 (re)implementation of Libc and the STL · hn · 2026-06-05 · 6 upvotes · similarity 0.43
- win4wine · github · 2026-10-11 · 123 upvotes · similarity 0.42
- Our space game has a built-in RISC-V emulator that runs Linux · hn · 2026-10-02 · 94 upvotes · similarity 0.42
- ViFastOs · github · 2026-11-08 · 13 upvotes · similarity 0.40
- hyperlang · github · 2026-10-26 · 33 upvotes · similarity 0.40
- Microterm runs Linux VM in any browser tab via WASM, RISCV64 emulation · hn · 2026-02-22 · 6 upvotes · similarity 0.39
The niche, labels, vibe code rating and competitor comparison on this page are analysis by Nicheloom. If you use them, please credit nicheloom.com. How you may use our data.