Building SaaS on Bluesky & the AT Protocol: A Comprehensive Market Analysis

Section 1: Bluesky Current State (February 2026)

User Numbers

Growth Trajectory

Key pattern: Growth is event-driven, not organic. Each “X exodus wave” brings a spike, followed by significant churn. The platform went from adding ~5M users/month at peak (Nov 2024) to ~1.6M/month by mid-2025.

The Twitter/X Exodus Waves

1. Apr 2023: NPR leaves X over “state-affiliated media” label controversy
2. Sep 2023: Musk teases X paywall; modest Bluesky influx
3. Aug 2024: Brazil bans X; Bluesky downloads hit 420K/day
4. Oct 2024: Musk weakens X block feature; +500K users in one day
5. Nov 2024: US presidential election; +1M users in one week, then +7.5M over 19 days (largest wave)
6. Nov 2024: The Guardian stops posting on X; European Federation of Journalists (300K members) announces departure
7. Late 2024–2025: Scientists, academics, and medical community mass-migrate to Bluesky
8. Jan 2026: Deepfake controversy on X; Bluesky downloads +49% week-over-week (19.5K to 29K iOS downloads/week in US)

Revenue & Monetization Status

• Current revenue: Effectively $0. Bluesky does not generate meaningful product revenue
• Funding raised: $36M total ($8M seed + $15M Series A led by Blockchain Capital in Oct 2024 + other rounds). Board member: Kinjal Shah (Blockchain Capital)
• Planned monetization: Bluesky+ subscription at ~$8/month or $72/year (leaked mockup from GitHub). Features: longer videos, custom app icons, profile badges, avatar frames, color themes, inline translations, post analytics, bookmark folders
• Philosophy: No ads, no tokens, no crypto, no NFTs. Will not “hyperfinancialize the social experience.” Premium won’t boost visibility of paid users’ posts
• Creator monetization: Pushed back at least 12 months due to payment system complexity. Creators currently use Patreon, Ko-fi, Substack externally

Team Size

• Full-time employees: ~25 (up from 20 in Nov 2024)
• Contractors: ~100 (primarily content moderators)
• Planning to grow to: 30 FTEs
• Key constraint: Only about 6 people dedicated full-time to building app features
• Structure: Fully remote team; PBC (Public Benefit Corporation)

Platform Comparison (Feb 2026)

Context: Threads doubled from 200M to 400M MAU in under a year. Mastodon peaked at 2.6M MAU in Nov 2022, now below 690K—a cautionary tale for decentralized platforms. X remains dominant by raw numbers despite post-Musk turbulence.

Geographic Distribution

• United States: 42–56% of users
• Brazil: ~11%
• United Kingdom: ~7–7.5%
• Japan: ~6–7%
• Germany: ~3%

Demographics

• Age: 62%+ under 35. 35% aged 18–24, 28% aged 25–34
• Gender: 66.5% male (developer-skewed early adopter base)
• User types: Indie journalists, long-form writers, developers, academics, scientists, artists, zine-makers. Strong presence of news outlets breaking stories. More than half are passive consumers (lurkers)

Engagement Reality Check

• Engagement rates: 1.5–4% for micro-accounts (<5K followers); 6–10% for highly niche, engaged communities
• Median engagement: 4 interactions per post (same as X and Threads, per Buffer’s 1.7M post analysis)
• Retention rates: 1-day retention ~40%, 7-day ~28%, 30-day ~18%
• Post volume decline: Daily posts dropped from peak of 1.48M (Nov 19, 2024) to ~500K (Jun 2025)—a ~66% decline. Daily likes from 2.79M peak to ~998K
• Culture: Conversation quality over content volume. A post with 50 replies and 10 likes is valued more than 100 likes and 2 replies

2026 Roadmap (from Bluesky’s official blog)

• Better Discover feed with topic tags
• Improved “who to follow” recommendations
• Real-time event features (sports, elections)
• Drafts (already shipped Feb 2026)
• Better media handling (longer videos, faster uploads, more than 4 photos)
• Easier thread creation
• Live badges for streamers (LIVE Now feature, linking to Twitch/Streamplace)
• Curation tools for timely custom feeds during live events

Section 2: The AT Protocol — Technical Foundation

What Is the AT Protocol?

The Authenticated Transfer Protocol (“ATP” or “atproto”) is a decentralized social networking protocol developed by Bluesky Social PBC. Unlike traditional social platforms where a single company controls the data, algorithms, and access, AT Protocol separates these concerns into independent, interoperable services.

AT Protocol vs. ActivityPub (Mastodon)

Core Architecture

The AT Protocol consists of three main services:

1. Personal Data Servers (PDS): Host user repositories and media. Serve as the network access point for users. A single PDS can host 1 to hundreds of thousands of accounts. Users can self-host on modest hardware. Bluesky runs the largest PDS, but anyone can run their own.
2. Relays (formerly “Big Graph Servers” / BGS): Crawl the network, subscribe to multiple PDSes, and output a combined “firehose” event stream. Downstream services subscribe to this single firehose to get all network events. Functions as both a relay (rebroadcasting) and full-network mirror (storing all repo contents).
3. App Views: Semantically-aware services downstream from a Relay. Assemble feeds, aggregate data, and produce views that enable apps to show curated content to users. Analogous to a prism that takes in the Relay’s raw firehose and outputs usable views.

Data flow: All PDSes → Relay → App View → App (your phone)

The Firehose

The firehose is an aggregated real-time stream of all public data updates in the entire network, accessible via WebSocket at the com.atproto.sync.subscribeRepos endpoint. No authentication required. Produces hundreds of events per second. Completely free to consume.

JetStream: A lighter-weight alternative introduced by Bluesky that relays all messages via WebSockets in JSON format for a fraction of the payload size. Official Jetstream instances available for free, no auth needed.

Who uses the firehose: Feed generators, labelers, bots, search engines, analytics tools, real-time monitoring tools (like Firesky.tv), generative art projects, trend analysis systems, and social listening tools.

Custom Feeds (Algorithmic Choice)

• 50,000+ custom feeds exist on Bluesky
• Anyone can create a feed generator service that provides a custom algorithm
• Users can subscribe to and switch between feeds freely
• Vast majority of feeds are built by independent third-party developers
• Examples: cat photos, NBA content, news aggregation, gaming, art, politics, fitness
• Graze alone powers 4,500 feeds from ~3,000 creators

Labelers and Moderation (Ozone)

• Ozone: Open-source tool for collaborative content labeling and moderation
• Individuals and teams can run independent moderation services
• Users subscribe to labelers on top of Bluesky’s default moderation
• Custom labels can be created with custom behaviors (hide, warn, flag)
• Multiple people can manage a moderation service together
• Examples: phobia warnings, Twitter cross-post labels, AI-generated image labels, spoiler warnings, joke labels (beans)
• “Stackable moderation”: users combine multiple labelers to customize their experience

Identity System

• Handles: DNS domain names that resolve to a DID (e.g., @yourdomain.com)
• DIDs (Decentralized Identifiers): W3C-standard secure, stable IDs. Two methods supported:
  • did:plc — novel method developed by Bluesky
  • did:web — W3C standard based on HTTPS/DNS
• Custom domain handles: Use any domain you own as your handle; acts as decentralized verification
• Account portability: DID-based identity means your account can move between servers without losing identity or followers

Lexicons (API Schema)

• Strongly-typed schemas defining record types, API routes, and extension points
• New lexicons must be identified under a domain you control
• Enforces predictable data formats across the ecosystem
• Custom schemas allow third-party apps to define new record types stored in user repositories

API Access: Bluesky vs. X

Developer SDKs

GitHub activity: The main bluesky-social/atproto repo has 8,900+ stars. The organization has 37 repositories. Active developer community with discussions, grants, and conferences.

Section 3: Existing Bluesky Ecosystem & Third-Party Tools

Analytics & Monitoring

Social Media Management Platforms Supporting Bluesky

Feed Generators & Custom Feeds

Graze is the standout story here. It is one of the only platforms monetizing custom Bluesky feeds, doing so with Bluesky’s blessing. The ads are not targeted by personal data but by feed topic. Feed operators choose which ads appear, how often, and at what price. This is the closest thing to an advertising ecosystem on Bluesky.

Third-Party Clients & Apps

AT Protocol Apps (Beyond Bluesky)

Cross-Posting & Automation Tools

• Buffer: Official Bluesky partner. Cross-post + schedule alongside other platforms
• dlvr.it: Bluesky automation; connect Substack → Bluesky automatically
• Circleboom: RSS feed → Bluesky posts
• rss.app: Bluesky-to-RSS and RSS-to-Bluesky integration
• Sky Follower Bridge: Browser extension to find X followers on Bluesky and follow them
• Zapier/Make/n8n: Bluesky automations via workflow builders

Bots

• 21 bots in Bluesky’s official community showcase
• Types: Earthquake magnitude alerts, photo archive bots, legal bots (The Big Cases Bot, Antitrust Bot by American Economic Liberties Project), tech bots, AI-related bots
• Bot problem: Porn bots, impersonation bots (44% of top 100 accounts have doppelgangers, only 16% labeled), partisan division bots, LLM-authored reply bots
• Framework: bsky-event-handlers (TypeScript framework for building Bluesky bots)

Embeds & Integration

• Bluesky supports oEmbed for post embedding on websites/blogs
• embed.bsky.app generates embed code snippets
• HTML metadata enables automatic oEmbed discovery in third-party CMS platforms
• Third-party Bluesky Feed widgets available for websites

Developer Ecosystem Support

• AT Protocol Grants: $10,000 in microgrants ($500–$2,000/project). Must be open source. Paid via GitHub Sponsorships. No longer accepting applications as of 2025
• AWS Activate: $5,000 in AWS credits for atproto developers
• Skyseed Fund: World’s first VC fund/incubator for Bluesky ecosystem. $1M+ committed capital. Grants of $5,000–$25,000. Founded by Peter Wang (open source veteran)
• ATmosphere Conference: First in-person AT Protocol conference. Seattle, March 22–23, 2025. 179 in-person + 186 livestream attendees. Bluesky CTO Paul Frazee keynoted

Section 4: The Business Case — Why Build on Bluesky?

1. Free, Open API (vs. $42K/Month on X)

This is the single biggest structural advantage. X charges $5,000–$42,000/month for API access. Bluesky’s entire API—including the full network firehose—is free and requires no authentication for read access. This eliminates the primary cost barrier that killed dozens of Twitter-based businesses in 2023.

2. Designed for Third-Party Development

Unlike Twitter, which progressively locked down its API from 2012 onward, the AT Protocol is architecturally designed to enable third-party apps. Custom feeds, labelers, clients, and entirely new social apps are first-class citizens of the protocol. Bluesky has funded developer grants, held conferences, and partnered with tools like Buffer.

3. Developer-Heavy Early Adopter Community

66.5% male, 62% under 35, heavy representation of developers, academics, journalists, and tech workers. This is the exact demographic that early-adopts tools, gives feedback, and builds word-of-mouth. It mirrors early Twitter (2007–2010), which spawned a $100M+ ecosystem of tools before the API lockdown.

4. The “Twitter API Apocalypse” Displacement

In February 2023, Twitter killed free API access, destroying Tweetbot, Twitterrific, and hundreds of other apps. Developers who built Twitter tools for years were suddenly without a platform. Many are now looking for alternatives. Bluesky is the most developer-friendly option.

5. Open Protocol = Structural Protection Against Platform Risk

If you build on Twitter’s API, Twitter can change the rules overnight (and has, repeatedly). The AT Protocol is an open standard, now being standardized through the IETF. Even if Bluesky the company disappeared, the protocol would continue. Your app talks to the protocol, not to a company’s proprietary API.

6. Comparison with Early Twitter Ecosystem

Early Twitter (2007–2012) spawned multiple successful businesses before the API crackdown:

• TweetDeck: Acquired by Twitter for $40M (2011)
• Buffer: Started Twitter-first; now $22.6M ARR across 7+ platforms
• Hootsuite: Built on Twitter API; now $350M revenue, $690M valuation
• Sprout Social: Public company (Nasdaq: SPT); ~$455M revenue

Bluesky in 2026 feels like Twitter in 2008–2010: small but growing, developer-friendly, with a vibrant ecosystem forming. The critical difference is that AT Protocol is an open standard, not a proprietary API.

7. Weak Competition in the Bluesky Tools Space

Most existing Bluesky tools are free, community-built side projects. Very few are monetizing. The ones that are (BlueSkyHunter at $15–$29/mo, Graze with $1 CPM ads) are early and underbuilt. There is massive white space for polished, paid tools.

Section 5: Historical Precedent — Building on Social Platforms

Winners: Social Platform Tool Businesses

Casualties: Killed by Platform Changes

The Key Insight: Why AT Protocol Is Structurally Different

Every casualty above was killed by the same mechanism: a single company changed its proprietary API terms. The AT Protocol is fundamentally different:

• Open standard: Being standardized through the IETF (Internet Draft Sep 2025; Working Group charter Jan 2026)
• No single gatekeeper: Multiple PDSes, Relays, and App Views can operate independently
• Data portability: Users own their data and can move between providers
• Protocol, not permission: Your app talks to the protocol, not to Bluesky’s API specifically

However: In practice, Bluesky still operates the dominant Relay and App View. True federation is still evolving. The “open protocol” protection is real in theory but untested at scale.

Section 6: What SaaS Products Could Work on Bluesky?

The global social media management market is valued at $30–36B (2025–2026), growing at 14–17% CAGR. The social media analytics market is $10–16B, growing at 24–27% CAGR. Even a tiny slice of these markets, focused on Bluesky’s 40M users, could sustain a bootstrapped business.

Tier 1: Highest Viability (Clear demand, proven models, path to revenue)

Tier 2: Strong Potential (Clear need, less proven monetization)

Tier 3: Speculative (Interesting but unproven market)

Section 7: Risks & Challenges

1. Is Bluesky Growing Fast Enough?

Growth has decelerated from 5M users/month (peak Nov 2024) to 1.6M/month (mid-2025). Post volume has declined ~66% from peak. Daily likes down ~64%. The platform adds users but many don’t stick. With 30-day retention at 18%, Bluesky has a “revolving door” problem.

Counter-argument: 40M registered users with ~4M DAU is still meaningful. The platform continues to grow at ~0.5 users/second. Event-driven growth spikes will continue as long as X remains controversial.

2. Threads Competition

Meta’s Threads has 450M MAU and 137–150M DAU—more than 10x Bluesky on every metric. Threads doubled its user base in under a year (200M → 400M). It has Instagram’s built-in distribution and Meta’s ad infrastructure. For brands and mainstream users, Threads may be the “good enough” X alternative.

Counter-argument: Threads is a Meta product (centralized, algorithmic, data-harvesting). Bluesky appeals to a different audience: those who value openness, decentralization, and algorithmic choice. The two may coexist rather than compete directly.

3. The Mastodon Cautionary Tale

Mastodon peaked at 2.6M MAU in November 2022, now below 690K—a 73% decline. The “decentralized social network” pitch wasn’t enough to retain mainstream users. Difficulty recreating social graphs, confusing server selection, and arbitrary moderation drove people away.

Counter-argument: AT Protocol is architecturally superior to ActivityPub for user experience. Global namespace (no server confusion), account portability, algorithmic choice, and a single-app UX that hides protocol complexity. Bluesky has already surpassed Mastodon’s peak by an order of magnitude.

4. Monetization Uncertainty (Will Bluesky Eat Third-Party Tools?)

Bluesky’s 2026 roadmap includes features that overlap with third-party tools: better discovery, post analytics (in Bluesky+ mockup), drafts (shipped), and real-time event features. As Bluesky grows its team (from 25 to 30+ employees), the feature surface will expand.

Counter-argument: With only ~6 engineers building app features, Bluesky can’t build everything. The AT Protocol is explicitly designed to delegate functionality to third parties. Bluesky has partnered with Buffer rather than building their own scheduling. The cultural commitment to ecosystem support is genuine (grants, conferences, Skyseed fund).

5. Will X Stabilize?

X still has 540–570M MAU. If Musk’s leadership stabilizes or improves, the exodus could slow. Most “news influencers” who joined Bluesky are still more active on X. X’s network effects are powerful.

6. Protocol Maturity

AT Protocol is still evolving. OAuth support is just arriving. Custom schemas are still being defined. True federation (multiple independent Relays and App Views) is not fully realized. The IETF standardization process just started in Jan 2026.

7. Business Viability of Small Social Networks

Can a 40M-user platform with 4M DAU support a SaaS ecosystem? For context: social media management tools that survive tend to be multi-platform. Building on Bluesky alone limits your TAM. The “build for Bluesky + others” strategy is more defensible.

8. Post Volume and Engagement Decline

This is the most concerning signal. Despite adding users, Bluesky’s daily post volume fell from 1.48M (Nov 2024 peak) to ~500K (Jun 2025). A Pew Research Center analysis showed engagement fell ~50% from its peak. If the active core shrinks, the tooling market shrinks with it.

Section 8: The Bootstrapper Playbook

Strategy 1: Start Free, Convert to Paid

The Bluesky ecosystem values free, open-source tools. The most successful tools (ClearSky, SkyFeed, Blueview) are free. This means:

• Launch a free tool that solves a real pain point
• Build an audience and reputation within the Bluesky community
• Add premium features behind a paywall once you have users
• Example: BlueSkyHunter launched free analytics + $15/mo for scheduling and DMs
• Example: Graze launched free feed builder + ad monetization for feed creators

Strategy 2: Build for Two Platforms (Bluesky + X, or Bluesky + Mastodon)

This is the most defensible approach. It solves the “Bluesky is too small” problem while capturing the “Bluesky is the most developer-friendly” advantage.

• Bluesky + X: Largest addressable market. Most users are on both. X API is expensive ($5K–$42K/mo), so you’re offering value by bridging both
• Bluesky + Mastodon: “Decentralized social” positioning. Smaller market but ideologically aligned
• Bluesky + Threads: The two fastest-growing X alternatives. Threads API is limited, though

Strategy 3: Build in Public on Bluesky as Marketing

Bluesky’s culture is uniquely receptive to “building in public.” SaaS founders who build in public grow audiences 3x faster than those who don’t (per Hypefury). The platform values:

• Transparency and authenticity over polish
• Conversation over broadcasting
• Contrarian takes that challenge conventional wisdom
• Behind-the-scenes content showing process and failures

Content mix: 60% value-driven (tips, insights, UGC), 30% community engagement (replies, conversations, reposts), 10% direct promotion.

Strategy 4: Open Source as Growth Strategy

The Bluesky ecosystem is heavily open-source. The protocol itself is open. Developer grants require open-source. Consider open-core: free open-source tool + paid cloud hosting/premium features.

• Benefit: Community trust, contributions, and word-of-mouth
• Monetization: Managed hosting, premium analytics, team features, SLA support
• Example from outside Bluesky: Plausible Analytics, PostHog, Sentry

Strategy 5: Community-First Approach

Bluesky thrives on community. Build your tool’s community ON Bluesky itself:

• Create a custom feed for your tool’s community
• Create a labeler for your niche
• Participate actively in the ATmosphere developer community
• Apply for Skyseed Fund grants ($5K–$25K) and AT Protocol Grants
• Attend ATmosphere conferences

Pricing Models That Work for Social Tools

Categories with Fastest Path to Revenue

1. Cross-platform scheduling/management: Proven model, proven demand, existing customers willing to pay for multi-platform tools. Add Bluesky support to win customers from Buffer/Hootsuite
2. Analytics/insights: Data is free (firehose). Value is in the presentation and insights. Creators and brands pay for analytics today. Low technical cost to build
3. Social listening/brand monitoring: B2B buyers already budget for this. Free firehose = low infra cost. Bluesky as one of several monitored platforms
4. Feed builder with monetization: Graze has proven the model. Feed creators can earn ad revenue. Builds a marketplace dynamic

Key Numbers for Planning

The Bottom Line

Building a SaaS on Bluesky in February 2026 is a calculated bet on growth. The platform has real users (40M+), a genuinely open API (free), a developer-friendly culture, and structural protection against platform risk (open protocol). The downside is clear: engagement is declining from peak, retention is weak (18% at 30 days), and Threads is growing 10x faster.

The winning formula: Build a multi-platform tool that is Bluesky-first but supports X, Threads, and Mastodon. Use the free Bluesky API to build your product with near-zero data costs. Market by building in public on Bluesky itself. Start free, convert to paid. If Bluesky grows, you’re perfectly positioned. If it doesn’t, your multi-platform support means you can pivot emphasis.

The worst approach: Build something that works ONLY on Bluesky with no path to other platforms. History teaches us that single-platform dependency is the #1 killer of social tools businesses—even when the platform is open.

Sources

• Backlinko: Bluesky Statistics (2026)
• Business of Apps: Bluesky Revenue and Usage Statistics
• Sociallyin: Bluesky Social Statistics 2026
• Adam Connell: Bluesky Statistics 2026
• Sprout Social: Bluesky Growth Statistics 2026
• Social Media Today: Bluesky Reaches 40M Users
• Appfigures: Bluesky App Downloads
• BluePilot: Is Bluesky Dying? Growth Data and 2026 Outlook
• Bluesky Blog: What’s Next at Bluesky (2026)
• Bluesky Blog: Bluesky in 2026 Predictions
• Bluesky Blog: Series A Announcement
• Buffer: Analyzing 1.7M Posts on X, Threads, and Bluesky
• Buffer: December 2025 Shareholder Report
• Sprout Social: Q3 2025 Financial Results
• Latka: Hootsuite Revenue Data
• TechCrunch: Graze Raises $1M, Rolls Out Ads
• TechCrunch: Beyond Bluesky — Apps on AT Protocol
• TechCrunch: Mark Cuban Backs Skylight
• TechCrunch: Skyseed Fund
• TechCrunch: AT Protocol Grants
• TechCrunch: Apollo Shutdown
• Bluesky Docs: Federation Architecture
• Bluesky Docs: Firehose
• Bluesky Docs: Rate Limits
• AT Protocol: SDKs
• AT Protocol: Overview
• GitHub: bluesky-social/atproto
• Social Media Today: Bluesky 38M Users, Post Volume Declining
• TechCrunch: Bluesky 2026 Roadmap
• Backlinko: Number of Threads Users
• Backlinko: X (Twitter) Statistics
• Grand View Research: Social Media Management Market
• Fortune Business Insights: Social Media Analytics Market
• Nieman Lab: Nuzzel-like Tool for Bluesky