We may earn a commission if you buy through links on this page. It never changes a score or a ranking. How we make money
The bottom line
Strong browser-focused testing; check the annual bill, usage caps, and framework fit before switching.
Cypress covers end-to-end, component, and API testing, with Studio AI test generation, CI failure replay, and Smart Orchestration. The Starter plan is free for 10 users, but caps usage at 500 test results and 100 prompt executions per month, with 30-day data retention. Team is $799 per year, displayed as $67 per month, and includes 120,000 test results per year and 90-day retention. Separate monthly rates are not published.
Cypress is a more specialized option than Selenium, according to commenters comparing the tools: some describe it as a fit for browser-based, single-user E2E and component testing, while citing Selenium's broader language and platform coverage. One Reddit commenter said their company switched from Cypress to Playwright; that is a single report, not proof of a wider trend. We found no support details in the published sources, so that score is neutral.
Good fit if
- Teams focused on browser-based testing
- Frontend teams owning E2E tests
- Teams that need CI failure replay
Skip it if
- Teams needing broad language coverage
- Heavy users who may exceed plan caps
- Buyers requiring published monthly rates

ScoresHow it rates
What works
- Supports end-to-end, component, and API testing
- Runs tests in a real browser
- Studio AI records clicks into editable tests
- Failure replay includes DOM, network, and console data
- Smart Orchestration prioritizes and reruns tests
What doesn't
- Team and Business have no published monthly rates
- Starter caps results at 500 per month
- Starter includes only 100 prompt executions monthly
- UI Coverage and Accessibility add-on prices are unpublished
- Some Reddit commenters cite narrower language and platform coverage than Selenium
01What Cypress actually does
Cypress is a browser-based testing platform for end-to-end, component, and API tests. It runs tests in a real browser on a developer’s machine or in CI, with tools for creating tests, inspecting failures, tracking coverage and flakiness, and sharing results with a team.
The product covers more than test execution. Studio AI can record clicks and turn them into editable Cypress tests. Failure replay lets teams revisit CI failures with DOM, network-event, and console-log context. Smart Orchestration can parallelize specs, prioritize tests likely to fail, and rerun failed tests.
Cypress has a free Starter plan, plus paid Team and Business plans with annual billing listed at $799 and $3,199 per year, respectively. The pricing page displays those as $67 and $267 per month; separate monthly rates are not published. Enterprise pricing is also not published. A 30-day free trial is listed.
02Where Cypress is strong
Cypress’s clearest fit is browser-focused testing, especially when a team wants one platform for end-to-end flows and component tests. Tests run in a real browser, and the product also lists API testing as an included Cypress App capability. That makes it relevant to teams that want to check user-facing behavior alongside API work without treating Cypress as only a browser-clicking tool.
The workflow tools target the expensive part of CI: diagnosing and rerunning failures. Cypress says failure replay includes DOM, network events, and console logs. Smart Orchestration can parallelize specs, prioritize likely failures, and rerun only failed tests. Studio AI can record clicks and produce editable tests, rather than leaving the generated output as an uneditable recording.
The plan limits are explicit enough for smaller teams to estimate usage. Starter is free and includes 10 users, 500 test results per month, 100 prompt executions per month, and 30-day data retention. Team includes 50 users, 120,000 test results and 9,000 prompt executions per year, with 90-day retention. For a team already working in Cypress, those included amounts may be more useful than an attractive headline price alone.
03Where it falls short
Cypress is not an automatic fit for every automation stack. In one Reddit discussion, users described Selenium as more suitable for multi-user scenarios, broad language and platform support, and reusing code for mobile; other commenters characterized Cypress as more specialized for frontend teams and browser-based component or end-to-end work. These are user opinions, not a definitive feature comparison, but they point to a real switching question: check whether your existing test logic and team structure fit Cypress before migrating.
Price is also tied to annual commitments and usage ceilings. The pricing page lists Team at $799 per year, shown as $67 per month, and Business at $3,199 per year, shown as $267 per month; separate monthly rates are not published. Both plans include 50 users and 90-day retention. Team includes 120,000 test results and 9,000 prompt executions per year; Business includes the same result allowance but 24,000 prompt executions. Extra results cost $5.28 per 1,000 on Team or $4.40 on Business when bundled, with higher on-demand rates. Enterprise pricing and premium UI Coverage and Accessibility add-on prices are not published. Reddit claims that Cypress may shut down are speculation, not verified company information.
04Cypress pricing: what you'll actually pay
Cypress has a free Starter plan, but the paid plans are priced around annual billing. The pricing page lists Team at $799 per year, displayed as $67 per month, and Business at $3,199 per year, displayed as $267 per month. Separate monthly rates are not published, so budget for the annual bill rather than assuming you can pay month to month. The listed annual prices work out to about $66.58 and $266.58 per month, respectively.
Starter includes 10 users, 500 test results and 100 prompt executions per month, with 30-day data retention. Team raises the caps to 50 users, 120,000 results and 9,000 prompt executions per year; Business keeps the same user and result caps but allows 24,000 prompt executions. Both paid plans include 90-day retention. That’s a steep jump from free, especially if you need Business for its higher prompt allowance. A 30-day trial is listed.
Extra results cost $5.28 per 1,000 on Team, $4.40 on Business and $4 on Enterprise when bundled; on-demand rates are higher or custom. UI Coverage and Accessibility are premium add-ons, with prices not published.
05Switching to (or from) Cypress
Switching to Cypress means accounting for the work of moving existing tests into its browser-testing setup; switching away may mean rewriting Cypress-specific test logic for another tool. The actual effort depends on how much of your suite you move, and the published materials don’t give a migration guide or estimate. Cypress is a better fit if browser-based end-to-end or component testing is the priority. Teams that need broad language coverage should check that requirement before committing.
Before switching, check what happens to recorded results and other data. The plan details specify retention periods—30 days on Starter, 90 on Team and Business, and 180 on Enterprise—but data-export options are not published on the vendor's site. Don’t treat retention as a substitute for export access.
We can’t substantiate a “why people leave” summary from Reddit: no Reddit posts or comments were provided in the published material. The concrete reasons to review here are the annual billing, plan caps and whether the framework fits your stack. If your expected usage could exceed those caps, price the extra results before moving a large suite.
From the threadsWhat users say
Reddit sentiment is mixed and mostly anecdotal: some users report switching from Cypress, while others describe it as useful for developer-led browser and component testing. A shutdown prediction drew pushback for lacking evidence, so these threads do not establish that Cypress is closing.
All companies can fail and to be completely honest your assumption seems to have zero credibility, as stated by yourself
Our company just switched off cypress to playwright. So I could definitely see this happening
Selenium is old and clunky but I haven't run into many situations I couldn't find a solution to
Cypress is more suitable for single user e2e tests, for system test (mocking the backend) and component tests (web frameworks) on a browser
Questions people ask
What is Cypress used for?
Cypress is a testing platform for running tests in a real browser on your machine or in CI. It supports end-to-end tests for user flows, component tests in the browser, and API testing. The platform also includes tools for creating tests, inspecting failures, tracking coverage and flakiness, and sharing results with a team.
How much does Cypress cost?
Cypress lists a free Starter plan and a 30-day free trial. Team is billed annually at $799 per year, displayed as about $67 per month; Business is $3,199 per year, displayed as about $267 per month. Separate month-to-month rates are not published. Enterprise pricing is also not published.
What are the limits of Cypress’s free plan?
The Starter plan costs $0 and lists limits of 10 users, 500 test results per month, 100 prompt executions per month, and 30-day data retention. The pricing page describes Starter as intended for teams experienced with Cypress App. Check the current plan details before switching, especially if your team needs more results or longer retention.
What do Cypress’s paid plans include, and what do extra test results cost?
Team lists 50 users, 120,000 test results and 9,000 prompt executions per year, with 90-day retention. Business lists the same user and test-result limits but 24,000 prompt executions per year and 90-day retention. Bundled results cost $5.28 per 1,000 on Team and $4.40 on Business; on-demand results cost $6 and $5 per 1,000, respectively.
Is Cypress a good fit for my testing team?
One Reddit commenter describes Cypress as better suited to single-user end-to-end tests, backend mocking, and browser component tests. Other commenters point to Selenium’s broader language and platform coverage and suitability for multi-user scenarios. These are user opinions, not a definitive comparison. Cypress may fit teams focused on browser-based testing; weigh your own language, parallelization, and workflow needs.
