← Back to home
Comparison · Infra & APIs

Aviator vs Currents

A side-by-side editorial comparison of Aviator and Currents — release velocity, themes, recent moves, and the top alternatives to consider.

Aviator vs Currents: at a glance

FeatureAviatorCurrents
SectorInfra & APIsInfra & APIs
Velocity score2.56.3
Sparks · 30d01
Top themesmerge-queue, flaky-tests, stacked-prs, ai-coding-agentsplaywright, ci-observability, mcp, agent-access
Last editorial update23h ago2d ago
WebsiteVisit →Visit →

What is Aviator?

Aviator's MergeQueue now has an LLM tell flaky failures from real ones and rerun them.

Aviator is a merge queue and stacked PR platform; MergeQueue batches and validates pull requests to keep trunk green. The October 1 beta uses an LLM to read a failed check's logs, separate flaky failures from real ones, rerun the flakes and keep the PR queued instead of resetting everything behind it. September brought dark mode and merge timing metrics exportable to Prometheus or Datadog, and August added support for GitHub's native stacked pull requests.

Read the full Aviator trajectory →

What is Currents?

Currents now lets agents walk a Playwright trace instead of downloading it.

Currents is a Playwright test dashboard rebuilding itself around agent access. In six weeks it shipped agent-readable failure links, scoped personal access tokens, a hosted MCP server with OAuth, run attachments, and now a trace API built for agents. The trace API lets an agent read a Playwright trace one part at a time, choosing each next call from what it just read.

Read the full Currents trajectory →

Aviator vs Currents: editorial side-by-side

A
Aviator
INFRA · APIS
2.5

Aviator's MergeQueue now has an LLM tell flaky failures from real ones and rerun them.

◆ Current state

Aviator is a merge queue and stacked PR platform; MergeQueue batches and validates pull requests to keep trunk green. The October 1 beta uses an LLM to read a failed check's logs, separate flaky failures from real ones, rerun the flakes and keep the PR queued instead of resetting everything behind it. September brought dark mode and merge timing metrics exportable to Prometheus or Datadog, and August added support for GitHub's native stacked pull requests.

◆ Where it's heading

After exposing stacked PRs to AI coding agents in April, Aviator is now applying an LLM inside the queue itself, attacking the main cost of merge queues: one flaky test stalling every PR behind it. The timing metrics export points the same way: the product is being tuned for teams measuring queue throughput, and AI is used to raise it.

◆ Prediction

Expect the flaky test beta to move toward general availability, likely with flake reporting surfaced in Inbox or the metrics export. The entries do not indicate timing.

C
Currents
INFRA · APIS
6.3

Currents now lets agents walk a Playwright trace instead of downloading it.

◆ Current state

Currents is a Playwright test dashboard rebuilding itself around agent access. In six weeks it shipped agent-readable failure links, scoped personal access tokens, a hosted MCP server with OAuth, run attachments, and now a trace API built for agents. The trace API lets an agent read a Playwright trace one part at a time, choosing each next call from what it just read.

◆ Where it's heading

The sequence goes deeper each time: from a failure summary an agent can fetch, to a secure way in, to the logs around a run, to the trace itself. Currents is positioning as the place a coding agent goes to debug a CI failure, with humans as a second audience.

◆ Prediction

The likely next step is wiring the trace API and attachments into the MCP server so one agent session can reach all of it. The entries don't yet confirm that the trace API is exposed through MCP.

Alternatives to Aviator and Currents

Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Aviator or Currents.

See all Aviator alternatives → · See all Currents alternatives →

Recent activity from Aviator and Currents

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 3d agoCurrents[New] Trace API for agents ⚡
  2. 10d agoCurrents[New] Run attachments
  3. 16d agoAviatorAI-powered flaky test management (beta): rerun the flake, keep the queue
  4. 17d agoCurrents[New] Remote MCP Server with OAuth
  5. 23d agoCurrents[New] Personal Access Tokens
  6. 1mo agoAviatorDark mode is here, and see where your queue time goes
  7. 1mo agoCurrents[New] Shareable AI context for test failures ⚡
  8. 2mo agoAviatorMergeQueue now supports GitHub's native stacked pull requests
  9. 2mo agoCurrents[Improved] Better Slack notifications for CI test runs
  10. 3mo agoAviatorMeet Inbox: every PR that needs you, in one place
  11. 5mo agoAviatorChrome Extension gets a revamp
  12. 6mo agoAviatorUse stacked PRs with agent plugins ⚡

Frequently asked questions

What is the difference between Aviator and Currents?

They serve adjacent needs but don't currently overlap on shipped themes. Currents is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is Aviator better than Currents?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Currents is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

What are the best alternatives to Aviator?

Top Aviator alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Aviator alternatives" section above for the current picks, or visit /alternatives/aviator for the full list with editorial commentary on each.

What are the best alternatives to Currents?

Top Currents alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Currents alternatives" section above for the current picks, or visit /alternatives/currents-dev for the full list with editorial commentary on each.