Bluesky launched Bluesky Protocol Services on August 13, 2026, delivering unified infrastructure for the decentralized AT Protocol network. The release features Jetstream v2 with Network Replay for historical data access, new TypeScript and Go SDKs, and a restructured codebase designed to lower barriers for developers building open-network applications.
Decentralized social architectures have long suffered from a structural friction point: data accessibility. Historically, developers querying the AT Protocol network faced a rigid bifurcation. You either spun up local repositories to backfill historical states or hooked directly into the live WebSocket firehose, leaving a frustrating blind spot for anyone needing chronological depth without local storage overhead. According to Alex Garnett of Bluesky, this move directly addresses a persistent ecosystem bottleneck, noting that previous documentation made it difficult to determine what ran as a managed service or where to begin building.
Jetstream v2 and Network Replay Architecture
The core engineering achievement in this deployment is Jetstream v2, anchored by a feature called Network Replay. Instead of forcing clients to maintain local databases of historical records, the updated server architecture maintains a compressed archive of the entire network state. It serves this data via two distinct modes: HTTP-segmented downloads or a combined stream that merges historical replay seamlessly into the live WebSocket feed.
Under the hood, the server-side implementation remains stateless. There are no consumer-specific cursors, no registration subscriptions, and zero provisional client storage required to process deep archives. Developers can now execute complex server-side analytics spanning months of historical posts, recover gracefully from extended downtime, or generate precise network snapshots on demand. To safeguard this resource-intensive infrastructure against scraping abuse, Bluesky now enforces API token authentication exclusively for archive requests, while leaving the real-time live stream completely open and unauthenticated at endpoints like wss://jetstream.us-west.bsky.network.
Streamlined SDKs and Lexicon Hygiene
Raw infrastructure requires ergonomic tooling to gain traction among engineering teams. Alongside Jetstream v2, the platform released dedicated SDKs for TypeScript and Go. While Jetstream communicates natively via flat JSON payloads, these software development kits abstract away the operational overhead by automatically managing socket reconnections, event deduplication, cursor tracking, and event decoding into strongly typed records.
Consider the simplicity of the updated TypeScript implementation:
import { Jetstream } from '@bsky/jetstream'
import { app } from '@bsky/sdk/lexicons'
const js = new Jetstream('https://jetstream.us-east.bsky.network')
for await (const evt of js.live({ collections: [app.bsky.feed.post] })) {
if (evt.kind === 'commit' && evt.commit.operation === 'create') {
console.log(evt.commit.collection, evt.commit.record.text)
}
}This developer ergonomics upgrade extends deep into the core libraries. The primary Bluesky TypeScript SDK has been rebuilt entirely on top of @atproto/lex, cleanly purging legacy code paths that were historically tied specifically to Bluesky. This technical hygiene eliminates obsolete patterns and ensures that modern AI coding assistants stop recommending deprecated SDK structures to developers.
Unified Documentation and Endpoint Expansion
Infrastructure is only as good as its reference manuals. The entire developer portal has shifted to a newly organized structure at bsky.network, effectively replacing previous documentation at docs.bsky.app. Accompanying this portal redesign, the HTTP reference directory at endpoints.bsky.app incorporates explicit methods for the newly minted network.bsky.jetstream.* namespace.
Engineering teams gain direct programmatic access to robust primitives including planBackfill, listSegments, getSegment, and getBlock, complete with strict JSON schemas for request and response cycles. By consolidating these WebSocket endpoints and HTTP archival tools into a single source of truth, Bluesky is positioning the AT Protocol as a predictable alternative to walled-garden social APIs.
Operational Impact for Independent Builders
- Data Analytics: Startups specializing in market intelligence, trend tracking, or automated moderation can now ingest months of historical network data via Jetstream v2 without standing up complex local ingestion pipelines.
- Reduced Time-to-Market: The new Go and TypeScript SDKs handle low-level WebSocket management, cutting weeks of boilerplate setup time for client applications and automated bots.
- API Independence: Building on open lexicons shields early-stage companies from arbitrary monetization pivots or policy shifts imposed by centralized platform operators.
The maturation of open networking infrastructure points toward a future where developers can treat decentralized social graphs with the same reliability as traditional cloud databases. As teams begin stress-testing Network Replay and integrating the revised SDKs, the viability of open-protocol applications shifts from theoretical promise to production reality.
