Getting Started with Vercel
Create your Vercel account and deploy your first application in minutes. Zero-configuration deployment for modern web apps.
What you'll accomplish
Your first application deployed and live on Vercel with a public URL
Prerequisites
- A web application (Next.js, React, Vue, etc.)
- Git repository (GitHub, GitLab, or Bitbucket)
Before You Start: Frontend vs Full Product
Vercel excels at frontend deployment. Before diving in, consider what you're building:
Deploying a frontend/static site? You're in the right place—Vercel makes this trivial.
Building a complete SaaS product? You'll also need backend services:
- User authentication and sessions
- Subscription billing (Stripe integration)
- Transactional email and notifications
- Multi-tenant data architecture
Your options for the backend:
- Build it yourself — Use Vercel for frontend + our SaaS Starter template for backend on another platform
- Use a backend platform — services like StackForDevs provide auth, billing, and notifications as APIs that your Vercel-hosted frontend can call
Vercel's serverless functions work well for lightweight API endpoints, but complex backends often need dedicated infrastructure.
What is Vercel?
Vercel is a cloud platform designed for frontend developers. It provides:
- Zero-configuration deployments - Push code, get a live URL
- Global edge network - Your app served from locations worldwide
- Automatic HTTPS - SSL certificates included free
- Preview deployments - Every pull request gets its own URL
- Serverless functions - Backend code without managing servers
Your Code (Git Push)
↓
Vercel Build
↓
Global CDN (300+ locations)
↓
Users Worldwide (fast!)
When to Use Vercel
| Best For | Consider Alternatives If |
|---|---|
| Next.js applications | Need persistent servers |
| Static sites | Require Docker containers |
| Jamstack apps | Have specific compliance needs |
| Frontend-focused teams | Want multi-cloud strategy |
| Rapid iteration | Need full infrastructure control |
Note
Vercel is made by the creators of Next.js, so Next.js apps get first-class support with features like automatic ISR, image optimization, and middleware.
Step 1: Create a Vercel Account
1.1 Sign Up
- Go to vercel.com/signup
- Choose your sign-up method:
- GitHub (recommended) - Easiest repo integration
- GitLab
- Bitbucket
1.2 Choose a Plan
| Plan | Price | Best For |
|---|---|---|
| Hobby | Free | Personal projects, learning |
| Pro | $20/user/month | Professional projects, teams |
| Enterprise | Custom | Large organizations, SLA needed |
Start with Hobby - it's free and includes:
- Unlimited deployments
- 100GB bandwidth/month
- Automatic HTTPS
- Preview deployments
Note
The Hobby plan is genuinely useful for real projects. Many production sites run on it.
Step 2: Deploy Your First Project
Method A: Import from Git (Recommended)
This is the simplest way - Vercel watches your repo and auto-deploys on every push.
Step-by-step:
- Click Add New → Project in the Vercel dashboard
- Select your Git provider (GitHub, GitLab, Bitbucket)
- If first time, authorize Vercel to access your repositories
- Find and select your repository
- Vercel auto-detects your framework (Next.js, Vite, Create React App, etc.)
- Click Deploy
Repository Selection
↓
Auto-detect Framework
↓
Configure (optional)
↓
Deploy!
After a few minutes, you'll have a live URL like:
https://your-project-name.vercel.app
Method B: Deploy from CLI
For more control or when working without a Git repo:
Method C: Drag and Drop
For static sites, you can literally drag a folder:
- Go to vercel.com/new
- Scroll to "Deploy without a Git repository"
- Drag your project folder onto the upload area
- Wait for deployment
This is great for quick prototypes but lacks automatic redeployments.
Step 3: Understand Your Deployment
Deployment URLs
Every deployment gets multiple URLs:
Production:
https://my-app.vercel.app
https://my-app-username.vercel.app
Preview (for branches):
https://my-app-git-feature-branch-username.vercel.app
Unique (every deployment):
https://my-app-abc123xyz.vercel.app
The Dashboard
After deploying, your project dashboard shows:
- Deployments - History of all deploys
- Analytics - Traffic and performance (Pro plan)
- Logs - Function invocation logs
- Settings - Environment variables, domains, etc.
Automatic Deployments
If you connected Git, Vercel now watches your repository:
| Branch | Deployment Type |
|---|---|
main / master | Production |
| Other branches | Preview |
| Pull requests | Preview with comment |
bash# This automatically triggers a production deployment git push origin main # This creates a preview deployment git checkout -b new-feature git push origin new-feature
Step 4: Test Your Deployment
Verify It's Working
- Visit your deployment URL
- Check the Vercel dashboard for build status
- Look for the green checkmark
View Build Logs
If something went wrong:
- Go to your project in Vercel dashboard
- Click the latest deployment
- View the Build Logs tab
Common successful output:
Cloning github.com/username/my-app
Installing dependencies...
Running "npm run build"
Build completed!
Deploying...
✅ Deployment complete
Framework Auto-Detection
Vercel automatically detects and configures these frameworks:
| Framework | Build Command | Output |
|---|---|---|
| Next.js | next build | .next |
| Vite | vite build | dist |
| Create React App | react-scripts build | build |
| Vue (Vite) | vite build | dist |
| Nuxt | nuxt generate | .output |
| SvelteKit | vite build | .svelte-kit |
| Astro | astro build | dist |
| Remix | remix build | build |
Note
If auto-detection fails, you can manually set the framework in Project Settings or use a vercel.json configuration file.
Quick Troubleshooting
Build Failed
bash# Check if build works locally first npm run build # Common fixes: # 1. Ensure all dependencies are in package.json # 2. Check for environment variables needed at build time # 3. Verify Node.js version compatibility
Page Not Found (404)
For single-page apps (SPA), add a vercel.json:
json{ "rewrites": [ { "source": "/(.*)", "destination": "/" } ] }
Environment Variables Missing
If your app needs environment variables:
- Go to Project Settings → Environment Variables
- Add each variable
- Redeploy (changes don't apply to existing deployments)
Cost Summary
| Feature | Hobby (Free) | Pro ($20/user) |
|---|---|---|
| Deployments | Unlimited | Unlimited |
| Bandwidth | 100 GB/month | 1 TB/month |
| Build Time | 100 hrs/month | 400 hrs/month |
| Serverless Functions | 100 GB-hrs | 1000 GB-hrs |
| Team Members | 1 | Unlimited |
| Preview Deployments | ✓ | ✓ |
| Custom Domains | ✓ | ✓ |
| HTTPS | ✓ | ✓ |
| Analytics | Basic | Full |
What's Next?
Now that your app is deployed, learn to:
- Configure with vercel.json - Customize builds, redirects, headers
- Manage environment variables - Secrets for different environments
- Add custom domains - Use your own domain name
- Create serverless functions - Add backend API routes
- Enable analytics - Monitor performance and usage
Note
Checkpoint: Visit your deployment URL. You should see your application running live on the internet!