Every site gets its own subdomain.

A single file shares fine from a path on the main domain. A website wants an address of its own. When you host a ZIP and the archive has an index.html inside, NudgeHost unpacks it and serves the result at https://your-slug.nudgehost.site, a subdomain that belongs to that project. Everything sits at the root of that address, so stylesheets, scripts, and images load from exactly the paths the build wrote.

Serving from the root is also what keeps client-side routing alive. A request for a path that does not match a file in the bundle is rewritten to the index, so a React Router app answers direct visits to its own routes instead of returning a 404, while requests for files that genuinely do not exist still fail correctly. The result behaves like any static site, served as files with nothing rebuilding per visit; the glossary entry on what a static site is covers why that needs no server.

AI builder exports get the most out of this. A Lovable or v0 project is a built React app the moment it leaves the chat, so you can host a Lovable export and it lands at its own subdomain with deep links working; our Lovable hosting walkthrough covers the whole flow on a real project. Replace the ZIP in your dashboard and the subdomain stays the same, so a client who bookmarked the link sees the new build on their next visit.

The subdomain is also a security boundary. Site JavaScript runs on its own origin, away from the main domain where your account session lives. A password-protected site shows its gate on the main domain first, then hands the visitor to the subdomain with a one-time token, so the lock holds without the site origin ever seeing account cookies. Anonymous uploads get a subdomain too, with a small attribution banner on served HTML pages, and the free plan keeps ten links live with no expiry once you sign up.