# Vercel

Canonical: https://inetgeek.com/hosting/vercel/

Frontend cloud platform for modern web applications, with Git-driven deployments and a framework-aware CDN.

## 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.

## Adoption signals

- Detected running on 4,244,009 live sites (BuiltWith, checked 2026-09-12)

## iScore

75 / 100 (80% interval 68–81), rank 1 of 6 in hosting — interval overlaps the next rank, so this is an ordering, not a finding.

inetGeek's own reading, computed from sourced facts against category peers by disclosed rules. Not a provider claim. Intervals are 80%; a provider with few documented facts is pulled toward the category middle rather than scored on what little is known.
Method: https://inetgeek.com/iscore/. Full output with every criterion's basis: https://inetgeek.com/scores.json. Every hosting peer ranked: https://inetgeek.com/hosting/vercel/alternatives/

- Price: 80 (59–100), weight 25%, 2 of 5 criteria scored; scored for peers, not here — undocumented or stated without a number or a yes/limited/no: egress_overage_price, free_card_required, minimum_paid_price
- Capacity and limits: 50 (43–56), weight 20%, 4 of 8 criteria scored; scored for peers, not here — undocumented or stated without a number or a yes/limited/no: bandwidth_included, concurrent_builds, cpu_time_limit, max_request_duration
- Capabilities: 79 (63–95), weight 20%, 7 of 10 criteria scored; scored for peers, not here — undocumented or stated without a number or a yes/limited/no: managed_databases, persistent_processes, persistent_storage
- Trust and compliance: 75 (60–90), weight 15%, 8 of 10 criteria scored; scored for peers, not here — undocumented or stated without a number or a yes/limited/no: private_networking, support_included
- Evidence: 97 (97–97), weight 10%, 4 of 4 criteria scored
- Adoption: 80 (70–90), weight 10%, 1 of 2 criteria scored

## What the documentation says

### Pricing

- Free tier: Yes ([source](https://vercel.com/docs/plans/hobby), read 2026-09-05)
- Kind of free offer: Free tier ([source](https://vercel.com/docs/plans/hobby), read 2026-09-05)
- Entry paid plan: $20 per developer seat / month (Pro) ([source](https://vercel.com/docs/plans/hobby), read 2026-09-05)
- Pricing model: Per-seat subscription plus metered resource usage; CDN charges cover requests, data transfer to visitors and Fast Origin Transfer, and vary by the region a request comes from. ([source](https://vercel.com/docs/cdn), read 2026-09-14)
- Egress over allowance: Fast Data Transfer: first 1 TB included, then $0.15-$0.35 per GB depending on region. ([source](https://vercel.com/docs/pricing/regional-pricing), read 2026-09-13)
- When you exceed a cap: Billed automatically: extra usage beyond the included amount or Pro credit is charged, not throttled or suspended ([source](https://vercel.com/docs/pricing), read 2026-09-05)
- Startup credit program: Vercel for Startups: up to $30,000 in Flexible Commitment Amount, Enterprise-tier access, and startup-focused support for eligible teams. ([source](https://vercel.com/startups), read 2026-09-11)

### Limits

- Memory (entry plan): 2 GB and 1 vCPU by default on every plan; Pro and Enterprise can raise it to 4 GB and 2 vCPU. ([source](https://vercel.com/docs/functions/limitations), read 2026-09-13)
- Sites or apps included: 200 projects on Hobby; unlimited on Pro and Enterprise. ([source](https://vercel.com/docs/limits), read 2026-09-13)
- 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. ([source](https://vercel.com/docs/limits), read 2026-09-13)
- File, inode or volume limit: 15,000 source files per CLI deployment (platform-wide); no upper limit on output files created during a build ([source](https://vercel.com/docs/limits), read 2026-09-14)
- Build allowance: No monthly build-minute allowance. Build CPU minutes are billed from $0.0035 each on Pro, against the plan's usage credit, and any single build is capped at 45 minutes. ([source](https://vercel.com/docs/limits), read 2026-09-06)
- Concurrent builds: Pro: up to 500 concurrent deployments with on-demand concurrency, or 3 if on-demand concurrency is off ([source](https://vercel.com/docs/builds/managing-builds), read 2026-09-14)
- Max request duration: Hobby: 300s default and maximum. Pro and Enterprise: 300s default, 800s maximum, and 1800s extended maximum ([source](https://vercel.com/docs/functions/limitations), read 2026-09-13)

### Execution

- Edge function timeout: Edge runtime: a response must begin within 25 seconds to keep streaming beyond that point, and streaming can then continue for up to 300 seconds. ([source](https://vercel.com/docs/functions/limitations), read 2026-09-13)
- 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. ([source](https://vercel.com/docs/functions/limitations), read 2026-09-05)
- Managed connection pooling: Limited ([source](https://vercel.com/guides/connection-pooling-with-serverless-functions), read 2026-09-05)

### Deployment

- Git deployment: Supported ([source](https://vercel.com/docs/git), read 2026-09-14)
- Scheduled jobs: Supported ([source](https://vercel.com/docs/cron-jobs), read 2026-09-05)

### Infrastructure

- Edge network: Supported ([source](https://vercel.com/docs/cdn), read 2026-09-05)
- Scales to zero: Supported ([source](https://vercel.com/docs/fundamentals/what-is-compute), read 2026-09-05)
- Autoscaling: Supported ([source](https://vercel.com/docs/functions/concurrency-scaling), read 2026-09-05)
- Regions: 20 compute-capable regions, from Stockholm and Mumbai to Cleveland and Cape Town; functions default to iad1 (Washington, D.C.). ([source](https://vercel.com/docs/regions), read 2026-09-14)
- Uptime SLA: 99.99% on Enterprise, which is custom-priced. Hobby and Pro publish no uptime SLA. ([source](https://vercel.com/pricing), read 2026-09-14)

### CDN

- Points of presence: 126 points of presence across 51 countries. ([source](https://vercel.com/docs/cdn), read 2026-09-14)

### Compliance

- SOC 2: SOC 2 Type 2 attestation. ([source](https://vercel.com/security), read 2026-09-12)
- ISO 27001: ISO 27001:2013 certified. ([source](https://vercel.com/security), read 2026-09-12)
- HIPAA: HIPAA compliance supported for enterprise customers. ([source](https://vercel.com/security), read 2026-09-12)
- GDPR / data residency: No data stored permanently inside EU regions; static assets/Serverless Function responses may cache in EU regions but only ephemerally. ([source](https://vercel.com/security), read 2026-09-12)
- PCI DSS: Attestations for both service providers (SAQ-D) and merchants (SAQ-A) under PCI DSS v4.0, on request. ([source](https://vercel.com/security), read 2026-09-14)
- Encryption at rest: AES-256 at rest and HTTPS/TLS in transit, including access tokens and secrets. ([source](https://vercel.com/security), read 2026-09-14)
- Role-based access control: Role-based access control, assigning roles per project. ([source](https://vercel.com/security), read 2026-09-14)
- Dedicated infrastructure: Enterprise teams get their own build infrastructure, isolated from Hobby and Pro accounts. ([source](https://vercel.com/security), read 2026-09-14)

## Compared with

- [Vercel vs Cloudflare Pages](https://inetgeek.com/compare/vercel-vs-cloudflare-pages/)
- [Vercel vs Netlify](https://inetgeek.com/compare/vercel-vs-netlify/)
- [Vercel vs AWS Amplify](https://inetgeek.com/compare/vercel-vs-aws-amplify/)