How HostX works.
HostX takes a folder of static files and gives back a live HTTPS URL. There is no build step, no runtime and no configuration file. Start with the quickstart, or connect your AI.
Deployments
Every publish creates a new immutable deployment. A deployment is a manifest — a map of path to content hash — so files that did not change between publishes are stored once and uploaded never. Each deployment keeps its own permanent URL, which is what makes rollback safe: promoting an older deployment moves a pointer, it never moves bytes.
rollback({ site: "atlas-docs" })
→ atlas-docs.xhost.buzz now serves dep_71AA3KQ9ZC2MRouting
Requests resolve in a fixed order: an exact file, then a directory index, then an extensionless .html match, then the site's not-found behaviour. You can serve /404.html, fall back to /index.html for a single-page app, or return a bare 404. Trailing slashes can be left alone, always added, or always removed.
Domains
Every site gets a xhost.buzz link the moment it is created. To use your own domain, point a CNAME at domains.xhost.buzz and verify it. HostX checks DNS directly, then sets up HTTPS for you.
TYPE CNAME
NAME docs
VALUE domains.xhost.buzzAnalytics
Views, visitors, requests and bandwidth, plus top pages, referrers, countries and devices. Visitors are counted with a daily-rotating hash of IP, user agent and site, held for 24 hours — no IP is stored and the hash is meaningless across days. There are no funnels, cohorts or session replay, and there will not be.
Limits
A site may be up to 100 MB and 5,000 files, with no file over 25 MB. A ZIP or inline publish sent in one request may be up to 25 MB and 1,000 files; anything bigger uses the two-phase publish flow, which uploads only the files HostX does not already have. An account may have 25 sites, 10 custom domains (3 of them waiting to go live at a time) and 1 GB of stored files. HostX keeps each site's live version and its 20 newest others; older versions are removed.
What HostX does not do
HostX publishes static files. There is no server runtime, no database, no serverless functions, no background jobs and no code execution of any kind. If your site needs a server, HostX is the wrong tool — and saying so is cheaper for both of us than finding out later.