Duplicati
Duplicati turns Hyper-V and MSSQL backups into restorable, named sources.
A side-by-side editorial comparison of Currents and Payload CMS — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Payload v4 enters beta: redesigned admin, TanStack Start support and agent instructions.
Payload 4.0 moved from canaries to beta on October 9, bundling an admin UI redesign, TanStack Start as a second framework alongside Next.js, hierarchies, tags, grid view, upload versioning and a rewritten MCP server. Two betas followed within a week; beta.2 moves the TanStack adapter to stable TanStack Start and renames LLM instructions to agent instructions. The canaries also flipped the Local API to enforce access control by default.
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.
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.
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.
Payload 4.0 moved from canaries to beta on October 9, bundling an admin UI redesign, TanStack Start as a second framework alongside Next.js, hierarchies, tags, grid view, upload versioning and a rewritten MCP server. Two betas followed within a week; beta.2 moves the TanStack adapter to stable TanStack Start and renames LLM instructions to agent instructions. The canaries also flipped the Local API to enforce access control by default.
Payload is loosening its Next.js dependency and building agent features into the CMS itself: editors can manage instructions that flow into the CLI and MCP schemas, and upgrades come with an agent-assisted codemod. The betas are now mostly fixes and documentation, which points toward a stable 4.0.
Expect weekly betas focused on migration fixes and docs, with more framework-adapter work for TanStack Start. The entries don't give a 4.0 stable date.
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 Payload CMS.
Duplicati turns Hyper-V and MSSQL backups into restorable, named sources.
Caddy 2.11's betas add ECH key rotation and a release process without its founder.
Tolgee adds task-aware filters as editor gains and billing plumbing alternate.
Cloudflare Tunnel keeps a steady release cadence, but its notes list checksums, not changes.
Skipper patches a cache() filter security advisory amid routine maintenance tags.
ToolJet's latest tags are maintenance; the AI Builder features still wait on beta.
See all Currents alternatives → · See all Payload CMS 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 Payload CMS 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 Payload CMS 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 Payload CMS alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Payload CMS alternatives" section above for the current picks, or visit /alternatives/payload-cms for the full list with editorial commentary on each.