Former developers from Signal, working with researchers at Microsoft Research and Harvard University, have released Encrypted Spaces — an open-source platform for building collaborative applications where data stays encrypted and all operations can be verified using cryptography. A whitepaper titled "Encrypted Collaboration Spaces" was published on June 11, 2026, with the main project site launching the next day.

The central idea is simple to state but complex to execute: instead of encrypting data only while it moves between devices or sits on a server, Encrypted Spaces pushes encryption deeper — into the application layer itself. When collaborators make edits, grant access, or change shared state, these operations are not just recorded. They are structured so that any participant can independently verify that what happened actually happened, without needing to trust that the central server is telling the truth. The work sits under Microsoft Research's research umbrella, while the former Signal developers bring real-world experience shipping encrypted collaboration at consumer scale.

What Problem Does It Solve?

Today's collaborative software — shared documents, team workspaces, project management tools — relies on a central server that everyone trusts. That server sees the unencrypted data, resolves conflicts between simultaneous edits, and decides who can access what. It works operationally, but it creates a weak point: if the server is compromised, breached, or compelled by authorities, everything inside it is exposed. Encrypted Spaces aims to eliminate that vulnerability. Because operations are cryptographically verifiable, participants can check what happened in a shared space on their own terms, without accepting the platform operator's version of events.

This problem is not new. Researchers have explored secure multi-party computation (systems where multiple parties can calculate something together without revealing their individual inputs), verifiable secret sharing (ways to split a secret so that no single person can reconstruct it alone), and encrypted group protocols. What Encrypted Spaces attempts to do differently — at least based on the published whitepaper — is assemble these existing cryptographic building blocks into a coherent, usable architecture that applications can be built on top of, not just a research demonstration. The open-source release signals that the team believes it is ready for external review and real-world use.

The Signal connection matters. The Signal Protocol became the industry standard for encrypted messaging not because it was the first strong proposal, but because it was engineered for actual deployment: low latency, practical key management, and properties that held up in messy real-world conditions with real users. The key question practitioners will ask of Encrypted Spaces is whether it meets the same standard — whether the cryptographic promises hold under attack without making developers' lives miserable.

The Team and What Comes Next

The collaboration structure is worth noting. Microsoft Research brings institutional resources and a track record in applied cryptography; Harvard contributes academic credibility and presumably access to peer review and graduate researchers. The Signal alumni bring engineering discipline and practical deployment experience, which academic cryptography projects often lack. That combination is rare enough to merit attention from anyone building privacy-sensitive collaborative tools.

The project is currently at the whitepaper-and-launch stage. The cryptographic claims in the paper will require independent verification by security researchers, and the distance between a well-designed architecture and a production-ready software library is often large. History shows many cryptographically sound systems that turned out to have exploitable weaknesses once real engineers built implementations, or that imposed so much computational overhead that few people adopted them. The open-source release is an invitation for exactly this kind of adversarial testing, which should happen next.

For security leaders and developers in regulated industries — healthcare, law, finance, government — the underlying problem is real and expensive. Over the past decade, federated identity management and zero-trust network architecture have reduced how much you need to trust a central server. But cryptographic integrity for collaborative applications has largely remained unsolved outside narrow cases like signed software supply chains or blockchain systems. If Encrypted Spaces delivers on its design, it would extend cryptographic verification into collaborative workflows across many industries.

You can find the project's homepage, the whitepaper, and details about the collaborators at encryptedspaces.org. The source code is available for inspection and contribution — that is where the real technical assessment will happen.