Share on Facebook Tweet on Twitter Share on LinkedIn Share by email

OS and tools for building dependable systems. The Singularity research codebase and design evolved to become the Midori advanced-development OS project. While never reaching commercial release, at one time Midori powered all of Microsoft's natural language search service for the West Coast and Asia.

" is impossible to predict how a singularity will affect objects in its causal future." - NCSA Cyberia Glossary

What's New?

The Singularity Research Development Kit (RDK) 2.0 is now available for academic non-commercial use. You can download it from CodePlex, Microsoft's open source project hosting website, here.

Our recent article in Operating Systems Review, Singularity: Rethinking the Software Stack, is a concise introduction to the Singularity project. It summarizes research in the current Singularity releases and highlights ongoing Singularity research.


Singularity is a research project focused on the construction of dependable systems through innovation in the areas of systems, languages, and tools. We are building a research operating system prototype (called Singularity), extending programming languages, and developing new techniques and tools for specifying and verifying program behavior.

Advances in languages, compilers, and tools open the possibility of significantly improving software. For example, Singularity uses type-safe languages and an abstract instruction set to enable what we call Software Isolated Processes (SIPs). SIPs provide the strong isolation guarantees of OS processes (isolated object space, separate GCs, separate runtimes) without the overhead of hardware-enforced protection domains. In the current Singularity prototype SIPs are extremely cheap; they run in ring 0 in the kernel’s address space.

Singularity uses these advances to build more reliable systems and applications. For example, because SIPs are so cheap to create and enforce, Singularity runs each program, device driver, or system extension in its own SIP. SIPs are not allowed to share memory or modify their own code. As a result, we can make strong reliability guarantees about the code running in a SIP. We can verify much broader properties about a SIP at compile or install time than can be done for code running in traditional OS processes. Broader application of static verification is critical to predicting system behavior and providing users with strong guarantees about reliability.



Project Members


Galen Hunt
Jim Larus


Mark Aiken
Paul Barham
Richard Black
Trishul Chilimbi
Chris Hawblitzel
John DeTreville
Ulfar Erlingsson
Manuel Fähndrich
Wolfgang Grieskamp
Tim Harris
Orion Hodson
Rebecca Isaacs
Mike Jones
Steven Levi
Roy Levin
Nick Murphy
Dushyanth Narayanan
Sriram Rajamani
Jakob Rehof
Wolfram Schulte
Dan Simon
Bjarne Steensgaard
David Tarditi
Ted Wobber
Brian Zill
Ben Zorn