Zed Drops AGPL to Unblock Enterprise Developers Banned From Using It
Zed drops AGPL from its core repo, replacing it with standard GPL to unblock enterprise and OSS adoption
Takeaways
- Zed has removed AGPL from its core repository, replacing it with standard GPL to ease enterprise and OSS adoption.
- AGPL's network-interaction clause required sharing source code for any network-accessible modifications, a common corporate blocker.
- Google and many large companies have blanket bans on AGPL software, making this change significant for enterprise adoption.
- The core editor remains free and open source (GPL-3.0); the GPUI framework stays Apache 2.0.
- Zed Pro is $10/month; the team is offering direct help getting Zed approved at companies via hi@zed.dev.
- The change follows Zed's 1.0 release, $32M Sequoia funding, and growing competition in the AI code editor space.
Zed, the GPU-accelerated, Rust-built code editor from the creators of Atom and Tree-sitter, just made a quiet but consequential licensing change: it has removed AGPL from its core repository and replaced it with standard GPL. The move is aimed squarely at unblocking developers who wanted to use Zed at work but kept running into a wall with their legal teams.
When Zed first went open source, the code was available under a copyleft license, with GPL covering the editor and AGPL covering server-side components. That split made sense philosophically, but it created a real-world adoption problem that the team has now decided to address head-on.
Why AGPL Was the Blocker
To understand why this matters, it helps to know what makes AGPL different from regular GPL. The AGPL builds upon the standard GPL by addressing software use over a network, requiring that any modified version accessed over a network be made available to users under the same license. That single clause is what gives corporate lawyers headaches.
The AGPL is notorious for its strict terms, which can be a deterrent for large companies. Google, for instance, has explicitly banned the use of AGPL software on its corporate servers due to concerns about the license's requirement for source code disclosure whenever the software interacts with a network, stemming from the risk of inadvertently exposing proprietary software.
Many companies find the AGPL's requirements restrictive, especially for proprietary business models, as the obligation to share modifications can conflict with their desire to keep proprietary innovations confidential. The problem is not always about actual legal risk -- perceptions of the difficulty of compliance or its risks can be as big a stumbling block as the actual risks themselves.
As one developer noted in Zed's own GitHub discussions, "AGPL-phobia" is common enough that giving people a non-AGPL option could unlock a nontrivial amount of new users. Zed has now acted on exactly that signal.
What Actually Changed
The change removes AGPL from the core repository and replaces it with GPL. The LICENSE-AGPL file still exists in the repo (as a historical artifact), but the governing license for the core codebase is now GPL-3.0. The three-license structure Zed launched with -- GPL for the editor, AGPL for server components, Apache 2.0 for the GPUI framework -- has been simplified to remove the AGPL piece from the main repo.
- Core editor: GPL-3.0 (unchanged from original)
- Server-side components: Moved from AGPL to GPL
- GPUI framework: Apache 2.0 (unchanged)
GPL still requires that modifications be shared when software is distributed, but it does not carry AGPL's network-interaction clause. While the GPL allows software to be used without sharing modifications if it's not distributed, the AGPL mandates that network-based interactions also require sharing modifications, effectively extending the copyleft requirement to SaaS environments. Dropping that clause is the key unlock for enterprise use.
The Bigger Picture for Zed
Zed reached a version 1.0 milestone and is making serious waves in the developer community. Built from scratch in Rust and GPU-accelerated, it is natively multiplayer. Independent tests show roughly a 0.6-second cold start and about 222 MB of idle memory, compared to multi-gigabyte footprints in Electron-based editors like VS Code.
The editor now supports parallel agents, the open-weight Zeta2 edit-prediction model, and a flexible runtime that plugs into Claude, GPT, Gemini, MCP servers, and external CLI agents like Claude Code, Codex, and OpenCode through the open Agent Client Protocol (ACP).
In 2025, the project announced they had received $32 million in funding from Sequoia Capital. With 1.0 shipped and a growing enterprise interest, the licensing friction was becoming a real growth ceiling. The AGPL removal is a direct response to that.
Who This Unblocks
The practical impact is clearest for a few specific groups:
- Enterprise developers at companies with blanket AGPL bans (like Google's well-known policy) who wanted to use Zed but couldn't get it approved.
- OSS contributors building tools or integrations on top of Zed's server components, who previously had to navigate AGPL compliance.
- Platform teams considering Zed for internal developer tooling, where AGPL's network clause created ambiguity about whether internal deployments triggered disclosure obligations.
Zed is free to use. The core editor is free and open source under the GPL-3.0 license, with a Pro plan at $10/month that adds hosted model credits and Zed's own completions. If you're trying to get Zed approved at your company, the team is actively offering to help -- they've opened a direct line at hi@zed.dev for exactly that.
This is a minor but strategically meaningful change. Zed is not relaxing its commitment to copyleft -- GPL still ensures that improvements flow back to the community. It's simply removing the one clause that was giving legal teams an easy reason to say no.