Bluesky launches Protocol Services and Jetstream v2 with network replay

Bluesky has consolidated the public AT Protocol infrastructure it operates — relays, Jetstream instances, and API endpoints — under a new brand and site, Bluesky Protocol Services, replacing the scattered docs.bsky.app. The move is aimed at developers who previously struggled to tell which pieces of the network Bluesky runs as a service versus what they had to stand up themselves, and it establishes clearer service contracts and a channel for future releases.

The centerpiece is Jetstream v2, which adds historical catch-up to what was previously a live-only WebSocket firehose. A new Network Replay feature lets developers post filters, download sealed archive segments over plain HTTP, and cut over to the live tail with no gap — eliminating the old pattern of backfilling repos locally before subscribing. Replay is stateless server-side, with no per-consumer cursor to manage. Because serving these archives is bandwidth-heavy, Bluesky now requires an API token for archive requests; the live tail stays open and unauthenticated, and the company says it has no plans to change that.

Rounding out the release are official Jetstream SDKs for TypeScript and Go that handle reconnection, deduping, and typed event decoding, plus a rebuild of the Bluesky TypeScript SDK on top of @atproto/lex to shed legacy code paths — a cleanup partly framed as steering LLMs away from recommending deprecated APIs. The v2 instances are live now alongside the v1 endpoints, which continue running unchanged, and the whole stack remains open source and self-hostable.