Sonarr
Sonarr's 5.0 builds move from UI rework to safer restores and keyboard-friendly selects.
A side-by-side editorial comparison of Aviator and TestingBot — release velocity, themes, recent moves, and the top alternatives to consider.
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.
A browser grid that spent the summer becoming a team product, and is now opening itself to agents.
TestingBot runs a cross-browser and real-device cloud, and the last three months have gone almost entirely into what surrounds a test run rather than the run itself: custom roles enforced identically in dashboard and API, service accounts so pipelines stop borrowing a person's credentials, enforced two-factor authentication, comments with @mentions on failed runs, one-click filing into GitHub, Jira, Trello, Asana or Azure DevOps, and a notification inbox tying it together. The grid work continues underneath — WebRTC streaming for iOS simulators, a rebuilt web inspector, new devices and browser versions on the usual cadence.
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.
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.
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.
TestingBot runs a cross-browser and real-device cloud, and the last three months have gone almost entirely into what surrounds a test run rather than the run itself: custom roles enforced identically in dashboard and API, service accounts so pipelines stop borrowing a person's credentials, enforced two-factor authentication, comments with @mentions on failed runs, one-click filing into GitHub, Jira, Trello, Asana or Azure DevOps, and a notification inbox tying it together. The grid work continues underneath — WebRTC streaming for iOS simulators, a rebuilt web inspector, new devices and browser versions on the usual cadence.
Two directions are visible. The platform is being made safe for organisations rather than individuals, which is what roles, service accounts, 2FA and audit-friendly reporting add up to. Alongside it, the grid is being made reachable by software instead of people: an Insights API exposing pass rates and flakiness, embeddable build reports for CI dashboards, GitHub checks on every pull request, and now Vibium's CLI and MCP server pointed straight at the grid over WebDriver BiDi. The AI work so far reads results — failure analysis, documentation questions — while Vibium is the first path where something other than a human-written script drives the browser.
Expect the agent-facing path to be developed further, since supporting Vibium's MCP server without extra configuration is a small step from offering a first-party one, and expect the device and browser catalogue to keep rotating on its established cadence.
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 TestingBot.
Sonarr's 5.0 builds move from UI rework to safer restores and keyboard-friendly selects.
Cursor puts its cloud agent environments behind an API and lets agents ship interactive canvases.
Railway is adding guardrails for teams moving off the dashboard and into code and the CLI.
Jackett ships daily to keep hundreds of torrent indexers working as sites move and close.
CircleCI now sizes parallelism to the tests Smarter Testing actually selects.
GitHub makes open source license compliance a ruleset-enforced GA for Enterprise Cloud.
See all Aviator alternatives → · See all TestingBot alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. TestingBot is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. TestingBot is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 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.
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.
Top TestingBot alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "TestingBot alternatives" section above for the current picks, or visit /alternatives/testingbot for the full list with editorial commentary on each.