Ably vs WorkOS
Side-by-side trajectory, velocity, and editorial themes.
Ably is spinning up an AI-agent transport layer at 0.x speed
Ably is iterating hard on a new AI Transport SDK — four releases (0.2 through 0.5) in about a month — aimed at making agent conversations durable, resumable, and branchable over its realtime channels. Alongside it, the core Pub/Sub and Chat SDKs keep getting steady, mostly incremental maintenance: React hook ergonomics, presence reliability fixes, and better LiveObjects visibility in the dashboard.
The AI Transport line is the story. Each release layers on capability that matters for production agents — declarative codecs, external data hydration, and now durable execution that survives process restarts inside frameworks like Temporal and Vercel's WDK. Ably is positioning its realtime infrastructure as the transport substrate for AI agents, not just chat and pub/sub, while keeping the mature core SDKs stable. The frequent breaking changes signal a product still finding its API shape.
Expect the AI Transport SDK to keep its fast breaking-change cadence toward a 1.0 with a stabilized session/run API, and likely SDKs beyond JS as the surface settles. The entries don't yet indicate a GA date.
WorkOS ships three new surfaces in a week, pushing into front-end widgets and agent-run admin.
WorkOS is an enterprise identity and auth infrastructure provider, best known for AuthKit, SSO, directory sync, and audit logs. The changelog shows an unusually dense shipping burst: three distinct new product surfaces in a single week, the Widgets API, a Management MCP server, and an API Gateway, layered on top of steady AuthKit feature work like step-up authentication, waitlists, and an Astro integration.
Two directions are visible. First, AuthKit is growing from a backend auth library into a fuller front-end toolkit, adding client widgets, framework SDKs, and richer session flows. Second, the platform is becoming programmable by agents and unified at the edge, via the MCP server and the API Gateway. WorkOS is moving up the stack from backend primitives toward client UI and agent-driven administration.
Expect more AuthKit framework integrations and additional agent-facing tooling built on the MCP server, plus broadening coverage for the newer Widgets API and API Gateway. The pace suggests WorkOS is racing to own both the front-end auth UI layer and the agent-administration layer at once.
See more alternatives to Ably →
See more alternatives to WorkOS →