You can host a static site — a landing page, a brand kit, a deck — for free, on infrastructure that will not fall over on launch day. This is what we use for delivery ourselves.

:hax-action: The short path

If you are not technical, do not follow a tutorial. Do this instead:

1. Create a free Cloudflare account.
2. In the Cloudflare dashboard, create an API token that can manage Pages.
3. Open your site folder in an AI coding agent and give it the token.
4. Tell it: publish this site to Cloudflare Pages, connect my domain, and make the contact form send submissions to my email address.

<aside> 🔐 Treat the token like a password. Give it only the permissions it needs, and delete it afterwards if you do not plan to redeploy.

</aside>

:hax-list: What is actually happening

Worth understanding, so you can tell whether it worked:

• Hosting — your files are copied to Cloudflare's network and served from a URL. Free, and fast everywhere.
• Your domain — you point your domain's DNS at that site.
• The contact form — a static page cannot send email by itself, so a small function sits alongside the site, receives the submission and forwards it to an email service. Your email key lives in the project's settings, never in the page, because anything in the page is public.

:hax-audit: The one thing to check

<aside> ✉ Decide where submissions go before you launch, and send yourself a test. The most common launch-day failure is a form that reports success and posts into nowhere.

</aside>

<aside> 💡 This guide is generalised on purpose. Cloudflare's interface changes and your stack is your own. For step-by-step instructions matched to your setup, ask ChatGPT or Gemini, or hand the whole task to a coding agent as above.

</aside>