If your site is static HTML, CSS, and JavaScript, it can usually be hosted for free on GitHub Pages or Cloudflare Pages. You can do it yourself, pay us once to set it up, or use our optional custodian service if you would rather not touch the hosting accounts.
Traditional hosting rents you server space. A static website usually does not need a server running WordPress, PHP, databases, plugins, or a control panel. It just needs a place to serve files quickly and securely.
Static sites are made of files a browser can read directly. That makes them simple to store, move, back up, and publish.
GitHub Pages and Cloudflare Pages both support static websites, custom domains, HTTPS, and automatic deployment from a repository.
You can manage the platform yourself, or we can handle the setup and act as the middle layer for updates.
Both are good free choices for static websites. The right pick depends on how technical you want the setup to be and whether you already use Cloudflare for DNS.
| Question | GitHub Pages | Cloudflare Pages |
|---|---|---|
| Best fit | Simple static sites where the files live in a GitHub repository. | Static sites that benefit from Cloudflare DNS, edge delivery, previews, and room for future technical features. |
| Cost for most static sites | Free for public repositories on GitHub Free. Private repository publishing requires a paid GitHub plan. | Free plan available with generous static site limits, including custom domains and build minutes. |
| Custom domain | Supported. You point DNS records to GitHub Pages and can use HTTPS. | Supported. Apex domains work best when the domain uses Cloudflare nameservers; subdomains can use a CNAME. |
| Traffic and limits | Good for normal small business traffic. GitHub lists soft limits such as published site size and monthly bandwidth. | Good for normal small business traffic. Cloudflare lists free-plan limits for builds, files, custom domains, and asset size. |
| Ease for non-technical owners | Simple once configured, but GitHub can feel unfamiliar if you do not use repositories. | Clear dashboard, but DNS and Pages settings can still be intimidating if you have never used Cloudflare. |
| My usual recommendation | Use it when you want the simplest repository-to-website setup and do not need extra platform features. | Use it when you want strong DNS control, fast global delivery, and a path toward more advanced web features later. |
Plain-English version: GitHub Pages is usually the simplest free home for a basic static site. Cloudflare Pages is usually the stronger long-term platform if your domain is already on Cloudflare or you may want more advanced web infrastructure later.
You do not have to buy hosting from us. This is only for people who want the benefits of free static hosting without managing GitHub or Cloudflare themselves.
GitHub Pages or Cloudflare Pages setup
We connect the repository, configure the deployment, point the domain, check HTTPS, and hand over the basic access details.
About $5/month, billed annually
We manage the static hosting layer for you. We monitor the repository and act as the middle layer for updates to the live website.
This is not a design retainer. The custodian service covers the static hosting middle layer and simple provided updates. If you want new design work, layout changes, new functionality, or custom edits, that is handled separately at an hourly rate.
A typical shared hosting plan is often around $15/month before add-ons, renewals, backups, security tools, or managed services. For a static site, that is usually paying for machinery you do not need.
Free static hosting means the platform cost can be $0. Our custodian option is for convenience, not because the site technically needs paid hosting.
No database updates, plugin conflicts, PHP versions, server panels, or WordPress security chores for a normal static site.
Your website remains plain files in a repository. If you ever want to move platforms, the site can move with you.
We can set up GitHub Pages or Cloudflare Pages for a fee, and the optional $60/year custodian service keeps us in the middle so you do not have to manage the static hosting workflow yourself.