Loophole Labs Archives Their Open Source Projects
Loophole Labs is a small startup doing interesting work on Kubernetes live migration. While researching their technology, I noticed something: their open source projects were recently archived. Here's what I found, and what it might mean.
What We Know (Public Facts)
Loophole Labs is a New York-based startup founded in 2019 by Shivansh Vij. They've raised $13.4M from investors including Cervin Ventures, Materialized View Capital, Deep Acre, and Haystack.
Their GitHub organization hosted several open source projects:
- Drafter - A compute primitive for live migration, licensed AGPL-3.0, archived October 15, 2025
- Silo - A storage primitive for data migration, licensed AGPL-3.0, archived September 30, 2025
- Scale - A WebAssembly plugin framework, licensed Apache-2.0, 632 stars, archived October 17, 2025
Their commercial product, Architect, hibernates Kubernetes workloads and wakes them instantly. It's currently in early access with a waitlist.
The Timeline (Verifiable Dates)
From GitHub release history and API data:
- June 18, 2024 - Last Scale release (v0.4.8)
- January 8, 2025 - HN post announcing Architect, stating "all core components are open source"
- June 1, 2025 - Investment from Materialized View Capital (per PitchBook)
- July 23, 2025 - Last Drafter release (v0.7.4)
- August 7, 2025 - Last Silo release (v0.2.21)
- September 30, 2025 - Silo repository archived
- October 15, 2025 - Drafter repository archived
- October 17, 2025 - Scale repository archived
The archived repositories contain no announcement, issue, or README update explaining the archival. The GitHub issues are dependency bumps from Dependabot.
What We Didn't Find
I searched for public discussion about the archival:
- No blog post on loopholelabs.io explaining the change
- No GitHub issue or discussion about deprecation
- No Hacker News thread discussing the archival
- No Twitter/X or Bluesky posts about it
- No Reddit discussion
The Open Source Startup Podcast (Episode 97) featured Loophole Labs, but no transcript is available to check if they discussed licensing strategy.
What We Can Infer (Speculation)
A product focus shift. Scale (WebAssembly) went quiet in mid-2024. The team appears to have concentrated on Kubernetes live migration instead. This is a common startup pivot - finding product-market fit often means narrowing scope.
A licensing strategy change. The AGPL-3.0 license on Drafter and Silo was unusual for a VC-backed company. AGPL requires network users to release modifications, which makes cloud providers reluctant to adopt it. The archival might reflect a decision to keep future development proprietary.
Funding timing is suggestive but not conclusive. The June 2025 investment from Materialized View Capital occurred between the January "open source" messaging and the September-October archival. New funding often comes with strategic discussions, but we can't know what those conversations contained.
The Technology Is Real
Whatever the business decisions, the technical work is impressive. Drafter used Linux USERFAULTFD for memory tracking, Firecracker for microVM isolation, and custom PVM patches for nested virtualization. The team demonstrated live migration of Redis pods between AWS, GCP, and Azure at KubeCon NA 2024.
The AGPL code remains available for forking. Someone motivated could continue development independently.
Context: This Happens
Open source projects from VC-backed startups sometimes get archived. HashiCorp relicensed Terraform. Elastic changed Elasticsearch's license. Redis moved to dual licensing. The dynamics between venture capital, open source sustainability, and commercialization are genuinely difficult.
Loophole Labs isn't unusual in facing these tensions. What's notable here is the absence of public communication about the change.
Questions We Can't Answer
- Was the archival planned from the start, or a recent decision?
- Did investor pressure influence the timing?
- Will any of the code be maintained or relicensed?
- Is Architect built on the same codebase, or a rewrite?
Without statements from Loophole Labs, these remain open questions.
What This Means for Users
If you were considering building on Drafter or Silo:
- The code is archived but still accessible under AGPL-3.0
- No security updates or bug fixes will come from Loophole Labs
- You could fork and maintain it yourself
- The commercial Architect product may offer similar capabilities
If you're evaluating open source infrastructure from any VC-backed startup, this is a reminder that licenses describe current state, not future commitment. Maintainership can change.