Rank #4 of 6 in Edge & App Platforms
Access
Install
npm i -g vercelShowcase


Products
Vercel, product by product →Vercel ships more than one product — each judged line competes in its own arena on the same stories as everyone else.
| Line | Arena | Rank | PA Score | Agent-ready |
|---|---|---|---|---|
| Vercelthis page | Edge & App Platforms | #4/6 | 25/100 | 44/100 |
| v0 | Vibe-Coding App Builders | #4/6 | 21/100 | 24/100 |
| Vercel Sandbox | Agent Sandboxes & Code Execution | #5/8 | 25/100 | 41/100 |
| Vercel AI Gateway | Model Gateways & Routers | #3/7 | 29/100 | 41/100 |
| skills.sh | Agent Skills & Extensions | #5/5 | 18/100 | 29/100 |
Verified integrations
Connections to other tracked products — hover a chip for the verbatim evidence quote behind it.
By theme — the product's score on each story themeBy theme
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Deploy workflow — the commit-to-production path — builds, previews, rollbacksDeploy workflowevidence →
The commit-to-production path — builds, previews, rollbacks
Dev experience — day-to-day developer experience — setup friction, docs, debugging, iteration speedDev experienceevidence →
Day-to-day developer experience — setup friction, docs, debugging, iteration speed
Edge compute — running code at the edge — regions, cold starts, runtime limitsEdge computeevidence →
Running code at the edge — regions, cold starts, runtime limits
Networking security — network controls and isolation — private access, firewalls, encryptionNetworking securityevidence →
Network controls and isolation — private access, firewalls, encryption
Observability — seeing what the system is doing — logs, metrics, traces, alertsObservabilityevidence →
Seeing what the system is doing — logs, metrics, traces, alerts
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limitsevidence →
Free-tier ceilings, usage caps, and rate limits before you have to pay
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Storage data — storing and moving data — persistence, formats, durabilityStorage dataevidence →
Storing and moving data — persistence, formats, durability
Story verdicts — every judged story with its evidenceStory verdicts
What’s free: 0 free · 0 paid · 3 enterprise · 34 not stated in evidence
Follow the green: where the map greys out is where Vercel stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
✓8/10
unlocks → Webhooks · Versioning policy · Full data export · The documented rate limits and concurrency caps for APIs and functions so I can plan for scale
Subscribe to events via webhooks
—–
Build against official SDKs
~6/10
Issue scoped/least-privilege API credentials for an agent
~3/10
Connect an agent via an official MCP server
~5/10
Download a machine-readable API spec (OpenAPI or equivalent)
✓9/10
unlocks → Interactive API docs
Rely on versioned APIs with a documented deprecation policy
—0/10
Test against a sandbox environment without touching production data
~6/10
Explore an interactive API reference with runnable examples
—0/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
—–
Operate the product with natural-language commands
~6/10
Plug MCP servers into this product so it can use their tools
—0/10
Get AI-generated insights and suggestions from my data inside the product
~3/10
Set up automations that run autonomously in the background
~6/10
The documented rate limits and concurrency caps for APIs and functions so I can plan for scale
—–
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Automation depth
Define rules that trigger actions automatically on events
~4/10
unlocks → Develop and test my app locally using a simulator that matches the production runtime · Deploy applications packaged as Docker containers · Define, deploy, and version my entire architecture with a single configuration file
Schedule recurring jobs or workflows
~5/10
Perform bulk operations across many items at once
—–
Version, review, and roll back my automations
~6/10
Deploy workflow — the commit-to-production path — builds, previews, rollbacksDeploy workflow
The commit-to-production path — builds, previews, rollbacks
Cli tooling
Deployment strategies
Git integration
Define, deploy, and version my entire architecture with a single configuration file
—–
Deploy a project by uploading a folder of files directly, with no Git repo required and the new deployment kept private until I choose to publish it
~4/10
Preview envs
Roll back a deployed service to any previous version in one click
✓8/10
Deploy one-click templates and starters for common use cases
~4/10
Dev experience — day-to-day developer experience — setup friction, docs, debugging, iteration speedDev experience
Day-to-day developer experience — setup friction, docs, debugging, iteration speed
Collaboration
Spin up unlimited isolated environments so my whole team can ship simultaneously
✓8/10
Rely on the same core APIs and primitives from prototype through massive scale, without rearchitecting or migrating platforms as usage grows
~6/10
Manage team-level access, secrets, and environment variables centrally
~6/10
Tool continuity
Visualize and edit my entire infrastructure stack on a visual canvas without writing config files
n/an/a
Edge compute — running code at the edge — regions, cold starts, runtime limitsEdge compute
Running code at the edge — regions, cold starts, runtime limits
Give my coding agent a persistent runtime environment that checkpoints its state automatically while working
—0/10
Ai inference
Placement latency
Handle persistent WebSocket connections from within edge/serverless functions for real-time apps
—–
Runtime compatibility
Run untrusted code in hardware-isolated, disposable sandboxes
✓7/10
Scaling
Serverless runtime
Deploy durable, long-running workflows as code without manually wiring queues and retries
✓7/10
Networking security — network controls and isolation — private access, firewalls, encryptionNetworking security
Network controls and isolation — private access, firewalls, encryption
Put simple password protection on a deployed site without standing up a custom auth system
✓8/10
Protect my app from automated bot traffic with invisible challenge-based protection
✓8/10
Have DDoS protection and a web application firewall applied to every request by default
!4/10
Domains
Isolate non-production environments from accessing production services
~5/10
Secure internal apps, deployments, and agents using my organization's identity provider
~5/10
Keep internal service-to-service traffic off the public internet without VPC complexity
—0/10
Serve HTTP, TCP, gRPC, and WebSocket traffic from the same deployed service without separate protocol configuration
—–
Get free, automatically renewing TLS certificates for every domain including wildcards
~6/10
Observability — seeing what the system is doing — logs, metrics, traces, alertsObservability
Seeing what the system is doing — logs, metrics, traces, alerts
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limits
Free-tier ceilings, usage caps, and rate limits before you have to pay
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Storage data — storing and moving data — persistence, formats, durabilityStorage data
Storing and moving data — persistence, formats, durability
Serve static assets faster using a global CDN with edge caching
~5/10
Connect my code to external services like databases, APIs, and storage through native bindings with minimal boilerplate instead of hand-wiring SDKs and credentials
~6/10
Use a Redis-compatible key-value store for low-latency caching and job queues
—–
Resize and optimize images on demand via a built-in image CDN
✓8/10
Persist user-generated uploads using built-in object storage
—0/10
Sorted by importance (agentic first) (high → low) · 96/96 stories · click a row’s chevron for the rationale and evidence
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 8/10 | Tprobed | |
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | partial | 5/10 | Cclaimed | |
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | 0/10 | ||
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | untested | none yet | |
The documented rate limits and concurrency caps for APIs and functions so I can plan for scale G Api quality | developer | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | untested | none yet | |
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 9/10 | Tprobed | |
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 9/10 | Tprobed | |
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 7/10 | Tprobed | |
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Tprobed | |
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Tprobed | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Cclaimed | |
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 3/10 | Cclaimed | |
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 3/10 | Cclaimed | |
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | partial | 6/10 | Xcommunity | |
Automatically deploy my app on every Git push C Git integration | developer | Deploy workflow — the commit-to-production path — builds, previews, rollbacksDeploy workflow | 3 | full | 9/10 | Cclaimed | |
Deploy my app by simply connecting my repo without manual build configuration C Git integration | developer | Deploy workflow — the commit-to-production path — builds, previews, rollbacksDeploy workflow | 3 | full | 9/10 | Cclaimed | |
Deploy serverless functions and full-stack apps with no servers to manage C Serverless runtime | developer | Edge compute — running code at the edge — regions, cold starts, runtime limitsEdge compute | 3 | full | 9/10 | Xcommunity | |
Get an automatic preview URL for every pull request C Preview envs | developer | Deploy workflow — the commit-to-production path — builds, previews, rollbacksDeploy workflow | 3 | full | 9/10 | Cclaimed | |
Access hundreds of AI models through a single unified gateway endpoint C Ai inference | ai-native builder | Edge compute — running code at the edge — regions, cold starts, runtime limitsEdge compute | 3 | full | 8/10 | Cclaimed | |
Roll back a deployed service to any previous version in one click C Rollback recovery | developer | Deploy workflow — the commit-to-production path — builds, previews, rollbacksDeploy workflow | 3 | full | 8/10 | Cclaimed | |
Run my code on a global edge network close to end users C Serverless runtime | developer | Edge compute — running code at the edge — regions, cold starts, runtime limitsEdge compute | 3 | full | 7/10 | Cclaimed | |
Get free, automatically renewing TLS certificates for every domain including wildcards C Tls certs | devops-lead | Networking security — network controls and isolation — private access, firewalls, encryptionNetworking security | 3 | partial | 6/10 | Cclaimed | |
Run AI model inference globally with a single call without managing GPUs or capacity planning C Ai inference | ai-native builder | Edge compute — running code at the edge — regions, cold starts, runtime limitsEdge compute | 3 | partial | 6/10 | Cclaimed | |
View all my build, deploy, and runtime logs in one place C Unified logging | developer | Observability — seeing what the system is doing — logs, metrics, traces, alertsObservability | 3 | partial | 6/10 | Cclaimed | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | partial | 4/10 | Cclaimed | |
Have DDoS protection and a web application firewall applied to every request by default C Ddos waf | devops-lead | Networking security — network controls and isolation — private access, firewalls, encryptionNetworking security | 3 | disputed | 4/10 | Dcontradicted | |
Provision a fully-managed Postgres database with point-in-time recovery, replicas, and high availability C Relational db | developer | Storage data — storing and moving data — persistence, formats, durabilityStorage data | 3 | partial | 3/10 | Cclaimed | |
Run unmodified Node.js code and npm packages in edge/serverless functions instead of a restricted runtime subset C Runtime compatibility | developer | Edge compute — running code at the edge — regions, cold starts, runtime limitsEdge compute | 3 | partial | 3/10 | Cclaimed | |
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | 0/10 | ||
The CPU and wall-clock execution time limits for functions so I can tell whether long-running or agentic workloads will fit C Execution limits | devops-lead | Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limits | 3 | none | 0/10 | ||
The exact overage fee schedule for exceeding plan usage limits (bandwidth, invocations, build minutes) before I get billed G Overage fees | devops-lead | Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limits | 3 | none | 0/10 | ||
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | untested | none yet | |
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | none | untested | none yet | |
Review a published uptime SLA with defined credits for downtime G Reliability sla | devops-lead | Observability — seeing what the system is doing — logs, metrics, traces, alertsObservability | 3 | none | untested | none yet | |
Get ephemeral full-stack preview environments for every pull request C Preview envs | developer | Deploy workflow — the commit-to-production path — builds, previews, rollbacksDeploy workflow | 2 | full | 9/10 | Cclaimed | |
Attach custom domains to my deployed services C Domains | developer | Networking security — network controls and isolation — private access, firewalls, encryptionNetworking security | 2 | full | 8/10 | Cclaimed | |
Deploy my project directly from the command line without using a web dashboard C Cli tooling | developer | Deploy workflow — the commit-to-production path — builds, previews, rollbacksDeploy workflow | 2 | full | 8/10 | Tprobed | |
Put simple password protection on a deployed site without standing up a custom auth system C Access control | developer | Networking security — network controls and isolation — private access, firewalls, encryptionNetworking security | 2 | full | 8/10 | Cclaimed | |
Roll out new deployments incrementally to reduce blast radius C Deployment strategies | devops-lead | Deploy workflow — the commit-to-production path — builds, previews, rollbacksDeploy workflow | 2 | full | 8/10 | Cclaimed | |
Scaffold and deploy a new project with a single CLI command C Cli tooling | developer | Deploy workflow — the commit-to-production path — builds, previews, rollbacksDeploy workflow | 2 | full | 8/10 | Tprobed | |
Deploy durable, long-running workflows as code without manually wiring queues and retries C Workflows | developer | Edge compute — running code at the edge — regions, cold starts, runtime limitsEdge compute | 2 | full | 7/10 | Cclaimed | |
Run untrusted code in hardware-isolated, disposable sandboxes C Sandboxing | developer | Edge compute — running code at the edge — regions, cold starts, runtime limitsEdge compute | 2 | full | 7/10 | Cclaimed | |
Connect my code to external services like databases, APIs, and storage through native bindings with minimal boilerplate instead of hand-wiring SDKs and credentials C Integrations | developer | Storage data — storing and moving data — persistence, formats, durabilityStorage data | 2 | partial | 6/10 | Xcommunity | |
Deploy instances that boot in under a second and scale to tens of thousands under load C Scaling | devops-lead | Edge compute — running code at the edge — regions, cold starts, runtime limitsEdge compute | 2 | partial | 6/10 | Xcommunity | |
Keep using my existing Git, CI, editor, and framework workflows without adopting proprietary tooling C Tool continuity | developer | Dev experience — day-to-day developer experience — setup friction, docs, debugging, iteration speedDev experience | 2 | partial | 6/10 | Tprobed | |
Manage team-level access, secrets, and environment variables centrally C Secrets management | devops-lead | Dev experience — day-to-day developer experience — setup friction, docs, debugging, iteration speedDev experience | 2 | partialenterprise | 6/10 | Xcommunity | |
Pay only for active compute time rather than idle wall-clock time G Usage billing | devops-lead | Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limits | 2 | partial | 6/10 | Xcommunity | |
Rely on load-based autoscaling to absorb large traffic bursts automatically C Scaling | devops-lead | Edge compute — running code at the edge — regions, cold starts, runtime limitsEdge compute | 2 | partial | 6/10 | Xcommunity | |
Rely on the same core APIs and primitives from prototype through massive scale, without rearchitecting or migrating platforms as usage grows C Scaling continuity | developer | Dev experience — day-to-day developer experience — setup friction, docs, debugging, iteration speedDev experience | 2 | partialenterprise | 6/10 | Xcommunity | |
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | partial | 5/10 | Cclaimed | |
Secure internal apps, deployments, and agents using my organization's identity provider G Identity | devops-lead | Networking security — network controls and isolation — private access, firewalls, encryptionNetworking security | 2 | partial | 5/10 | Cclaimed | |
Serve static assets faster using a global CDN with edge caching C Cdn assets | developer | Storage data — storing and moving data — persistence, formats, durabilityStorage data | 2 | partial | 5/10 | Cclaimed | |
Deploy a project by uploading a folder of files directly, with no Git repo required and the new deployment kept private until I choose to publish it P Manual deploy | developer | Deploy workflow — the commit-to-production path — builds, previews, rollbacksDeploy workflow | 2 | partial | 4/10 | Tprobed | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 4/10 | Tprobed | |
Programmatically provision and route custom domains for my own multi-tenant SaaS customers C Domains | developer | Networking security — network controls and isolation — private access, firewalls, encryptionNetworking security | 2 | partial | 4/10 | Tprobed | |
Query a serverless SQL database directly from my code with no connection management C Relational db | developer | Storage data — storing and moving data — persistence, formats, durabilityStorage data | 2 | partial | 4/10 | Xcommunity | |
Set up alerts that notify me via chat or email when specific conditions are met C Alerting | devops-lead | Observability — seeing what the system is doing — logs, metrics, traces, alertsObservability | 2 | partial | 4/10 | Cclaimed | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 3/10 | Cclaimed | |
Set hard spending limits to control my cloud costs G Cost controls | devops-lead | Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limits | 2 | disputed | 3/10 | Dcontradicted | |
Deploy applications packaged as Docker containers C Deployment strategies | developer | Deploy workflow — the commit-to-production path — builds, previews, rollbacksDeploy workflow | 2 | none | 0/10 | ||
Develop and test my app locally using a simulator that matches the production runtime C Cli tooling | developer | Deploy workflow — the commit-to-production path — builds, previews, rollbacksDeploy workflow | 2 | none | 0/10 | ||
Give my coding agent a persistent runtime environment that checkpoints its state automatically while working C Agent runtime | ai-native builder | Edge compute — running code at the edge — regions, cold starts, runtime limitsEdge compute | 2 | none | 0/10 | ||
Keep internal service-to-service traffic off the public internet without VPC complexity C Private networking | devops-lead | Networking security — network controls and isolation — private access, firewalls, encryptionNetworking security | 2 | none | 0/10 | ||
Persist user-generated uploads using built-in object storage C Object storage | developer | Storage data — storing and moving data — persistence, formats, durabilityStorage data | 2 | none | 0/10 | ||
Rely on automatic compute placement near backend data to optimize latency C Placement latency | devops-lead | Edge compute — running code at the edge — regions, cold starts, runtime limitsEdge compute | 2 | none | 0/10 | ||
Write code against standard runtime APIs so it runs unmodified across multiple edge platforms instead of being locked into proprietary storage/runtime APIs C Tool continuity | developer | Dev experience — day-to-day developer experience — setup friction, docs, debugging, iteration speedDev experience | 2 | none | 0/10 | ||
Write edge functions in languages other than JavaScript such as Python, Go, or Rust C Runtime compatibility | developer | Edge compute — running code at the edge — regions, cold starts, runtime limitsEdge compute | 2 | none | 0/10 | ||
Attached disk/storage auto-grows with usage and I'm billed only for bytes actually written rather than pre-provisioned capacity P Usage billing | devops-lead | Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limits | 2 | n/a | untested | none yet | |
Build custom dashboards combining metrics from any service C Metrics dashboards | devops-lead | Observability — seeing what the system is doing — logs, metrics, traces, alertsObservability | 2 | none | untested | none yet | |
Check a public status page with historical incident postmortems before committing G Reliability sla | devops-lead | Observability — seeing what the system is doing — logs, metrics, traces, alertsObservability | 2 | none | untested | none yet | |
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Define, deploy, and version my entire architecture with a single configuration file C Infra as code | devops-lead | Deploy workflow — the commit-to-production path — builds, previews, rollbacksDeploy workflow | 2 | none | untested | none yet | |
Deploy my application to specific regions closer to my users C Placement latency | devops-lead | Edge compute — running code at the edge — regions, cold starts, runtime limitsEdge compute | 2 | none | untested | none yet | |
Handle persistent WebSocket connections from within edge/serverless functions for real-time apps C Realtime connections | developer | Edge compute — running code at the edge — regions, cold starts, runtime limitsEdge compute | 2 | none | untested | none yet | |
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | none | untested | none yet | |
The guaranteed support response times and escalation paths for my plan tier G Reliability sla | devops-lead | Observability — seeing what the system is doing — logs, metrics, traces, alertsObservability | 2 | none | untested | none yet | |
Use a Redis-compatible key-value store for low-latency caching and job queues C Kv cache | developer | Storage data — storing and moving data — persistence, formats, durabilityStorage data | 2 | none | untested | none yet | |
Visualize and edit my entire infrastructure stack on a visual canvas without writing config files C Visual infra | devops-lead | Dev experience — day-to-day developer experience — setup friction, docs, debugging, iteration speedDev experience | 2 | n/a | untested | none yet | |
Whether pricing is per-seat with minimum seat counts that increase cost as my team grows G Overage fees | devops-lead | Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limits | 2 | none | untested | none yet | |
Let teammates and collaborators comment directly on preview and production environments C Collaboration | developer | Dev experience — day-to-day developer experience — setup friction, docs, debugging, iteration speedDev experience | 1 | full | 8/10 | Cclaimed | |
Protect my app from automated bot traffic with invisible challenge-based protection C Bot protection | developer | Networking security — network controls and isolation — private access, firewalls, encryptionNetworking security | 1 | full | 8/10 | Cclaimed | |
Resize and optimize images on demand via a built-in image CDN C Media | developer | Storage data — storing and moving data — persistence, formats, durabilityStorage data | 1 | full | 8/10 | Cclaimed | |
Spin up unlimited isolated environments so my whole team can ship simultaneously C Environments | developer | Dev experience — day-to-day developer experience — setup friction, docs, debugging, iteration speedDev experience | 1 | full | 8/10 | Cclaimed | |
Use an in-browser toolbar to leave feedback, manage feature flags, and inspect performance directly on my live site C Collaboration | developer | Dev experience — day-to-day developer experience — setup friction, docs, debugging, iteration speedDev experience | 1 | full | 8/10 | Cclaimed | |
Track site performance and visitor behavior with built-in analytics C Metrics dashboards | devops-lead | Observability — seeing what the system is doing — logs, metrics, traces, alertsObservability | 1 | partial | 6/10 | Cclaimed | |
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | partial | 6/10 | Cclaimed | |
Isolate non-production environments from accessing production services C Env isolation | devops-lead | Networking security — network controls and isolation — private access, firewalls, encryptionNetworking security | 1 | partialenterprise | 5/10 | Xcommunity | |
Deploy one-click templates and starters for common use cases C Templates | developer | Deploy workflow — the commit-to-production path — builds, previews, rollbacksDeploy workflow | 1 | partial | 4/10 | Cclaimed | |
Receive migration credits when moving my production infrastructure to a new platform C Cost controls | devops-lead | Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limits | 1 | none | untested | none yet | |
Serve HTTP, TCP, gRPC, and WebSocket traffic from the same deployed service without separate protocol configuration C Protocols | developer | Networking security — network controls and isolation — private access, firewalls, encryptionNetworking security | 1 | none | untested | none yet |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 67 stories with headroom
What would move Vercel’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Agenticness — how well agents can access and operate the productDelegate tasks to a built-in AI assistant inside the product
nonemoves Built-in AIimpact 45
The evidence shows Vercel providing AI infrastructure (AI Gateway, AI SDK, Workflow SDK) and integration hooks for external coding agents (Claude Code, Cursor, etc.) to interact with Vercel, but no evidence of a built-in AI assistant inside the Vercel product itself that a user can delegate tasks to.
Agenticness — how well agents can access and operate the productPlug MCP servers into this product so it can use their tools
nonemoves agent-readyimpact 45
Missing: any documentation of Vercel connecting to third-party MCP servers as a client and invoking their tools.
Agenticness — how well agents can access and operate the productThe documented rate limits and concurrency caps for APIs and functions so I can plan for scale
nonemoves API qualityimpact 45
The evidence pack describes general platform capabilities (Fluid compute for concurrency, Functions, CDN, etc.) but contains no documentation of specific rate limits, concurrency caps, or quota numbers that a developer could use for capacity planning.
Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payThe CPU and wall-clock execution time limits for functions so I can tell whether long-running or agentic workloads will fit
nonemoves PA Scoreimpact 30
Missing: explicit maxDuration/timeout numbers per plan, CPU allocation limits, and any pricing-page or docs citation stating these limits.
Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payThe exact overage fee schedule for exceeding plan usage limits (bandwidth, invocations, build minutes) before I get billed
nonemoves PA Scoreimpact 30
The evidence pack contains no vendor documentation of a specific overage fee schedule for bandwidth, invocations, or build minutes — only general product/feature docs unrelated to billing granularity.
Openness — open source, data portability, and self-hosting storiesExport all of my data in open formats and leave
nonemoves PA Scoreimpact 30
No evidence pack item addresses data export, portability, or account/data deletion in open formats for Vercel; nothing about exporting project data, logs, or analytics in a standard/open format for migration.
Openness — open source, data portability, and self-hosting storiesSelf-host the core product
nonemoves PA Scoreimpact 30
Vercel is a proprietary managed cloud platform; there is no evidence of a self-hostable core product, on-prem package, or open-source server offering—only CLI and SDK tooling that deploy to Vercel's own infrastructure.
Privacy posture — data-handling and privacy storiesPrevent my data from being used to train AI models
nonemoves PA Scoreimpact 30
No evidence in the pack addresses AI training data opt-out or data usage policies for AI model training; Vercel's docs cover deployment, AI Gateway, sandboxes, and infra but never mention data-training controls.
Showing the top 8 of 67 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map7 surfaces · 60 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
docs56 stories
- Point an agent at llms.txt or agent-oriented docs
- Run the product headlessly / in CI for automation
- Connect an agent via an official MCP server
- Use an official CLI
- Drive the product through a documented public API
- Issue scoped/least-privilege API credentials for an agent
- Build against official SDKs
- Get AI-generated insights and suggestions from my data inside the product
- Set up automations that run autonomously in the background
- Operate the product with natural-language commands
- Test against a sandbox environment without touching production data
- Define rules that trigger actions automatically on events
- Schedule recurring jobs or workflows
- Version, review, and roll back my automations
- Deploy my project directly from the command line without using a web dashboard
- Scaffold and deploy a new project with a single CLI command
- Roll out new deployments incrementally to reduce blast radius
- Automatically deploy my app on every Git push
- Deploy my app by simply connecting my repo without manual build configuration
- Deploy a project by uploading a folder of files directly, with no Git repo required and the new deployment kept private until I choose to publish it
- Get ephemeral full-stack preview environments for every pull request
- Get an automatic preview URL for every pull request
- Roll back a deployed service to any previous version in one click
- Deploy one-click templates and starters for common use cases
- Use an in-browser toolbar to leave feedback, manage feature flags, and inspect performance directly on my live site
- Let teammates and collaborators comment directly on preview and production environments
- Spin up unlimited isolated environments so my whole team can ship simultaneously
- Rely on the same core APIs and primitives from prototype through massive scale, without rearchitecting or migrating platforms as usage grows
- Manage team-level access, secrets, and environment variables centrally
- Keep using my existing Git, CI, editor, and framework workflows without adopting proprietary tooling
- Run AI model inference globally with a single call without managing GPUs or capacity planning
- Access hundreds of AI models through a single unified gateway endpoint
- Run unmodified Node.js code and npm packages in edge/serverless functions instead of a restricted runtime subset
- Run untrusted code in hardware-isolated, disposable sandboxes
- Deploy instances that boot in under a second and scale to tens of thousands under load
- Rely on load-based autoscaling to absorb large traffic bursts automatically
- Run my code on a global edge network close to end users
- Deploy serverless functions and full-stack apps with no servers to manage
- Deploy durable, long-running workflows as code without manually wiring queues and retries
- Put simple password protection on a deployed site without standing up a custom auth system
- Protect my app from automated bot traffic with invisible challenge-based protection
- Have DDoS protection and a web application firewall applied to every request by default
- Attach custom domains to my deployed services
- Programmatically provision and route custom domains for my own multi-tenant SaaS customers
- Isolate non-production environments from accessing production services
- Secure internal apps, deployments, and agents using my organization's identity provider
- Get free, automatically renewing TLS certificates for every domain including wildcards
- Set up alerts that notify me via chat or email when specific conditions are met
- Track site performance and visitor behavior with built-in analytics
- View all my build, deploy, and runtime logs in one place
- Do everything through the API that I can do in the UI
- Set hard spending limits to control my cloud costs
- Pay only for active compute time rather than idle wall-clock time
- Serve static assets faster using a global CDN with edge caching
- Connect my code to external services like databases, APIs, and storage through native bindings with minimal boilerplate instead of hand-wiring SDKs and credentials
- Resize and optimize images on demand via a built-in image CDN
GitHub README15 stories
- Run the product headlessly / in CI for automation
- Use an official CLI
- Deploy my project directly from the command line without using a web dashboard
- Scaffold and deploy a new project with a single CLI command
- Automatically deploy my app on every Git push
- Deploy my app by simply connecting my repo without manual build configuration
- Deploy a project by uploading a folder of files directly, with no Git repo required and the new deployment kept private until I choose to publish it
- Get ephemeral full-stack preview environments for every pull request
- Get an automatic preview URL for every pull request
- Deploy one-click templates and starters for common use cases
- Spin up unlimited isolated environments so my whole team can ship simultaneously
- Keep using my existing Git, CI, editor, and framework workflows without adopting proprietary tooling
- Deploy serverless functions and full-stack apps with no servers to manage
- Do everything through the API that I can do in the UI
- Read the product's source under an open license
Hacker News13 stories
- Test against a sandbox environment without touching production data
- Rely on the same core APIs and primitives from prototype through massive scale, without rearchitecting or migrating platforms as usage grows
- Manage team-level access, secrets, and environment variables centrally
- Keep using my existing Git, CI, editor, and framework workflows without adopting proprietary tooling
- Deploy instances that boot in under a second and scale to tens of thousands under load
- Rely on load-based autoscaling to absorb large traffic bursts automatically
- Deploy serverless functions and full-stack apps with no servers to manage
- Have DDoS protection and a web application firewall applied to every request by default
- Isolate non-production environments from accessing production services
- Set hard spending limits to control my cloud costs
- Pay only for active compute time rather than idle wall-clock time
- Connect my code to external services like databases, APIs, and storage through native bindings with minimal boilerplate instead of hand-wiring SDKs and credentials
- Query a serverless SQL database directly from my code with no connection management
vercel.com9 stories
- Issue scoped/least-privilege API credentials for an agent
- Manage team-level access, secrets, and environment variables centrally
- Run unmodified Node.js code and npm packages in edge/serverless functions instead of a restricted runtime subset
- Run untrusted code in hardware-isolated, disposable sandboxes
- Deploy instances that boot in under a second and scale to tens of thousands under load
- Rely on load-based autoscaling to absorb large traffic bursts automatically
- Deploy serverless functions and full-stack apps with no servers to manage
- Isolate non-production environments from accessing production services
- Secure internal apps, deployments, and agents using my organization's identity provider
OpenAPI spec6 stories
- Run the product headlessly / in CI for automation
- Drive the product through a documented public API
- Build against official SDKs
- Download a machine-readable API spec (OpenAPI or equivalent)
- Programmatically provision and route custom domains for my own multi-tenant SaaS customers
- Do everything through the API that I can do in the UI
Marketplace docs5 stories
- Let teammates and collaborators comment directly on preview and production environments
- Set up alerts that notify me via chat or email when specific conditions are met
- Connect my code to external services like databases, APIs, and storage through native bindings with minimal boilerplate instead of hand-wiring SDKs and credentials
- Provision a fully-managed Postgres database with point-in-time recovery, replicas, and high availability
- Query a serverless SQL database directly from my code with no connection management
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
2 of 16 testable claims verified · 1 contradicted → integrity 0/100
17 distinct capability claims found in Vercel’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
2
Verified
13
Unverified
1
Contradicted
43
Undersold
Verified (2)
“Use the Vercel CLI to scaffold and deploy a project”
Scaffold and deploy a new project with a single CLI commandfullproof ↗
“Use the Vercel CLI to scaffold and deploy a project”
Deploy my project directly from the command line without using a web dashboardfullproof ↗
Unverified (13)
“Auto-deploy your app on every push to a connected Git repository”
“Automatic preview environments are created for testing changes before production”
Get an automatic preview URL for every pull requestfullproof ↗
“Automatic preview environments are created for testing changes before production”
Get ephemeral full-stack preview environments for every pull requestfullproof ↗
“Get started by importing an existing project to deploy without manual config”
Deploy my app by simply connecting my repo without manual build configurationfullproof ↗
“Choose a starter template to deploy a new project”
Deploy one-click templates and starters for common use casespartialproof ↗
“Access hundreds of AI models through a single gateway endpoint with budgets, fallbacks, and monitoring”
Access hundreds of AI models through a single unified gateway endpointfullproof ↗
“Run untrusted code in secure, ephemeral sandboxed execution environments”
Run untrusted code in hardware-isolated, disposable sandboxesfullproof ↗
“Roll back to a previous deployment to recover quickly from incidents”
Roll back a deployed service to any previous version in one clickfullproof ↗
“Roll out new deployments incrementally to reduce risk”
Roll out new deployments incrementally to reduce blast radiusfullproof ↗
“In-browser toolbar for leaving feedback, managing feature flags, previewing drafts, and inspecting performance”
Use an in-browser toolbar to leave feedback, manage feature flags, and inspect performance directly on my live sitefullproof ↗
“Teams and collaborators can comment directly on preview and production environments”
Let teammates and collaborators comment directly on preview and production environmentsfullproof ↗
“Invisible CAPTCHA protects against sophisticated bots without user challenges”
Protect my app from automated bot traffic with invisible challenge-based protectionfullproof ↗
“Secure every internal agent, app, and deployment using your organization's identity provider”
Secure internal apps, deployments, and agents using my organization's identity providerpartialproof ↗
Contradicted (1)
“Run production workloads in isolated containers”
Deploy applications packaged as Docker containersnoneproof ↗
Undersold (43)
Point an agent at llms.txt or agent-oriented docsfullproof ↗
Run the product headlessly / in CI for automationfullproof ↗
Drive the product through a documented public APIfullproof ↗
Issue scoped/least-privilege API credentials for an agentpartialproof ↗
Get AI-generated insights and suggestions from my data inside the productpartialproof ↗
Set up automations that run autonomously in the backgroundpartialproof ↗
Operate the product with natural-language commandspartialproof ↗
Download a machine-readable API spec (OpenAPI or equivalent)fullproof ↗
Test against a sandbox environment without touching production datapartialproof ↗
Define rules that trigger actions automatically on eventspartialproof ↗
Deploy a project by uploading a folder of files directly, with no Git repo required and the new deployment kept private until I choose to publish itpartialproof ↗
Spin up unlimited isolated environments so my whole team can ship simultaneouslyfullproof ↗
Rely on the same core APIs and primitives from prototype through massive scale, without rearchitecting or migrating platforms as usage growspartialproof ↗
Manage team-level access, secrets, and environment variables centrallypartialproof ↗
Keep using my existing Git, CI, editor, and framework workflows without adopting proprietary toolingpartialproof ↗
Run AI model inference globally with a single call without managing GPUs or capacity planningpartialproof ↗
Run unmodified Node.js code and npm packages in edge/serverless functions instead of a restricted runtime subsetpartialproof ↗
Deploy instances that boot in under a second and scale to tens of thousands under loadpartialproof ↗
Rely on load-based autoscaling to absorb large traffic bursts automaticallypartialproof ↗
Run my code on a global edge network close to end usersfullproof ↗
Deploy serverless functions and full-stack apps with no servers to managefullproof ↗
Deploy durable, long-running workflows as code without manually wiring queues and retriesfullproof ↗
Put simple password protection on a deployed site without standing up a custom auth systemfullproof ↗
Programmatically provision and route custom domains for my own multi-tenant SaaS customerspartialproof ↗
Isolate non-production environments from accessing production servicespartialproof ↗
Get free, automatically renewing TLS certificates for every domain including wildcardspartialproof ↗
Set up alerts that notify me via chat or email when specific conditions are metpartialproof ↗
Track site performance and visitor behavior with built-in analyticspartialproof ↗
View all my build, deploy, and runtime logs in one placepartialproof ↗
Do everything through the API that I can do in the UIpartialproof ↗
Read the product's source under an open licensepartialproof ↗
Pay only for active compute time rather than idle wall-clock timepartialproof ↗
Serve static assets faster using a global CDN with edge cachingpartialproof ↗
Connect my code to external services like databases, APIs, and storage through native bindings with minimal boilerplate instead of hand-wiring SDKs and credentialspartialproof ↗
Resize and optimize images on demand via a built-in image CDNfullproof ↗
Provision a fully-managed Postgres database with point-in-time recovery, replicas, and high availabilitypartialproof ↗
Query a serverless SQL database directly from my code with no connection managementpartialproof ↗
Claims outside our story set (3)
Real capability claims found in Vercel’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.
“Build tools that let AI agents interact with your systems”
source ↗“View unpublished headless CMS content directly on your live site”
source ↗“Let AI agents deploy a project and hand off control to a human”
source ↗
Business model
Free Hobby tier; Pro is $20/mo per seat plus included usage credit; usage-based overages for functions/requests/bandwidth; Enterprise custom.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
Agent surface uptime llms.txt 100% · openapi.json 100% (30d, checked every 6h since Sep 8 '26)
