{"id":23266,"date":"2026-08-14T12:37:47","date_gmt":"2026-08-14T12:37:47","guid":{"rendered":"https:\/\/scannn.com\/introducing-bluesky-protocol-services-at-protocol\/"},"modified":"2026-08-14T12:37:47","modified_gmt":"2026-08-14T12:37:47","slug":"introducing-bluesky-protocol-services-at-protocol","status":"publish","type":"post","link":"https:\/\/scannn.com\/lv\/introducing-bluesky-protocol-services-at-protocol\/","title":{"rendered":"Introducing Bluesky Protocol Services - AT Protocol"},"content":{"rendered":"\n
\n

Today we\u2019re launching Bluesky Protocol Services<\/a><\/strong>: a new brand, and a new website, for the public infrastructure Bluesky operates on the AT Protocol<\/a> network.<\/p>\n

Bluesky has always run more than the Bluesky app. We operate Jetstream instances, relays, and the Bluesky API endpoints built on atproto. But if you were a developer trying to build on that infrastructure, our docs didn\u2019t always make it easy to tell what we run as a service or where to start. We\u2019re fixing that today. Bluesky Protocol Services organizes all the documentation developers need within the ecosystem, clarifies the service contracts around Bluesky-provided infrastructure, replaces the old docs.bsky.app site and gives us a clean way to ship future releases like the ones in this post!<\/p>\n

The headline release shipping alongside the new site is Jetstream v2<\/strong>. Jetstream is the best way for most developers to use the network at scale: you describe the slice you want, and it arrives as plain JSON over a WebSocket. What it couldn\u2019t give you was history<\/em>. If you needed the records that already existed on the network, you had to backfill repos yourself then cut over to the live stream.<\/p>\n

Jetstream v2 adds that capability to the server. It keeps a compressed archive of the whole network and adds a new way to consume it, alongside the live tail:<\/p>\n

Network Replay<\/strong> lets you catch up from any point in the past and cut over to live with no gap. You POST<\/code> your filters to planSnapshot<\/code>, download the sealed segments it returns over plain HTTP, then connect the live WebSocket once at the tip. Replay is stateless on the server<\/strong>, with no per-consumer cursor, no subscription to register, and nothing to stage on the client. Jetstream is your buffer.
\nYou can also just<\/em> snapshot the network \u2014 a point-in-time copy of the archive over HTTP only (listSegments<\/code> + getSegment<\/code>), with no live tail. Same archive, same filters, no WebSocket.<\/p>\n

This unlocks much more sophisticated server-side slicing without ever backfilling locally: you can spin up an App<\/a>, run an analysis over a month of posts, or recover from downtime, all through the same JSON shape as the live tail.<\/p>\n

Serving these archives is bandwidth-intensive. To ensure the service remains reliable and cheap to run, we\u2019re now requiring an API token just for these requests<\/a>. The live tail remains open and unauthenticated, it\u2019s only when you request an archive that we require a token. We have no plans to introduce an auth requirement for the live stream.<\/p>\n

The v2 instances are live now at wss:\/\/jetstream.us-west.bsky.network<\/code> and wss:\/\/jetstream.us-east.bsky.network<\/code>. The existing v1 instances will keep running unchanged for a while, and the live tail behaves identically on both, so there\u2019s no rush to move. Read the full flow in the Network Replay docs<\/a>.<\/p>\n

And! As always, this infrastructure is open source and self-hostable. See Running your own Jetstream<\/a> for details.<\/p>\n

Jetstream is plain JSON, so you never need<\/em> an SDK. But there\u2019s some common glue: reconnecting, deduping, cursor management, decoding events into typed records. Hence, the new Jetstream SDKs<\/strong>: TypeScript and Go clients where you construct a Jetstream<\/code> object, pass a filter, and for await<\/code> over decoded, typed events:<\/p>\n

\n
\n
\n
\n
import<\/span> { Jetstream } <\/span>from<\/span> <\/span>'@bsky\/jetstream'<\/span><\/span>\nimport<\/span> { app } <\/span>from<\/span> <\/span>'@bsky\/sdk\/lexicons'<\/span><\/span>\n\nconst<\/span> <\/span>js<\/span> <\/span>=<\/span> <\/span>new<\/span> <\/span>Jetstream<\/span>(<\/span>'https:\/\/jetstream.us-east.bsky.network'<\/span>)<\/span><\/span>\n\nfor<\/span> <\/span>await<\/span> (<\/span>const<\/span> <\/span>evt<\/span> <\/span>of<\/span> <\/span>js<\/span>.live<\/span>({ collections<\/span>:<\/span> [<\/span>app<\/span>.<\/span>bsky<\/span>.<\/span>feed<\/span>.post] })) {<\/span><\/span>\n  <\/span>if<\/span> (<\/span>evt<\/span>.kind <\/span>===<\/span> <\/span>'commit'<\/span> <\/span>&&<\/span> <\/span>evt<\/span>.<\/span>commit<\/span>.operation <\/span>===<\/span> <\/span>'create'<\/span>) {<\/span><\/span>\n    <\/span>console<\/span>.log<\/span>(<\/span>evt<\/span>.<\/span>commit<\/span>.collection<\/span>,<\/span> <\/span>evt<\/span>.<\/span>commit<\/span>.<\/span>record<\/span>.text)<\/span><\/span>\n  }<\/span><\/span>\n}<\/span><\/span>\n<\/code><\/pre>\n