webpack
webpack is absorbing its own loader ecosystem — TypeScript, CSS and HTML now build natively.
A side-by-side editorial comparison of Ably and Thanos — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Ably | Thanos |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 7.5 | 0.0 |
| Sparks · 30d | 2 | 0 |
| Top themes | realtime-infrastructure, ai-agents, durable-execution, liveobjects | prometheus-storage, multi-tenancy, receive-component, query-fanout |
| Last editorial update | 2d ago | 1h ago |
| Website | — | Visit → |
Ably is building an agent transport layer, shipping a new AI SDK version roughly every ten days.
The AI Transport JS SDK moved from 0.4.0 to 0.7.0 inside a single month, each release adding a distinct piece of agent infrastructure: seeding a conversation from an app's own message store, a Step primitive that survives process restarts under Temporal or Vercel's Workflow Development Kit, mid-run steering through run.steer(), and a codec that streams the OpenAI Responses API over a channel with client-executed tools and human approvals. In parallel, the established Pub/Sub line is spreading LiveObjects further — a path-based API in the Java SDK, a useObject React hook, and React Native push support.
Thanos is rebuilding Receive around multi-tenancy, and shipping it through a stuttering RC train.
Thanos is working through the 0.42.0 release candidates, where the headline work is on Receive: tenant lifecycle handling, per-endpoint configuration, and fanout information surfaced in Thanos Query. The line also adopted Go's *os.Root API, which rc.2 exists mainly to clean up after. The release pipeline itself has been unreliable — rc.0 was skipped outright because base image SHA updates broke it, so rc.1 and rc.2 carry identical feature notes.
The AI Transport JS SDK moved from 0.4.0 to 0.7.0 inside a single month, each release adding a distinct piece of agent infrastructure: seeding a conversation from an app's own message store, a Step primitive that survives process restarts under Temporal or Vercel's Workflow Development Kit, mid-run steering through run.steer(), and a codec that streams the OpenAI Responses API over a channel with client-executed tools and human approvals. In parallel, the established Pub/Sub line is spreading LiveObjects further — a path-based API in the Java SDK, a useObject React hook, and React Native push support.
The pattern is a realtime messaging company treating agent runs as the thing its network transports. Each AI Transport release closes a gap that would otherwise force developers to build around the channel — history reconciliation, crash recovery, changing direction mid-response, and now speaking a specific model provider's wire format. The LiveObjects work runs on a slower track and points the same way: path-based subscriptions that survive structural change are aimed at the fast-mutating state agents and collaborative apps produce.
Expect the codec pattern to extend to other model provider APIs beyond OpenAI Responses, and the LiveObjects path-based API to keep propagating across the remaining SDK languages after Java.
Thanos is working through the 0.42.0 release candidates, where the headline work is on Receive: tenant lifecycle handling, per-endpoint configuration, and fanout information surfaced in Thanos Query. The line also adopted Go's *os.Root API, which rc.2 exists mainly to clean up after. The release pipeline itself has been unreliable — rc.0 was skipped outright because base image SHA updates broke it, so rc.1 and rc.2 carry identical feature notes.
The centre of gravity is multi-tenant operation. Per-endpoint configuration and tenant lifecycle handling are what an operator needs to run one Thanos install for many teams rather than one per team, and the Query fanout view is the observability that makes such a topology debuggable. The parallel fixes to multi-tier query setups — preserving external label matchers across Query A → Query B → Sidecar chains — point at the same reality: deployments are getting deeper, not just wider.
A 0.42.0 stable should follow once the *os.Root regressions settle. The RC notes are cumulative and the feed is quiet since June, so treat cadence here as release-train artefact rather than a slowdown in the project.
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 Thanos.
webpack is absorbing its own loader ecosystem — TypeScript, CSS and HTML now build natively.
CAS 8.0 is six release candidates deep with notes that describe nothing
LibreELEC's changelog stops dead at the 12.0 release in May 2024
Node-RED 5.0 rebuilt the editor, and the patches since are settling it in
Jaeger folds its MCP server into the query service and drops Elasticsearch 6
Biome's patch train is really a type-aware linting project in disguise
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Ably is currently shipping more aggressively (velocity 7.5 vs 0.0), with 2 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. Ably is currently shipping more aggressively (velocity 7.5 vs 0.0), with 2 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 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 Thanos alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Thanos alternatives" section above for the current picks, or visit /alternatives/thanos for the full list with editorial commentary on each.