Access Swarm
Connect directly, or through an on-ramp
Direct access means running a Swarm client yourself — installed on your machine, or inside your browser. Indirect access means a service runs one for you. Both put your data on the network; only the first puts you on it.
Run a client yourself, or let a service run one for you. Both put your data on the network; only the first puts you on it.
Direct access
Become a peer in the network
By installing a client, you become a direct participant in the network. If Swarm is the protocol, a client is the software that lets your device speak it, so you store, retrieve and share data directly.
Let your browser run the client
Several Swarm clients designed to run inside ordinary browsers (Chrome, Brave, Safari etc) are nearing release, while a Web3 native browser already supports Swarm.
Freedom Browser
Independently built • Web3 native browser • Available now
freedombrowser.eth.limo
In-browser clients
Ordinary browsers • Nearing release
—
Indirect access
On-ramps for a quick taste of Swarm
Gateways and other on-ramps connect to Swarm through a service-operated node. Your data still enters the Swarm network, but the service handles the connection for you.
Where to go next
Clients are one part of the picture
VisionWhy any of this exists
The argument for infrastructure that nobody owns, and why Swarm was built the way it is.
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.