Prerender Limits in SolidStart: Choosing Static or SSR for Low‑Traffic Cost Savings

Goal

We want to deploy a read‑only dashboard that receives <10 requests per minute, and we want to keep compute costs minimal.

Constraints & Uncertainty

SolidStart’s prerender flag produces static HTML at build time, eliminating a Node.js runtime for those routes. However, the framework does not ship a built‑in cache‑invalidation or incremental regeneration trigger, so data that changes more often than the build schedule may become stale. Switching from prerender to SSR requires route re‑configuration and may alter client hydration behavior, potentially impacting the perceived performance of the low‑traffic site.

Questions

• What is the maximum data freshness interval that can be guaranteed when using prerender without manual regeneration scripts?
• Does SolidStart provide any experimental or community‑maintained hooks for automatic cache invalidation on content updates?
• In a low‑traffic deployment, how does the cold‑start latency of an SSR route compare to the static file delivery latency of a prerendered route on a typical edge platform?