What Is Vercel? What It Does, What It Costs You, and When to Use Something Else
Vercel is a hosting platform built around frontend frameworks, especially Next.js: push to GitHub and your site is live. What it actually does, what serverless functions mean for your app, where the limits are, and when a regular server is a better fit.
If you've built an app with v0, Bolt, or Claude, someone has probably told you to "just put it on Vercel." Vercel is a hosting platform: you connect a GitHub repository, and every time you push, it builds your site and puts it online at a URL. It's made by the same company that makes Next.js, so Next.js apps work there with almost no setup.
What Vercel actually does
- Builds your code. It runs your build command (
npm run build) on its own machines. - Serves the static parts from a CDN. HTML, CSS, JavaScript and images are copied to servers around the world, so they load fast everywhere. (What is a CDN?)
- Runs your backend code as functions. API routes and server-rendered pages don't run on a server that's always on. They run as serverless functions: little pieces of code that start when a request arrives and stop afterwards. (What is serverless?)
- Gives every branch a preview URL. Push a branch, get a link to that version. This is genuinely useful for showing changes before they go live. (Preview environments explained)
- Handles domains and SSL. Point your domain at it and HTTPS just works.
Why people like it
- Zero server management. No operating system, no patching.
- The free tier is enough for a personal project or a demo.
- Git-push-to-deploy is the smoothest workflow there is.
For a marketing site, a portfolio, or a frontend that talks to someone else's API, it's hard to beat.
Where the model starts to pinch
Serverless is a trade-off, and AI-built apps often hit its edges:
- No long-running work. Functions have time limits. A job that takes ten minutes — processing a video, a long AI task, a nightly import — needs to live somewhere else. (Background jobs)
- No persistent disk. Files your code writes disappear after the request. User uploads must go to object storage. (Where should user uploads go?)
- No database included by default. You connect an external database (Vercel's marketplace offers partners such as Neon and Supabase). That's another account and another bill.
- Database connections. Thousands of short-lived functions can each open a database connection and exhaust it. You'll need a pooler. (Connection pooling explained)
- WebSockets and always-on processes don't fit the function model well.
- Usage-based billing. The bill depends on requests, function time and bandwidth. That's cheap at low traffic and can surprise you if a page goes viral or a bot hammers an endpoint.
None of this is a flaw — it's the shape of the product. It just means "deploy to Vercel" is the complete answer only for apps that are mostly frontend.
Vercel vs a regular server
| Vercel | A server (VPS or managed) | |
|---|---|---|
| Setup | Connect GitHub, done | More setup, unless managed |
| Static sites | Excellent | Fine |
| Long jobs, queues, cron | Limited | Natural |
| Database | External | Can live on the same machine |
| Pricing | Usage-based | Flat monthly |
| WebSockets | Awkward | Natural |
(VPS vs PaaS goes deeper into this choice.)
Do you have to use Vercel for Next.js?
No. Next.js runs anywhere Node.js runs — next build then next start, or a Docker container. A few Vercel-specific conveniences need replacing, which we cover in self-hosting Next.js.
The summary
- Vercel builds your app from GitHub and serves it worldwide, with backend code as serverless functions.
- It's excellent for frontends, marketing sites and preview links.
- Long jobs, file storage, databases and WebSockets need other services.
- Billing is usage-based; a regular server is flat-priced.
EasySpawn runs your whole app — frontend, backend, background jobs and a Postgres database — on one dedicated server with flat monthly pricing, automatic SSL and daily backups. See how it works for AI-built apps or join the waitlist.
Related: Vercel vs Netlify vs Cloudflare Pages · How to Deploy a v0 App · Self-Hosting Next.js Without Vercel · What Is Serverless?
Keep reading
Why Does My App Work Locally but Not in Production?
The app runs perfectly on your machine and breaks the moment it's deployed. It's almost always one of about a dozen causes — missing environment variables, localhost URLs, a filesystem that doesn't persist. How to find which one, in the order most likely to be it.
What Is Web Hosting? A Plain-English Guide for First-Time App Builders
Your app has to run on a computer that's always on and connected to the internet. That's hosting. The main kinds — static hosting, app hosting, servers you manage, and managed platforms — what each is for, and how to tell which one your app needs.