Optimize Your Vercel Account

Vercel's defaults are tuned to get you shipping fast, and they do. Past that first deploy, there's a whole layer of customization to make the account your own: controls that lock down a leaking preview, settings that trim a surprise bill, knobs that skip builds you never needed.

This course walks through the configurations that move the needle on cost and security, with a checklist you can run with your team in an afternoon.

What you'll actually build

You'll deploy Saturday, the public site for a fictional indie sneaker brand. Hero product shots, a drop schedule, a waitlist form, a stock-check API, a webhook that flips a drop from "coming soon" to "buy now." Real consumer brand stakes: production is public and gets traffic, previews contain unannounced drops that absolutely cannot leak.

The code lives at vercel-labs/academy-optimize-vercel-account. The main branch is the starter you'll deploy; the complete branch is the finished reference with every change from this course already applied.

Then you'll go through every setting in your Vercel dashboard that affects how Saturday (and every other project you own) runs. By the end you'll have:

Tighter security:

• Sensitive environment variables, sensitive-by-default for new ones
• Deployment Protection gating previews so unannounced drops stay quiet
• A firewall rule rate-limiting your stock-check endpoint against sneaker bots
• Bot Protection observing your traffic
• Activity Log reviewed

Lower costs:

• Fluid Compute reducing function bills
• Runtime Cache cutting invocations on inventory lookups
• On-demand ISR replacing timer revalidation on the drop schedule
• Image optimization tuned for product shots
• Speed Insights and Web Analytics sampling instead of capturing everything
• The Ignored Build Step skipping unnecessary builds

Operational maturity:

• 2FA enforced (Pro+)
• RBAC mapping real team roles (Pro+)
• Retention policies on deployments (Pro+)
• SAML, Audit Logs, network isolation (Enterprise)

Prerequisites

• A Vercel account. Hobby works for most lessons. Pro and Enterprise sections are flagged clearly.
• A GitHub account connected to Vercel
• Node.js 22 or later installed locally
• Admin access to a Vercel team (most settings need Owner or Admin)
• Basic familiarity with deploying a Next.js app to Vercel

Course sections

Section 1: Foundations

Deploy Saturday and tour the four places in the Vercel dashboard where every setting in this course lives.

Section 2: Lock It Down

Tighten security on what every Vercel team can configure today, regardless of plan. Sensitive env vars, Deployment Protection for previews, custom firewall rules for sneaker bots, Bot Protection, and the Activity Log.

Section 3: Compute & Caching

Cut function costs by changing what runs, when, and how often. Fluid Compute, Runtime Cache, on-demand ISR.

Section 4: Bandwidth & Builds

Reduce data transferred, requests served, and minutes spent building. Image optimization, prefetching strategy, the Ignored Build Step, and observability sampling.

Section 5: Pro Upgrades

Configure the controls that come with a Pro team: 2FA enforcement, RBAC with Access Groups, deployment retention policies.

Section 6: Enterprise Controls

The big-ticket controls for compliance and scale: SAML, Audit Logs, Trusted IPs, Secure Compute, managed firewall rulesets, plus a sidebar on compliance certifications.