When a Large Company Forks an Open‑Source Project: The Spegel vs. Peerd Controversy

Philip Laine, a former Kubernetes engineer, created Spegel – a stateless, local OCI registry designed to cache container images on each node and improve pull performance for Kubernetes clusters. The project was released under the permissive MIT license to solve reliability issues caused by external image registries.

After Microsoft reached out expressing interest in collaborating, Laine engaged with a Microsoft engineer, helped deploy Spegel, and expected a formal partnership. However, at KubeCon the Spegel project was presented as a case study without Laine’s involvement, and Microsoft later released a new project called Peerd that incorporated Spegel’s code, examples, and even Laine’s personal comments.

Evidence showed large sections of identical source code, test cases, and documentation copied from Spegel into Peerd, with only a brief “inspired by” note in the README. The copied files lacked proper attribution, violating the spirit of the MIT license which requires preservation of original copyright notices.

This incident sparked a broader discussion about open‑source ethics, the power imbalance between individual maintainers and tech giants, and the adequacy of existing licenses to protect contributors. Laine highlighted how Microsoft’s brand influence can eclipse smaller projects, making it difficult for them to receive recognition.

Microsoft later responded publicly, acknowledging the missing attribution and submitting a pull request to add proper license headers to the affected files. The community’s reaction on platforms like Hacker News was mixed, with many questioning whether such corporate practices amount to exploitation.

Laine concluded that independent maintainers must consider alternative licensing models or stronger community safeguards to prevent similar situations, and he continues to develop Spegel while seeking sustainable funding through GitHub sponsorship.