The creator of Spegel says Microsoft built a forked version of his peer-to-peer container image distribution project, Peerd, in a way that copied code and test cases closely enough to create confusion about where the work came from. The supplied Philip Laine post frames the episode as a personal and professional blow for a solo open-source maintainer who had hoped for collaboration.
The account begins with the original problem Spegel tried to solve: Kubernetes clusters that needed to keep scaling even when image registries were unavailable. The author says the idea emerged after a Black Friday traffic surge collided with a GitHub container registry outage, leaving clusters unable to fetch critical images. He built Spegel as a stateful-mirror alternative that aimed to reduce operational overhead.
Microsoft later reached out to discuss Spegel, according to the post. The maintainer says he helped engineers get the project running and answered architecture questions, expecting the conversation might lead to contributions or new maintainers. Instead, he later saw Peerd discussed in a KubeCon Paris talk and found a Microsoft project positioned as a peer-to-peer image distribution solution. At the bottom of Peerd's README, he says, there was a thank-you to him and to Spegel.
What disturbed him most was not just the similarity of the broader idea but the apparent reuse of implementation details. He says function signatures and comments looked familiar and that test cases referenced Spegel and a previous employer. The supplied excerpt says some of those references remained visible. The author therefore argues that Microsoft took inspiration from his project and then developed a version of its own under Microsoft's MIT license.
The licensing issue is central. The post notes that Spegel itself was published under MIT, which permits forking and modification without requiring contributions upstream. But the author argues that the license does not permit removing the original attribution and presenting the work as though it were created elsewhere. That distinction turns this from a normal open-source fork into a dispute about provenance and credit.
The practical effect, he says, has been confusion among users. Newcomers ask about the differences between Spegel and Peerd, and the maintainer says that as a community contributor he wants to remain factual and unbiased, even while feeling that a much larger company has taken up space next to a project he built from scratch. He says the experience made him question whether continuing Spegel was worth the effort.
The post concludes that he persisted and that Spegel still has traction, with more than 1.7k stars and 14.4 million pulls at the time of writing. He has also enabled GitHub Sponsors and is considering a license change. The reporting does not include Microsoft’s response, so the account stands as the maintainer's own version of what happened. Still, it captures a recurring open-source tension: permissive licensing allows reuse, but attribution and community trust remain critical when a large vendor enters the same technical space.
The episode also highlights the reputational asymmetry that often shapes open-source disputes. A solo maintainer can spend years earning trust around a project, while a large vendor can enter the same space with far more visibility and distribution power. The author says that imbalance made it harder for Spegel to stand out even before users began asking whether the Microsoft project and his own work were related.
