news / 18 Aug 2026 / 2 min read
Windsurf is gone from the index
windsurf.com now redirects to devin.ai/desktop. The product is discontinued, so it has been removed from the roster, the raw runs, every leaderboard, every compare pair and the matrix, not just flagged as inactive.
By Daniel Osei | Updated 19 Aug 2026
What we found
On a routine check ahead of this cycle's publication, windsurf.com returned a 301 redirect to devin.ai/desktop rather than the product's own marketing page. That is a discontinuation signal, not a rebrand: the destination is a different company's product page, not a Windsurf page under a new name.
What we did about it
We do not keep a dead product in a live index with a note attached. A benchmark that still shows a ranked row for something nobody can sign up for is worse than useless, it is actively misleading to anyone comparing options today. So Windsurf has been removed completely.
That removal touched more than one table. Its row is gone from the roster. Every one of its recorded run executions is gone from the raw runs export. It no longer appears on the app builder leaderboard, on any of the six axis leaderboards, in the comparison matrix, or in any curated compare pair. The two compare pages that featured it no longer resolve, rather than resolving to a page about a product that is not there.
Why we do not just mark products inactive
We considered a softer approach, a status flag and a greyed out row. We rejected it. The moment a product cannot be measured going forward, its historical numbers stop being a live comparison and start being an epitaph, and an epitaph does not belong in a ranked table next to products you can still evaluate and buy today. If you need the historical figures for a research purpose, write to the lab address on the contact page and we can provide the archived rows outside the public index.
What this means for the roster count
The cohort now stands at the products that remain live and evaluable. Every count on the site, from the about page to the data page to the sitemap, reflects the roster after this removal, not before it. We check every dependency at removal time precisely so a stale count never survives a roster change.