# Why AT Protocol Has No Instances > Understanding why comparing Bluesky to Mastodon is a category error that misses how modern decentralized social media works. - Title: Why AT Protocol Has No Instances · Overreacted — Shortify - Summary: Understanding why comparing Bluesky to Mastodon is a category error that misses how modern decentralized social media works. AT Protocol achieves… - Keywords: atproto, decentralization, bluesky, mastodon, web architecture, technology, design, Protocol, Instances, Overreacted - Source: Overreacted — https://overreacted.io/there-are-no-instances-in-atproto - Read time: 1 min - Topics: atproto, decentralization, bluesky, mastodon, web architecture, technology, design ## The instance question is a mistake Asking where the Bluesky instances are stems from a fundamental misunderstanding of AT Protocol. Instances are a Mastodon concept that simply does not apply. > The problem is, there are no instances in atproto! The question is a category error. ## How RSS got hosting right The early web separated data storage from data viewing. You published posts on your own blog host, and readers consumed them inside aggregators like Google Reader. > Note that hosting and aggregation are two separate things. Your posts don’t 'live' in an app like Google Reader. ## The centralized social trap Platforms like Facebook combined hosting and viewing into a single closed ecosystem. Users traded control over their identity and content for convenience and network effects. > We put a box around the whole thing so that everyone is enclosed in the same space so we can show ads and stuff. ## Mastodon's bundled fiefdom model Mastodon decentralized social media by creating independent mini-networks called instances. Each server bundles user data hosting together with app logic. > They’re kind of like countries—because you live 'inside' one of them... ## The hidden cost of instances Bundling identity with a specific server creates fragile networks. If an instance shuts down or admins defederate, your identity and social connections disappear permanently. > If your instance goes down, your identity ceases to exist. People who followed you followed you-from-that-instance... ## Erasing the bundled box AT Protocol discards the server-instance bundle completely. It returns to the RSS paradigm: data lives in independent storage while apps aggregate across the network. > In atproto, we cut hosting apart from the aggregation at the network level: There are no instances at all! ## Portable identity and hosting Decoupling hosting means you can migrate your profile to a new data provider whenever you want. Your identity, posts, and followers remain completely intact. > If you want to swap your hosting, you can... Aside from three or four UX snags, it was all automatic. ## Apps as projections of data Developers can build new user experiences without maintaining full database copies. Apps act as custom views built on top of a single shared data atmosphere. > In atproto, every app is a projection of the whole Atmosphere, just like Feedly and Google Reader are projections of the entire Blogosphere. ## Measuring true decentralization Counting instances is a misleading way to evaluate network health. Meaningful decentralization depends on host portability and open app creation. > Coupling hosting and apps was the original sin, and the fix is simple. Keep our stuff outside the apps; let the apps aggregate over it. ## Key takeaway AT Protocol achieves decentralization by decoupling data hosting from app aggregation, rendering Mastodon-style instances obsolete.