wouldit.work

Developer tools

Zed: a $32M bet on collaboration beyond code snapshots

Zed raised a company-reported $32M Series B for a fast editor and continuous collaboration. Investor-reported usage is traction, not proof of profitability.

Product
Zed
Founder
Nathan Sobo, Antonio Scandurra and Max Brunsfeld
Launched
n/a
Model
Open-source editor with optional paid services

Published · 2 min read · 2 sources

Key takeaways

  • Zed announced a $32M Series B in August 2025, bringing funding above $42M, according to the company.
  • Its lead investor reported 150,000 monthly active developers at that time; that is not a paid-customer count.
  • The next bet was operation-level version control and durable conversations tied to changing code.

What it is

Zed is a code editor built from scratch in Rust. Its founders Nathan Sobo, Antonio Scandurra and Max Brunsfeld previously worked on Atom, according to lead investor Sequoia (Investor account).

Timeline

  • By August 2025: Nathan Sobo said the team had spent four years building its editor foundation (Company announcement).
  • 20 August 2025: Zed announced a $32M Series B led by Sequoia, taking total funding above $42M. These are company-reported financing figures (Company announcement).
  • The same announcement: Zed described DeltaDB, operation-level version control designed to interoperate with Git and preserve discussions alongside evolving code (Company announcement).
  • At the round: Sequoia reported 150,000 monthly active developers. This is an investor-reported adoption figure, not revenue or paid conversion (Investor account).

Why it worked

  • A distinct technical bet. Rather than another VS Code fork, Zed rebuilt the editor for performance and collaboration. Sequoia presents that architecture as a core differentiator; it is an investor thesis, not our benchmark result (Investor account).
  • A clear pain beyond autocomplete. Zed argues that chat and review comments lose context as code changes. Its proposed durable links aim to preserve the reasoning behind edits (Company announcement).
  • Human collaboration became relevant to agents too. The company applies its continuous-collaboration thesis to rapid iteration with AI assistants (Company announcement).

What to learn

  1. Name the workflow failure your architecture fixes, rather than treating a rewrite as a customer benefit by itself.
  2. Distinguish active users, paying users, financing and profit in every traction claim.
  3. Show what survives as the code changes. Compare Windsurf and Conductor for different AI-development workflows.

Risks and what didn't work

  • The company announcement describes an ambitious roadmap, not a completed proof that operation-level history will become the default workflow (Company announcement).
  • Sequoia has a financial interest in the company. Its adoption figures and product praise are not independent validation (Investor account).
  • No profitability, ARR or paid-conversion evidence is established by these sources. Raising capital is a financing outcome, not the same as a sustainable business.

FAQ

Short answers drawn from the sections above.

What is Zed?

Zed is a code editor built from scratch in Rust. Its founders Nathan Sobo, Antonio Scandurra and Max Brunsfeld previously worked on Atom, according to lead investor Sequoia (Investor account).

Why did Zed work?

  • A distinct technical bet. Rather than another VS Code fork, Zed rebuilt the editor for performance and collaboration. Sequoia presents that architecture as a core differentiator; it is an investor thesis, not our benchmark result (Investor account).
  • A clear pain beyond autocomplete. Zed argues that chat and review comments lose context as code changes. Its proposed durable links aim to preserve the reasoning behind edits (Company announcement).
  • Human collaboration became relevant to agents too. The company applies its continuous-collaboration thesis to rapid iteration with AI assistants (Company announcement).

What can indie builders learn from Zed?

  1. Name the workflow failure your architecture fixes, rather than treating a rewrite as a customer benefit by itself.
  2. Distinguish active users, paying users, financing and profit in every traction claim.
  3. Show what survives as the code changes. Compare Windsurf and Conductor for different AI-development workflows.

What didn't work for Zed, and what are the risks?

  • The company announcement describes an ambitious roadmap, not a completed proof that operation-level history will become the default workflow (Company announcement).
  • Sequoia has a financial interest in the company. Its adoption figures and product praise are not independent validation (Investor account).
  • No profitability, ARR or paid-conversion evidence is established by these sources. Raising capital is a financing outcome, not the same as a sustainable business.

Sources

Every link cited above, in order of first use.

  1. 1.Investor account (sequoiacap.com)
  2. 2.Company announcement (zed.dev)

Related case studies

More in Developer tools →