Owning your domain is the first layer of infrastructure ownership. But a domain registered in your name and hosted on a platform you do not fully control is still partial ownership. The hosting layer is where most operators leave more dependency than they intend.
Here is what a genuinely owned infrastructure stack looks like — practical, not idealistic.
Domain registration: direct, not through a reseller
Register domains directly with a registrar — not through your web host, not through a website builder, not through a reseller. When you register through a hosting provider, the registrar account is often theirs. If you leave the host, access to the domain can become complicated.
Recommended registrars: Cloudflare Registrar (at-cost pricing, no markup), Porkbun (competitive pricing, clean interface), Namecheap (reliable, long track record). All three allow full account control and easy transfers if you ever need to move.
Verify that the WHOIS contact — or the registrant information in the registration — points to you, not to a privacy proxy you do not control.
DNS: separate from your host
Running your DNS through your web host ties your DNS uptime to your host's uptime and makes migrations harder. Moving DNS to a dedicated DNS provider decouples them.
Cloudflare's free tier is the practical default for most operators. It adds a CDN layer, DDoS protection, and a clean interface for managing records. The free tier is genuinely useful, not a loss leader that forces upgrades.
Web hosting: shared, VPS, or managed?
For a PHP flat-file site serving moderate traffic, shared or reseller hosting is sufficient and significantly cheaper than a VPS. The tradeoffs are less control and shared resources — neither matters much for a content site that does not do heavy computation.
A VPS makes sense when you need custom server configuration, when you are running multiple sites that justify the overhead, or when traffic has outgrown shared hosting's limitations. The additional control comes with additional maintenance responsibility: server updates, security patches, monitoring.
Managed WordPress hosting is not the right choice for a flat-file PHP site — it is optimised for WordPress specifically and adds cost without benefit for a custom stack.
Email: on your own domain
hello@yourdomain.com is a professional signal and a practical requirement for anyone representing a content operation. More importantly, an email address on your domain is portable in a way that a Gmail or Outlook address is not.
Options: Fastmail (clean, reliable, privacy-focused), Zoho Mail (free tier for custom domains), Google Workspace (familiar interface, higher cost). The specific provider matters less than having your email on your domain and not tied to a free-tier account that could be restricted.
Backup: off-host, automated
For a git-deployed site, the repository is the backup — every file is in version control, every change is reversible. The risk is the server-side state that is not in the repo: any uploaded files, any server configuration, any data that gets written outside the deployment path.
Keep the list of things that live only on the server as short as possible. What cannot be in the repo should be backed up off-host, automatically, on a schedule you have tested.