Traditional frontend hosting is fast to start, but you depend on one vendor account, one billing relationship, and one platform policy. Decentralized hosting shifts availability from one operator to a network of nodes.
Decentralized hosting shifts availability from one operator to a network of nodes.
Centralized patterns
Single-provider outages, account suspensions, geo blocks, and vendor lock-in can interrupt access even when your files are fine.
Decentralized patterns
Content stays addressable by hash and replicated across peers. If one path is unavailable, others can still serve the same exact bytes.
Example: if one CDN region has downtime during a launch, decentralized distribution can still serve identical content through other nodes and gateways.
Core concept
What is Swarm?
Swarm is a decentralized, open-source, peer-to-peer storage and communication network. Files are chunked, distributed, and redundantly stored across nodes rather than uploaded to one server.
You pay for storage durability with postage stamps. Traffic itself is not billed the same way as classic cloud egress.
Network building block
What is a node?
A node is a participant machine running Bee software. Nodes store and relay chunks, validate protocol rules, and keep content discoverable. The more healthy nodes, the stronger the network.
Stores chunks
Keeps pieces of uploaded content available.
Routes requests
Finds and serves chunks through the network.
Improves resilience
No single machine controls all availability.
Related protocol
What is IPFS?
IPFS is another decentralized content-addressed network. Like Swarm, it addresses files by content hash. In workshop terms: both move from location-based hosting to content-based hosting, while Swarm adds its own incentive/storage model through stamps.
Swarm
Content chunks + postage stamps
IPFS
Peer-to-peer content addressing
Useful framing for beginners: URL hosting says “where,” content-addressed systems say “what.”
Access layer: freedombrowser.eth.limo
What is Freedom Browser?
Freedom Browser is used in workshops as a user-friendly way to access decentralized web content directly, reducing friction for first-time users who are not yet comfortable with command-line tooling.
Beginner bridge
Helps users open decentralized sites with familiar browser behavior.
Workshop utility
Users can test uploaded frontend content and preloaded examples quickly.
02
Justdeploy Easy Mode
From wallet connection to ENS-linked frontend
Chain choice
What is Gnosis Chain?
Gnosis Chain is an EVM-compatible chain often used for lower transaction costs. It can be a practical option for buying storage resources with lower overhead than mainnet Ethereum.
Gnosis Chain
Low-cost EVM transactions
RPC endpoints
Wallet-to-chain connectivity
Takeaway: same wallet concepts, usually cheaper transactions.
Network plumbing
What is an RPC?
RPC means Remote Procedure Call. Your wallet uses an RPC endpoint to read chain data and broadcast signed transactions. If RPC is slow or down, your wallet feels broken even if the chain is healthy.
// Example mental model wallet -> RPC endpoint -> Gnosis Chain node // "send transaction", "get balance", "estimate gas"
Storage economics
What are postage/storage stamps?
Postage stamps prepay for storage persistence in Swarm. Think of them as storage validity windows: capacity + time. When the stamp depletes, content can fall out of guaranteed availability unless topped up.
Capacity
How much data the stamp covers.
Duration
How long your data remains funded.
Top-up
Extend life before expiry to avoid downtime.
Easy mode step 1
Connect your wallet in Beeport
Open Beeport, connect a compatible wallet, and choose the chain/token combination you want to use for storage purchase.
1 Connect
2 Buy
3 Upload
4 Access
5 ENS
Easy mode step 2
Buy storage (stamp)
In the Buy tab, select chain, payment token, storage size, and duration. Confirm transaction in wallet. This funds the storage backing for your upload.
Workshop tip: choose enough duration to cover demo + follow-up review period so links do not expire immediately.
Easy mode step 3
Upload your build folder
Use “Multiple files in a folder (one hash),” select your frontend output directory, and ensure `index.html` is at the folder root. Swarm serves that root entry point.
After upload, you get a content hash URL. The official gateway may restrict unreviewed content, while alternate gateways (like `bzz.limo`) can provide immediate access for testing.
Important concept: same content hash means same content bytes, no matter which compatible gateway resolves it.
Human-readable naming
What is ENS?
ENS maps human names like `yourname.eth` to decentralized resources. Instead of sharing raw hashes, you can point your ENS name to the latest content hash and publish a memorable frontend URL.
Result: `yourname.eth.limo` / `yourname.bzz.link` style access once records propagate.
ENS
eth.limo
bzz.link
Beeport
Easy mode step 5
Set ENS content hash
In upload history, use the ENS action to set content hash for your `.eth` name. Confirm transaction in wallet. Your decentralized frontend is now reachable via a human-readable domain.
1 Connect
2 Buy
3 Upload
4 Access
5 ENS
Operations
Keep it online: updates and stamp hygiene
Decentralized does not mean “set once and forget forever.” You still need an operator checklist.
Re-upload on updates
Each new build creates a new content hash.
Top up stamp early
Do not wait until expiry to renew storage funding.
Verify gateway access
Test both hash links and ENS links after deploy.
Quick fail-safe: keep a dated deploy log with hash, stamp used, and ENS status.
Beyond Easy mode
Other workshops/tracks
Browser / Easy
Fastest onboarding. Best for first deploy and live workshops.
Desktop App / Intermediate
GUI with local node workflow. Great for repeat publishing and feed management.
CLI / Advanced
Automation and CI/CD friendly. Best for teams shipping continuously.
Recommended workshop sequence: Easy first, Desktop second, CLI third for production teams.
Closing
Ship once, keep it reachable
A decentralized frontend stack is mostly familiar web tooling plus a new publication layer. The Easy path is enough to get your first site live in minutes, and the Desktop/CLI paths scale your workflow after that.
