ISR, Rollback & Deployment Protection

Incremental Static Regeneration

// Next.js — statically generated, but regenerates in the background
// after 60s without needing a full rebuild/redeploy for content updates
export async function getStaticProps() {
  const post = await fetchPost();
  return { props: { post }, revalidate: 60 };
}

// Middle ground between pure static (stale until rebuild) and full SSR
// (per-request compute cost) — good fit for content that changes
// occasionally but doesn't need per-request freshness.

Instant Rollback

Every deployment's built output is immutable and retained — rolling back to a previous deployment means promoting it back to production directly from the dashboard or CLI, with no rebuild needed.

Deployment Protection

A Preview URL, once known, is otherwise publicly guessable — unlike production, which is intentionally public. Password-protecting or requiring team authentication on Preview deployments (leaving Production's intended public access untouched) targets exactly that exposure risk without adding friction to the live site.

Monorepos

# Project Settings > Root Directory — points one Vercel project at a
# specific subfolder, e.g. "apps/web" or "apps/docs"
# Multiple Vercel projects share one git repo, each with independent
# build/deploy config and its own Preview deployments per branch.