The Swarm vision
The web should serve the people
A decentralized storage and communication network built on the conviction that data belongs to those who create it — not to the platforms that host it.
Why decentralization matters
The web we inherited
The web began as a network owned by no one.
Its strength came from openness: anyone could publish, connect, or build on what others had shared.
Over time, the scale of participation outgrew the infrastructure that sustained it. Hosting, indexing, and communication required servers, and servers required funding.
Gradually, most of the world’s data came to live on infrastructure owned by a few large providers. What was once distributed became centralized.
Social media amplified the effect.
Platforms could now collect personal data, then learned they could monetize it. Every interaction added to their insight into user behavior, preferences, and relationships. Surveillance grew as a by-product of business models that treated data as currency.
The same logic shaped the attention economy. Algorithms began to promote content that kept users engaged, but not necessarily informed. Advertising replaced service as the true source of revenue, turning the user from participant into product.
Meanwhile, the imbalance widened.
Millions of independent creators produced value that accumulated at the top. The infrastructure that was designed for openness now rewards concentration, leaving the system both dependent and fragile.
This is the web we have inherited: efficient, but captive; powerful, but easily distorted by those who own its foundations.
The challenge is no longer access, but autonomy. The question of how to rebuild what was lost, without repeating the same mistakes, is what inspired Swarm’s inception.
The collective mind of the internet
The commons exists, but it sits behind walls
Every interaction online leaves a trace: a comment, a review, a contribution to a shared codebase. Together, this data forms the collective memory of the internet: knowledge produced by millions of people acting, often unknowingly, in collaboration.
Over time, this collective information has become one of the most valuable resources in the world. It underpins research, innovation, and culture itself. Yet most of it lives on servers owned by private companies. The commons exists, but it sits behind the walls of platforms that claim to host it.

In this arrangement, value flows upward once again. The work of the many becomes the property of the few. The public parts of our activity stay visible, but the metadata—who connects, when, and how—is stored, analyzed, and monetized in private. The result is an internet that depends on the users while acting against its interests.

Peer-to-peer networks like Swarm change where data lives and who decides its fate. They make it possible for collective information to remain collectively owned—accessible, verifiable, and free from the custodianship of central authorities.
Building on this model means more than decentralizing storage. It means creating infrastructure worthy of the trust we place in it, one that protects what humanity knows together while keeping ownership where it belongs: with the people who created it.


Design principles for a lasting infrastructure
Built for a horizon beyond market cycles
The web has become the foundation of daily life. The systems that carry its data must endure beyond market cycles, institutions, or political pressure. Swarm was designed with that horizon in mind — a base layer built to remain stable, scalable, secure, and self-sustaining.
Stable
Resilient to change in participation or politics. The network adapts when nodes come and go.
See a file splitScalable
Designed to scale without losing reliability. Performance improves through distribution.
Go inside SwarmSecure
Protected against attacks and capture. Fault tolerance is built into every layer.
Privacy, on your termsSelf-sustaining
Continuity depends on aligned participation, not on any company or external funding.
How it pays for itself
Possibility spaces — Vision
Whoever controls the pipes, controls the information
Each story here reads three ways: imagine it, understand it, build it. This page leads with imagining it: what changes for people when the infrastructure does.
Decentralized Frontend
ClaimedYours to takeDecentralized hosting — no server to run, no middleman to depend on.
Read it as architecture
The site is split into content-addressed chunks stored across Swarm's network; a feed points at the current version so the same link survives every future update.
Read it as development
Beeport, Swarm Desktop, or swarm-cli each upload a build, buy a stamp, and point an ENS name at the result.
Vision
A website stays online only for as long as everything underneath it holds. Any link in that chain can break. A cloud provider can suspend an account over a billing dispute or an automated abuse flag, without a person ever reviewing the case. A registrar can seize a domain under pressure from one jurisdiction; a government can order a site blocked or restricted. And none of it has to be deliberate: when a major CDN or cloud region goes down, millions of sites vanish with it for hours. A policy change, a takedown order, or an outage on a Tuesday is enough to take a project offline by Wednesday.
Most builders never think about these dependencies until one breaks. A side project, a community tool, a small business's storefront: all of it sits on infrastructure owned by someone else, reachable only for as long as that someone else stays willing — and stays up.
Swarm removes the middleman from the equation. A site published to Swarm isn't installed on a server. It's split into pieces and distributed across a network of independent participants, none of whom individually decides whether the site stays up. There's no single account to suspend, no single machine whose failure takes the site down, and no central chokepoint where pressure can be applied. Censorship becomes structurally hard rather than one phone call away, and downtime becomes a local event the network routes around — resilience that grows with every participant that joins.
The address stays usable, too. A site can be updated, a new build, a fixed typo, a redesign, without anyone needing to notify visitors of a new link or re-point a domain. The reference people already have keeps resolving to whatever the latest version is.

Manifesto
The principles behind the project
The question of how to rebuild what was lost — without repeating the same mistakes — is what inspired Swarm's inception. Our manifesto lays out the reasoning in full.
It is a document about infrastructure, but also about values. About who gets to decide what information survives, who can access it, and on whose terms.
Where to go next
The vision is part of the picture
Swarm is a live network. Understand how it works, contribute to it, see what's being built on it — or start building today.
Inside SwarmFollow a chunk through
Swarm's answer to centralization is an architecture, not a policy. See how content addressing, storage and incentives work together.
CollaborationsFind it in the wild
Decentralized video, censorship-resistant publishing, AI agent storage. See what teams have in production today.
BlogRead the network updates
State of the Network reports, development updates and community calls — the public record, month by month.
Developer HubBuild on it
Tools, libraries, working examples, and a grant programme for builders who want support getting something shipped.
