Scouted · November 6, 2026
fast collaborative code editing
Zed is a venture-backed Rust GPU editor with a 93k-star head start and a non-permissive license; a solo dev cannot replicate or fork it into a paid product.
Why now?
Zed shows real GitHub momentum: 93,061 stars, 11,460 forks, 292 stars added today, and a recent push (2026-11-06). Built by the Atom/Tree-sitter creators in Rust on GPUI, its multiplayer framing fits current remote pair-programming workflows. But no HN, Reddit, download, or trends signals exist, so demand beyond GitHub is unproven.
The gap
The gap is around Zed, not a new editor: 3,027 open issues and a NOASSERTION license mean high adoption pressure but an ecosystem that is hard to extend commercially. The solo-dev opening is companion tooling — migration, config, collaboration setup — not a competing editor. Data does not support an underserved editor market.
Main competitor
VS Code is the named incumbent; Zed itself is what a solo dev would build around, and its NOASSERTION license blocks forking or wrapping it into a paid product.
Execution plan
- Scan Zed's 3,027 open issues and extension topics for one recurring pain point (VS Code migration, keybindings, collaboration setup).
- Build a small companion tool that does not fork Zed, and confirm the NOASSERTION license permits your use.
- Ship open-source with a hosted paid tier and post in Zed's discussions and Rust/editor communities to test conversion.
- Instrument installs, activation, and paid conversion from day one — the provided signals contain no download or revenue data.
- Expand scope only after repeat usage; avoid plans that redistribute or commercially wrap Zed's code.
Monetization
Sell a hosted team tier (per-seat subscription for config sync, onboarding, or collaboration setup) with the core open-source. The data shows GitHub attention only — no HN, Reddit, download, or revenue signals — so pricing and demand must be validated with real users, not projected.