Application hosting / PaaS: read the guide

Vercel

HostedPaaS

Agentic Infrastructure

Homepage Docs Pricing

Scanned 15 Oct 2026 · Schema v5 · features v21

From: $20/mo
Hobby free; Pro $20/month platform fee including one deploying seat and $20 monthly infrastructure credit, plus usage and $20/month for each additional deploying seat; Enterprise negotiated.
Free tier: Yes
Hobby: personal/non-commercial only, 4 active CPU-hours, 360 GB-memory-hours and 1M Function invocations/month; 100GB transfer and 1M CDN requests. Free plan has hard usage caps.
Isolation: Not disclosed
the public docs do not say
Regions: 19
Stockholm, Sweden (eu-north-1) · Mumbai, India (ap-south-1) · Paris, France (eu-west-3) · Cleveland, USA (us-east-2) · Cape Town, South Africa (af-south-1) · Dublin, Ireland (eu-west-1) +13
Capabilities: 32 / 61
7 partial · 22 fail · 0 not assessed
Agent readiness: 10/11 · 11/11
read · drive, pre-login surface

Advertised for

Static/CDN and SSR web apps · Serverless HTTP APIs on Node.js, Bun, Python and other supported Functions runtimes · Custom OCI/Dockerfile HTTP container Functions · Multi service projects with deployment scoped service bindings and previews · Durable JavaScript/TypeScript/Python workflows · Hosted MCP servers and AI applications using Gateway/Connect

Built for

Developers, then semi-technical builders

· Homepage: coding agents deploy with Vercel API, CLI, MCP and Skills (https://vercel.com).
· Deep Functions/Dockerfile/region references and active-CPU infrastructure pricing (https://vercel.com/docs/functions.md; https://vercel.com/docs/functions/usage-and-pricing.md).
· Git-push deployments and full-stack Services previews (https://vercel.com/kb/guide/full-stack-preview-deployments-on-vercel.md).

01 Pricing Hobby free; Pro $20/month platform fee including one deploying seat and $20 monthly infrastructure credit, plus usage and $20/month for each additional deploying seat; Enterprise negotiated.

Tier	EntryHobby	Pro	TopEnterprise
Price	$0/month	$20/month platform + $20/month per additional deploying seat + usage	Custom
Includes	Personal/non-commercial free plan with hard monthly Functions and delivery quotas.	One deploying seat, unlimited free Viewer seats, $20 monthly managed-infrastructure credit and the lowest Flat Rate CDN tier (1M CDN requests/1TB transfer capacity).	Negotiated usage, support/SLA, Enterprise access controls and optional Secure Compute.
Transfer	100 GB	—	—
vCPU hours	4 h	—	—
Request count	1000000	—	—
Memory gb hours	360 h	—	—
Seats	—	1	—
Seats overage	—	$20/seat	—
vCPU hours overage	—	$0.128/h	—
Request overage	—	$0.0000006 per request	—
Memory gb hours overage	—	$0.0106/h	—

Free tier: Hobby: personal/non-commercial only, 4 active CPU-hours, 360 GB-memory-hours and 1M Function invocations/month; 100GB transfer and 1M CDN requests. Free plan has hard usage caps.

Platform/team-month + additional deploying-seat-month + active CPU-hour + provisioned GB-memory-hour + per-invocation and product-specific infrastructure usage.·Card required: unconfirmed·vercel.com

Overages: Pro iad1 Functions: $0.128/active CPU-hour, $0.0106/GB-memory-hour, $0.60/1M invocations. Blob: $0.023/GB-month, $0.40/1M simple and $5/1M advanced operations, $0.05/GB transfer. Service Requests beta: $0.50/1M. CDN capacity tiers and regional resource rates apply; $20 monthly credit offsets eligible infrastructure.

02 Website design Desktop public website · assessed 15 Oct 2026

Complete assessment.

A restrained monochrome desktop website combines oversized sans-serif headings, generous whitespace and systematic alignment. Pricing uses a finely divided three-column grid with a pink trial accent; docs adapt the same visual language to navigation, terminal examples and outlined resource panels.

Editorial minimalism
Swiss-inspired

Landing page: captured
Pricing: captured
Docs: captured

03 Runtime Each fact carries its source; dots show confidence. Open a row for the evidence.

Isolation & lifecycle

Isolation primitive

Not disclosedthe public docs do not say

Persistence

Stateless Functions/container instances; durable application data is external to the instance in Blob, Global Config or Marketplace backing services. Workflows persist execution state and event logs across deployments/crashes.

Snapshots / forks

Resources & limits

Storage

Native Vercel Blob object storage; Global Config (renamed Edge Config) for globally replicated runtime configuration; Postgres/Redis/NoSQL/vector data through Marketplace providers such as Neon, Upstash and Supabase.

Limits & quotas

Fluid Functions: Hobby 2GB/1vCPU and 300s maximum; Pro/Enterprise up to 4GB/2vCPU, 300s default/800s GA maximum. Extended 1800s maximum is beta for specified Node.js/Bun/Python versions/configuration. Auto concurrency 30,000 (Hobby/Pro), 100,000+ Enterprise; payload 4.5MB; 1,024 shared file descriptors.

GPU

Access

Deploy interface

git-pushdockerfilecontainer-imageclisdkapimcpdashboardtemplate

SDK languages

TypeScriptJavaScriptPython

Network & secrets

Egress controls

Static outbound IPs on Pro/Enterprise; Enterprise Secure Compute adds dedicated VPC networks and VPC peering/VPN connectivity.

Secrets

Project environment variables (including sensitive values) and OIDC workload identity; Connect brokers short-lived scoped OAuth/API credentials.

Bring your own cloud

Placement & use

Jurisdiction

US vendor Vercel Inc.; 19 compute-capable regions worldwide, default iad1 (Washington, D.C., USA), plus 126 CDN PoPs across 94 cities in 51 countries.

Advertised workloads

Static/CDN and SSR web appsServerless HTTP APIs on Node.js, Bun, Python and other supported Functions runtimesCustom OCI/Dockerfile HTTP container FunctionsMulti service projects with deployment scoped service bindings and previewsDurable JavaScript/TypeScript/Python workflowsHosted MCP servers and AI applications using Gateway/Connect

04 Capabilities 32 pass · 7 partial · 22 fail · 61 of 61 assessed

Supported — Documented on the public surface and verified.
Partially supported — Exists with caveats: gated, thin, or enterprise-only.
Not supported — Checked and not offered.
Not assessed — Scanned before this capability was tracked. Not a lack.

Compute & storage 3/11

Persistent diskStorage that survives restart/stop (not ephemeral-only).

Not supported

Object storageManaged S3-compatible / blob object store the platform PROVIDES to a user's workloads (buckets, presigned URLs). DISTINCT from persistent-disk (block/volume attached to an instance) and from a self-host dependency (source.self_host.deps[]=["object-storage"] is an infra dep to RUN an OSS tool — the opposite direction). SCOPE varies and matters: native first-class (Railway Buckets, Cloudflare R2) vs a sibling SKU / extension (Fly Tigris, Bunny Storage, DigitalOcean Spaces) — record which in the evidence quote / note. Admitted v15.

Supported

Snapshots / forkingSnapshot or copy-on-write fork of a running instance (filesystem-only counts). Whether the snapshot also restores memory + running processes is recorded separately by memory-snapshot (v19).

Not supported

Live-state (memory) snapshotsA snapshot / checkpoint / pause captures a running instance's MEMORY and PROCESS state and restores it, so running processes continue where they left off instead of a freshly booted instance with the same files. Counts whether user-triggered (snapshot, checkpoint, pause-to-storage) or used to restore pre-initialised state (memory snapshots for fast cold starts). Distinct from snapshots-forks (any snapshot or fork, including filesystem-only; a product passing that key may still fail this one) and from scale-to-zero (an idle-cost property; suspension may or may not keep memory). Actor multiplexing (see scale-to-zero) records its live-state half here — only when the suspended actor's MEMORY/process state is what comes back, not a freshly booted worker with the actor's files.

Not supported

Scale to zeroIdle instances suspend at no / negligible cost. ACTOR MULTIPLEXING (many suspended stateful actors sharing a small pool of pre-warmed workers, woken on request — Agent Substrate, AX, kagent; Rivet's hibernating actors) has NO key of its own (proposal REJECTED v20) — score the idle-cost half HERE and the live-state half under memory-snapshot; the oversubscription ratio / density is a performance characteristic the registry does not key.

Supported

GPU computeGPU-backed instances available.

Not supported

Multi-regionCompute placeable in more than one geographic region.

Supported

Sandbox templates / custom imagesBuild reusable sandbox/VM images from an OCI image or Dockerfile (a base you fork instances from).

Not supported

Cloud-init / ignition configCustomise a VM / microVM / instance at boot via cloud-init (or ignition) user-data — the same boot-metadata interface as AWS/Azure/GCP. Inject packages, users, SSH keys, files, and run-commands declaratively at launch. Distinct from sandbox-templates (a PREBUILT image you fork instances from) — this is PER-LAUNCH declarative customisation, not a baked image.

Not supported

Desktop / computer-use sandboxA virtual desktop (GUI) for LLM computer-use — browser + desktop automation, often via noVNC/VNC.

Not supported

Selectable isolation runtimeThe user chooses the isolation runtime per workload / environment / sandbox from more than one option (e.g. microVM vs gVisor vs plain container, native namespaces vs gVisor, gVisor vs VM). Records the CHOICE; the isolation_primitive facet still records the best-evidenced primary. A platform that switches runtime automatically without a user choice (e.g. gVisor forced for GPU) does not pass on that alone.

Not supported

Networking & delivery 6/9

Automatic HTTPSTLS endpoints provisioned automatically per workload.

Supported

Built-in reverse proxyPlatform routes external traffic to workload services.

Supported

Custom domainsBring-your-own domain via CNAME/DNS.

Supported

Public preview URLsShareable per-deploy / per-branch URLs.

Supported

Direct public IPv6Per-instance stable public IPv6 for raw TCP/UDP (beyond a managed HTTPS proxy) — e.g. mosh / raw sockets.

Not supported

Egress controlsConfigurable OUTBOUND network policy — egress firewall / allowlist / egress proxy on traffic LEAVING a workload. Scoped to OUTBOUND only (v15): private-network REACHABILITY between a user's own services is private-networking, not this. Static-egress-IP belongs here (an outbound concept).

Partially supported

Private networkingA platform-internal private network between a user's OWN services — service-to-service connectivity, VPC, service mesh, and/or service discovery, not exposed to the public internet. DISTINCT from egress-controls (OUTBOUND firewall/allowlist), reverse-proxy (PUBLIC inbound ingress), and direct-ipv6 (per-instance PUBLIC addressing). Admitted v15.

Supported

Email send / receiveSend and/or receive email from the workload.

Partially supported

Edge KV storeA globally-replicated key-value store read from WITHIN an edge runtime at the PoP (low-latency, eventually-consistent) — Cloudflare Workers KV, Deno KV, Fastly KV Store, Akamai EdgeKV, Vercel Edge Config. Distinct from first-party-db (a managed DATABASE service you provision and connect to) and from http-query-api (HTTP access to an external store) — edge-kv is colocated with the edge compute and read at the edge.

Supported

Developer access 7/10

Public APIDocumented programmatic API.

Supported

OpenAPI specMachine-readable OpenAPI / Swagger spec published.

Supported

CLIOfficial command-line tool.

Supported

SDKOfficial client library/libraries.

Supported

SSH accessDirect SSH into workloads.

Not supported

Filesystem APIRemote file operations over the API (list/read/write/watch/copy/upload) without SSH.

Not supported

Git deployDeploy from a Git repo / push-to-deploy.

Supported

Private container registryHosted private image registry.

Supported

E2B-compatible APIDrop-in compatibility with the E2B sandbox API/SDKs — existing E2B client code runs against this product by changing the endpoint/domain + key, with no business-code changes. E2B itself passes as the reference implementation. Distinct from public-api / sdk (the product has its own API — this key says it also speaks another vendor's) and from self-host-oss (a self-hosted E2B-compatible server is scored on both).

Not supported

HTTP data APIQuery / read / write the stored DATA over plain HTTP/REST (or GraphQL) WITHOUT the native protocol driver (Postgres wire / Redis RESP) — agent- and edge-friendly data access via fetch(). The DATA plane; distinct from public-api (a control-plane / management API). Auto-generated-from-schema REST/GraphQL (PostgREST, pg_graphql) is a flavour of this.

Supported

AI & agents 7/12

Built-in coding agentShips a first-party AI coding agent in the product.

Partially supported

Agent skillsInstallable / declarable agent skills or tools.

Supported

AI app builderPrompt-to-app / vibe-coding generation surface.

Supported

MCP serverExposes a Model Context Protocol server for agents.

Supported

MCP clientActs as an MCP client / consumes MCP tools.

Supported

MCP-server hostingRun/host MCP servers as a workload on the platform (distinct from exposing a first-party MCP control server — that is mcp-server).

Supported

LLM gatewayRoutes LLM API calls through the platform (multi-provider).

Supported

BYOK for LLMsBring-your-own LLM provider keys.

Supported

Model inference API (first-party)A FIRST-PARTY hosted LLM/model inference API — the provider serves its OWN catalogue of (usually open-weight) models behind a (typically OpenAI-compatible) endpoint, billed per token. Distinct from llm-gateway (a multi-PROVIDER proxy/router for YOUR calls to external providers like OpenAI/Anthropic) and from byok-llm (bring your own provider keys) — here the platform IS the inference provider, serving its own models.

Not supported

Autonomous QA agentA first-party AUTONOMOUS AI agent that QA-TESTS a running app / implementation — exercising it like a real user (clicking through flows, checking behaviour) and reporting bugs/defects (often back to a coding agent, or before a human review). Distinct from built-in-agent (a code-AUTHORING agent — this one VERIFIES the result, it does not write the feature; a product can ship both), from ai-guided-code-review (organises a diff for a HUMAN to review — not an autonomous tester), and from observability (runtime metrics/logs, not active testing).

Not supported

Credential-injection proxyThe platform holds real secrets OUTSIDE the workload and injects them on the wire (an egress / broker proxy swaps a placeholder or phantom token for the real credential on matching outbound requests), so code running in the sandbox — e.g. an untrusted agent — never sees or can exfiltrate the real key. Distinct from secrets-management (storage + injection INTO the workload as env vars/files — the workload holds the secret) and from egress-controls (outbound allow/deny POLICY; a product can have an allowlist without injecting credentials, and vice versa).

Not supported

Preinstalled coding agentThe platform installs and launches a THIRD-PARTY coding agent (a harnesses.yml entry — Claude Code, Codex, OpenCode, Pi ...) inside a workspace/sandbox it provisions, with the agent's auth wired in (your own account or API key), so you start an agent session rather than an empty box. Distinct from built-in-agent (a FIRST-PARTY agent the vendor ships) and from harnesses[] (which records that a harness CAN target the product, not that the product runs it for you).

Not supported

Data 0/4

First-party databasePlatform-provided managed database.

Not supported

Database branchingCopy-on-write branch of a DATABASE (schema + data) as a dev-lifecycle primitive — branch your data like code, usually instant via a metadata operation. Distinct from snapshots-forks (forks a running compute INSTANCE / VM state) and from preview-environments (a full per-PR environment that may USE a DB branch). For a data product a CoW branch maps HERE, not to snapshots-forks.

Partially supported

Vector searchFirst-class storage, indexing, and similarity search of vector embeddings — a native vector type/index or a managed vector DB. The data-layer primitive for RAG / semantic retrieval.

Partially supported

Ephemeral instant DB (no-signup)Provision a working, usable instance via a single command / HTTP call with NO account, signup, or card — typically time-boxed (expires unless claimed). A zero-onboarding path an agent can hit directly.

Not supported

Platform & operations 4/6

Scheduled tasksCron / scheduled job primitive.

Supported

Durable workflowsDurable execution / long-running workflow primitive.

Supported

Preview environmentsA full EPHEMERAL environment spun up per PR / branch — compute + addons + (often) a DB branch — torn down on merge. More than preview-urls (which is just a shareable URL for one deploy).

Partially supported

Built-in observabilityFirst-party metrics / logs / tracing / APM / profiling included in the platform (no third-party stack required to see what a workload is doing).

Supported

Managed CI/CD runnersPlatform-hosted, drop-in CI/CD runner VMs (GitHub Actions / GitLab), typically faster and cheaper than the CI vendor's own hosted runners, billed per runner-minute; isolated + ephemeral per job. Distinct from git-deploy (push-to-deploy of an APP) and scheduled-tasks (cron) — this is managed CI COMPUTE you point your existing pipelines at.

Not supported

Project template marketplaceA marketplace / gallery of prebuilt PROJECT STARTER templates (apps or websites) a user clones or launches a new project from and then customises — the "start from a template" surface of a builder / PaaS. Distinct from sandbox-templates (a COMPUTE base IMAGE you fork runtime INSTANCES from — Dockerfile / OCI), from app-builder (the prompt-to-app GENERATION surface — a product can have both), and from one-click OSS-app catalogues / helm-addon-marketplace (deploy a FINISHED app as-is, not a starter you build on).

Supported

Organisation & security 5/9

Built-in authPlatform-provided authentication / IAM for workloads.

Supported

SSO / SAMLEnterprise single sign-on.

Partially supported

Secrets managementFirst-class secrets storage / injection.

Supported

TeamsMulti-user team accounts.

Supported

SharingShare a running workload/resource via link (optionally gated).

Supported

BYOCRuns inside the customer's own cloud account.

Not supported

Deploy into customers' VPCsA SaaS vendor uses the platform to deploy and operate ITS software inside ITS CUSTOMERS' cloud accounts / VPCs (nested or "customer BYOC"), managed from the vendor's control plane. Distinct from byoc (your own workloads in your own cloud account).

Not supported

Workload identityThe platform gives each workload its own verifiable identity (OIDC token, SPIFFE SVID, cloud IAM federation) that it exchanges for short-lived credentials, so no long-lived static secret is stored or injected. Distinct from secrets-management (stores / injects static secrets) and credential-injection-proxy (swaps real secrets in on the wire).

Supported

Self-host / OSS coreOpen-source core that can be self-hosted.

Not supported

Proposed, not verified

Capabilities the scan saw but the registry does not track yet. A key is admitted only once two distinct products exhibit it. These are not scored.

Vercel Queuesmessage-queue
“**[Vercel Queues](/docs/queues)** enqueue and execute those routes with reliability.” vercel.com

05 Agent readiness Pre-login surface · counts, not a grade

Can an agent read it?

parse-ability · docs, metadata, machine-readable surfaces

10/11

8 full · 2 partial · 91% of applicable checks

llms.txt
Supported
“https://vercel.com/llms.txt HTTP200; substantive platform API/CLI/MCP/Skills index links docs, pricing and per-section indexes.”
llms-full.txt
Supported
“https://vercel.com/docs/llms-full.txt HTTP200 text/plain; 10,764,727-byte comprehensive full documentation body fetched. Oversized original retained as dated URL/SHA256/header/excerpt pointer, not confused with server-side truncation.”
robots.txt AI policy
Partially supported
“https://vercel.com/robots.txt HTTP200: Content-Signal: search=yes, ai-input=yes, ai-train=no. Generic User-Agent:* and path-specific Disallow rules, no named major AI-UA allow/block stanza; ai-input consent is not explicit UA Allow under rubric v3.”
JSON-LD
Supported
“https://vercel.com homepage includes SoftwareApplication JSON-LD with name, description and offers.price=0 USD, plus Organization and Service. Extracted objects retained in refresh-2026-10-15-homepage-surface.json.”
Sitemap
Supported
“https://vercel.com/sitemap.xml HTTP200 redirects to /crawled-sitemap.xml; substantive 1,218,078-byte XML urlset. robots.txt names /sitemap.xml; URL/hash/sample retained under cap.”
Meta tags
Supported
“https://vercel.com title: Agentic Infrastructure - Vercel; descriptive meta and OpenGraph description: The autonomous stack for every app and agent. Head metadata retained in dated homepage pointer/surface JSON.”
Markdown negotiation
Supported
“https://vercel.com requested with Accept: text/markdown returned HTTP200 Content-Type:text/markdown; body begins # Agentic Infrastructure. Docs/product pages also serve native .md variants. Negotiated body and headers retained.”
Content efficiency
Not supported
“https://vercel.com HTML 607942 bytes; readable text 3711 bytes (0.610%). HTMLParser excludes script/style/noscript, strips nonempty text chunks and joins with newline. Below rubric 1% threshold; no assertion that the page is unrenderable.”
Docs discoverable
Supported
“https://vercel.com initial HTML has first-class Docs navigation linking /docs; link presence and extracted text retained, without requiring client JavaScript.”
Machine-readable pricing
Supported
“https://vercel.com/pricing HTTP200 parseable Hobby/Pro/Enterprise tiers and resource rate tables; platform fee/seat-credit details corroborated at /docs/plans/pro-plan.md and regional Functions rate tables.”
No anti-bot wall
Partially supported
“Homepage, docs, pricing and well-known machine files fetch directly. Public https://security.vercel.com returned raw HTTP403; real-browser rendered fetch succeeded (exit0) and exposed full held Compliance list. Some public access needs a browser, so partial; login-only protection is not penalized.”

Can an agent drive it?

act-ability · APIs, SDKs, MCP, credentials, webhooks

11/11

10 full · 1 partial · 100% of applicable checks

Public API
Supported
“https://vercel.com/docs/rest-api.md and /docs/rest-api/getting-started.md document actual GET /v10/projects and bearer-authenticated platform API/SDK examples.”
OpenAPI spec
Supported
“https://vercel.com/openapi.json HTTP200 application/json; OpenAPI3.0.3, title Vercel API, server https://api.vercel.com, paths object. Original 11,660,549 bytes; dated URL/hash/header/spec excerpt retained under cap.”
MCP server
Supported
“https://vercel.com/docs/agent-resources/vercel-mcp.md documents official Model Context Protocol server https://mcp.vercel.com and client-specific OAuth setup.”
SDK packages
Supported
“https://vercel.com/docs/rest-api/sdk.md documents @vercel/sdk TypeScript/JavaScript control-plane SDK. /docs/connect/python-sdk-reference.md documents official vercel-connect Python client; /docs/queues/python-sdk.md also covers Python platform workload SDK. No Sandbox SDK counted.”
Auth documented
Supported
“https://vercel.com/docs/accounts/access-tokens.md documents full-account, team and project-scoped access tokens with bearer examples; /docs/oidc.md documents short-lived deployment federation.”
Self-serve credentials
Supported
“https://vercel.com/docs/accounts/access-tokens.md: create/manage tokens programmatically via REST API or vercel tokens CLI. /docs/cli/tokens.md documents plaintext-once token creation. Caveat: minting requires an existing full-account token (OAuth login sessions/project tokens do not suffice); unauthenticated autonomous account bootstrap was not exercised.”
Webhooks
Supported
“https://vercel.com/docs/webhooks.md documents emitted webhooks, one-time webhook secret, x-vercel-signature verification and securing-webhooks API instructions.”
CLI tool
Supported
“https://vercel.com/docs.md documents npm i -g vercel, vercel login and vercel; official CLI deployment and API token commands have dedicated references.”
Error model
Supported
“https://vercel.com/docs/rest-api/errors.md documents JSON {error:{code,message}} payloads including not_found, method_unknown and platform-specific deployment errors.”
Rate limits documented
Partially supported
“https://vercel.com/docs/limits.md documents platform API limits with endpoint/rate-limit name/max/duration/scope tables and 429/reset behavior. Dedicated response rate-limit header definitions were not found in fetched reference/limits/getting-started sources, so not full under rubric v3.”
Agent config files
Supported
“https://vercel.com/.well-known/ai-catalog.json HTTP200 specVersion1.0 with platform MCP/OpenAPI/skills entries, plus /docs/agent-resources/skills.md installable skills and /docs/agent-resources/vercel-plugin.md context/agents/slash-command setup. Multiple real configuration surfaces, not guessed agents.md routes.”

06 Coding harnesses Which agents and IDEs are documented to run here

Advertised integrations 10

Claude Code Anthropic
Supported
“Claude Code”
Source vercel.com
Advertised platform management MCP/plugin integration, not execution of the harness inside Functions or Sandbox. OAuth/account bootstrap may require human authorization.
Codex CLI OpenAI
Supported
“Codex CLI”
Source vercel.com
Advertised platform management MCP/plugin integration, not execution of the harness inside Functions or Sandbox. OAuth/account bootstrap may require human authorization.
Cursor Anysphere
Supported
“Cursor”
Source vercel.com
Advertised platform management MCP/plugin integration, not execution of the harness inside Functions or Sandbox. OAuth/account bootstrap may require human authorization.
Windsurf Codeium
Supported
“Windsurf”
Source vercel.com
Advertised platform management MCP/plugin integration, not execution of the harness inside Functions or Sandbox. OAuth/account bootstrap may require human authorization.
Gemini CLI Google
Supported
“Gemini CLI”
Source vercel.com
Advertised platform management MCP/plugin integration, not execution of the harness inside Functions or Sandbox. OAuth/account bootstrap may require human authorization.
OpenCode opencode
Supported
“OpenCode”
Source vercel.com
Advertised platform management MCP/plugin integration, not execution of the harness inside Functions or Sandbox. OAuth/account bootstrap may require human authorization.
Cline Cline
Supported
“Cline”
Source vercel.com
Advertised platform management MCP/plugin integration, not execution of the harness inside Functions or Sandbox. OAuth/account bootstrap may require human authorization.
Kilo Code Kilo
Supported
“Kilo Code”
Source vercel.com
Advertised platform management MCP/plugin integration, not execution of the harness inside Functions or Sandbox. OAuth/account bootstrap may require human authorization.
Zed Agent Zed
Supported
“Zed”
Source vercel.com
Advertised platform management MCP/plugin integration, not execution of the harness inside Functions or Sandbox. OAuth/account bootstrap may require human authorization.
GitHub Copilot GitHub
Supported
“GitHub Copilot”
Source vercel.com
Advertised platform management MCP/plugin integration, not execution of the harness inside Functions or Sandbox. OAuth/account bootstrap may require human authorization.

Plausible compatibility 0

Derived, not stored: the product passes SSH access, so any CLI coding agent is installable inside it. This is plausible compatibility, not a supported integration.

No general shell access documented, so nothing is derived. Absence is not unsupported.

07 Compliance & regions Standards held, with ordinal rigor; never a score

Certifications held 10

ISO/IEC 27001
certifiedhostedRendered held Compliance list confirms ISO/IEC 27001. The public FAQ still names 2013; do not infer a newer version or current report period without the gated certificate.
“Yes, Vercel is ISO 27001:2013 certified.”
Source vercel.comConfidence: high
PCI DSS
self-attestedhostedPublic FAQ specifies SAQ-D service-provider and SAQ-A merchant AOCs based on PCI DSS v4.0; not evidence of a QSA Level-1 assessment.
“Self-Assessment Questionnaire (SAQ)-D Attestation of Compliance (AOC) for Service Providers”
Source vercel.comConfidence: high
SOC 2 Type II
certifiedhostedRendered Trust Center also lists SOC 2 and a SOC 2 report; no report contents were downloaded.
“Yes, Vercel has a SOC 2 Type 2 attestation.”
Source vercel.comConfidence: high
DORA
self-attestedhostedRendered held compliance claim; no third-party certification asserted.
“DORA”
Source security.vercel.comConfidence: medium
HIPAA
self-attestedhostedHIPAA is not a certifiable standard. Enterprise scope/contractual requirements apply; public report listing is not proof every workload is HIPAA-compliant.
“Vercel supports HIPAA compliance for enterprise customers.”
Source vercel.comConfidence: high
NIS 2
self-attestedhostedRendered held compliance claim; no third-party certification asserted.
“NIS2”
Source security.vercel.comConfidence: medium
SOC 3
certifiedhostedPresent in rendered held Compliance list and SOC 3 Report listing. Report contents/audit period not opened.
“SOC 3”
Source security.vercel.comConfidence: medium
CCPA
self-attestedhostedRendered Compliance also names CPRA; folded into the canonical California privacy-law entry, not an audit certification.
“CCPA”
Source security.vercel.comConfidence: high
GDPR
self-attestedhostedRendered held compliance claim; DPA/privacy documentation is public. GDPR has no certifying body.
“GDPR”
Source security.vercel.comConfidence: high
PIPEDA
self-attestedhostedRendered held compliance claim for Canadian privacy law, not an external certification.
“PIPEDA”
Source security.vercel.comConfidence: high

Regions 19

Stockholm, Sweden (eu-north-1)arn1
Mumbai, India (ap-south-1)bom1
Paris, France (eu-west-3)cdg1
Cleveland, USA (us-east-2)cle1
Cape Town, South Africa (af-south-1)cpt1
Dublin, Ireland (eu-west-1)dub1
Frankfurt, Germany (eu-central-1)fra1
São Paulo, Brazil (sa-east-1)gru1
Hong Kong (ap-east-1)hkg1
Tokyo, Japan (ap-northeast-1)hnd1
Washington, D.C., USA (us-east-1)iad1
Seoul, South Korea (ap-northeast-2)icn1
Osaka, Japan (ap-northeast-3)kix1
London, United Kingdom (eu-west-2)lhr1
Portland, USA (us-west-2)pdx1
San Francisco, USA (us-west-1)sfo1
Singapore (ap-southeast-1)sin1
Sydney, Australia (ap-southeast-2)syd1
Montréal, Canada (ca-central-1)yul1

19 production compute regions; local dev1 excluded. Default Functions region iad1. Global CDN has 126 PoPs across 94 cities/51 countries. Region availability and multi-region/failover configuration are workload/plan dependent. Sandbox region inventory is not inherited.

Legal

Privacy notice Terms of service

08 Company & presence Facts only, not scored

Company

Headquarters: Not disclosed
Founded: 4 Nov 2015
Team size: Not disclosed
Hiring: Hiring: official Open Positions board lists current roles across engineering, design, GTM and finance.

Activity

Last release: 2026-10-14: Amazon S3 joins the Vercel Marketplace (platform); the same dated global changelog also lists a Nemotron AI Gateway update. vercel.com
Last blog post: 2026-10-14: Findings from the $1M Vercel Sandbox challenge is the latest vendor blog entry; 2026-10-09 Rillet customer story is the latest platform-relevant listed story. vercel.com

Presence 9

Links found on the public surface scanned; not an exhaustive search.

09 Sources & method How this entry was produced

Public surface only

Everything here was read from vercel.com's unauthenticated pages, docs, pricing and repository on 15 Oct 2026. Nothing behind a login was used.

Statuses, not scores

Capabilities are pass, partial or fail against a written rubric (features v21). “Not assessed” means the scan predates the key.

Confidence is separate

Each fact carries its own confidence. Low-confidence facts are shown, never hidden, so you can weigh them.

Schema: scan v5
Features registry: v21
Keys tracked today: 61
Assessed on this entry: 61

Something wrong on this page?

Nearby in the atlas

All PaaS products →