What's actually behind your site.

How your site gets created

Submitting the order form doesn't queue a request for someone to action later — it triggers the real thing. Your own copy of the site template is set up, given its own process and its own subdomain, and started, typically inside a minute. You get an email with a one-time link to set your admin password the moment it's ready.

Nothing about this is a demo or a placeholder — it's the same infrastructure every other client site runs on, just automated instead of set up by hand.

The server

Sites run on a dedicated cloud VPS. It's a proper commercial server — not a shared hosting account, not a reseller plan. I manage it directly: operating system, web server, security updates, everything.

Each site runs as its own isolated application behind an nginx reverse proxy, with its own process, its own port, and its own systemd service. Your site doesn't share a process with anyone else's.

Backups

Two independent layers:

• Daily server snapshots — a complete image of the whole server, stored separately from the live disk, kept on a rolling schedule (recent days, plus a running month of weekly checkpoints). If the server itself fails, I restore from a snapshot onto a new instance — tested end-to-end, not just theoretical.
• Source code mirrored to GitHub — your site's code is also kept in a private repository, independent of the hosting provider. That's a second line of defence for the code specifically; day-to-day content — orders, uploaded photos, that kind of thing — lives in the daily snapshot, not a separate copy of its own.

Recovery target is same-day for anything short of a total infrastructure event. In practice, most issues are resolved in under an hour.

Cloudflare

Every site is proxied through Cloudflare before it reaches my server. That means:

• SSL certificates handled and renewed automatically — your site is always HTTPS.
• Basic DDoS mitigation and bot filtering without any configuration on your part.
• If my server goes down, Cloudflare automatically serves a clean, branded maintenance page to your visitors rather than a blank error. They see "back soon" rather than a broken site.

The maintenance page means your visitors get a professional response even during an outage, and you don't look bad while I'm fixing things.

Monitoring

Uptime monitoring runs continuously, checking every few minutes. If your site goes down, I get an alert within minutes — that part doesn't depend on the time of day. I do still have to sleep sometimes though, so fixing an overnight issue might take a little longer than one in the middle of the day. Either way, I'm not waiting for you to tell me something's wrong.

What I don't have

I don't have a 24/7 operations team, a formal SLA document, or a ticketing system. I'm a real person who manages a small number of sites and treats each one seriously.

If you need guaranteed four-nines uptime with contractual penalties, you need a dedicated managed hosting provider. I'll point you toward one. If you need someone competent who actually picks up the phone, I might be a better fit.

Domain and email

I can host your site without managing your domain registrar — you can keep control of that yourself, or hand it to me to manage. Both email options below need your own domain connected first — email addresses are tied to a domain, so on the default .nofusshost.com address there's nothing to route yet. Once it's connected: inbound forwarding to your own address is free by default. A real mailbox — one you log into from your phone or a normal mail app, not just webmail — is priced per box, to cover what it actually costs me to provide, not as a profit line.