Static hosting
One site, a real address, and the only real requirement is that a browser can read it without help — nothing running behind it, and nothing extra to pay for because there isn't anything back there.
A folder of files, handed to whoever asked for them.
That's the whole model, and it's what makes everything else on this page possible: no process to keep running, no dependency to patch, no database to secure. Just files, served the same way every time over a connection secured by SSL that's included by default — and because there's no server-side code executing anywhere, most of the attack surface a dynamic site has to worry about simply doesn't exist here.
What qualifies
Static means the files a visitor's browser receives are exactly the files you uploaded — no template engine assembling a page on the fly, no database supplying today's version of it.
HTML, CSS, JavaScript that runs in the browser, images, and fonts all qualify, because none of it needs a server to think before it can be handed over. That's a genuinely good fit for a portfolio, a brochure site, documentation, a landing page, or the export from a site builder or static-site generator.
It's a poor fit for anything that needs to remember a logged-in visitor, take a payment directly, or write to a database on its own — a forum, a store with live inventory, a comment section that saves what people type. Those need a server doing work on every single request, which is exactly what this plan doesn't run.
Getting there
Four handoffs, and none of them need you to configure anything.
Push a folder of HTML, CSS, JS and images — by Git, a zip upload, the CLI, or an assistant through the MCP server. Deploys enter a queue and publish in the order they arrive, comfortably handling up to about 100 a day.
Every site gets its own gigabyte — not a shared pool that shrinks as other accounts grow — with room for roughly 20,000 files and a 25 MB ceiling on any single one.
Copies propagate out to the edge network automatically. Full mechanics on the CDN page.
A request is answered from whichever location is closest to them, not from one server clear across the map.
What the numbers mean
Both numbers describe real usage, not a marketing ceiling. A typical text-and-photo portfolio runs a few dozen megabytes total, so 1 GB is roomy headroom rather than a tight fit, and 250 GB a month covers a small site being genuinely popular. If a site is trending hard enough to approach either one, we email you before anything changes — there's no automatic overage bill.
What counts
Worth knowing
We email you before anything changes — there's no automatic overage charge and no surprise shutoff. Most sites never get near either number.
Simpler in a way that happens to be more secure: there's no server-side code to exploit and no database to inject into, so a whole category of attack doesn't apply here.
A contact form typically posts to a third-party service, which still works fine on a static site. A full database or server-side logic is outside what this plan runs.
Either way, it's live on your subdomain the moment you publish. Compare the two on custom domains, or see every number on pricing.