Astro + Vercel: Choosing static vs hybrid output for low‑traffic cost reduction

The Most Cost-Effective Configuration

To minimize compute costs on Vercel for a low-traffic site with a small percentage of dynamic content, use output: 'hybrid' in your Astro configuration. In this mode, all pages are pre-rendered as static HTML by default, incurring zero runtime compute cost. You then explicitly opt-in only the necessary dynamic routes to Server-Side Rendering (SSR).

Implementation Steps

1. Configure Hybrid Mode: Set the output mode in astro.config.mjs:

   export default defineConfig({
     output: 'hybrid',
     adapter: vercel(),
   });

2. Mark Dynamic Pages: In the .astro files for your dynamic routes, add the following export to disable pre-rendering:

   export const prerender = false;
   

3. Verify Static Defaults: Ensure that all other pages omit this flag. They will be built as static assets and served via Vercel's Edge Network without triggering serverless function invocations.

Cost and Performance Analysis

Runtime Cost vs. Route Count
On Vercel, compute costs are driven by invocations (requests to a function) and execution time, not by the number of SSR routes defined in your code. Having 100 routes marked prerender = false costs nothing if no one visits them; however, a single high-traffic SSR route can quickly exhaust a free tier.

• Build-time: Consumes CI/CD minutes. For low-traffic sites, this is typically the cheaper option as it leverages the build pipeline rather than per-request billing.
• Runtime: Consumes Vercel Serverless Function invocations.

Static pre-rendering becomes "more expensive" only when the number of pages is so high (high-cardinality) that build times exceed CI limits or memory thresholds, forcing a move to SSR for those specific paths.

Verification

To verify your configuration is working as intended:

• Check the Vercel Dashboard > Usage tab. Monitor "Function Invocations" to ensure they only spike when your specific dynamic routes are accessed.
• Inspect the build logs to confirm that the majority of your pages are being listed as static assets.

Diagnostic Detail Needed: Are your dynamic routes based on a small, predictable set of IDs, or are they generated from an external API with thousands of unique entries? If the latter, the build-time memory limit may dictate whether you use prerender = true or false.