Alex Benzer says Bluesky is adding “communities” on the AT Protocol this year

Bluesky, the social platform built on the decentralized AT Protocol, is adding a new feature called “communities” sometime this year, according to Alex Benzer, head of product. The move is simple to describe and big to execute: smaller spaces where people can “go deeper and hang out with people who care about the same stuff.”

Benzer also framed this as a structural shift, not just another UI tweak. He says communities will be built on the decentralized AT Protocol that underpins Bluesky, and that “it’s a new structure for everyone,” part of “Atmosphere,” a shorthand for the AT Protocol ecosystem. In practical terms, Bluesky is about to let users create, join, and post within these community spaces, plus get updates from them, while keeping the core features on Bluesky “simpl...” (the key point being that the central experience stays intact).

Why does this matter for the people running social platforms, networks, and communities? Because “smaller spaces” directly changes the economics of attention. Instead of everything competing on one general feed, communities become engines for tighter clustering: people who already agree on topics, identities, or interests can find each other more easily, and content can circulate faster within a narrower group. That affects growth strategy, moderation priorities, and product metrics. It also changes what users expect to happen next. If you can join a community and get updates, the platform is implicitly training you to treat community membership as a primary navigation layer.

There is also an architectural reason this is news: communities will be built on the decentralized AT Protocol ecosystem. Benzer ties the plan to Atmosphere, meaning the communities are not being positioned as a closed, platform-only feature. In a decentralized setup, the “container” for social interaction can matter as much as the app itself. If communities are part of the AT Protocol structure, that influences how developers, integrations, and future features might plug in. It is the same underlying idea that has driven decentralized social for years: you can build social experiences that are not entirely dependent on one centralized network controlling everything from accounts to data flows.

For boards and executive teams, that raises the question of where power sits. Centralized platforms traditionally control user identity, content rules, and distribution. A protocol-based approach can shift some of that power to the ecosystem, while still leaving the product surface area under Bluesky's control. Benzer’s language, “new structure for everyone,” hints that even the people building and operating inside Bluesky will need to adapt, because the feature is not just launching; it is rethinking the architecture of how social spaces are organized.

Regulatory and policy pressures are also part of the backdrop, even when a feature announcement does not mention them directly. Social platforms today operate under constant scrutiny for moderation, user safety, and content governance. Smaller community spaces can either reduce harm by enabling more targeted rules and culture, or concentrate risk if communities become echo chambers with unclear boundaries. The product design therefore matters, because governance tools, reporting flows, and enforcement mechanisms need to match the community model. If communities allow “go deeper and hang out,” they also allow deeper and more sustained interaction, which typically increases both the upside (belonging, relevance) and the operational complexity (who moderates, how disputes are handled, what happens when content violates policy).

Benzer said the “few ideas we have in mind so far” were listed in a thread, and in that product framing he outlined the basic lifecycle: on Bluesky, users will be able to create communities, join them, post in them, and get updates. That sounds straightforward, but product teams know the hidden work is in the edges. How do communities discover new members? How do notifications avoid becoming spam? How do updates work without overwhelming people? How does the system handle community-level identity and consistency across the decentralized layers? These are the operational questions that determine whether “communities” become a durable engagement driver or just another setting users ignore.

Finally, the strategic stake: Bluesky is not only adding a feature; it is building a social map. If communities take hold, they could reshape competition within the broader social ecosystem by offering something that generalized feeds often struggle to deliver at scale, namely sustained relevance and shared context. For executives and investors watching protocol-based social, the signal is that decentralized infrastructure is moving from theory and identity to everyday product experiences. In other words, the AT Protocol ecosystem is not just hosting accounts and posts. It is being used to define how people gather, and how the platform organizes the “where” of social life. That is a big bet, and it lands directly on Benzer’s “new structure for everyone” comment.