Somewhere between nostalgia and defiance sits a small but determined project that most of the tech industry has never heard of. VitruvianOS — sometimes styled V-OS — is an independent, open-source operating system being built from the ground up, drawing deep inspiration from BeOS, the legendary multimedia operating system that briefly threatened Windows in the late 1990s before Palm Inc. acquired Be Inc. and let it die.
The project is led by Dario Casalinuovo, an Italian developer whose résumé reads like a love letter to alternative operating systems. He’s spent years contributing to Haiku, the most prominent open-source successor to BeOS, before deciding that a more radical path was necessary. His ambition with VitruvianOS isn’t to clone BeOS. It’s to take the design philosophy that made BeOS extraordinary — pervasive multithreading, a responsive media-centric architecture, elegant simplicity — and rebuild it for the modern era with no legacy constraints.
That’s either visionary or quixotic, depending on your tolerance for long odds.
From Haiku’s Orbit to a Clean-Sheet Design
In a detailed interview published by Desktop on Fire, Casalinuovo laid out his reasoning for leaving the Haiku project and starting fresh. His critique of Haiku is respectful but blunt: the project, he argues, has become too focused on binary and source compatibility with the original BeOS, which forces it to carry forward architectural decisions made in the mid-1990s. Some of those decisions were brilliant for their time but are now liabilities — particularly around security, modern hardware support, and the ability to attract new developers who have no emotional connection to BeOS.
“I think that the BeOS API is one of the best ever designed,” Casalinuovo told Desktop on Fire, but he was equally clear that preserving it in amber isn’t the way forward. VitruvianOS aims to take the core principles — the object-oriented C++ API design, the messaging architecture, the tight integration between the media framework and the kernel — and reimplement them without being handcuffed to 1990s-era binary compatibility.
This is a meaningful philosophical split. Haiku has spent over two decades painstakingly recreating BeOS R5 compatibility, and that effort has produced a working, usable desktop OS that can run original BeOS applications. For the BeOS faithful, that’s the entire point. For Casalinuovo, it’s a trap.
The VitruvianOS project page describes the effort as building “a new operating system inspired by the BeOS architecture and philosophy.” The name itself — a reference to Leonardo da Vinci’s Vitruvian Man — signals an aspiration toward ideal proportions and balance in system design. The project’s scope is enormous: a custom kernel, a new API framework, a graphics stack, a media kit, device drivers, and eventually a full desktop environment.
All of it from scratch. With a tiny team.
Operating system development is among the most demanding work in all of software engineering. The history of computing is littered with ambitious OS projects that never shipped — or shipped and were immediately forgotten. Even well-funded corporate efforts routinely fail. Microsoft spent billions on Longhorn before scrapping most of it. Google’s Fuchsia, despite enormous resources, has yet to become a mainstream product. The idea that a small open-source project could produce a viable desktop OS seems almost absurd.
And yet.
BeOS itself was built by a small team. Jean-Louis Gassée’s Be Inc. never had more than a few dozen engineers, and they produced an operating system that, in many respects, was technically superior to anything Microsoft or Apple offered at the time. BeOS could play multiple video streams simultaneously on hardware that choked running a single video under Windows 95. Its file system, BFS, supported metadata attributes that anticipated features other operating systems wouldn’t adopt for years. The responsiveness of the UI under heavy load was — and in some ways still is — unmatched.
That legacy is what keeps people like Casalinuovo working on nights and weekends.
According to the main VitruvianOS site, the project is still in early stages. There’s no downloadable ISO yet. The work is happening in public repositories, and progress updates appear periodically. The project uses a microkernel-influenced design, though the exact kernel architecture is still evolving. Casalinuovo has indicated that the system will be POSIX-compatible to some degree, which would ease the porting of existing Unix and Linux software — a practical concession that pure BeOS philosophy might not have demanded but modern usability requires.
Why Desktop Operating Systems Still Matter
The conventional wisdom in Silicon Valley is that the desktop OS wars ended years ago. Windows dominates enterprise desktops. macOS owns the creative professional market. Linux runs servers and, increasingly, developer workstations. Chrome OS carved out a niche in education. Everything else is a rounding error.
But this framing misses something. The desktop OS market is stagnant precisely because there’s been so little genuine innovation. Windows 11 is, architecturally, still recognizable as a descendant of Windows NT from 1993. macOS carries forward design decisions from NeXTSTEP. Linux desktop environments like GNOME and KDE are sophisticated, but they’re built on top of a kernel and userspace stack designed primarily for servers, not desktop interactivity.
Nobody has seriously attempted to rethink the desktop from first principles in decades.
That’s the gap VitruvianOS is trying to fill. Whether it can actually fill it is another question entirely. The barriers aren’t just technical — they’re commercial. Hardware vendors don’t write drivers for niche operating systems. Application developers don’t port their software to platforms with a few hundred users. Users don’t switch to operating systems that can’t run their applications or support their hardware. It’s a vicious cycle that has killed every alternative desktop OS that wasn’t backed by a major corporation.
Casalinuovo appears to understand this. In his Desktop on Fire interview, he discussed the importance of making VitruvianOS accessible to developers who don’t have BeOS experience. The API needs to be clean, well-documented, and appealing on its own merits — not just as a tribute to a dead platform. He also emphasized the need for modern security features, something BeOS essentially lacked and Haiku has been slow to add.
There’s a broader context here too. The open-source world has seen renewed interest in alternative operating systems in recent years. Redox OS, written in Rust, is exploring memory-safe kernel design. SerenityOS, created by Andreas Kling, attracted a passionate community before Kling shifted focus to the Ladybird web browser project. RISC-V is creating new hardware platforms that aren’t locked into existing OS monopolies. The idea that the operating system is a solved problem is being challenged from multiple directions.
VitruvianOS fits into this broader movement, but its BeOS lineage gives it a distinctive character. Where Redox is primarily a systems programming experiment and SerenityOS was partly a retro-computing exercise, VitruvianOS is explicitly trying to build something you’d want to use as your daily driver. Eventually.
The “eventually” is doing a lot of heavy lifting in that sentence.
Right now, the project needs contributors. Kernel developers. Graphics programmers. People who understand audio and video pipelines. Technical writers. Testers. The project website makes it clear that help is welcome, and the codebase is open for anyone to examine and contribute to.
The Long Bet on Taste
What makes VitruvianOS interesting isn’t its current state — which is embryonic — but the bet it represents. Casalinuovo is wagering that the design sensibility behind BeOS wasn’t a product of its time but a genuinely better way to build a personal computer operating system. That pervasive multithreading, clean object-oriented APIs, and a system designed around media from the kernel up would still be superior to the layered, backward-compatible, compromise-laden architectures that dominate today.
It’s a bet on taste. On the idea that elegance in system design matters, that it produces measurably better user experiences, and that a small team making uncompromising choices can produce something that a large corporation optimizing for quarterly earnings never would.
BeOS proved that thesis once. Whether VitruvianOS can prove it again — in a world with far more competition, far higher user expectations, and far less patience for incomplete software — remains to be seen. But the attempt itself is worth watching. In an industry that has largely given up on rethinking the desktop, someone is still trying.
And sometimes, that’s how the interesting things start.
WebProNews is an iEntry Publication