WillItSurvive

Cypress.io

Cypress.io makes a JavaScript framework and cloud platform for testing web apps end to end.

Losing its protection
Assessed 24 July 2026 · Evidence as of 24 July 2026
The structural protection is eroding.
On the recordSince 24 July 2026 · Checkable from Q4 2026 · Every call on the record Checkpoint: State of JS 2026 survey results on framework satisfaction and usage
The call

Cypress survives on existing enterprise workflows while Playwright, free and Microsoft-backed, keeps pulling ahead in downloads and developer sentiment.

Cypress builds tools that help developers test websites and apps automatically. It was once popular, but Microsoft released a free competitor called Playwright that works better and is easier to get started with, and more developers are switching to it. Cypress has tried adding new features like AI-powered test writing and cloud analytics to stay relevant, but these haven't stopped the slide in users or brought in new money. The company could turn things around if it either secures fresh investment and grows again, or if developers start preferring Cypress over Playwright enough to close the gap in satisfaction scores.

Why
01
AI pressure: AI coding agents (Copilot, Cursor) that default to writing Playwright test scripts. AI agents increasingly generate Playwright tests by default, and Cypress's own AI bets like cy.prompt have not reversed that pull. Could AI do the core job? Only partly.
02
Bigger players: Microsoft (Playwright). Playwright is free, backed by Microsoft, and has already passed Cypress in downloads and developer satisfaction. Could a giant copy it? Yes, easily.
03
What protects it. Existing customers built CI pipelines and dashboards around Cypress Cloud and Test Replay, and switching costs slow departures.
What would change this call
Cypress announces a new priced funding round breaking its silence since Dec 2020. Would show investors still believe in a turnaround despite share losses.
State of JS 2026 survey results on framework satisfaction and usage share. Would show whether the Playwright gap keeps widening or Cypress stabilizes.
Cypress headcount trend over the next two quarterly filings/profiles. Would show whether cost-cutting continues or the break-even mandate has stabilized staffing.
Key numbers
  • Headcount fell from 121 to 94 employees (2026-06-30)
  • No priced funding round since $40M Series B (2026-06-30)
  • Playwright npm downloads passed Cypress mid-2024 (2026-04-15)
Named risks
  • No priced funding round since December 2020, over five years of financing silence. Severity: high
  • Sustained download and satisfaction share loss to Microsoft-backed Playwright through mid-2026. Severity: high
  • Headcount decline from about 121 (2023) to roughly 94-101 (2026) amid break-even mandate. Severity: medium
  • Revenue estimates conflict widely ($6.7M to $17.8M+), indicating low financial transparency. Severity: medium
  • LLM pipelines already generate Cypress-compatible test scripts, threatening core authoring workflow. Severity: medium
Rivals, as read in July 2026
RivalDirectionEvidence
Playwright (Microsoft)losing toOvertook Cypress in npm downloads by mid-2024; 94% vs 57% satisfaction gap as of June 2026
Microsoft (Playwright distribution via VS Code, GitHub, Azure DevOps)losing toFree tool bundled into Microsoft dev ecosystem, no structural barrier, as of June 2026
SeleniumcontestingLegacy incumbent holding roughly 22% of automation-testing market as of June 2026
Katalon StudiocontestingSimilar-scale commercial testing platform, estimated ~$60.5M revenue vs Cypress's disputed estimates, 2026-07-06
Questions people ask
Is Cypress.io profitable in 2026?
Cypress.io is targeting break-even rather than reporting confirmed profit. It cut 11 roles on June 13, 2024 under an explicit cash-flow break-even mandate, and headcount kept falling toward roughly 94-101 employees by mid-2026, per BuiltIn and Crustdata data.
Could AI replace Cypress.io's testing tools?
Academic pipelines (arXiv, 2025) already generate executable Cypress scripts from user stories via LLMs, threatening test authoring. Cypress itself responded by shipping cy.prompt(), Studio AI, and Cloud MCP (GA May 20, 2026) to keep users inside its platform rather than losing them to generic AI coding agents.
Is Cypress.io losing to Playwright?
Yes. Playwright, backed by Microsoft, overtook Cypress in npm downloads by mid-2024, and the State of JS 2025 survey shows roughly 94% satisfaction for Playwright versus about 57% for Cypress as of June 2026, with no reversal despite Cypress's new AI features.
Who owns Cypress.io?
Cypress.io is a privately held, venture-backed company, not publicly traded. It raised a $40M Series B in December 2020 led by OpenView Venture Partners with Bessemer, Battery, Sapphire, Stripes, and Las Olas participating; no priced round has followed since.
Has Cypress.io raised any funding recently?
No. Cypress.io's last disclosed priced funding round was a $40M Series B closed in December 2020. As of mid-2026, over five years have passed with no new round announced, per PRNewswire and Latka data.
Did John Deere acquire Cypress.io?
No. A blog post claiming Cypress.io was being acquired by John Deere was published March 31, 2025, in the style of an April Fool's joke, and no press release, filing, or credible news source has ever corroborated it.
Timeline
  • 2026-05-20Cloud MCP reaches general availability on all Cypress Cloud plans
  • 2026-04-15Reports confirm Playwright npm downloads overtook Cypress since mid-2024
  • 2026-04-03Test Replay canvas support released for canvas-rendered UI debugging
  • 2024-06-13Cypress.io cuts 11 roles under cash-flow break-even mandate
  • 2023-09-14Cypress 13 launches with Test Replay, the platform's signature feature
  • 2023-01Layoffs occur as part of broader restructuring
  • 2020-12-16Cypress.io raises $40M Series B led by OpenView Venture Partners
  • 2019-06-19Cypress.io raises $9.3M Series A led by Bessemer Venture Partners
Revision history
24 July 2026
First assessed. Losing its protection. The text above is fixed as of this date and is not edited afterwards.
In the same band
Sources