comparisons beginner ⏱️ 9 minutes

Nostr vs Bluesky: Which Is Actually Decentralised? (2026)

Honest 2026 comparison of Nostr and Bluesky: how each decentralises, who can ban you, moderation, account portability, and what UK regulation means for a protocol versus a company.

Updated: 8 September 2026 By

Introduction

Nostr and Bluesky are the two serious answers to the same question: what replaces Twitter if you no longer trust a single company to run it?

Both call themselves decentralised. Both let you post short messages, follow people and build a following. And both are frequently recommended in the same breath, as though they were variations on one idea.

They are not. They decentralise different things, and the difference decides who can remove you, whether your identity survives a fallout with the people running the infrastructure, and how each one sits under UK regulation.

This guide compares them honestly, including the places where Bluesky is straightforwardly better.

Quick Comparison Table

NostrBluesky
Identity modelA cryptographic key pair that you holdAn account on a server, identified by a DID
Who can ban youNobody from the network; relays can refuse to carry youYour server can suspend you; Bluesky can refuse to federate a server
InfrastructureMany independent relays, run by anyonePDS, Relay and App View, mostly run by Bluesky today
Federation realityDecentralised in design and in practiceDecentralised in design, centralised in practice
ModerationYou choose relays and client-side filtersComposable labelers, plus the platform’s own defaults
Account portabilityTotal: your keys work in any clientPossible in principle, dependent on your server in practice
Network sizeMuch smaller, hard to countRoughly 46 million registered accounts
UX and polishRougher, improving quicklyFamiliar, polished, close to Twitter
PaymentsLightning zaps built into the cultureNone native
UK regulatory exposureNo company to compelA regulable company under the Online Safety Act
Learning curveSteeper: you manage keysGentle: sign up with an email

Two philosophies of decentralisation

This is the heart of it, and almost every other difference follows from it.

Bluesky: decentralised architecture, centralised reality

Bluesky runs on the AT Protocol, which splits a social network into three parts:

  • a Personal Data Server (PDS) that holds your account, your posts and your signing keys
  • a Relay that crawls the network and emits a firehose of everything happening
  • an App View that assembles that firehose into the feeds you actually read

This is a genuinely thoughtful design. Federation with third-party servers opened in early 2024, and an IETF working group was chartered in January 2026 to standardise the protocol, which matters: a standard with a life outside one company is harder to quietly close.

The gap is between design and deployment. Today the overwhelming majority of Bluesky users are on Bluesky’s own bsky.social servers, and the Relay and App View that most people depend on are Bluesky’s too. Self-hosting a PDS is possible, and people do it, but it operates under account and rate limits, and Bluesky can decline to federate with a server it does not want to carry.

So the honest summary is that Bluesky is decentralised in architecture and centralised in practice. The escape hatches exist. Almost nobody uses them, and the company retains a decisive position in the middle.

Nostr: decentralising identity itself

Nostr starts from a different place. Your identity is not an account on a server. It is a key pair: a public key that others follow, and a private key that signs everything you publish.

Relays are deliberately unambitious. They are store-and-forward pipes that accept signed messages and hand them out again. They hold no authority over who you are, because your identity was never issued by them in the first place.

That inversion is the whole argument. On Bluesky, decentralisation is a property of the infrastructure, and your identity depends on some server honouring it. On Nostr, decentralisation is a property of the identity, and the infrastructure is interchangeable.

It is simpler, genuinely decentralised, and noticeably rougher to use.

Where Bluesky is genuinely stronger

A comparison that cannot name the other side’s strengths is not worth reading.

Scale. Bluesky has roughly 46 million registered accounts. Nostr is much smaller, and harder to count honestly, because it is a protocol rather than a platform and nobody sits in a position to count it. If your priority is finding an existing audience, Bluesky is the larger room by a wide margin.

One nuance worth stating, because it cuts against the simple story: Bluesky’s active base is not tracking its registration count. Third-party measurement put its mobile app at around 10.4 million monthly active users in June 2026, down about 27% year on year. Bluesky does not publish active-user figures itself, so treat outside estimates with appropriate caution. Registered accounts and engaged users are drifting apart.

Onboarding. Bluesky’s sign-up is an email address and a password. Nostr’s is a key pair you are responsible for forever. For most people, most of the time, Bluesky’s is the better first experience, and pretending otherwise helps nobody.

Composable moderation. This is Bluesky’s most interesting contribution, and Nostr has nothing equivalent. Bluesky’s labeling system lets independent moderation services publish labels that users can subscribe to, so moderation becomes a marketplace of opinions rather than one company’s ruling. It is a real advance in the design of moderation, and it deserves credit.

Polish. Bluesky feels like Twitter. Threading, search, notifications and media handling all work the way people already expect.

Where Nostr is stronger

You actually hold your identity. Not a claim on an account. The keys are yours, they exist independently of any company, and they work in every client that speaks the protocol.

Censorship resistance that survives contact with a hostile operator. If a relay refuses your posts, publish to a different one, or run your own. Your followers still follow the same public key. Nothing about your identity depended on the relay that rejected you. On Bluesky, losing your server means engaging a migration process that depends on cooperation you may not get.

No company to capture or compel. There is no Nostr Inc. This is the point most comparisons miss, and the section on UK regulation below is where it stops being abstract.

Value transfer that works. Lightning zaps let readers send small payments directly to authors, instantly, with no intermediary taking a cut. Bluesky has no native equivalent.

Moderation you choose. Nobody imposes a default set of values on your feed, because there is no central operator positioned to.

Moderation, compared

These are two coherent and genuinely different answers, and which is better depends on what you want.

Bluesky offers structure. The labeling system is composable and independent moderation services can operate within it, which is a real strength. But the operator still sets defaults, and defaults are what the vast majority of users ever experience. The values of the company running the App View shape the feed most people see.

Nostr offers no structure and no imposed culture. You choose your relays, and your client filters what you would rather not see. The strength and the weakness are the same fact: nobody curates for you. That means no company can impose its politics on your feed, and equally that a new user gets less help than Bluesky gives them.

Bluesky’s approach is better engineered. Nostr’s is harder to capture. Both statements are true at once.

Identity and account portability

Bluesky uses DIDs, and did:plc identifiers are designed so an account can move between servers. In principle this is real portability, and it is a meaningful improvement on the traditional platform account.

In practice the signing keys are usually managed by your server. Moving therefore depends on that server cooperating, which is exactly the situation portability is supposed to protect you from. Portability that requires the incumbent’s goodwill is weaker than it sounds.

Nostr’s answer is blunter and stronger: your private key is the account, so there is nothing to migrate. Paste it into another client and you are already there, with your followers intact.

The trade-off is severe and worth stating plainly. There is no password reset on Nostr. Lose the private key and the identity is gone, permanently, with nobody to appeal to. Bluesky can recover your account; Nostr cannot, and that is the direct cost of nobody holding it on your behalf. If you value a safety net over sovereignty, that is a legitimate preference, and Bluesky serves it better.

The UK angle: regulating a company versus a protocol

This is where the architectural difference produces a concrete, practical divergence, and it is the clearest illustration of what “decentralised” is actually worth.

The UK’s Online Safety Act is in active enforcement. Ofcom’s Protection of Children Codes took effect on 25 July 2025, and in June 2026 the Government confirmed it will bar under-16s from mainstream social media from Spring 2027, delivered through secondary legislation under the Children’s Wellbeing and Schools Act rather than a new Act. Services named in the announcement include Snapchat, TikTok, Instagram and YouTube. Separately, 16 and 17 year olds will get a default overnight curfew between midnight and 6am with notifications muted, and Ofcom has been asked to research how services might detect VPN traffic used to bypass these rules.

Read that list of obligations again and notice what every one of them requires: a company. A legal entity that can be fined up to £18 million or 10% of global turnover, ordered to verify ages, or blocked in the UK.

Bluesky is such an entity. It is a company operating a platform, which puts it squarely within the Online Safety Act’s scope and makes it the type of service these rules are designed to capture as it grows. It is not on the named list today, and the straightforward explanation is size rather than anything suspicious: the named services are the largest platforms, and Bluesky is an order of magnitude smaller. That is a threshold, not a carve-out, and thresholds move as services grow.

Nostr is not such an entity. There is no company to serve notice on, no central account database to age-verify against, and no service to block. This is a structural fact, not a loophole, and it is worth being precise about what it does and does not mean. Regulation can still reach clients, because apps in the App Store and Play Store have publishers who are companies with obligations. What it cannot reach is the protocol itself: relays can be run anywhere by anyone, and a user can always run their own.

So the two systems are not merely differently decentralised. They are differently regulable, and that difference is not a matter of policy or good intentions. It follows from the architecture.

For more on this, see our guide to the Online Safety Act and Nostr.

Which should you choose?

Choose Bluesky if you want a Twitter-like experience that works today, you want to find an existing audience, you value polished onboarding and a safety net on your account, and you are comfortable with company-run infrastructure and curated defaults.

Choose Nostr if you want to own your identity outright, you want censorship resistance that holds even when an operator turns hostile, you care about Lightning payments, or you want a system that no regulator can compel because there is nothing at the centre to compel.

Use both if you are like most people who have thought about this seriously. They are not mutually exclusive. Many use Bluesky for reach and Nostr for ownership, and there is nothing incoherent about that.

Conclusion

Bluesky is the more polished product with the larger network and the more sophisticated moderation design. If those are your priorities, it is the better choice today, and this guide is not going to pretend otherwise.

But the two “decentralised” labels are not equivalent, and the difference is not cosmetic. Bluesky decentralises infrastructure while a company retains the decisive position in the middle. Nostr decentralises identity, which is the part that determines whether anyone can take your account away.

If what you want from decentralisation is a better-run platform, Bluesky delivers it. If what you want is the guarantee that no company or regulator sits between you and your own identity, only one of these two is built to provide it.

Ready to try Nostr? Get started here and see how it feels to hold your own identity.


Related Guides:

Frequently asked questions

Is Bluesky actually decentralised?

Partly. Bluesky runs on the AT Protocol, which is decentralised by design: anyone can in principle run a Personal Data Server, Relay or App View. In practice it is highly centralised today, because the vast majority of users and infrastructure sit with Bluesky's own servers, self-hosting is constrained by account and rate limits, and Bluesky can decline to federate. Nostr, by contrast, ties your identity to a key pair rather than a server, so no single company sits in the middle.

Can you be banned on Nostr like on Bluesky?

Not in the same way. On Bluesky your account lives on a server, usually bsky.social, that can suspend it, and Bluesky can refuse to federate entire servers. On Nostr your identity is a cryptographic key that no relay owns, so if a relay refuses your posts you publish to others or run your own. Individual relays and clients still moderate what they carry, but nobody can delete your identity from the network.

Will the UK under-16 social media ban affect Nostr and Bluesky?

They sit very differently under UK regulation. Bluesky is a company running a platform, so it falls under the Online Safety Act and is the type of service the under-16 rules are designed to capture as it grows, with those rules taking effect from Spring 2027 and enforced by Ofcom. Nostr is an open protocol with no company at its centre, so there is no single entity for a regulator to compel. Age-assurance pressure can only reach individual apps, while relays and self-hosting route around it.