Cypress Cloud vs Currents
Currents is the answer every listicle gives to "cheaper Cypress Cloud", and on price it is right. This page is about the sentence those listicles leave out: Currents documents that it does not support Cypress 13 and above, and the package it depends on stopped shipping in June 2025. If you are on a current Cypress, that single line decides the comparison before pricing enters it.
Pick Currents if you are on Cypress 12 or older and want the same recorded runs, orchestration and longer retention for roughly a quarter of what Cypress Business costs. Stay on Cypress Cloud if you are on Cypress 13, 14 or 15, because Currents is not an option there at any price, and the third-party dashboard market for modern Cypress is effectively empty.
Side by side
Cypress Cloud vs Currents at a glance
| Cypress Cloud | Currents | |
|---|---|---|
| Billing unit | test results, one per it() | test results, one per it() |
| Free plan | Starter, 500 results a month, 50 users | trial, check current terms |
| Entry paid tier | Team $67/mo or $799/yr, 120k results a year | $49/mo, 10,000 results a month |
| Overage | upgrade the plan | +$5 per extra 1,000 results |
| 120k results a year costs | $799 on Team, $3,199 on Business | $588 |
| Retention | 30 days on Starter | up to 1 year |
| At the free cap | parallelization disabled, new results hidden | metered overage instead |
| Cypress 12 and older | ✓ | ✓ |
| Cypress 13, 14, 15 | ✓ | ✗ docs say not supported |
| Integration package | built into the Cypress binary | cypress-cloud, last release 1.13.1 in June 2025 |
| Self-hosting | ✗ | ✗ Bring Your Own Storage on Enterprise |
| Other frameworks | Cypress only | ✓ Playwright first, plus others |
| Best for | modern Cypress with vendor-backed orchestration | legacy Cypress 12 suites, and Playwright teams |
Sources: Cypress Cloud pricing · Cypress Cloud FAQ · Currents pricing · Currents Cypress docs. Compiled July 2026.
Where Currents wins
The same volume, for a quarter of the price
Cypress prices its two main tiers at $799 and $3,199 a year, and both include the same 120,000 test results, which means the step up buys SSO, Spec Prioritization and Auto Cancellation rather than capacity. Currents Team is $49 a month for 10,000 results a month, so the same 120,000 a year lands at $588. If volume rather than features is what pushed you toward Business, that is a four-figure difference for an identical unit of work.
Overage instead of a killswitch
This is a difference in behaviour, not just in price. The Cypress Cloud FAQ says that at the free cap tests keep running with --record, but parallelization is disabled and new test results are hidden until you upgrade or a new cycle starts. Currents meters overage at $5 per extra 1,000 results. One model stops your parallel CI mid-sprint, the other sends a slightly larger invoice.
Retention long enough to be useful
Retention on Cypress Starter is 30 days. Currents advertises retention up to a year, with Bring Your Own Storage on Enterprise. If you actually chase flake trends across quarters rather than across sprints, that is the feature you are buying.
Where Cypress Cloud still wins
It works on the Cypress you are running. The Currents docs state that Currents "is not currently supporting Cypress 13+" and that cypress-cloud is "suspending support starting from Cypress 13", so the documented ceiling is Cypress 12.x. Its cypress-cloud package last published 1.13.1 on 25 June 2025. Cypress itself is on v15.19.0 as of 21 July 2026. For the majority of teams reading this, that gap ends the discussion, and no amount of pricing math reopens it.
Currents has also visibly changed direction. Its own homepage now describes it as a Playwright-focused dashboard, reporter and test orchestrator, and it publishes a migrate-from-Cypress guide. Read that as a signal rather than a slight: the best-known Cypress Cloud alternative is not betting on Cypress. sorry-cypress, the self-hosted sibling, is in the same position, still MIT and still online but with its last code push on 14 September 2025 and no documented Cypress 13 support, since it routes through the same package.
If you are on Cypress 13 or newer
There is no dashboard to migrate to, so pick which cost you would rather carry:
1. Keep Cypress Cloud. You are paying for duration-based spec balancing and Auto Cancellation, which are genuinely hard to reproduce. If your suite is uneven, that is worth real money.
2. Keep the specs, move the parallelism into your own CI. Run the Cypress Docker image in your pipeline and give each parallel job a slice of the suite with --spec. No record key, no per-result meter, and your bill becomes minutes. What you give up is the load balancing and the hosted flake history. Our shortlist ranks Buddy's native Cypress action first for exactly this lane.
3. Change the framework. Playwright shards for free with --shard and merge-reports. The cost is the rewrite, paid per spec file.
4. Do not plan a migration onto sorry-cypress. It still runs where it already runs. Adopting a stale self-hosted dashboard in 2026 buys you the maintenance, not the savings.
Common questions
FAQ: Cypress Cloud vs Currents
Does Currents support Cypress 13, 14 or 15?
No. The Currents documentation states that Currents is not currently supporting Cypress 13 and above, and that the cypress-cloud integration package is suspending support starting from Cypress 13. The documented ceiling is Cypress 12.x. Published patch numbers for that ceiling differ between doc pages, so treat the safe reading as Cypress 12 supported, 13 and newer not supported, and confirm with Currents before committing.
Is Currents cheaper than Cypress Cloud for the same volume?
For equal volume, yes, and by a lot. 120,000 test results a year is the allowance on both Cypress Team at 799 dollars a year and Cypress Business at 3,199 dollars a year. On Currents Team, 10,000 results a month at 49 dollars a month covers the same 120,000 for 588 dollars a year. That comparison is only usable if your project is on Cypress 12 or older, otherwise Currents is not an option at any price.
What should you use instead if you are on Cypress 13 or newer?
There is no third-party dashboard to move to; both Currents and sorry-cypress stop at Cypress 12. That leaves three honest options. Stay on Cypress Cloud and pay for the orchestration. Keep your specs and run them in your own CI, splitting the suite across parallel jobs so you pay for minutes instead of test results. Or move the framework to Playwright, where sharding is a free CLI flag. Which one fits depends on whether the Cloud dashboard or the Cloud bill is the actual problem.