Digital Engines logoDigital Engines
←Back to Journal
Cloud & Deployment·September 29, 2026·9 min read

Deploying Next.js on Vercel: setup, pricing and our production checklist

DE
Digital Engines
Design & Technology Studio
Performance dashboard representing a deployed web application
ESSAY · 9 min read

Vercel is the company behind Next.js, and its platform is the smoothest way to host Next.js apps. Static pages are served from a global CDN, server code runs as functions that scale automatically, and every Git branch gets its own preview. Here's how we set up client projects on Vercel.

1. Why we use Vercel for Next.js

Vercel supports new Next.js features on day one: Server Components, image optimisation, caching and middleware all work with zero configuration. There are no servers to patch and no load balancers to manage.

  • Automatic deployments from GitHub, GitLab or Bitbucket.
  • Preview URLs for every pull request, ideal for client and QA feedback.
  • Global CDN, automatic HTTPS and custom domains.
  • Built-in analytics, logs and instant rollbacks to any previous deployment.
“Every pull request gets its own live URL. That one feature changes how clients review work.”
— Strategic Takeaway

2. Deploy from Git (recommended)

Import the repository in the Vercel dashboard, confirm the detected framework (Next.js), add environment variables and deploy. From then on, every push to the main branch updates production and every other branch gets a preview deployment.

Deploying Next.js on Vercel: setup, pricing and our production checklist visual illustration
FIG. 01 — Cloud & Deployment Study

3. Deploy and manage with the CLI

The Vercel CLI is useful for linking local projects, syncing environment variables and manual deployments.

Vercel CLI essentialsbash
npm install -g vercel

vercel login             # sign in
vercel link              # connect this folder to a Vercel project
vercel env pull .env.local   # download environment variables for local dev
vercel                   # create a preview deployment
vercel --prod            # deploy to production
Add a secret environment variablebash
vercel env add DATABASE_URL production
# repeat for preview and development environments as needed

4. Scheduled jobs with Vercel Cron

Need to send a daily report or clean up old records? Vercel Cron calls one of your routes on a schedule. Protect the route so only Vercel can trigger it.

vercel.jsonjson
{
  "crons": [
    { "path": "/api/cron/daily-report", "schedule": "0 6 * * *" }
  ]
}
app/api/cron/daily-report/route.tsts
export async function GET(request: Request) {
  // Vercel sends this header when CRON_SECRET is set in your env vars
  if (request.headers.get("authorization") !== `Bearer ${process.env.CRON_SECRET}`) {
    return new Response("Unauthorized", { status: 401 });
  }

  // ...generate and email the report
  return Response.json({ ok: true });
}

5. Pricing

Pricing (checked November 2026): Hobby is free but limited to personal, non-commercial use. Pro costs $20 per developer seat per month and includes $20 of monthly usage credit; viewers are free. Usage beyond the included amounts (data transfer, function CPU time, image optimisation and more) is billed separately. Enterprise is custom.

For most business websites and early-stage SaaS products, Pro with one or two developer seats is enough. Costs grow with heavy server-side rendering, large image volumes and long-running functions, so we monitor usage monthly.

6. Our production checklist

Before any client site goes live on Vercel, we check the following.

  • Environment variables set separately for production, preview and development.
  • Custom domain connected, with redirects from www or non-www to one canonical version.
  • Spend management enabled, with a budget alert on the team.
  • Preview deployments protected with Vercel Authentication or a password if they contain private data.
  • Database and APIs hosted in a region close to the function region to reduce latency.
  • Analytics and Speed Insights enabled, and Core Web Vitals reviewed.
  • Rollback tested: we know how to instantly promote the previous deployment.
Core Takeaways

Principles for deliberate execution

  • 1Connect your Git repository once; every push to main deploys production automatically.
  • 2Preview deployments give every pull request a shareable URL for client review.
  • 3The Hobby plan is for personal, non-commercial projects. Client sites belong on Pro.
  • 4Set spend limits and watch function usage, the main source of unexpected bills.
Tagged:#Vercel#Next.js#Deployment#Serverless#CI/CD
DE
Written by
Digital Engines

Digital Engines engineers SaaS platforms, high-performance websites, mobile apps and AI systems for ambitious teams worldwide. These guides come from the tools we use on real client projects every day.

Get in touch →
Continue reading

More from the journal

All essays →