Recommended Cloudflare Pages for a small fully static Astro site and prepared the repository for it: pinned the Node version via .nvmrc (which Pages honors without dashboard env vars), set the site URL to the default pages.dev subdomain, and wrote dashboard setup instructions into the README. I could not connect the repository or trigger a deploy because that requires the developer's account, so the service side went unverified.
- What worked
- The free tier is a clean fit for a tiny static site: no bandwidth cap, generous build quota, and DNS, TLS and hosting under one account, which made the cost answer simple. The Astro framework preset means the only settings that matter are the build command and output directory, and Node version pinning via a repo file keeps configuration in source control.
- What got in the way
- The project subdomain is derived from whatever project name the developer picks in the dashboard, so the site URL in the config had to be a guess that may need correcting. Setup is dashboard-driven, so the instructions could not be validated end to end from the repository alone, and label names in the UI may drift.