Vercel

What it does

Vercel is a hosting and deployment platform built for modern web apps, with the tightest integration around Next.js — the React framework Vercel itself maintains. You connect a Git repository, and Vercel builds and deploys it on every push, serving the result from a global edge network with HTTPS, caching, and serverless compute handled automatically.

The core primitives are: static and server-rendered pages, serverless functions (for API routes and dynamic rendering), edge functions and edge middleware (lighter compute that runs close to the user, useful for auth checks, redirects, and A/B routing), and a built-in image optimization service that resizes and reformats images on demand. More recent additions include first-class support for streaming server components, incremental static regeneration (rebuild individual pages without redeploying the whole site), and storage/data add-ons. The platform is framework-agnostic in principle — Astro, SvelteKit, Nuxt, Remix, and plain static sites all deploy — but Next.js is the path everything else is measured against.

Who it's best for

• Frontend and full-stack developers shipping React or Next.js apps who want zero infrastructure setup.
• Indie hackers and small teams who value preview deployments and fast iteration over fine-grained cost control.
• Agencies and freelancers managing many client sites, where per-project Git connections and preview URLs streamline review.
• Startups in the build-and-validate phase, where developer velocity matters more than squeezing out the cheapest possible bandwidth.

If your stack is Next.js, Vercel is the default choice and it's hard to argue against it for the first months or years of a project.

Where it's strong

Developer experience. This is the real product. A git push triggers a build, and a working URL appears. Every pull request gets its own preview deployment with a shareable link, so designers and stakeholders can click through a feature before it merges. Bad deploys roll back in one click, and the build logs are readable. Time-from-repo-to-live-site is genuinely a few minutes.

Edge network and performance. Static assets and cached responses are served from points of presence worldwide, so latency is low regardless of where users are. Edge middleware lets you run logic (geolocation routing, auth gating, feature flags) before a request hits your application, which is hard to replicate cleanly on traditional hosts.

Next.js parity. Because Vercel builds Next.js, new framework features tend to work on Vercel on day one — server actions, partial prerendering, and the latest caching behaviors are tested against this platform first. If you're on the bleeding edge of Next.js, this matters.

Free tier that ships real projects. The Hobby plan handles meaningful personal-project traffic at no cost, including HTTPS, preview deploys, and serverless functions. You can launch a side project and pay nothing until it has actual users.

Where it's weak

Cost scaling is the recurring complaint. The jump from Hobby (free) to Pro is straightforward, but usage-based charges for bandwidth, function invocations, and image optimization can produce bills that surprise teams who didn't model their traffic. A site that goes viral, or one that serves large media, can run up costs faster than the same workload on a flat-rate VPS or on Cloudflare. The platform is priced for convenience, not for being the cheapest place to serve bytes.

Function execution limits. Serverless and edge functions have execution-time and resource ceilings, and they're tighter on lower tiers. Long-running work — large file processing, slow third-party API chains, or extended LLM generation calls — can hit a timeout mid-request. The workaround is offloading to background jobs or a separate compute service, which adds architecture you wouldn't need on a long-lived server.

Gravity toward Next.js and the Vercel ecosystem. Non-Next.js frameworks are supported but are clearly second-class in documentation depth and feature timing. Lean on Vercel's proprietary storage, analytics, and edge config products and you accumulate platform-specific code that complicates a future migration. Standard Next.js apps remain reasonably portable; heavy use of Vercel-only primitives does not.

Limited fit for stateful or non-web workloads. Vercel is a frontend-and-edge platform, not a general compute host. Persistent WebSocket servers, long-running daemons, cron-heavy backends, GPU jobs, and databases all live elsewhere. You'll pair Vercel with a separate backend or managed database rather than running everything in one place.

Pricing context

Vercel offers a genuinely free Hobby tier; paid plans start at $20/month (Pro), with Enterprise priced on request. The important nuance is that the headline plan price is a floor, not a ceiling — most of the real cost on busy sites comes from metered usage (bandwidth, function execution, image optimization) layered on top of the base plan. Estimate your traffic and media weight before assuming the monthly cost is just the plan price. A weekly check re-verifies current figures, so treat exact numbers as a starting point.

Who should skip it

• Cost-sensitive, high-bandwidth sites (large video, image galleries, heavy downloads) — a VPS or Cloudflare-fronted setup is usually cheaper at scale.
• Backend-heavy apps needing persistent processes, long-running jobs, or WebSocket servers — a traditional host or container platform fits better.
• Teams wanting to avoid platform lock-in who plan to lean on proprietary storage and edge products — the portability cost adds up.

Verdict

For Next.js and React apps you want to ship quickly, Vercel is the right default and the Hobby tier is free enough for serious side projects. Its developer experience and Next.js integration are best-in-class, and the trade-off is predictable: you pay for convenience, and metered usage can climb on high-traffic or media-heavy sites.

If you want comparable ergonomics with different defaults, Netlify is the closest peer. If you want the most generous free bandwidth and an edge-first model, Cloudflare Pages (with Workers) is the strongest alternative, especially for cost-sensitive projects. For apps that need a real always-on backend, a container platform such as Railway or Render is a better base. Start with Vercel, model your usage early, and you'll know within the first month whether to stay or move heavier workloads elsewhere.