> For the complete documentation index, see [llms.txt](https://prodocs.webhash.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prodocs.webhash.com/introduction.md). # Introduction WebHash Pro is the easiest way to put your website on the **decentralized web**. Connect a GitHub repository, click deploy, and your site is published to **IPFS** - a peer-to-peer network where your files live on the permanent web instead of a single company's server. You can then point an **ENS domain** (like `yourname.eth`) at your site, and pay for storage using crypto. If you've ever used a host like Vercel or Netlify, WebHash Pro will feel familiar. The difference is *where* your site lives: instead of traditional cloud servers, your build is pinned to IPFS and addressed by a content hash that anyone can verify. ![WebHash Pro landing and sign-in page](/files/yFWCK300phaXd5J9wNji) {% hint style="info" %} **New to web3?** You don't need to be a blockchain expert. The first 20 MB of storage are free, and you can deploy a site without ever touching crypto. Wallets and ENS domains only come into play when you want a custom `.eth` address or more storage. {% endhint %} ## The value, in one line > **Deploy your GitHub repo to IPFS, point your ENS domain at it, and pay for storage in crypto - all in a few clicks.** WebHash Pro gives you three things working together: * **Decentralized hosting on IPFS.** Every deployment produces a content identifier (a **CID**) and a public **gateway URL** you can share immediately. Because the content is addressed by its hash, it can't be silently changed and isn't tied to one server. * **Your own web3 address with ENS.** Connect an ENS name you own (such as `yourname.eth`) and your site becomes reachable at a human-readable, self-owned address. * **Pay-as-you-go storage in crypto.** Start free, then top up with ETH, USDC, or USDT when you need more space. No credit card required. ## Who it's for WebHash Pro is built for anyone who wants to ship a site to the decentralized web without managing servers: * **Builders and indie developers** publishing static sites, portfolios, docs, or client-side React apps. * **Web3 communities and projects** that already own an ENS domain and want a real homepage behind it. * **Creators and teams** who value censorship-resistant, content-addressed hosting and want to pay in crypto. You should be comfortable pushing code to GitHub. Everything else - IPFS, gateways, ENS, and crypto payments - is handled through the dashboard with guided steps. ## How it compares to traditional hosting If you know Vercel or Netlify, here's the mental model: | | Traditional hosting (Vercel / Netlify) | WebHash Pro | | ----------------------------- | -------------------------------------- | ------------------------------------------------------------------- | | **Where your site lives** | The host's cloud servers | The IPFS network (content-addressed, decentralized) | | **How a build is identified** | A deployment URL on the host's domain | A **CID** (content hash) + a public gateway URL | | **Custom domain** | A DNS domain you configure | An **ENS domain** (`yourname.eth`) you own and control | | **Who controls the domain** | Your DNS provider / registrar | **You** - ENS updates are signed by your own wallet, self-custodial | | **How you pay** | Credit card subscription | **Crypto** (ETH / USDC / USDT), pay-as-you-go, first 20 MB free | | **Connect from GitHub** | Yes | Yes | | **Auto-deploy on push** | Yes | Yes (via a GitHub webhook) | The familiar parts - connect GitHub, deploy, auto-deploy on every push - work just like you'd expect. The web3 parts (IPFS, ENS, crypto) replace the centralized pieces with ones you own and verify. {% hint style="success" %} **Self-custodial by design.** WebHash Pro never holds your ENS domain or your funds. When you connect a domain, *you* sign the on-chain update from your own wallet. WebHash Pro only ever shows you what to sign. {% endhint %} ## How it works Getting a site live is four steps: 1. **Connect GitHub.** Sign in with your GitHub account and pick the repository you want to deploy. 2. **Deploy.** Choose your project type - a **Static** site (HTML/CSS/JS, served from the repo) or a **React** app (built with a command like `npm run build`) - then deploy. WebHash Pro builds your project and pins the output to IPFS. 3. **Get your IPFS link.** When the build succeeds, you receive a **CID** and a **gateway URL**. Your site is live and shareable right away. 4. **(Optional) Connect an ENS domain.** Connect your wallet, pick an ENS name you own, and sign the update. Your site is now reachable at your `.eth` address. ``` Connect GitHub → Deploy to IPFS → Get CID + gateway URL → (optional) Connect ENS domain ``` Want to publish on every commit? Turn on **auto-deploy** for a repository and WebHash Pro installs a GitHub webhook, so each push to your chosen branch triggers a fresh deployment automatically. {% hint style="info" %} **Pricing at a glance.** Your first **20 MB** of storage is free. Beyond that, storage is **$5 per GB**, payable in **ETH, USDC, or USDT** on Ethereum mainnet, Base, Arbitrum, or Optimism. You only pay for what you store. {% endhint %} ## Where to next * **Get started** - sign in with GitHub and deploy your first site. * **Connect an ENS domain** - point your `.eth` name at a deployment. * **Storage & billing** - understand the free tier, pricing, and how to pay in crypto. * **Auto-deploy** - publish automatically on every push. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://prodocs.webhash.com/introduction.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.