Vercel
Frontend cloud platform for modern web applications, with Git-driven deployments and a framework-aware CDN.
- frontend serverless
- Yes
- $20 per developer seat / month (Pro)
- 126 PoPs across 51 countries
Who it suits.
Teams building on a framework the CDN understands natively, who want a predictable per-seat cost with metered usage on top. The Git integration covers GitHub, GitLab, Bitbucket and Azure DevOps, so it drops into an existing review workflow.
Consider something else if…
The team is large enough that $20 per developer seat dominates the bill rather than the metered usage underneath it.
Editorial · Palash Bagchi · approved
What the documentation says.
Each value below links to the page it was read from, with the sentence it came from. Criteria Vercel does not publish are not listed.
Pricing
Free tier
Yes
Sources (1) →Sources ↓
- Vercel Hobby Plan ↗
“The Hobby plan is free and aimed at developers with personal projects, and small-scale applications.”
Read 2026-09-05 · official docs
Entry paid plan
$20 per developer seat / month (Pro)
Sources (1) →Sources ↓
- Vercel Hobby Plan ↗
“Developer seats cost $20 per user / month, while Viewer seats are free”
Read 2026-09-05 · official docs
Pricing model
Per-seat subscription plus metered resource usage
Sources (1) →Sources ↓
- Vercel CDN overview ↗
“CDN pricing covers three billable resources: Edge Requests, Fast Data Transfer, and Fast Origin Transfer.”
Read 2026-09-05 · official docs
Egress over allowance
Fast Data Transfer: 1 GB for $0.15 - $0.35 (after First 1 TB included)
Sources (1) →Sources ↓
- Regional Pricing - Vercel Docs ↗
“| Fast Data Transfer | First 1 TB | 1 GB for $0.15 - $0.35 |”
Read 2026-09-05 · official pricing
When you exceed a cap
Billed automatically: extra usage beyond the included amount or Pro credit is charged, not throttled or suspended
Sources (1) →Sources ↓
- Pricing on Vercel ↗
“Some resources include an amount of usage your projects can use within your billing cycle. Pro teams also receive a monthly usage credit and can use many resources on demand. If you exceed an included amount or credit, Vercel charges for the extra usage.”
Read 2026-09-05 · official docs
Limits
Memory (entry plan)
Vercel Functions on Pro: 2 GB / 1 vCPU default, 4 GB / 2 vCPU maximum. Basic build machine has 2 vCPUs and 8 GB of memory.
Sources (1) →Sources ↓
- Vercel Functions Limits ↗
“Vercel Functions have the following defaults and maximum limits: | Pro / Enterprise | 2 GB / 1 vCPU | 4 GB / 2 vCPU |”
Read 2026-09-05 · official docs
Sites or apps included
Unlimited Projects on Pro (200 on Hobby)
Sources (1) →Sources ↓
- Limits ↗
“| Projects | 200 | Unlimited | Unlimited |”
Read 2026-09-05 · official docs
Monthly visits cap
No hard visit cap on Pro. Pro includes the first 10,000,000 Edge Requests and the first 1 TB of Fast Data Transfer, with additional consumption billed on demand.
Sources (1) →Sources ↓
- Limits ↗
“Pro includes a credit that you can use across billable resources and a pay-as-you-go model for additional consumption. Vercel automatically charges extra usage at the following rates: [...] | [Fast Data Transfer](/docs/pricing/regional-pricing) | Regional | First 1 TB | [...] | [Edge Requests](/docs/pricing/regional-pricing) | Regional | First 10,000,000 |”
Read 2026-09-05 · official docs
File or inode limit
15,000 source files per CLI deployment (platform-wide); no upper limit on output files created during a build
Sources (1) →Sources ↓
- Limits ↗
“The maximum number of files that can be uploaded when creating a CLI Deployment is `15,000` for source files. Deployments that contain more files than the limit will fail at the build step. Although there is no upper limit for output files created during a build, you can expect longer build times as a result of having many thousands of output files (100,000 or more, for example).”
Read 2026-09-05 · official docs
Concurrent builds
Pro: up to 500 concurrent deployments with on-demand concurrency, or 3 if on-demand concurrency is off
Sources (1) →Sources ↓
- Managing Builds ↗
“**Pro:** Up to 500 concurrent deployments with on-demand concurrency (3 if on demand is off). You are billed for the build minutes you use.”
Read 2026-09-05 · official docs
Max request duration
Hobby: 300s default and maximum. Pro and Enterprise: 300s default, 800s maximum, and 1800s extended maximum
Sources (1) →Sources ↓
- Vercel Functions Limits - Vercel Docs ↗
“Maximum duration | Hobby: 300s default and maximum. Pro and Enterprise: 300s default, 800s maximum, and 1800s extended maximum .”
Read 2026-09-05 · official docs
Execution
Edge function timeout
Edge runtime: must begin sending a response within 25 seconds to keep streaming beyond that point; streaming may then continue for up to 300 seconds. Stated for the Edge runtime specifically, not plan-differentiated (applies on Pro, the cheapest paid plan).
Sources (1) →Sources ↓
- Vercel Functions Limits ↗
“Edge runtime — Vercel Functions using the Edge runtime must begin sending a response within 25 seconds to maintain streaming capabilities beyond this period, and can continue streaming data for up to 300 seconds.”
Read 2026-09-05 · official docs
Streaming response limit
Edge runtime streaming: up to 300 seconds, provided the response starts within 25 seconds. For Node.js/Bun/Python runtimes the docs state that max duration covers streamed responses too (Pro: 300s default, 800s maximum). Not plan-differentiated for the Edge figure.
Sources (1) →Sources ↓
- Vercel Functions Limits ↗
“Vercel Functions using the Edge runtime must begin sending a response within 25 seconds to maintain streaming capabilities beyond this period, and can continue streaming data for up to 300 seconds.”
Read 2026-09-05 · official docs
Managed connection pooling
Limited
Sources (1) →Sources ↓
- Connection Pooling with Vercel Functions — Vercel Guides ↗
“On Fluid compute, the default execution model for new Vercel projects, Functions reuse global state within a warm instance. Multiple concurrent invocations share the same instance, so they can share a single database connection or connection pool instead of opening a new connection on every request. To pool connections safely, initialize your pool in the global scope and register it with attachDatabasePool from @vercel/functions [...] This helper closes idle connections before an instance suspends, which keeps your connection count under control.”
Read 2026-09-05 · official docs
Deployment
Git deployment
Supported
Sources (1) →Sources ↓
- Deploying Git Repositories with Vercel ↗
“Vercel allows for automatic deployments on every branch push and merges onto the production branch of your GitHub, GitLab, Bitbucket, and Azure DevOps Pipelines projects.”
Read 2026-09-05 · official docs
Scheduled jobs
Supported
Sources (1) →Sources ↓
- Cron Jobs - Vercel Docs ↗
“Vercel supports cron jobs for Vercel Functions. Cron jobs can be added through vercel.json or the Build Output API.”
Read 2026-09-05 · official docs
Infrastructure
Edge network
Supported
Sources (1) →Sources ↓
- Vercel CDN overview ↗
“Vercel operates 126 Points of Presence (PoPs) across 51 countries.”
Read 2026-09-05 · official docs
Scales to zero
Supported
Sources (1) →Sources ↓
- What is Compute? - Vercel Docs ↗
“You never pay for idle CPU, and you pay nothing between requests.”
Read 2026-09-05 · official docs
Autoscaling
Supported
Sources (1) →Sources ↓
- Concurrency scaling - Vercel Docs ↗
“All functions on Vercel scale automatically based on demand to manage increased traffic loads. [...] Automatic concurrency scaling is available on all plans.”
Read 2026-09-05 · official docs
Regions
126 PoPs across 51 countries
Sources (1) →Sources ↓
- Vercel CDN overview ↗
“Vercel operates 126 Points of Presence (PoPs) across 51 countries.”
Read 2026-09-05 · official docs