GravityKit
GravityKit folds every GravityView extension into one Pro plugin.
A side-by-side editorial comparison of Ably and Currents — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Ably | Currents |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 7.5 | 7.5 |
| Sparks · 30d | 2 | 1 |
| Top themes | ai transport, realtime messaging, agents, mau-billing | playwright, agent-access, mcp, agent-sessions |
| Last editorial update | 20h ago | 1d ago |
| Website | — | Visit → |
Ably's AI Transport hits 1.0 and plugs straight into Vercel's useChat with resumable streams.
Ably is repositioning its realtime pub/sub network as the transport layer for AI agent output. AI Transport JS 1.0 runs on ordinary Pub/Sub channels and ships adaptors for the Vercel AI SDK, OpenAI Responses API and AG-UI, plus a useChat transport that resumes a stream after a reload. It lands a week after the switch to monthly-active-user pricing and breaking SDK majors that split every client into device and server packages.
Currents starts recording any agent task, not just Playwright test runs.
Currents built a Playwright test dashboard and has spent the autumn opening it to agents: shareable failure links, scoped tokens, a hosted MCP server with OAuth, run attachments, a trace API and listings in the Claude and ChatGPT/Codex plugin directories. On November 12 it added Sessions, where an agent saves the browser recording or files from any task and gets one link with a page for people and a Markdown version for other agents.
Ably is repositioning its realtime pub/sub network as the transport layer for AI agent output. AI Transport JS 1.0 runs on ordinary Pub/Sub channels and ships adaptors for the Vercel AI SDK, OpenAI Responses API and AG-UI, plus a useChat transport that resumes a stream after a reload. It lands a week after the switch to monthly-active-user pricing and breaking SDK majors that split every client into device and server packages.
The November releases fit one plan: split clients so MAU billing can count end users, then make the AI layer a thin adaptor on top of the same channels used for chat, presence and LiveObjects. Server-side additions in Java and JS (HTTP LiveObjects, channel pools, a Temporal plugin) point at agent backends as the intended publisher.
Expect more agent framework adaptors and server SDKs reaching AI Transport parity, with Chat and LiveObjects examples built around agents joining human conversations.
Currents built a Playwright test dashboard and has spent the autumn opening it to agents: shareable failure links, scoped tokens, a hosted MCP server with OAuth, run attachments, a trace API and listings in the Claude and ChatGPT/Codex plugin directories. On November 12 it added Sessions, where an agent saves the browser recording or files from any task and gets one link with a page for people and a Markdown version for other agents.
Until now every release made test results easier for agents to read. Sessions turns the direction around: agents write their own work into Currents, and the product's scope widens from CI test runs to a record of what agents did. The pattern of pairing a human page with a Markdown twin, first used for failure links in September, is now the product's standard output.
Expect Sessions to be wired into the existing pull request comment and MCP server next, since earlier releases connected each new artifact to both within weeks.
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 Ably or Currents.
GravityKit folds every GravityView extension into one Pro plugin.
Payload's v4 beta.9 keeps every past image crop and raises the Node floor again.
Nautobot 3.3 alpha 2 adds test helpers and a cable location filter after 3.2.9's token-leak fix.
Clair 4.10 RC can read SBOMs to match Java vulnerabilities.
Shuffle tags builds almost daily, but the notes are empty.
KrakenD's community edition is shipping only dependency bumps.
See all Ably alternatives → · See all Currents alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Ably and Currents are shipping at a similar cadence (velocity 7.5 vs 7.5, 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. Ably and Currents are shipping at a similar cadence (velocity 7.5 vs 7.5, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top Ably alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Ably alternatives" section above for the current picks, or visit /alternatives/ably for the full list with editorial commentary on each.
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.