Hosting a website on an anonymous VPS: the practical guide
Publish a site from a no-ID server with no traffic logging — domain choice, DNS, TLS with Caddy, deploy workflow, and the operational realities of running a public site this way.
A public website is the hardest thing to host privately, because by definition it is meant to be found. This guide covers what a no-KYC VPS changes about hosting a site, what it does not, and the concrete steps from domain to deploy.
What is different on a no-KYC host
The infrastructure is the same Linux you know; what changes is the relationship. There is no verified identity on the account, no card on file, and — because no traffic logs are kept — a much smaller record of who visited. The practical consequences are real: fewer abuse-evasion options and a slightly more exposed operation.
Note · Not keeping logs is a privacy feature, but it also means we cannot retroactively identify whoever caused an abuse report. Expect less tolerance for repeated abuse than a provider who logs.
Domain and DNS
Choose a domain, then point an A record at your server's IPv4 — and an AAAA record at your IPv6 if you serve dual-stack. Decide separately whether you want the domain registration itself anonymous; a standard registrar's WHOIS is public even if your hosting is not. Our comparison with the proxy model covers that distinction.
TLS with Caddy
Caddy is the fastest route to correct HTTPS: it obtains and renews certificates automatically the moment you name a domain. A minimal config gets you a public HTTPS site with no certificate handling at all.
Run Caddy as a service, put your domain in the Caddyfile with a reverse_proxy to your app's local port, and let it handle certificates. The Caddy guide covers the full pattern, including running the app on 127.0.0.1 so only Caddy is exposed.
Deploy workflow
- ▹Keep the site in git on the server and deploy with git pull plus a build step — simple and auditable.
- ▹Or build locally and rsync the output; faster for static sites.
- ▹Run the app as a systemd service so it restarts on reboot and crash.
- ▹Keep the app bound to 127.0.0.1 and let Caddy be the only thing on 80/443.
Backups
A public site accumulates data — content, database, uploads — and no-KYC hosting does not change that. Use restic or a scheduled rsync to somewhere off the machine. Our Restic backups guide covers encrypted off-site backups.
The reality of public hosting
You will get scanners, and occasionally abuse complaints. Without traffic logs, proving a report is unfounded is harder, so the answer is to be a reasonable operator: moderate what you host, respond to legitimate complaints, and do not become a free proxy or open relay for strangers.
Performance expectations
A $6–15 VPS with NVMe and unmetered bandwidth serves ordinary static and dynamic sites well. You are bandwidth-rich and CPU-limited; for most sites that is the right trade. If you outgrow it, Nocturne at $25 or a dedicated server covers genuinely heavy workloads.
FAQ
QIs my domain WHOIS still public?
AIf you register with a normal registrar, yes — the domain registration is public even when your hosting is anonymous. Use a proxy registrar if that matters.
QWill no logs make my site vulnerable?
ANo — logging is an observability feature, not a security control. Harden the server instead; the hardening checklist is the place to start.
QCan I run a site with real traffic here?
AYes. Unmetered bandwidth on every tier means a popular static or moderate dynamic site is fine; the limit is CPU/RAM, not data.
QHow do I handle abuse complaints?
ARespond to legitimate ones and fix the issue. Expect less ability to disprove unfounded reports, because there are no traffic logs to consult.