The Launch Phase

What you will need

To launch your site, three things are required. All are free or low-cost, and we will walk you through anything you are not sure about:

• A Cloudflare account — free; this is where your site is hosted
• A domain name — approximately €10–15 per year; registered separately
• A GitHub account — free; optional, but strongly recommended

Cloudflare account

Cloudflare Pages is where your site lives. It is free — unlimited bandwidth, global CDN, automatic HTTPS, and no monthly hosting costs. You register at cloudflare.com with an email address; it takes about two minutes. We then set up your Pages project, connect it to your domain, and configure everything. Once it is running, you do not need to touch the Cloudflare dashboard unless you want to. We are happy to walk you through the sign-up process or do a screen-share if anything is unclear.

Domain name

Your domain is the address people type to reach your site — for example, yourbusiness.com. It is registered separately from hosting and renewed once a year. A few good options:

• Cloudflare Registrar — domains at cost, no markup over what registries charge; easiest to manage alongside your Pages project
• Namecheap — reliable, straightforward, competitive pricing
• Porkbun — often the cheapest option for popular TLDs (.com, .dev, .io)
• Typical cost: €10–15/year for .com or .eu; some TLDs are cheaper

GitHub account

GitHub is where your site's code is stored. It is free, and connecting it to Cloudflare Pages enables automatic deployments — every time a change is pushed, your site rebuilds and goes live within about two minutes. It also gives you a full history of every change ever made, and makes it easy to hand the project off or collaborate later. If you do not want a GitHub account, we can deploy directly to Cloudflare Pages manually. Everything still works; you just lose the automatic deploy workflow.

What we handle

Once accounts are in place, we take care of the rest:

• Setting up the Cloudflare Pages project and connecting it to your GitHub repository
• Configuring your custom domain and DNS records
• Enabling HTTPS — automatic and included
• Deploying the final site and confirming everything is live
• A brief handoff so you know where things are and how to reach us if anything comes up