If you’ve spent even five minutes in the fediverse, you’ve seen the argument. Someone says, “ATProto has no instances.” Someone else replies, “What do you mean? Bluesky runs on servers, right?” And then it devolves into a semantic flame war that ends with everyone more confused than when they started.
Both sides are wrong. And both sides are right. But the real issue isn’t about definitions — it’s about power. Who controls the boundaries of your online community? Who decides what content is acceptable? Who gets to kick you out?
Strip away the protocol jargon, and that’s what this fight is actually about. Decentralization without boundaries is just centralization with extra steps. And ATProto is making a radical bet that those boundaries never really mattered anyway.
The Architecture of Disappearing Servers
Let’s get the technical part out of the way, because it’s actually elegant. ATProto separates identity from hosting. Your handle — your did — is not tied to any particular server. Your data is replicated across a relay and a personal data server (PDS), but you can move that data without changing who you are. The social graph, the feed, the interactions — all of it lives in a layer that’s independent of the machine that happens to store it right now.
What does that mean for you, the user? It means you don’t care which server you’re on. You don’t choose a community when you join Bluesky — you just choose a service provider. The server becomes like an email host: important for delivery, irrelevant for your identity.
Compare that to ActivityPub, where choosing an instance is a social act. You pick a Mastodon server based on its rules, its vibe, its moderation stance. That choice is part of your identity. On ATProto, that choice is reduced to a technical detail. The server doesn’t disappear. Its meaning does.
The Debate Nobody’s Having
So when people say “there are no instances in ATProto,” they’re technically wrong — servers exist, obviously. But they’re socially right: instances have ceased to be a meaningful unit of community. The federation is still there, but it’s been pushed so deep into the infrastructure that users never touch it.
That’s the part that scares me. Because when you remove the visible instance layer, you don’t eliminate the need for boundaries. You just make them invisible. And invisible boundaries are controlled by algorithms, not by communities.
Moderation doesn’t go away. It goes into a black box. On Mastodon, if you don’t like the rules, you can literally pack your bags and move to another instance. On Bluesky, you can change your PDS, but the moderation feeds and the algorithmic curation are handled by a separate layer — one that’s far more opaque and far less accountable.
This isn’t a bug. It’s a philosophical choice. ATProto is betting that the future of social media is about individual autonomy, not community sovereignty. That you should be able to talk to anyone, regardless of where they’re hosted, and that the community boundaries of the old federated world were holding us back.
The Hidden Cost of Freedom
That sounds liberating. And for many users, it will be. But every architectural decision has a price. When you make instances invisible, you also make them irrelevant. And when instances are irrelevant, no one has a home. No one is responsible for you. No one has a stake in your wellbeing.
Ask any moderator on a large Mastodon server. They’ll tell you that the sense of shared space, of being part of a small town with its own police and courts, is what makes federation work. It’s messy. It’s inefficient. But it’s human.
ATProto optimizes for frictionless connection. In doing so, it sacrifices the very thing that makes social networks feel like communities: friction. Boundaries. The ability to say “this is our space, and you follow our rules.”
When instances become invisible, power doesn’t vanish — it just gets harder to see. And the hardest power to fight is the power you can’t point to.
So Who’s Right?
I’m not going to sit on the fence. The “no instances” crowd is right, but for the wrong reasons. They see the architecture as a technical triumph — and it is. But they miss the social catastrophe lurking inside. The moment you remove the visible instance, you hand the keys to the castle to the people who write the algorithms.
Bluesky’s moderation system is being built with a lot of transparency and community input. I’ll give them credit for that. But the structural risk remains: when the boundaries are hidden, they’re easy to exploit. And unlike a Mastodon admin who has to answer to their users, the people who control the invisible layers have no such obligation.
This is the architectural bet of ATProto. It might pay off. It might create a world where you can move your social graph across providers without anyone noticing, where moderation is a set of composable pieces you can choose from, where the network is truly open and free.
Or it might create a world where the most important decisions about your online life are made by a few opaque algorithms that no one voted for and no one can audit.
I don’t know which world we’ll get. But the next time someone tells you “ATProto has no instances,” don’t just nod. Ask them where the boundaries are. Ask them who gets to draw them. And ask them what happens when the person who draws the lines is the same person who owns the algorithm.
The server didn’t die. It just learned to hide.
FAQ
Q: Does ATProto actually have servers?
A: Yes, of course. There's a relay, a personal data server, and a big graph service. But the point is that servers no longer define your social identity. You can switch providers without changing who you are or losing your network. That's what people mean by 'no instances'—not that hardware vanished, but that the social unit of 'instance' is gone.
Q: What's the practical takeaway for someone building on ATProto?
A: Stop worrying about where data lives and start worrying about how moderation and jurisdiction are enforced. Since users aren't tied to a server, you can't rely on server-level bans or community norms. You need to build robust, portable moderation tools and understand that the network's boundaries are now algorithmic, not administrative.
Q: Isn't this just a semantic debate?
A: No, it's a power shift. When instances are invisible, the people who write the scheduling algorithms and ranking logic become the real gatekeepers. They have no accountability to a community, because there is no community to be accountable to. That's a structural change, not a vocabulary preference.