Modern hosting: Git + Vercel
For a simple landing site, a very good route is Git + Vercel. The site lives in a repository, and Vercel publishes it online automatically. Every time you change the site and push an update to Git, Vercel can publish the new version automatically.
Advantages
- free or very cheap hosting for simple sites;
- very good for static or modern sites;
- less maintenance than a classic WordPress;
- no WordPress plugins to keep updated;
- it pairs well with AI-generated or AI-assisted websites.
Disadvantages
- you need to understand at least the basics of Git;
- some things that were simple in cPanel become more technical;
- email must be managed separately, for example through Google Workspace or Microsoft 365;
- setting up the domain and DNS can be confusing at first.
This is the route I use now. It fits very well with a site built with the help of AI: you build it in code, put it in Git, and Vercel publishes it. Later changes are made in code and publish themselves.
How the flow looks
- Your site lives in a Git repo.
- You connect the repo to Vercel.
- Vercel publishes the site and gives you a link.
- You connect the domain through DNS.
- Any change in Git publishes automatically.
Vercel isn't the only option. The exact same flow (Git → automatic deploy) works with Cloudflare Pages or Netlify too. The differences are small for a landing site, pick based on where you already have your domain/account and which interface you prefer.
Vercel, Cloudflare Pages or Netlify?
| Platform | Free tier | Good at | Worth noting |
|---|---|---|---|
| Vercel | yes, generous for small sites | most optimised for Next.js and modern sites | the step-by-step example in Publishing on Vercel is on Vercel |
| Cloudflare Pages | yes, very generous (unlimited bandwidth and requests) | static + fast global CDN | if your domain/DNS is already on Cloudflare, everything (domain, DNS, site) lives in one place |
| Netlify | yes | static and modern sites, simple forms | Git → deploy flow is almost identical |
For a simple site, all three are practically interchangeable. In the image guide we use Vercel as the example, but the logic is the same anywhere.
Next step
Move on to the Git repo for the website to understand where the site lives, then to Publishing on Vercel.