Currents
By Currents. Category: Results analysis and triage. Homepage
Currents' documentation describes a dashboard, reporter and orchestrator for Playwright test runs in CI. It also supports Cypress, Jest, Vitest and any framework that outputs JUnit XML. It records results, detects flaky tests and groups errors by root cause. Its AI features pass failure context to an external coding agent through an MCP server, n8n workflow or webhook. That agent then drafts a fix or pull request. The docs cover GitHub Actions, GitLab, CircleCI, Jenkins, Azure DevOps and other CI systems. Currents is a hosted service, and the Enterprise plan adds self-hosting.
Description written from the vendor's documentation.
Status
Status: Active
Facts
| Fact | Value | Evidence | Source | Verified on |
|---|---|---|---|---|
| Status | Active | Documented | currents.dev | |
| Founded | Not documented | Not documented | None found | |
| Headquarters | Not documented | Not documented | None found | |
| AI capabilities | Documented | docs.currents.dev | ||
| Test creation | Not documented | Not documented | None found | |
| Test output | Not documented | Not documented | None found | |
| Surfaces | Documented | docs.currents.dev | ||
| Hosting | Documented | currents.dev | ||
| Pricing model | Documented | currents.dev | ||
| Free tier | No | Documented | currents.dev | |
| CI integrations | Documented | docs.currents.dev | ||
| Self-healing | Documented | Documented | docs.currents.dev | |
| Agent integration | Currents MCP server: local npm package @currents/mcp (stdio) and hosted remote MCP endpoint https://api.currents.dev/mcp; IDE extension for VS Code and Cursor; an agent skill for Playwright test authoring | Documented | docs.currents.dev |
Published prices
| Plan | Price | Billing |
|---|---|---|
| Scale | $49 / month (10K test results / month, then $4.9 for every 1k test results) | billed monthly |
| Business | $99 / month (10K test results / month, then $9.9 for every 1k test results) | billed monthly |
Vendor-stated, verbatim
What Currents says about its product, quoted as published and not confirmed in documentation.
“Up to 50% faster compared to Playwright native sharding.”
“35% faster!”
Alternatives
Tools in the same category (Results analysis and triage), ordered by the number of shared creation and surface values, then by name. Each line lists documented facts that differ from Currents.
- Appsurify TestBrain: Results analysis and triage; no documented difference in output, creation, hosting or free tier
- StageWright: documents hosting hybrid; a free tier
- TestBeats: documents a free tier
- TestDino: documents a free tier
- Testkube: documents creation by prompt to test; hosting hybrid
- CloudBees Smart Tests: documents status renamed
Questions
Is this page a review of Currents?
No. This page is a fact sheet. Each fact shows its evidence level, its source and the date it was checked. We do not rate or rank tools.
Does Currents have a free tier?
No. Currents has no free tier. This is documented, checked on 2026-09-24.
What test output does Currents produce?
The test output format is not documented as of 2026-09-24.
Is Currents still available?
Status: Active, checked on 2026-09-24.
Sources
- Currents homepage Opened
- Currents Pricing Opened
- About Currents Opened
- Currents Changelog Opened
- Currents Documentation Opened
- Currents documentation index (llms.txt) Opened
- AI overview | Currents Documentation Opened
- MCP Server | Currents Documentation Opened
- Remote MCP Server | Currents Documentation Opened
- IDE Extension | Currents Documentation Opened
- CI Setup | Currents Documentation Opened
- Playwright - GitHub Actions | Currents Documentation Opened
- Playwright - GitLab CI/CD | Currents Documentation Opened
- Playwright - CircleCI | Currents Documentation Opened
- Jenkins | Currents Documentation Opened
- Playwright - Azure DevOps | Currents Documentation Opened
- Plans & Pricing | Currents Documentation Opened
- Bring Your Own Storage | Currents Documentation Opened
Spotted an outdated or wrong fact about Currents? Send the source and we apply it at the next monthly update.