Developers now pick infrastructure on what AI assistants tell them, and the first thing someone building an AI agent hits is a dropped stream. Ably already has the deepest writing on this, but it is spread across a dozen blog posts with no single page that answers "what should I use?".
First action
Outline the decision table (connection drop, tab switch, device switch, multi-agent, human handoff) with an honest yes/no/partial for each option.
How to measure it
Signups from the resumable-streaming comparison
- Now
- –
- Target
- 250 in the first quarter
- By
- 12 weeks
Steps
Map the four options
Vercel AI SDK resumable-stream, Workflow DevKit, roll-your-own SSE, Ably AI Transport, each with its real limits.
Developer Relations Manager 1 day
Build the decision table
Rows for the failure modes developers actually hit; be fair about where Ably is overkill.
Developer Relations Manager 3 hours
Write runnable snippets
A before/after in the Vercel AI SDK that a developer can paste and run.
Developer Relations Manager 1 day
Fix the duplicate explainers
Collapse the /vercel/ and /topic/ai-stack/ versions to one URL so the canonical page is unambiguous.
Senior Developer Experience Writer 1 hour
Make it AI-readable
A clean markdown version in llms.txt so assistants quote the current page.
Senior Developer Experience Writer 2 hours
Seed it honestly
The DR shares it in the Vercel and Temporal communities as a resource, not an ad.
Developer Relations Manager ongoing
Why it works
Publish one authoritative, regularly dated page that lays out the four ways to keep an AI session alive across a dropped connection (the Vercel AI SDK resumable-stream, Vercel Workflow DevKit, build-your-own on SSE, and Ably AI Transport), what each covers and does not, with a decision table and runnable snippets. Written to be quoted by AI assistants, not just ranked.
The DevRel role is hired to make AI Transport known to developers who "ask AI assistants which realtime infrastructure to use" and already names LangGraph reconnection failures and Temporal objections. A single honest comparison is the page an assistant cites and a developer forwards.
Risks and how to handle them
Reads as marketing in a developer community
Lead with the cases where Ably is the wrong choice; credibility is the point.
Evidence
- HiringDeveloper Relations Manager: "Ably hasn't had a dedicated DevRel function in some time", so the role builds one; be "the feedback loop between developers and Ably", build a genuine presence in the Temporal and Vercel communities, and get "Ably showing up accurately when developers ask AI assistants to support technical evaluations and builds". Developers now choose infrastructure on "what AI assistants tell them, not search rankings alone".Source
- Your websiteThe blog has a deep AI Transport series (why AI agents need a durable session layer, Vercel AI SDK production session layer, Temporal workflow streams, OpenAI Responses API, mid-run steering, database hydration) and a long-form "Vercel AI SDK resumable stream: what it covers and what it doesn't" explainer.Source
- Your websiteAI Transport (ably.com/ai): a durable session layer that keeps an AI session alive across dropped connections, tab switches, device changes and crashes, with resumable streaming, mid-response steering and multi-agent coordination; integrates the Vercel AI SDK, LangGraph, Temporal and ag-ui and the OpenAI, Anthropic and Google models. A free proof-of-concept tier gives 500 MAUs with no card; self-serve starts at $29/month; the AI support chatbot pricing example is about $109.50/month.Source
- Your websiteTwo near-identical AI-stack explainers exist at ably.com/vercel/... and ably.com/topic/ai-stack/..., both with the canonical set to the /vercel/ URL. The /compare pages are generated in bulk, including many rival-vs-rival pairings that do not mention Ably (for example amazon-eventbridge-vs-pubnub).Source