Static Site Hosting across clouds
Git-connected hosting for static sites and front ends - Amplify Hosting, Azure Static Web Apps, Cloudflare Pages - with preview branches that are not public by accident.
3 verified modules, 1 of them live-tested apply→verify→destroy; the rest are static-validated, live-test pending.
Compare by provider
| Provider | Module | Verification |
|---|---|---|
| AWS | An Amplify App Whose Previews Are Behind Basic Auth and Whose Branches Do Not Multiply | static-validated |
| Azure | Azure Static Web App | ✓ live-tested |
| Cloudflare | A Pages Project Whose Previews Are Not Public by Accident | static-validated |
How to choose
Every one of these builds every branch and serves it at a URL; the difference is whether that URL is public by default and what closes it. Compare the preview policy, whether a custom domain and its certificate are managed, and what a build can read (the environment variables are plaintext on all of them).
When not to use
These host files and functions at the edge; they are not a place to keep a secret. A preview of the pricing branch, or a build log with a token in it, is the incident these services produce.