We said MAYBE on August 3, 2026. Not settled — due August 3, 2027.
Read this with the caveat. We tested the engine that produced this verdict against 292 launches whose outcomes we already knew, and could not show it predicted which survived. Some of its data sources were also dead at the time of scoring. The verdict stays up, dated and unedited, because a record you can quietly revise is not a record — but it is worth less than it looked when it was written.
Demand is genuine and multi-channel—growing keywords, engaged threads, and four paying competitors prove people pay to understand codebases. But this is a battlefield of well-capitalized giants moving fast, and the wedge requires heavy infrastructure engineering; a solo founder can carve a narrow niche but faces real structural pressure, making this a cautious SKIP unless the founder commits hard to the underserved legacy/offline segment.
Multiple channels agree: growing search demand with commercial-intent keywords, active Reddit/HN threads about understanding codebases, and at least four products already charging money in this space.
The identified wedges (affordable persistent indexing, doc generation, offline) are real but the incumbents are heavily-funded giants (Cursor, Augment, ChatGPT/Claude) iterating fast, and the core engineering—polyglot parsing, embeddings, vector indexing, persistent memory—is exactly the expensive part a solo dev must build to compete.
The axes lean SKIP, but the strongest case FOR building: the giants are all racing toward the general 'AI code editor' use case and explicitly leave affordable, offline, persistent-index, auto-documentation for legacy/polyglot codebases underserved—a solo dev could win a narrow, unsexy niche (security-conscious small teams, legacy shops) that Cursor and Augment will never prioritize.
What is worth more than this page. The register records what became of 6,266 real launches. No engine has to be right for that to be true.