Ably vs Kubernetes
Side-by-side trajectory, velocity, and editorial themes.
Ably is rebuilding its realtime stack around AI agents: transport SDK and agent-native CLI
Ably is repositioning its realtime messaging infrastructure around AI agents. The clearest evidence is a dedicated AI Transport SDK, now with a session/run model, conversation branching, and human-in-the-loop handoff, plus a CLI rebuilt to be agent-operable that installs Agent Skills into Claude, Cursor, and Windsurf and emits structured JSON for self-healing automation. Underneath, the core Pub/Sub and Chat SDKs keep maturing and platform reach widens with a new Dart/Flutter SDK.
The trajectory is realtime-as-agent-infrastructure: the AI Transport SDK is iterating fast toward production agent apps with branching, suspend/resume, and tool-calling, while the tooling is built so AI coding agents, not just humans, can drive Ably. The conventional SDK and CLI work continues in parallel, but the directional energy is clearly aimed at the agent stack.
Expect the AI Transport SDK to keep adding agent-conversation primitives on its march to 1.0, and the Dart SDK to fill toward parity with the JS line.
Kubernetes 1.36 leans into workload-aware scheduling while clearing legacy security debt.
Kubernetes is mid-release cycle around v1.36, with multiple long-running features graduating to Beta or GA — Mixed Version Proxy, PSI metrics, volume group snapshots, and DRA maturation. The project is simultaneously deprecating Service.externalIPs over a six-year-old CVE class and archiving the official Dashboard in favor of Headlamp. The cadence is steady upstream release-train work, weighted toward AI/ML workload primitives this quarter.
The center of gravity is shifting toward batch and AI/ML workloads — the new PodGroup API, gang scheduling, DRA expansion, and workload-aware scheduling primitives all point that way. Security and ecosystem hygiene (CVE record correction, ExternalIPs removal, Dashboard sunset) are getting equal weight, suggesting the project is using v1.36 to clear inherited liabilities. etcd 3.7 entering beta means storage-layer changes are queued for the next release.
Expect v1.37 to make workload-aware scheduling defaults-on for batch workloads and graduate at least one DRA sub-feature to GA. The ExternalIPs removal will likely land as default-disabled in the same release.
See more alternatives to Ably →
See more alternatives to Kubernetes →