OpenStatus
OpenStatus scopes API keys per resource and lets its MCP server set up monitors.
A side-by-side editorial comparison of Currents and Pacemaker — release velocity, themes, recent moves, and the top alternatives to consider.
Currents lists itself in the Claude and ChatGPT/Codex plugin directories.
Currents is a Playwright test dashboard rebuilding itself around agent access. Since September it shipped agent-readable failure links, scoped personal access tokens, a hosted MCP server with OAuth, run attachments and a trace API. On November 3 it appeared in the Claude and ChatGPT/Codex plugin directories, so users connect from the listing without typing a server URL.
Pacemaker is putting TLS and X509 auth between its cluster nodes, then hardening the wire code.
Two branches ship in parallel: the 3.0.x line carrying new work and 2.1.x taking backported fixes. The 3.0 series added TLS for Pacemaker Remote nodes, X509 authentication, TLS certificates for remote CIB operations, and then PSK authentication for those same operations, alongside large-IPC and multipart message support. The most recent releases on both branches are the same security train, fixing CVE-2026-10649 and a set of integer overflows and size checks in the remote message code.
Currents is a Playwright test dashboard rebuilding itself around agent access. Since September it shipped agent-readable failure links, scoped personal access tokens, a hosted MCP server with OAuth, run attachments and a trace API. On November 3 it appeared in the Claude and ChatGPT/Codex plugin directories, so users connect from the listing without typing a server URL.
The agent-access stack is built; Currents is now working on distribution. Plugin directory listings put the OAuth MCP server in front of users inside the agents themselves, while the October Project Overview serves people reading the dashboard.
Expect more agent-directory listings or deeper Claude Code and Codex workflows built on the trace API.
Two branches ship in parallel: the 3.0.x line carrying new work and 2.1.x taking backported fixes. The 3.0 series added TLS for Pacemaker Remote nodes, X509 authentication, TLS certificates for remote CIB operations, and then PSK authentication for those same operations, alongside large-IPC and multipart message support. The most recent releases on both branches are the same security train, fixing CVE-2026-10649 and a set of integer overflows and size checks in the remote message code.
The cluster's internal transport is being rebuilt on the assumption that the network between nodes is not trusted. Authentication and encryption arrived first, and the fixes that followed, overflow guards and a maximum remote message size, are the hardening pass on the same code paths. Release discipline is heavy and visible: each version ships a release candidate with an identical commit set days earlier, and every 3.0 release documents the regressions it introduced and where they were fixed.
Remote CIB operations now support both X509 certificates and PSK, and the recent fixes all sit in message framing and size limits; further work is most likely to continue in that message-handling code rather than adding another authentication mechanism.
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 Currents or Pacemaker.
OpenStatus scopes API keys per resource and lets its MCP server set up monitors.
Hoppscotch adds an enterprise cloud tier and an AI assistant, then turns to desktop trust.
Grype keeps tightening match accuracy while making its database diff tool usable at scale
AdGuard Home's 1.0 beta matches stable's security fixes and reworks client settings
Snort 3.13.2 is a broad bounds-checking sweep across SMB, HTTP and industrial protocol parsers
DNSimple's origin name servers answer a quarter faster at p90 after erldns work
See all Currents alternatives → · See all Pacemaker alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Currents and Pacemaker are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). 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. Currents and Pacemaker are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
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.
Top Pacemaker alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Pacemaker alternatives" section above for the current picks, or visit /alternatives/pacemaker for the full list with editorial commentary on each.