A guide to deploying your frontend on Vercel, the company behind Next.js. Covers GitHub integration, environment variables, custom domains, Preview deployments, and Functions — all focused on real-world workflows.
Hobby plan
Free for personal use
Pro plan
$20/mo/user
Requirements
GitHub account
Overview
The Hobby plan prohibits commercial use. Company projects must use Pro or higher to stay compliant with the ToS. Custom domains work on the free plan, but team collaboration, analytics, and security features start with Pro.
GitHub repo
The project repository to deploy.
Domain registrar
Whois, Gabia, Cloudflare, etc.
Separate env vars
Never commit .env.local.
Region selection
Functions default to icn1 (Seoul).
Step by Step
SIGNUP
Create an account at vercel.com.
CONNECT
Link GitHub with Vercel.
ENV
Register required env vars before deploy.
DEPLOY
Push to main for an automatic Production deploy.
DOMAIN
Attach your domain to the project.
SECURITY
Hide preview URLs from the public.
FUNCTIONS
Configure Serverless and Edge Functions.
ANALYTICS
Enable visitor and performance metrics.
Pitfalls
Commercial use on Hobby
Running a company site or paid service on Hobby violates the ToS. Upgrade to at least Pro ($20/mo).
Misusing NEXT_PUBLIC_
Anything with this prefix ends up in the browser bundle. Never prefix DATABASE_URL or API_SECRET with NEXT_PUBLIC_.
Edge Runtime compatibility
Node-only modules like pg, bcrypt, and fs do not run on the Edge. Use the Node.js runtime or switch to serverless.
Committing .env.local
It is in .gitignore, but once committed it stays in history. Rotate keys immediately.
Changing the Production Branch
Switching the Production Branch away from main moves your domain to that branch. Avoid mistakes.
Projects at JAICYLAB include everything from developer account setup to launch and ops.