ProSitesHub is itself an example of the thing it writes about: a real, live website built entirely on free tools. Here's the exact stack, documented as we used it — partly because it's a useful reference, and partly because transparency about the process is more interesting than another generic "how to start a website" post.
The stack
| Layer | Tool | Cost |
|---|---|---|
| Code hosting | GitHub | Free |
| Deployment | Vercel (Hobby tier) | Free |
| Domain DNS | Hostinger (domains already owned) | Domain cost only |
| Analytics | Google Analytics 4 | Free |
| Search visibility | Google Search Console | Free |
Why static sites
Each site in the portfolio — including this one — is a static HTML/CSS build with no server-side backend. Static sites deploy instantly, cost nothing to host at this scale on Vercel's free tier, and are fast by default, which matters for both visitors and search ranking.
The deploy pipeline
Every site follows the same repeatable sequence: push the site files to a GitHub repository, connect that repository to a new Vercel project, then point the domain's DNS at Vercel (an A record for the root domain, a CNAME for www). From that point, every future update is just a new commit — Vercel redeploys automatically.
Getting analytics right
GA4 and Search Console are set up before the first real visitor arrives, not after — waiting means losing early data that's genuinely useful once you start comparing what content performs. Search Console's domain-property verification uses a DNS TXT record, which covers the root domain and all subdomains (including www) with a single verification.
What actually took the most time
Not the deployment — that part is mechanical once you've done it once. The time sink was, unsurprisingly, writing content that's actually useful rather than generic. Every comparison article on this stack of sites is built from checking current pricing pages and product documentation directly, because outdated "best of" lists are one of the most common complaints about this kind of content.
The bottom line
If you're following our guide to launching a website for free, this is the same stack in production, not a theoretical example. Zero-cost infrastructure is no longer a compromise — it's a legitimate way to run a real project.