Jamstack low-traffic site: drawing the line between pre-rendered pages and billed serverless functions

Drawing the Architectural Line

For a low-traffic site, the goal is to shift as much logic as possible to the build phase or the client's browser to avoid metered serverless invocations. Of your three planned features, only gated content genuinely requires server-side logic for security.

Feature Breakdown

Feature	Recommended Approach	Cost Impact
Contact Form	Form-as-a-Service (e.g., Netlify Forms, Formspree)	Zero to low (usually free tier)
Site Search	Client-side JSON index or free-tier external API	Zero (client-side) or low (API)
Gated Content	Serverless Function / Edge Middleware	Metered per request

Implementation Logic

• Contact Forms: Do not write a custom function to handle POST requests. Use a managed form endpoint. This removes the need for a billed function invocation and handles spam filtering automatically.
• Site Search: For low-traffic content sites, generate a search.json file at build time containing titles, slugs, and excerpts. Use a client-side library (like Fuse.js) to query this file. This moves the computation to the user's device.
• Gated Content: Since client-side "gating" (hiding elements with CSS/JS) is easily bypassed, you must use a serverless function or Edge Middleware to verify a session cookie or JWT before serving the content.

Estimating Invocation Volume

To estimate costs before committing, use a conservative formula based on user behavior rather than raw traffic:

Monthly Invocations = (Monthly Unique Visitors × Avg. Sessions per Visitor) × (Probability of accessing gated area × Requests per gated session)

For a low-traffic site, this usually falls well within the free tiers (often 100k to 1M requests/month) of modern platforms. The primary risk is not organic traffic, but bot scraping or DDoS attacks, which can exhaust free quotas quickly.

Revalidation vs. Full Rebuilds

On-demand revalidation (ISR) is generally not worth the lock-in for content updated a few times per week. Full rebuilds are more portable and ensure a consistent state across the entire site.

Recommendation: Stick to full rebuilds. If build times exceed your platform's free minutes, optimize your build pipeline (e.g., by caching dependencies) before moving to a vendor-specific revalidation strategy.

Verification Steps

1. LCP Check: If using client-side search, check the size of your search.json. If it exceeds 100KB, it may negatively impact Largest Contentful Paint (LCP).
2. Build Audit: Run a full production build locally to estimate the time required, then compare this against your provider's monthly build-minute quota.

Note: To refine the gated content recommendation, are you using a third-party Auth provider (like Auth0 or Clerk) or a custom database?