Cypress

Test result counting is per spec file per run

each spec file execution that is recorded to Cypress Cloud counts as one test result, regardless of how many individual test cases (it blocks) are inside. A spec file with 50 tests counts as 1 result, but running that file 10 times in CI (e.g., on 10 PRs) counts as 10 results. High-frequency CI pipelines burn through the 120,000/year allocation faster than expected

Annual billing only

Team ($799/year) and Business ($3,199/year) are billed annually, no monthly option is published. This means $799 or $3,199 upfront before you start, with no ability to pay month-to-month while evaluating

Parallelization requires CI infrastructure

Cypress Cloud orchestrates parallel test distribution, but you provide the CI machines. Running 10 parallel containers in GitHub Actions, CircleCI, or AWS costs $50-200/month in CI compute alone. Cypress Cloud does not include compute, it only coordinates which tests run where

Overage accumulates without alerts by default

at $5-6 per 1,000 test results over the 120,000/year cap, a team running 200,000 results/year pays $480-$528 in overage on top of the plan cost. Set up usage monitoring early to avoid surprise charges at year-end

Data retention is limited

Starter retains data for 30 days, Team and Business for 90 days, Enterprise for 180 days. Historical test trend analysis beyond these windows requires exporting data before it expires or upgrading to Enterprise

Component testing results also count

if you use Cypress for both E2E and component testing, component test results count against the same quota. A comprehensive component test suite can consume a significant portion of your allocation before E2E tests even run

No Playwright or other framework support

Cypress Cloud only works with the Cypress test framework. If your team also uses Playwright, WebdriverIO, or other tools, you need separate dashboards and potentially separate billing for those frameworks