Decentralized server

Everything a server does, without a single off switch.

Read the manifesto Build on Swarm

100%

Download availability

100%

Upload availability

7.5 MiB/s

Download speed

Why Swarm exists

Web2 problems, architectural answers

Each of these problem spaces exists because centralized infrastructure makes it structurally unavoidable. Here's what changes when the infrastructure does.

The problem

You bookmarked something important. An article, a tool, a piece of history. One day you went back and found a 404. The content existed. Someone decided it shouldn't anymore.

Swarm’s answer

Content is addressed by what it is, not where it lives. Every chunk is identified by a hash of its own content — so it can be served by any node that holds it. No origin server to seize. No URL that breaks when a company shuts down.

The problem

On August, 2022, a developer was arrested for writing code. Within hours, Infura blocked access, and GitHub erased the repository. The blockchain itself was untouched, but the application had vanished.

Swarm’s answer

Content published to Swarm is addressed by what it contains, not where it lives. Any node holding the chunks can serve it. There's no hosting account to suspend, no API to block, no company to pressure into taking it down.

The problem

You clicked "accept all." You always do. In the small print you'd already signed over your data — your age, your politics, your fears, your habits. The free service was never free. You were the product.

Swarm’s answer

ACT encrypts at the chunk level — access is controlled cryptographically, by the person who published the data. No platform owns what you store. No algorithm decides what you see. The popup is a symptom of architecture. Swarm changes the architecture.

The problem

Go viral in the early web and you paid for it — bandwidth bills that scaled with every new reader, until the page went offline under the load. The platforms solved that. In exchange, they kept the audience.

Swarm’s answer

Postage stamps prepay for storage once. After that, serving costs the publisher nothing — regardless of how many times the content is retrieved. As demand grows, so does distribution. The network handles it. The publisher doesn't pay again.

The problem

Moxie Marlinspike minted an NFT in 2022. When OpenSea delisted it, it vanished from his wallet too — because wallets use OpenSea's API. The token was on-chain. The image was not. Ownership was decentralized. Visibility was not.

Swarm’s answer

On Swarm, the content hash is the address. The image and the token point to the same thing — data identified by what it is. No hosting provider can change what the hash resolves to. No platform can make it disappear by removing a listing.

The problem

In centralized systems, demand is a vulnerability. High traffic crashes servers. DDoS attacks flood them until they stop. The moment everyone needs the service is the moment it fails.

Swarm’s answer

In Swarm, demand creates resilience. As chunks are retrieved, nodes cache them, spreading copies across the network. The more a file is requested, the more widely distributed it becomes. The system grows stronger under load — not weaker.

The problem

Wikipedia exists because a foundation keeps paying. OpenStreetMap persists because volunteers keep the lights on. The knowledge commons is only as permanent as whoever happens to be funding it this year.

Swarm’s answer

Permissionless participation means anyone can contribute storage, anyone can retrieve — no approval, no account, no single institution holding the keys. A commons on Swarm is maintained by the network itself. It outlives any particular funder.

01 / 08

Possibility spaces

What can you build on Swarm today?

Each story here reads three ways: imagine it, understand it, build it. Start with the one that fits you; each leads to the page that tells it in full.

Decentralized Frontend

ClaimedYours to take

Decentralized hosting — no server to run, no middleman to depend on.

Full use case (PDF)

Core principles

Built on values, not policies

The Book of Swarm

The foundation and philosophy behind the Swarm network.

Tracing the evolution of the web from its early days to the decentralized future, the Book of Swarm explores the ideas, architecture, and economic principles that power a self-sovereign digital society. It bridges vision and engineering - from peer-to-peer incentives to privacy by design - showing how Swarm makes digital freedom technically and economically sustainable.

Read the book

The Book of Swarm, by Viktor Trón: cover

Ecosystem Highlights

Grantee
Metaprovide
Migrating from IPFS to Swarm without changing your endpoints. IPSH keeps familiar protocols intact while adding Swarm's built-in storage incentives underneath.
Ecosystem partner
Solar Punk
Open-source libraries for audio, video, and group chat that run without central servers. Middleware for developers building censorship-resistant multimedia applications on Swarm.
Fellowship
Datafund
Tooling for tracking data and model provenance in AI applications, built on Swarm's decentralised storage. Focused on auditability, ethical compliance, and secure data lineage for AI workflows.
Collaboration
Shtuka Research
A year-long programme of econometric and mechanism design research supporting Swarm's tokenomics. Monthly reports and open community discussion on the Research channel.
Grantee
Etherna
Decentralised video streaming and on-demand playback, built directly on the Swarm network. A working video platform and Gateway-as-a-Service for accessing decentralised content today.
Ecosystem partner
Fair Data Society
Infrastructure and dApps for a fairer data economy, built on the principle of digital sovereignty. A coordinated network using Swarm as the foundation for human-rights-aligned data tools.