Pages

Static sites, on the edge that already serves you.

Upload a directory and it is served worldwide, with a certificate, caching and the same rules Shield applies to everything else.

01

Your domain, not ours

A Pages site is served only on a hostname you own. There is no subdomain of ours to publish on, and that is a decision rather than a missing feature: user content under our own name would put the console, the identity provider, the status page and every device using our public resolver behind a single browser blocklist entry. Your domain carries your reputation, which is the right place for it.

02

Two tiers

Store

Held centrally and cached by each location on first use. For sites with real content.

  • Up to 50 MB per project
  • Up to 5000 files
  • One fetch per location per file

Edge

Copied onto every location and served with no origin at all — so it is up whenever the location is.

  • Up to 5 MB per project
  • Up to 200 files
  • No origin to be unreachable
03

Deploys and going back

Each upload is a deploy, and a deploy never changes once it is finished. Going back to an earlier one is instant: nothing is copied and nothing is rebuilt, because the deploy is part of where its files are stored — only a pointer moves. The edge is told to drop its cache at the same moment, so a rollback is visible immediately rather than when the last cached file happens to expire.

04

What it serves

Ordinary static-site behaviour, stated rather than guessed at: /docs is docs.html when that exists and docs/index.html otherwise; a directory asked for without its trailing slash is redirected rather than served, so relative links resolve where their author meant; a missing page gets your 404.html with a 404 status, not a 200. A _redirects file gives exact and wildcard rules, and _headers lets you set your own response headers — though not ones that would rewrite what the edge decided.

05

Questions

Can I publish on a subdomain of yours?

No, and that will not change. Arbitrary user content under our own name would put every service we run behind one browser blocklist entry — including the resolver that other people's devices depend on. Bring a hostname you own.

Which tier should I use?

Store, unless the site is small and you want it to survive anything. The edge tier holds a copy on every location, which is why it is capped at 5 MB — it is for landing pages, documentation and redirects, not for a site with a photo gallery.

Do I get a certificate?

Yes, issued and renewed automatically, the same way every Shield hostname gets one.

Is there a build step?

No. You upload the finished files. Build wherever you already build — the output is what we serve.