Astro server-side rendering

How Astro server-side rendering delivers fast first paint on ProbeHarbor home, about, and dashboard pages versus static prerender.

Home desk with laptop, external monitor, and keyboard in a living space
Household members check the same dashboard from wherever they already work. Photo: David Wellbeloved / Flickr. CC BY 2.0

Astro renders most pages on the server at request time or build time, shipping HTML with minimal client JavaScript. For a monitoring site, that means fast first paint for public probe cards and SEO-friendly about documentation without a heavy SPA bundle.

SSR in this project

The home page fetches live JSON during SSR via server-side probe fetch. About articles are static content with optional expanded blocks from generated TypeScript. API routes handle auth and history writes.

Benefits for monitoring

  • Secrets stay server-side: feed URLs and Supabase keys never ship to the browser wholesale.
  • Edge deployment on Cloudflare reduces latency: see Cloudflare Workers deployment.
  • Progressive enhancement for dashboard features that need client state.

Related reading

Interactive widgets use Astro islands. Compare with Next.js monitoring dashboards.

FAQ

Does ProbeHarbor use Astro SSR?
Yes. Marketing, about, and dashboard shells render on the Cloudflare Workers edge via the Astro adapter for fast first paint.

Is everything static HTML?
No. Many routes are SSR. Interactive pieces hydrate as islands; see probeharbor.dev/about/astro-islands-and-hydration.