Thanos
Thanos is rebuilding Receive around multi-tenancy, and shipping it through a stuttering RC train.
A side-by-side editorial comparison of Ably and Biome — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Ably | Biome |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 7.5 | 5.0 |
| Sparks · 30d | 2 | 0 |
| Top themes | realtime-infrastructure, ai-agents, durable-execution, liveobjects | type-aware-linting, false-positives, svelte, css-formatter |
| Last editorial update | 2d ago | 2h 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.
Biome's patch train is really a type-aware linting project in disguise
Biome is shipping weekly 2.5.x patches with no minor release in the window, and the fixes cluster tightly. One cluster is type-aware lint rules — noMisusedPromises, noBaseToString, useNullishCoalescing, useExhaustiveSwitchCases — where the work is about what to do when type inference is incomplete or expensive. The other is framework coverage: Svelte store subscriptions and bindable props, Astro and Vue text interpolation, CSS Modules parser recovery.
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.
Biome is shipping weekly 2.5.x patches with no minor release in the window, and the fixes cluster tightly. One cluster is type-aware lint rules — noMisusedPromises, noBaseToString, useNullishCoalescing, useExhaustiveSwitchCases — where the work is about what to do when type inference is incomplete or expensive. The other is framework coverage: Svelte store subscriptions and bindable props, Astro and Vue text interpolation, CSS Modules parser recovery.
Biome is buying credibility in the two areas that decide whether a project can drop typescript-eslint: rules that need type information, and correct handling of single-file-component frameworks. The recurring pattern of suppressing diagnostics rather than reporting from partial type information is a deliberate stance — Biome would rather miss a finding than emit a false positive, which is the right trade for a tool asking to be adopted as the default.
Expect the type-aware rule set to keep expanding with the same suppress-on-incomplete-inference policy, and Svelte-specific nursery rules to graduate as their false-positive reports dry up.
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 Biome.
Thanos is rebuilding Receive around multi-tenancy, and shipping it through a stuttering RC train.
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
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 5.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 5.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 Biome alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Biome alternatives" section above for the current picks, or visit /alternatives/biome for the full list with editorial commentary on each.