dAppling Network hosts static sites and Web3 frontends on IPFS with GitHub deploys, ENS domains, and CI/CD. See pricing, features, and how it works.
dAppling Network is a hosting platform built specifically for Web3 frontends and decentralized applications. Instead of serving files from a centralized server, it builds and stores site files on IPFS, a distributed peer-to-peer storage protocol, so that hosted applications remain accessible and resistant to censorship or single points of failure.
The platform is aimed at developers who want a familiar, GitHub-connected deployment workflow similar to mainstream hosts, but with the decentralization guarantees that Web3 projects, such as decentralized exchanges and DAOs, often require.
Developers connect a GitHub repository, and dAppling automatically builds the project and deploys the resulting static files to IPFS, typically in under a minute. New pushes trigger automatic redeployments, and preview builds are generated for branches or pull requests before changes go live.
dAppling supports both traditional DNS domains and ENS (Ethereum Name Service) domains, so a hosted dApp can be reached through a conventional web address or a blockchain-native name, and deployments can be tied to smart contracts for added verifiability and control.
The Free plan includes 500 megabytes of IPFS storage, 50,000 IPFS API requests, 100 gigabytes of CDN bandwidth, and 1 million CDN requests at no cost, along with access to dedicated IPFS gateways.
Usage beyond the free tier is billed under a Pay as You Grow model at roughly 0.015 US dollars per gigabyte and per 10,000 requests, while a flat-rate Business plan at roughly 200 US dollars per month provides substantially higher limits, including up to 10 terabytes of storage and up to 100 million CDN requests.
dAppling Network is used to host static sites and Web3 application frontends on IPFS, giving decentralized applications censorship-resistant, distributed hosting instead of a centralized server.
Yes, dAppling offers a free tier with 500 megabytes of storage, 50,000 IPFS API requests, and 100 gigabytes of CDN bandwidth, with paid usage-based and flat-rate plans available beyond that.
You connect your GitHub account, select a repository, and dAppling automatically builds and deploys the site to IPFS, typically within about a minute.
Yes, dAppling supports both ENS (Ethereum Name Service) domains and traditional DNS domains for accessing hosted sites.
Usage beyond the free tier is billed under a Pay as You Grow model at roughly 0.015 US dollars per gigabyte and per 10,000 requests, or organizations can choose a flat-rate Business plan at roughly 200 US dollars per month.
Instead of storing files on centralized servers, dAppling stores site files on IPFS, a decentralized peer-to-peer storage network, making hosted sites more resistant to censorship or single points of failure.
It is technically possible, but dAppling is purpose-built for Web3 frontends and IPFS-native hosting, so conventional hosting platforms are typically a better fit for standard websites.
dAppling is commonly compared to Fleek, another decentralized hosting provider with a similar GitHub-connected deployment workflow for Web3 frontends.