Vercel vs Railway
Vercel wins · 37–22 (26 drawn)
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round drawnDirect probe evidence confirms Vercel serves a live llms.txt at vercel.com/llms.txt (HTTP 200) with a machine-readable product summary, plus a full docs.md markdown mirror of documentation, both explicitly agent-oriented formats. Missing for 10: independent third-party confirmation that agents actually consume and act on these files effectively.
- [probe] “PROBE llms.txt: HTTP 200 at https://vercel.com/llms.txt # Vercel > Vercel is a cloud platform for building, deploying, and scaling web appl…”
- [probe] “PROBE docs-md: HTTP 200 at https://vercel.com/docs.md --- title: index product: vercel url: /docs/index canonical_url: "https://vercel.com/d…”
Railway hosts a live llms.txt confirmed by direct probe (HTTP 200) plus dedicated agent-oriented docs like agents.md and cloud-agents.md pages designed for AI assistants to consume. missing for 10: independent third-party confirmation that agents actually use these files successfully in practice.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.railway.com/llms.txt # Railway Documentation > Railway is an all-in-one intelligent cloud provider…”
- [claimed-docs] “Install the Railway CLI and configure agent support — skills, MCP, and authentication — in one command.”
- [claimed-docs] “It lets AI assistants create projects, deploy templates, manage environments, pull variables, and redeploy services.”
- [claimed-docs] “The use-railway skill teaches AI coding agents how to operate Railway.”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round to VercelVercel ships an official CLI (vercel-docs-4/vercel-gh-1, vercel-probe-4, vercel-gh-2) that supports git push-based and CLI-driven deploys usable in CI pipelines, plus REST/OpenAPI API access (vercel-probe-3) for scripted automation, and CI-friendly features like environment variable management and rollback/promote commands (vercel-docs-23, vercel-docs-29). Missing for 10: no explicit GitHub Actions/CI recipe documentation or independent hands-on report of running the CLI fully headlessly in a third-party CI system.
- [github] “Get started by importing a project, choosing a template, or using the Vercel CLI. Then, git push to deploy.”
- [github] “To opt into the native binary and replace existing global vercel and vc commands, install the native package explicitly”
- [probe] “PROBE openapi: HTTP 200 at https://vercel.com/openapi.json — contains "openapi" key”
- [probe] “official CLI documented at https://vercel.com/docs/cli”
- [claimed-docs] “Manage local, preview, production, and custom environments and the variables each one uses.”
- [claimed-docs] “Revert production to a previous deployment without a rebuild when something breaks.”
Railway ships an official CLI for local development and deploying from the terminal, which implies scriptable/headless usage in automation contexts, but the evidence pack has no explicit documentation of CI/CD pipeline integration, GitHub Actions examples, or non-interactive auth tokens for CI. missing for 10: explicit CI/CD integration docs, non-interactive auth/token flow for automation, examples of headless CI usage.
- [claimed-docs] “Develop locally and deploy from your terminal with the Railway CLI.”
- [probe] “official CLI documented at https://docs.railway.com/guides/cli”
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · round to RailwayVercelnone0/10The evidence shows Vercel exposing its own capabilities as tools for AI agents (vercel-docs-4, vercel-docs-15) and building agent infrastructure (Workflow SDK, AI Gateway), but there is no evidence that Vercel itself can act as an MCP client, ingesting external MCP servers so it can use their tools. Missing for 10: any documentation of Vercel connecting to third-party MCP servers as a client and invoking their tools.
- [claimed-docs] “Create tools for AI agents to interact with your systems.”
- [claimed-docs] “Give your coding agent deployment skills, framework best practices, and slash commands. Works with Claude Code, OpenAI Codex, Grok Build, Cu…”
- [claimed-docs] “Build durable, observable applications and AI agents with the Workflow SDK on a fully managed platform.”
Railway's docs explicitly describe connecting external MCP servers (Notion, Linear, Sentry, or any custom remote MCP server) to the Railway Agent so it can read from and use their tools while operating on projects, directly matching the story. Missing for 10: independent/hands-on corroboration beyond first-party docs, and detail on tool-use scope/limitations when using third-party MCP servers.
- [claimed-docs] “Connect Notion, Linear, or Sentry from the catalog, or point Railway at any remote MCP server you run, and the agent can read from it while …”
- [claimed-docs] “The Railway Agent is a chat-based AI assistant built into the Railway dashboard. It can operate the platform on your behalf: creating and co…”
- [claimed-docs] “Build with Railway using Agent Skills and the MCP server for AI-powered workflows.”
ai-native userConnect an agent via an official MCP server
weight 3 · round to RailwayVercel's docs mention agent-facing capabilities like 'Create tools for AI agents to interact with your systems' and 'Allow AI agents to deploy a project and let a human take over,' plus agent skill/slash-command support for coding agents (Claude Code, Cursor, etc.), suggesting some official agent-integration surface. However, none of the evidence explicitly names an MCP server, MCP protocol support, or an MCP endpoint. Missing for 10: explicit documentation of an official MCP server/endpoint, MCP protocol naming, or third-party confirmation that agents connect via MCP rather than generic APIs/CLI.
- [claimed-docs] “Create tools for AI agents to interact with your systems.”
- [claimed-docs] “Allow AI agents to deploy a project and let a human take over.”
- [claimed-docs] “Give your coding agent deployment skills, framework best practices, and slash commands. Works with Claude Code, OpenAI Codex, Grok Build, Cu…”
Railway ships an official documented MCP server (docs.railway.com/ai/mcp-server.md) that lets AI assistants create projects, deploy templates, manage environments, pull variables, and redeploy services, plus a one-command CLI setup for agent/MCP/auth configuration and an 'use-railway' skill teaching agents to operate the platform. This is first-party, well-documented, and clearly targets AI-native agent connectivity. missing for 10: independent/hands-on third-party corroboration of the MCP server working in practice, and more detail on auth/security model for remote agent connections.
- [claimed-docs] “Build with Railway using Agent Skills and the MCP server for AI-powered workflows.”
- [claimed-docs] “Install the Railway CLI and configure agent support — skills, MCP, and authentication — in one command.”
- [claimed-docs] “It lets AI assistants create projects, deploy templates, manage environments, pull variables, and redeploy services.”
- [claimed-docs] “The use-railway skill teaches AI coding agents how to operate Railway.”
ai-native userUse an official CLI
weight 2 · round to RailwayVercel ships an official CLI (vercel-probe-4, vercel-gh-1, vercel-gh-2) and explicitly extends it toward AI-native agent workflows via deployment skills, framework best practices, and slash commands for coding agents like Claude Code, Cursor, and GitHub Copilot (vercel-docs-15), plus AI-agent deployment handoff features (vercel-docs-10). missing for 10: independent/hands-on verification of the CLI's agentic slash-command features beyond first-party docs.
- [probe] “official CLI documented at https://vercel.com/docs/cli”
- [github] “Get started by importing a project, choosing a template, or using the Vercel CLI. Then, git push to deploy.”
- [github] “To opt into the native binary and replace existing global vercel and vc commands, install the native package explicitly”
- [claimed-docs] “Give your coding agent deployment skills, framework best practices, and slash commands. Works with Claude Code, OpenAI Codex, Grok Build, Cu…”
- [claimed-docs] “Allow AI agents to deploy a project and let a human take over.”
Railway ships a well-documented official CLI (docs-15, docs-18, probe-3) and explicitly extends it for AI-native workflows via a one-command agent setup that installs skills, MCP, and authentication (docs-19), making it directly usable by AI coding agents (docs-21, docs-16). missing for 10: independent/hands-on community confirmation of the CLI's AI-native agent setup specifically.
- [claimed-docs] “Develop locally and deploy from your terminal with the Railway CLI.”
- [claimed-docs] “Railway is an all-in-one intelligent cloud provider that makes it easy to provision infrastructure, develop locally, and deploy to the cloud…”
- [claimed-docs] “Install the Railway CLI and configure agent support — skills, MCP, and authentication — in one command.”
- [claimed-docs] “Build with Railway using Agent Skills and the MCP server for AI-powered workflows.”
- [claimed-docs] “The use-railway skill teaches AI coding agents how to operate Railway.”
- [probe] “official CLI documented at https://docs.railway.com/guides/cli”
ai-native userDrive the product through a documented public API
weight 3 · round to VercelVercel exposes a documented public OpenAPI spec (vercel-probe-3), an official CLI (vercel-probe-4, vercel-gh-2), and llms.txt/docs.md machine-readable docs (vercel-probe-1, vercel-probe-2), confirming a documented API surface AI-native users can drive programmatically. Additional docs describe AI-agent-oriented tool creation and agent deployment flows (vercel-docs-4, vercel-docs-10, vercel-docs-15). missing for 10: independent/hands-on third-party corroboration of API completeness and no explicit API versioning/rate-limit docs cited.
- [probe] “PROBE openapi: HTTP 200 at https://vercel.com/openapi.json — contains "openapi" key”
- [probe] “official CLI documented at https://vercel.com/docs/cli”
- [probe] “PROBE llms.txt: HTTP 200 at https://vercel.com/llms.txt # Vercel > Vercel is a cloud platform for building, deploying, and scaling web appl…”
- [probe] “PROBE docs-md: HTTP 200 at https://vercel.com/docs.md --- title: index product: vercel url: /docs/index canonical_url: "https://vercel.com/d…”
- [claimed-docs] “Create tools for AI agents to interact with your systems.”
- [claimed-docs] “Allow AI agents to deploy a project and let a human take over.”
Railway documents an MCP server and CLI that let AI agents create projects, deploy templates, manage environments, and redeploy services (railway-docs-20, railway-docs-15), which functions as a programmatic interface for AI-native drivers. However, probing for a standard public API spec (OpenAPI/Swagger) returned 404 on all candidate paths, indicating no conventional documented REST/GraphQL API surface (railway-probe-2). Missing for 10: a discoverable OpenAPI/GraphQL API reference, independent confirmation of API completeness beyond MCP tool coverage.
- [claimed-docs] “It lets AI assistants create projects, deploy templates, manage environments, pull variables, and redeploy services.”
- [claimed-docs] “Develop locally and deploy from your terminal with the Railway CLI.”
- [claimed-docs] “Build with Railway using Agent Skills and the MCP server for AI-powered workflows.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.railway.com/openapi.json, https://docs.railway.com/swagger.json, https://docs.railway.c…”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round to VercelVercel documents securing 'every internal agent, app, and deployment with your identity provider' (vercel-docs-13), implying some access-control mechanism for agents, but there is no concrete documentation of issuing scoped/least-privilege API tokens or credentials specifically for AI agents. Missing for 10: explicit scoped API token/credential creation flow for agents, granularity of permissions, and independent confirmation of least-privilege enforcement.
- [claimed-docs] “Secure every internal agent, app, and deployment with your identity provider.”
- [claimed-docs] “Create tools for AI agents to interact with your systems.”
Railwaynone0/10Evidence shows Railway offers an MCP server and CLI-based agent authentication (railway-docs-19, railway-docs-20) but nothing describes scoped or least-privilege credential issuance — the agent integration docs only mention broad capabilities (create projects, deploy templates, manage environments, pull variables) with no token-scoping or permission-tiering language. missing for 10: any mention of scoped/limited API tokens, role-based or read-only credentials, or documentation of least-privilege agent authentication.
- [claimed-docs] “Install the Railway CLI and configure agent support — skills, MCP, and authentication — in one command.”
- [claimed-docs] “It lets AI assistants create projects, deploy templates, manage environments, pull variables, and redeploy services.”
- [claimed-docs] “Railway prepares the environment and carries available coding-agent credentials from your machine. Your files stay on the agent's disk, and …”
ai-native userBuild against official SDKs
weight 2 · round to VercelVercel documents official SDKs like the AI SDK and Workflow SDK, an OpenAI-compatible endpoint, and an OpenAPI spec, giving AI-native builders concrete first-party SDK surfaces to build against. However, evidence is limited to doc summaries and a bare OpenAPI probe with no independent hands-on validation of SDK completeness or developer experience. missing for 10: independent/hands-on corroboration of SDK usage, deeper docs on SDK API surface/versioning, and confirmation of SDK stability beyond marketing copy.
- [claimed-docs] “Call hundreds of models through one endpoint with the AI SDK, any OpenAI-compatible SDK, or cURL, with budgets, fallbacks, and usage monitor…”
- [claimed-docs] “Build durable, observable applications and AI agents with the Workflow SDK on a fully managed platform.”
- [probe] “PROBE openapi: HTTP 200 at https://vercel.com/openapi.json — contains "openapi" key”
- [claimed-docs] “Create tools for AI agents to interact with your systems.”
Railwaynone0/10Railway documents a CLI, MCP server, and agent skills for AI-driven workflows, but no evidence of official SDKs (client libraries) for building against Railway programmatically; a probe for OpenAPI/SDK specs returned 404s. Missing for 10: any first-party SDK (Python, Node, Go, etc.), API client library documentation, or SDK release notes.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.railway.com/openapi.json, https://docs.railway.com/swagger.json, https://docs.railway.c…”
- [claimed-docs] “Develop locally and deploy from your terminal with the Railway CLI.”
- [claimed-docs] “Build with Railway using Agent Skills and the MCP server for AI-powered workflows.”
ai-native userSubscribe to events via webhooks
weight 2 · round drawnVercelnone0/10No evidence pack item documents a webhooks subscription API or event-driven webhook feature; the closest is a Slack integration for deployment notifications, which is not a webhook mechanism for AI-native subscription. Missing for 10: any docs on a webhooks API, event types, subscription setup, or agent-facing usage of webhooks.
Agentic features
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · round to RailwayVercel's docs mention 'framework-aware insights' across apps and AI workflows for monitoring traffic, function performance, and errors (vercel-docs-30), which suggests some automated analysis of the user's own deployment/app data, but there is no clear evidence of AI-generated suggestions or recommendations (e.g., anomaly detection, actionable AI advice) surfaced inside the product. Missing for 10: explicit description of an AI/ML-driven insights engine that generates suggestions from user data, independent corroboration or screenshots of such a feature, and detail on how 'insights' differ from standard dashboards/metrics.
- [claimed-docs] “Monitor traffic, function performance, and errors with framework-aware insights across your apps and AI workflows.”
The Railway Agent (dashboard chat assistant) can inspect deployments, diagnose failures, and surface insights like opening PRs to fix broken builds, which is a form of AI-generated insight/suggestion within the product; connectors to Notion/Linear/Sentry extend this. However, this is framed as an operational/agentic assistant rather than data-analytics insights (e.g., no evidence of AI-generated insights over metrics, logs analytics, or cost/usage trends beyond failure diagnosis). Missing for 10: evidence of proactive AI-driven analytics/insights over metrics or usage data, independent user validation of insight quality, and broader scope beyond deployment troubleshooting.
- [claimed-docs] “The Railway Agent is a chat-based AI assistant built into the Railway dashboard. It can operate the platform on your behalf: creating and co…”
- [claimed-docs] “If the fix is in your code, the agent can open a pull request with the change so you can review and merge it.”
- [claimed-docs] “Connect Notion, Linear, or Sentry from the catalog, or point Railway at any remote MCP server you run, and the agent can read from it while …”
ai-native userSet up automations that run autonomously in the background
weight 2 · round drawnVercel's Workflow SDK explicitly supports building 'durable, observable applications and AI agents' on a managed platform, and scheduled ISR regeneration ('on a schedule') shows some background automation capability, but there is no dedicated cron/scheduler product documentation or independent evidence of long-running autonomous agent automations in production. missing for 10: explicit cron/scheduled-job feature docs, evidence of persistent background agent execution beyond ISR, and independent/hands-on confirmation that Workflow SDK automations run unattended reliably.
- [claimed-docs] “Build durable, observable applications and AI agents with the Workflow SDK on a fully managed platform.”
- [claimed-docs] “Regenerate static pages on a schedule or on demand without rebuilding your whole site.”
- [claimed-docs] “Run server-side code on demand with Fluid compute, which scales concurrency for AI and I/O-heavy workloads.”
Railway's Cloud Agents keep coding-agent machines running persistently in the background even after disconnecting, and the built-in Railway Agent can autonomously diagnose failures, create/configure services, and open PRs, plus condition-based Slack/Discord/email alerts run without manual triggering. However, evidence shows these are mostly agent-assisted or chat-triggered rather than fully scheduled/cron-style autonomous workflows, and there's no independent corroboration of unattended background automation reliability. Missing for 10: explicit scheduled/triggered automation framework (e.g. cron jobs), independent hands-on verification of autonomous background runs.
- [claimed-docs] “Railway prepares the environment and carries available coding-agent credentials from your machine. Your files stay on the agent's disk, and …”
- [claimed-docs] “The Railway Agent is a chat-based AI assistant built into the Railway dashboard. It can operate the platform on your behalf: creating and co…”
- [claimed-docs] “If the fix is in your code, the agent can open a pull request with the change so you can review and merge it.”
- [claimed-docs] “Slack, Discord, or emails the moment conditions you specify are met.”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · round to RailwayVercelnone0/10The 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.
Railway ships a built-in chat-based AI assistant ("Railway Agent") directly in the dashboard that can create/configure services, inspect deployments, diagnose failures, and open PRs to fix issues, plus Slack integration for delegating tasks conversationally. Missing for 10: independent/hands-on corroboration of the Railway Agent's real-world reliability and depth beyond vendor docs.
- [claimed-docs] “The Railway Agent is a chat-based AI assistant built into the Railway dashboard. It can operate the platform on your behalf: creating and co…”
- [claimed-docs] “If the fix is in your code, the agent can open a pull request with the change so you can review and merge it.”
- [claimed-docs] “Connect Notion, Linear, or Sentry from the catalog, or point Railway at any remote MCP server you run, and the agent can read from it while …”
- [claimed-docs] “Mention @Railway in Slack to ask the Railway Agent about your projects, inspect deployments, read logs, and make changes without leaving the…”
ai-native userOperate the product with natural-language commands
weight 2 · round to RailwayVercel ships agent-facing 'skills' and slash commands so coding agents (Claude Code, Cursor, Copilot, etc.) can drive deployments and framework tasks via natural language, and allows AI agents to deploy projects and hand off to a human — evidence of AI-native operability rather than a full built-in NL interface. This relies on third-party coding agents/CLIs rather than a native conversational control surface for the whole platform (dashboard, env vars, domains, etc.). Missing for 10: evidence of a first-party natural-language interface covering the full product surface, and independent hands-on validation that these agent skills reliably execute complex operations.
- [claimed-docs] “Give your coding agent deployment skills, framework best practices, and slash commands. Works with Claude Code, OpenAI Codex, Grok Build, Cu…”
- [claimed-docs] “Allow AI agents to deploy a project and let a human take over.”
- [claimed-docs] “Create tools for AI agents to interact with your systems.”
- [probe] “official CLI documented at https://vercel.com/docs/cli”
Railway ships a chat-based 'Railway Agent' in-dashboard and via Slack (@Railway) that lets users create/configure services, inspect deployments, diagnose failures, and open PRs using natural language, plus an MCP server and Agent Skills for AI assistants to manage projects, deploy templates, and redeploy services conversationally. This directly matches the ai-native/agenticness story of operating the product via natural-language commands. Missing for 10: independent/hands-on validation of the Railway Agent's reliability and accuracy beyond first-party docs.
- [claimed-docs] “The Railway Agent is a chat-based AI assistant built into the Railway dashboard. It can operate the platform on your behalf: creating and co…”
- [claimed-docs] “If the fix is in your code, the agent can open a pull request with the change so you can review and merge it.”
- [claimed-docs] “Connect Notion, Linear, or Sentry from the catalog, or point Railway at any remote MCP server you run, and the agent can read from it while …”
- [claimed-docs] “Mention @Railway in Slack to ask the Railway Agent about your projects, inspect deployments, read logs, and make changes without leaving the…”
- [claimed-docs] “It lets AI assistants create projects, deploy templates, manage environments, pull variables, and redeploy services.”
- [claimed-docs] “Install the Railway CLI and configure agent support — skills, MCP, and authentication — in one command.”
- [claimed-docs] “The use-railway skill teaches AI coding agents how to operate Railway.”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round drawnVercelnone0/10Evidence confirms Vercel exposes a machine-readable OpenAPI spec (openapi.json) and standard docs pages, but nothing in the pack describes an interactive, in-browser API reference with runnable/try-it examples (e.g., a Swagger-style console). Missing for 10: evidence of an interactive API console, 'try it now' runnable request feature, or embedded code execution in the docs UI.
Railwaynone0/10No evidence of an interactive API reference or runnable examples; the openapi probe explicitly returned 404s for all candidate spec paths, and no docs item mentions an API explorer or try-it-out console.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.railway.com/openapi.json, https://docs.railway.com/swagger.json, https://docs.railway.c…”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round to VercelA probe confirms Vercel publishes a machine-readable OpenAPI spec at vercel.com/openapi.json returning valid OpenAPI JSON, directly satisfying the story. Missing for 10: independent third-party corroboration or documentation describing spec versioning/coverage.
- [probe] “PROBE openapi: HTTP 200 at https://vercel.com/openapi.json — contains "openapi" key”
Railwaynone0/10The probe evidence explicitly shows all standard OpenAPI spec paths (openapi.json, swagger.json, etc.) return 404, and no docs mention a downloadable machine-readable API spec; only an llms.txt file and CLI/MCP docs are found. missing for 10: a hosted OpenAPI/Swagger spec, any documented machine-readable API schema.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.railway.com/openapi.json, https://docs.railway.com/swagger.json, https://docs.railway.c…”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.railway.com/llms.txt # Railway Documentation > Railway is an all-in-one intelligent cloud provider…”
ai-native userTest against a sandbox environment without touching production data
weight 1 · round drawnVercel provides preview/deployment environments with separate environment variables (docs-1, docs-23, docs-27) and sandboxed ephemeral execution for untrusted/agent-generated code (docs-3, docs-17), which together support testing without touching production data. However, evidence doesn't explicitly confirm data isolation (e.g., separate databases per preview) beyond env var management, and community feedback notes friction connecting databases securely without enterprise plans (vercel-comm-11). missing for 10: explicit documentation of production-data isolation/masking in preview/sandbox environments, independent hands-on confirmation that sandbox testing never touches prod data.
- [claimed-docs] “Connect your Git repository to deploy on every push, with automatic preview environments for testing changes before production.”
- [claimed-docs] “Run untrusted code in secure, ephemeral execution environments.”
- [claimed-docs] “Run untrusted or agent-generated code in isolated, ephemeral execution environments.”
- [claimed-docs] “Manage local, preview, production, and custom environments and the variables each one uses.”
- [claimed-docs] “Connect GitHub, GitLab, or Bitbucket to deploy on every push, with a preview URL for every branch.”
- [community] “"if you want to connect Vercel securely to a database with more than a password, you need to 'contact sales' about 'enterprise'... needing t…”
Railway supports isolated per-branch/PR preview environments and 'unlimited environments' for separate dev/staging vs production, which lets a user test changes without touching production (railway-docs-11, railway-docs-12). Cloud agents also run in isolated, ephemeral environments with their own disk (railway-docs-22). However, there is no explicit documentation of sandboxed test data, database seeding/copying, or safeguards preventing accidental production data access. Missing for 10: explicit sandbox/test-data isolation guidance, database cloning/seeding for previews, and independent confirmation that preview environments never touch production data.
- [claimed-docs] “Unlimited environments mean everyone can ship simultaneously.”
- [claimed-docs] “Every pull request gets its own preview. No surprises after merge.”
- [claimed-docs] “Railway prepares the environment and carries available coding-agent credentials from your machine. Your files stay on the agent's disk, and …”
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round drawnVercelnone0/10There is an OpenAPI spec exposed (vercel-probe-3), showing an API exists, but no evidence of API versioning scheme or a documented deprecation policy anywhere in the pack. Nothing addresses version numbers, sunset timelines, or breaking-change communication practices.
- [probe] “PROBE openapi: HTTP 200 at https://vercel.com/openapi.json — contains "openapi" key”
Railwaynone0/10No evidence of API versioning scheme or a documented deprecation policy; the openapi probe returned 404s on all candidate paths and no docs mention API versioning/deprecation commitments.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.railway.com/openapi.json, https://docs.railway.com/swagger.json, https://docs.railway.c…”
developerThe documented rate limits and concurrency caps for APIs and functions so I can plan for scale
weight 3 · round drawnVercelnone0/10The 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. Community evidence also does not address this topic.
Railwaynone0/10No evidence pack item documents rate limits or concurrency caps for Railway's APIs, MCP server, or functions; OpenAPI probe returned 404s and no rate-limit documentation is cited.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.railway.com/openapi.json, https://docs.railway.com/swagger.json, https://docs.railway.c…”
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userPerform bulk operations across many items at once
weight 2 · round drawnVercelnone0/10While Vercel exposes a CLI and REST/OpenAPI API (vercel-probe-3, vercel-probe-4) that could theoretically be scripted for bulk actions, the evidence pack contains no documentation of a bulk/batch operation feature (e.g., bulk deploy, bulk env-var update, bulk domain management) that an AI-native user could invoke across many items at once.
Railwaynone0/10Railway's docs describe MCP/CLI actions on individual projects, deployments, and variables (e.g., create projects, deploy templates, manage environments, pull variables, redeploy services), but no evidence shows any bulk or batch operation across many items at once. Missing for 10: documentation of batch/bulk API calls, multi-service scripting examples, or CLI flags for operating on multiple resources simultaneously.
- [claimed-docs] “It lets AI assistants create projects, deploy templates, manage environments, pull variables, and redeploy services.”
- [probe] “official CLI documented at https://docs.railway.com/guides/cli”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round to RailwayVercel supports several built-in event-triggered automations (deploy on git push, scheduled/on-demand ISR revalidation, middleware executing before requests, gradual/percentage rollouts, and a Workflow SDK for durable agent workflows), which are automatic actions tied to events. However, there is no evidence of a general user-configurable rules engine where an AI-native user can define arbitrary conditional 'if event X, then action Y' automations across the platform. Missing for 10: a documented rules/automation API or dashboard for custom event-trigger definitions, examples of user-defined conditional logic beyond fixed platform behaviors, and independent confirmation of such a feature working in practice.
- [claimed-docs] “Connect your Git repository to deploy on every push, with automatic preview environments for testing changes before production.”
- [claimed-docs] “Regenerate static pages on a schedule or on demand without rebuilding your whole site.”
- [claimed-docs] “Run code before a request completes to rewrite, redirect, or personalize responses.”
- [claimed-docs] “Build durable, observable applications and AI agents with the Workflow SDK on a fully managed platform.”
- [claimed-docs] “Send a new deployment to a percentage of traffic first, then promote it or roll back.”
Railway supports notification-style alerts ('Slack, Discord, or emails the moment conditions you specify are met') which is a basic trigger-action mechanism, and its Railway Agent/MCP ecosystem allows AI-driven actions like opening PRs on failed deployments, but there's no evidence of a general user-defined rules engine (custom conditions/triggers mapped to arbitrary actions) beyond alerting. missing for 10: a documented rules/automation engine letting users define arbitrary event-condition-action workflows, evidence of custom trigger configuration UI/API, and independent confirmation of reliability of these triggers.
- [claimed-docs] “Slack, Discord, or emails the moment conditions you specify are met.”
- [claimed-docs] “The Railway Agent is a chat-based AI assistant built into the Railway dashboard. It can operate the platform on your behalf: creating and co…”
- [claimed-docs] “If the fix is in your code, the agent can open a pull request with the change so you can review and merge it.”
ai-native userSchedule recurring jobs or workflows
weight 2 · round to VercelVercel docs mention regenerating content 'on a schedule' (ISR) and a Workflow SDK for building 'durable, observable applications and AI agents,' which together suggest some scheduled/automation capability, but neither explicitly describes a general-purpose cron/recurring-job scheduler for AI-native workflows. missing for 10: explicit dedicated cron/scheduled-jobs feature docs, examples of recurring AI workflow automation, and independent confirmation of scheduling reliability.
- [claimed-docs] “Regenerate static pages on a schedule or on demand without rebuilding your whole site.”
- [claimed-docs] “Build durable, observable applications and AI agents with the Workflow SDK on a fully managed platform.”
Railwaynone0/10The evidence pack covers deployments, scaling, environments, alerts, and AI agent integrations, but contains no mention of cron jobs, scheduled tasks, or recurring workflow execution capabilities. Missing for 10: any documentation of a cron/scheduler feature, recurring job configuration, or workflow automation triggers.
ai-native userVersion, review, and roll back my automations
weight 1 · round to RailwayVercel provides strong deployment-level version control, review, and rollback (git-based deploys, preview environments, comments, instant rollback, gradual rollout) and explicitly supports AI agents deploying with human takeover (vercel-docs-10), which maps well to versioning/reviewing/rolling back automations triggered by AI. However, evidence doesn't show version history, review, or rollback specifically for Workflow SDK-based agent workflows or tool-call automations themselves, only for deployments. Missing for 10: explicit versioning/rollback UI for AI agent workflows/tool executions (not just code deployments), independent corroboration of this specific AI-automation rollback flow.
- [claimed-docs] “Roll back to a previous deployment for swift recovery from production incidents.”
- [claimed-docs] “Revert production to a previous deployment without a rebuild when something breaks.”
- [claimed-docs] “Roll out new deployments in increments.”
- [claimed-docs] “Send a new deployment to a percentage of traffic first, then promote it or roll back.”
- [claimed-docs] “Let teams and invited collaborators comment on your preview and production environments.”
- [claimed-docs] “Allow AI agents to deploy a project and let a human take over.”
- [claimed-docs] “Build durable, observable applications and AI agents with the Workflow SDK on a fully managed platform.”
- [claimed-docs] “Connect your Git repository to deploy on every push, with automatic preview environments for testing changes before production.”
Railway explicitly supports git-based versioning of deployments, per-PR preview reviews before merge, and instant rollback to any previous version, and its Railway Agent can open pull requests for review before changes are merged — covering version/review/rollback of automations end-to-end. missing for 10: independent/hands-on corroboration that rollback and PR-review flows work reliably in practice (community evidence focuses on platform outages, not rollback failures).
- [claimed-docs] “Every pull request gets its own preview. No surprises after merge.”
- [claimed-docs] “Rollback to any previous version instantly when something breaks.”
- [claimed-docs] “Unlimited environments mean everyone can ship simultaneously.”
- [claimed-docs] “The Railway Agent is a chat-based AI assistant built into the Railway dashboard. It can operate the platform on your behalf: creating and co…”
- [claimed-docs] “If the fix is in your code, the agent can open a pull request with the change so you can review and merge it.”
Deploy workflow — the commit-to-production path — builds, previews, rollbacksDeploy workflow
The commit-to-production path — builds, previews, rollbacks
Cli tooling
developerDeploy my project directly from the command line without using a web dashboard
weight 2 · round drawnVercel provides an official CLI (vercel deploy/vc) documented at vercel.com/docs/cli, and the GitHub README confirms users can get started via the CLI to deploy without importing through the dashboard. This directly supports CLI-based deployment as a core, well-documented workflow. Missing for 10: independent hands-on walkthrough of a full CLI deploy session and more detail on CLI command coverage beyond the docs link.
- [probe] “official CLI documented at https://vercel.com/docs/cli”
- [github] “Get started by importing a project, choosing a template, or using the Vercel CLI. Then, git push to deploy.”
- [github] “To opt into the native binary and replace existing global vercel and vc commands, install the native package explicitly”
Railway documents a CLI that lets developers develop locally and deploy from the terminal, with a dedicated CLI guide page confirming this is an official, supported workflow. missing for 10: no independent/hands-on corroboration of CLI deploy experience, and no detail on full command coverage (e.g., env management, rollbacks) via CLI alone versus dashboard.
- [claimed-docs] “Develop locally and deploy from your terminal with the Railway CLI.”
- [claimed-docs] “Railway is an all-in-one intelligent cloud provider that makes it easy to provision infrastructure, develop locally, and deploy to the cloud…”
- [probe] “official CLI documented at https://docs.railway.com/guides/cli”
developerScaffold and deploy a new project with a single CLI command
weight 2 · round to VercelThe official GitHub README explicitly describes getting started by importing a project, choosing a template, or using the Vercel CLI, then deploying with git push, and docs confirm a dedicated CLI (vercel-docs-cli) plus zero-config framework deployment (vercel-docs-14). This directly matches scaffold-and-deploy via a single CLI workflow, though the pack lacks a concrete example transcript of a single command producing a scaffolded+deployed app or independent hands-on confirmation. Missing for 10: an explicit worked example of a single CLI invocation (e.g., `vercel init` + `vercel deploy`) and independent/community verification of the scaffold step's simplicity.
- [github] “Get started by importing a project, choosing a template, or using the Vercel CLI. Then, git push to deploy.”
- [probe] “official CLI documented at https://vercel.com/docs/cli”
- [claimed-docs] “Deploy Next.js with zero configuration, or bring one of 40+ supported frameworks.”
Docs confirm a dedicated CLI for local development and terminal deploys, plus one-click templates/starters, but no evidence details a single command that both scaffolds a new project and deploys it end-to-end. missing for 10: explicit CLI command sequence (e.g. init+up) demonstrating one-command scaffold-and-deploy, independent hands-on confirmation of speed/simplicity.
- [claimed-docs] “Develop locally and deploy from your terminal with the Railway CLI.”
- [claimed-docs] “One-click deployable applications and starters for common use cases.”
- [probe] “official CLI documented at https://docs.railway.com/guides/cli”
developerDevelop and test my app locally using a simulator that matches the production runtime
weight 2 · round to RailwayVercelnone0/10Evidence mentions the Vercel CLI and management of local/preview/production environments, but nothing in the pack claims a local simulator that matches the production runtime (e.g., serverless/edge function emulation). Missing for 10: explicit documentation of a local dev runtime (e.g., 'vercel dev') that mirrors production execution, and any hands-on confirmation of runtime parity.
- [claimed-docs] “Manage local, preview, production, and custom environments and the variables each one uses.”
- [probe] “official CLI documented at https://vercel.com/docs/cli”
Railway's CLI lets developers 'develop locally and deploy from your terminal' and inject production-like environment variables, but there's no evidence of an actual local simulator/emulator that mirrors the production runtime (e.g., container parity, network topology, or service mesh simulation). Missing for 10: documentation of a local runtime emulator, evidence of environment parity beyond env-var injection, and any independent confirmation that local dev closely mirrors production behavior.
- [claimed-docs] “Develop locally and deploy from your terminal with the Railway CLI.”
- [probe] “official CLI documented at https://docs.railway.com/guides/cli”
Deployment strategies
developerDeploy applications packaged as Docker containers
weight 2 · round drawnVercelnone0/10Vercel's evidence focuses on Git-push deploys, framework support (Next.js/40+ frameworks), functions, and isolated 'container' sandboxes for running untrusted code—none of this describes deploying a developer-supplied Docker image/Dockerfile as the deployment artifact. There is no documentation of Docker container deployment as a supported workflow.
- [claimed-docs] “Run production workloads in isolated containers on Vercel.”
- [claimed-docs] “Deploy Next.js with zero configuration, or bring one of 40+ supported frameworks.”
- [claimed-docs] “Connect GitHub, GitLab, or Bitbucket to deploy on every push, with a preview URL for every branch.”
- [github] “Get started by importing a project, choosing a template, or using the Vercel CLI. Then, git push to deploy.”
Railwaynone0/10The evidence pack describes Railway's git-based auto-config, canvas UI, CLI, and AI agent features, but no citation explicitly confirms deploying pre-built Docker container images or Dockerfiles as a supported workflow. missing for 10: explicit docs on Dockerfile/Docker image deployment support, evidence of container registry integration.
devops-leadRoll out new deployments incrementally to reduce blast radius
weight 2 · round to VercelVercel's docs explicitly describe incremental rollout with percentage-based traffic splitting and promote/rollback controls (vercel-docs-6, vercel-docs-28), plus instant rollback for recovery (vercel-docs-5, vercel-docs-29), directly matching the story of reducing blast radius via incremental deploys. Missing for 10: independent/hands-on corroboration of gradual rollout behavior in practice, and no detail on automated rollout policies (e.g., canary analysis or auto-rollback thresholds).
- [claimed-docs] “Roll out new deployments in increments.”
- [claimed-docs] “Send a new deployment to a percentage of traffic first, then promote it or roll back.”
- [claimed-docs] “Roll back to a previous deployment for swift recovery from production incidents.”
- [claimed-docs] “Revert production to a previous deployment without a rebuild when something breaks.”
Git integration
developerAutomatically deploy my app on every Git push
weight 3 · round to VercelVercel's core value proposition is Git-push deployment: docs explicitly state connecting GitHub/GitLab/Bitbucket triggers automatic deploys with preview URLs per branch, and the official GitHub README confirms the 'git push to deploy' workflow. This is corroborated by both first-party docs and the GitHub repo. Missing for 10: independent hands-on verification beyond vendor docs/GitHub description.
- [claimed-docs] “Connect your Git repository to deploy on every push, with automatic preview environments for testing changes before production.”
- [claimed-docs] “Connect GitHub, GitLab, or Bitbucket to deploy on every push, with a preview URL for every branch.”
- [github] “Get started by importing a project, choosing a template, or using the Vercel CLI. Then, git push to deploy.”
Railway's docs explicitly describe connecting a repo for auto-config deploys, per-PR preview environments, and unlimited environments so pushes deploy simultaneously, which directly covers git-push-triggered deployment workflows. Missing for 10: independent hands-on confirmation of push-to-deploy behavior and explicit mention of branch-based auto-deploy configuration options.
- [claimed-docs] “Connect your repo, Railway handles the rest. Auto-config, instant previews, no new tools to learn.”
- [claimed-docs] “Every pull request gets its own preview. No surprises after merge.”
- [claimed-docs] “Unlimited environments mean everyone can ship simultaneously.”
- [claimed-docs] “Railway is an all-in-one intelligent cloud provider that makes it easy to provision infrastructure, develop locally, and deploy to the cloud…”
developerDeploy my app by simply connecting my repo without manual build configuration
weight 3 · round to VercelVercel's docs and GitHub repo describe connecting a Git repo (GitHub/GitLab/Bitbucket) to auto-deploy on push with preview URLs, plus zero-config deployment for Next.js and 40+ frameworks, directly matching the story. This is corroborated by both docs and the official GitHub README describing the 'git push to deploy' flow. Missing for 10: independent hands-on verification beyond vendor docs/README confirming zero manual config in practice.
- [claimed-docs] “Connect your Git repository to deploy on every push, with automatic preview environments for testing changes before production.”
- [claimed-docs] “Connect GitHub, GitLab, or Bitbucket to deploy on every push, with a preview URL for every branch.”
- [claimed-docs] “Deploy Next.js with zero configuration, or bring one of 40+ supported frameworks.”
- [github] “Get started by importing a project, choosing a template, or using the Vercel CLI. Then, git push to deploy.”
Railway's docs explicitly state that connecting a repo triggers auto-configuration with no manual setup needed, YAML being optional, and instant PR previews without extra tooling — directly matching the story. Community evidence discusses reliability/outages but does not contradict the repo-connect/auto-config workflow itself. Missing for 10: independent hands-on developer confirmation of zero-config deploys and more detail on edge cases where manual config is still required.
- [claimed-docs] “Connect your repo, Railway handles the rest. Auto-config, instant previews, no new tools to learn.”
- [claimed-docs] “Modify settings directly from the canvas. YAML optional.”
- [claimed-docs] “Every pull request gets its own preview. No surprises after merge.”
- [claimed-docs] “Railway is an all-in-one intelligent cloud provider that makes it easy to provision infrastructure, develop locally, and deploy to the cloud…”
Infra as code
devops-leadDefine, deploy, and version my entire architecture with a single configuration file
weight 2 · round to RailwayVercelnone0/10No evidence pack item describes a single configuration file (e.g., vercel.json or IaC-style manifest) that defines and versions an entire architecture; docs mention environment variable management, CLI deploys, and marketplace integrations but nothing about unified architecture-as-code.
Railway's docs mention that settings can be modified via YAML ("YAML optional") alongside a visual canvas, and rollback/versioning of deployments is supported, hinting at config-as-code support, but there is no evidence of a single manifest file that defines and version-controls an entire multi-service architecture (e.g., a documented railway.json/toml schema covering networking, environments, and services in one file). missing for 10: explicit single-file architecture schema/manifest documentation, examples of defining multi-service topology in one file, and confirmation that this file is the primary/versioned source of truth rather than the canvas.
- [claimed-docs] “Modify settings directly from the canvas. YAML optional.”
- [claimed-docs] “Rollback to any previous version instantly when something breaks.”
- [claimed-docs] “Unlimited environments mean everyone can ship simultaneously.”
Manual deploy
developerDeploy 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
weight 2 · round to VercelEvidence confirms Vercel has a CLI (vercel-probe-4, vercel-gh-1) that can be used as an alternative to Git-based deploys, and preview/production URLs can be locked down via authentication or passwords (vercel-docs-26), which supports the 'private until published' part of the story. However, no evidence explicitly describes a folder-upload (no-Git) deploy flow or confirms new deployments are private-by-default. Missing for 10: explicit documentation of a drag-and-drop or CLI folder-upload deploy without any Git repo, and confirmation that such deployments default to private/unpublished state.
- [probe] “official CLI documented at https://vercel.com/docs/cli”
- [github] “Get started by importing a project, choosing a template, or using the Vercel CLI. Then, git push to deploy.”
- [claimed-docs] “Control who can open your preview and production URLs with Vercel Authentication, passwords, or trusted IPs.”
Railwaynone0/10Evidence shows Railway's primary deploy paths are Git-repo connection and CLI/local deploy, but nothing describes a folder-upload deploy flow or a private-until-published toggle for a new deployment.
- [claimed-docs] “Connect your repo, Railway handles the rest. Auto-config, instant previews, no new tools to learn.”
- [claimed-docs] “Develop locally and deploy from your terminal with the Railway CLI.”
- [probe] “official CLI documented at https://docs.railway.com/guides/cli”
Preview envs
developerGet ephemeral full-stack preview environments for every pull request
weight 2 · round to VercelVercel's docs explicitly describe automatic preview environments for every push/branch/PR, environment variable management across preview/production, preview URL access controls, and comment/collaboration on preview environments—covering the full-stack preview workflow. Missing for 10: independent hands-on verification of preview environment fidelity/performance beyond vendor docs.
- [claimed-docs] “Connect your Git repository to deploy on every push, with automatic preview environments for testing changes before production.”
- [claimed-docs] “Connect GitHub, GitLab, or Bitbucket to deploy on every push, with a preview URL for every branch.”
- [claimed-docs] “Manage local, preview, production, and custom environments and the variables each one uses.”
- [claimed-docs] “Let teams and invited collaborators comment on your preview and production environments.”
- [claimed-docs] “Control who can open your preview and production URLs with Vercel Authentication, passwords, or trusted IPs.”
- [github] “Get started by importing a project, choosing a template, or using the Vercel CLI. Then, git push to deploy.”
Railway's docs explicitly state every PR gets its own preview environment with instant, auto-configured full-stack previews and unlimited environments for parallel work. missing for 10: independent/hands-on verification of PR preview behavior at scale and details on environment teardown/ephemerality lifecycle.
- [claimed-docs] “Connect your repo, Railway handles the rest. Auto-config, instant previews, no new tools to learn.”
- [claimed-docs] “Unlimited environments mean everyone can ship simultaneously.”
- [claimed-docs] “Every pull request gets its own preview. No surprises after merge.”
developerGet an automatic preview URL for every pull request
weight 3 · round to VercelVercel's docs explicitly state that connecting a Git repo (GitHub, GitLab, Bitbucket) triggers automatic preview environments with a unique preview URL for every branch/push, which directly matches the PR-preview workflow story, and the GitHub repo confirms the git push-to-deploy flow. Missing for 10: independent hands-on confirmation beyond vendor docs of PR-specific (vs branch-only) preview URLs.
- [claimed-docs] “Connect your Git repository to deploy on every push, with automatic preview environments for testing changes before production.”
- [claimed-docs] “Connect GitHub, GitLab, or Bitbucket to deploy on every push, with a preview URL for every branch.”
- [github] “Get started by importing a project, choosing a template, or using the Vercel CLI. Then, git push to deploy.”
Railway docs explicitly state "Every pull request gets its own preview. No surprises after merge" and marketing highlights "instant previews" upon connecting a repo, directly matching the story. Missing for 10: independent/hands-on confirmation of PR preview URLs working in practice and details on configuration/limitations.
- [claimed-docs] “Every pull request gets its own preview. No surprises after merge.”
- [claimed-docs] “Connect your repo, Railway handles the rest. Auto-config, instant previews, no new tools to learn.”
Rollback recovery
developerRoll back a deployed service to any previous version in one click
weight 3 · round to VercelVercel's docs explicitly describe instant rollback to a previous deployment without rebuild for swift incident recovery, matching the one-click rollback story closely (vercel-docs-5, vercel-docs-29). This is corroborated by related gradual-rollout/promote-or-rollback functionality. missing for 10: independent hands-on confirmation of the rollback UX and any edge-case limitations (e.g., config/env var changes not covered by rollback).
- [claimed-docs] “Roll back to a previous deployment for swift recovery from production incidents.”
- [claimed-docs] “Revert production to a previous deployment without a rebuild when something breaks.”
- [claimed-docs] “Send a new deployment to a percentage of traffic first, then promote it or roll back.”
Railway's own docs explicitly claim 'Rollback to any previous version instantly when something breaks,' directly matching the story, but this is a single marketing-style claim with no independent/hands-on corroboration or detail on the one-click UX flow. Community evidence discusses platform stability incidents but does not specifically test or contradict rollback functionality. missing for 10: independent/hands-on verification of the rollback flow, documentation detail on how rollback is triggered (UI steps), confirmation it works across all deploy types.
- [claimed-docs] “Rollback to any previous version instantly when something breaks.”
Templates
developerDeploy one-click templates and starters for common use cases
weight 1 · round to Railwayvercel-gh-1 confirms users can start a deployment by 'choosing a template' alongside importing a project or using the CLI, which supports one-click templates/starters, but the evidence pack lacks any documentation of a template gallery, specific starter examples, or a dedicated one-click deploy flow beyond this single mention. missing for 10: dedicated template/starter gallery docs, specific example templates, independent hands-on confirmation of one-click deploy UX.
- [github] “Get started by importing a project, choosing a template, or using the Vercel CLI. Then, git push to deploy.”
- [claimed-docs] “Deploy Next.js with zero configuration, or bring one of 40+ supported frameworks.”
Docs explicitly state "One-click deployable applications and starters for common use cases" and the platform overall emphasizes quick repo-to-deploy workflows, supporting a template/starter deploy story. Missing for 10: independent hands-on verification of the template gallery experience and details on breadth/quality of available templates.
- [claimed-docs] “One-click deployable applications and starters for common use cases.”
- [claimed-docs] “Railway is an all-in-one intelligent cloud provider that makes it easy to provision infrastructure, develop locally, and deploy to the cloud…”
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
Environments
developerSpin up unlimited isolated environments so my whole team can ship simultaneously
weight 1 · round drawnVercel's preview environments automatically spin up an isolated deployment for every git push/branch, enabling parallel work by any team member without conflict, and environment/variable management supports local, preview, production, and custom environments concurrently. This directly matches the story of unlimited isolated environments for simultaneous shipping. Missing for 10: explicit confirmation of 'unlimited' concurrency limits/pricing tiers and independent hands-on validation of scale under heavy team usage.
- [claimed-docs] “Connect your Git repository to deploy on every push, with automatic preview environments for testing changes before production.”
- [claimed-docs] “Connect GitHub, GitLab, or Bitbucket to deploy on every push, with a preview URL for every branch.”
- [claimed-docs] “Manage local, preview, production, and custom environments and the variables each one uses.”
- [github] “Get started by importing a project, choosing a template, or using the Vercel CLI. Then, git push to deploy.”
Railway docs explicitly claim unlimited environments enabling simultaneous team shipping, backed by per-PR preview environments and instant rollback, directly matching the story. Missing for 10: independent/hands-on corroboration of environment isolation at scale and no detail on limits/costs for large teams.
- [claimed-docs] “Unlimited environments mean everyone can ship simultaneously.”
- [claimed-docs] “Every pull request gets its own preview. No surprises after merge.”
- [claimed-docs] “Rollback to any previous version instantly when something breaks.”
Scaling continuity
developerRely on the same core APIs and primitives from prototype through massive scale, without rearchitecting or migrating platforms as usage grows
weight 2 · round to VercelVercel's docs describe a consistent platform: zero-config framework deploys, Git-based push-to-deploy that works from prototype through production, and 'Fluid compute' explicitly designed to scale concurrency for demanding AI/I/O workloads without changing the deployment model (vercel-docs-14, vercel-docs-19, vercel-docs-27). However, community evidence shows real friction as usage grows — e.g. needing to 'contact sales' about 'enterprise' for basic secure database connections, and surprise large bills from traffic spikes — suggesting the platform isn't fully frictionless at scale and some capabilities require plan/negotiation changes rather than pure API continuity (vercel-comm-11, vercel-comm-12). Missing for 10: independent case studies of apps scaling from prototype to massive production traffic on unchanged APIs, and clearer evidence that enterprise-gated features don't require workflow changes.
- [claimed-docs] “Deploy Next.js with zero configuration, or bring one of 40+ supported frameworks.”
- [claimed-docs] “Run server-side code on demand with Fluid compute, which scales concurrency for AI and I/O-heavy workloads.”
- [claimed-docs] “Connect GitHub, GitLab, or Bitbucket to deploy on every push, with a preview URL for every branch.”
- [community] “"if you want to connect Vercel securely to a database with more than a password, you need to 'contact sales' about 'enterprise'... needing t…”
- [community] “"Waking up to a 10k vercel bill is pretty common, especially when a DDoS goes undetected."”
Railwaydisputedcontradicted4/10Railway's docs claim seamless scaling via the same primitives (scale CPU/RAM, add replicas, multi-region deploy) without new tooling, but independent community reports describe a platform-wide outage that took down the entire service and raised doubts about stability and trust at scale, directly undercutting the 'same core APIs from prototype to massive scale' promise. Missing for 10: first-party case studies of large-scale customers not hitting limits, and resolution of the stability concerns raised in the outage thread.
- [claimed-docs] “Scale CPU and RAM or add replicas with load balancing.”
- [claimed-docs] “Run your application closer to where your users are.”
- [claimed-docs] “Railway is an all-in-one intelligent cloud provider that makes it easy to provision infrastructure, develop locally, and deploy to the cloud…”
- [community] “Sorry, I have a hard time blaming Google for this, when Railway seems to be having increasing trouble keeping the platform stable. Something…”
- [community] “This is bad. Even their own website is down at railway.com. Looks like total dependency on google cloud. Surprising for a company of their s…”
- [community] “Railway is back, but I'm not sure if I can trust keeping my projects there, so I'm going to migrate to another company.”
Secrets management
devops-leadManage team-level access, secrets, and environment variables centrally
weight 2 · round to VercelDocs confirm centralized environment variable management across local/preview/production/custom environments and identity-provider based security for internal agents/apps/deployments, which supports centralized secrets/access control. However, there is no explicit documentation of team roles/permissions (RBAC) or audit logging, and a community report notes secure DB connections beyond a password require an 'enterprise' sales conversation, suggesting some access-control features are gated. Missing for 10: dedicated team roles/permissions docs, audit-log evidence, and confirmation that secret-sharing controls are available outside enterprise tiers.
- [claimed-docs] “Manage local, preview, production, and custom environments and the variables each one uses.”
- [claimed-docs] “Secure every internal agent, app, and deployment with your identity provider.”
- [community] “"if you want to connect Vercel securely to a database with more than a password, you need to 'contact sales' about 'enterprise'... needing t…”
Evidence only hints at environment management (unlimited environments, 'pull variables' via MCP) but never documents team roles/permissions, secrets vaults, or centralized access control for a devops-lead. Missing for 10: explicit team/role-based access control docs, shared secrets management features, and independent confirmation of these enterprise controls.
- [claimed-docs] “Unlimited environments mean everyone can ship simultaneously.”
- [claimed-docs] “It lets AI assistants create projects, deploy templates, manage environments, pull variables, and redeploy services.”
Tool continuity
developerKeep using my existing Git, CI, editor, and framework workflows without adopting proprietary tooling
weight 2 · round to RailwayVercel documents git-push deploys with GitHub/GitLab/Bitbucket, support for 40+ frameworks (including zero-config Next.js), and an optional CLI, which lets developers keep their existing Git and editor workflows largely intact (vercel-docs-1, vercel-docs-14, vercel-docs-27, vercel-gh-1, vercel-probe-4). However, community feedback flags real limitations: the platform is seen as effectively locked to the Node/JS/TS/Go ecosystem with 'WebAssembly gimmicks' for other languages, and some users feel it favors its own Next.js stack over full interoperability with arbitrary third-party CI systems (vercel-comm-7, vercel-comm-14). Missing for 10: explicit evidence of compatibility with external CI pipelines (Jenkins/CircleCI/etc.), broader language support beyond JS/TS/Go, and independent confirmation that non-Next.js frameworks get equally first-class treatment.
- [claimed-docs] “Connect your Git repository to deploy on every push, with automatic preview environments for testing changes before production.”
- [claimed-docs] “Deploy Next.js with zero configuration, or bring one of 40+ supported frameworks.”
- [claimed-docs] “Connect GitHub, GitLab, or Bitbucket to deploy on every push, with a preview URL for every branch.”
- [github] “Get started by importing a project, choosing a template, or using the Vercel CLI. Then, git push to deploy.”
- [probe] “official CLI documented at https://vercel.com/docs/cli”
- [community] “"There is no serious reason to use Vercel, other than for those being locked into the NextJs ecosystem and demo projects."”
- [community] “"I dislike how Vercel and Netlify build up on AWS and then we only get JS/TS/Go, or WebAssembly gimmicks." — complaint about limited languag…”
Railway's docs show it connects directly to existing Git repos with auto-config, PR-based preview environments, and a CLI for local development/deploy — i.e., no proprietary editor or framework required (railway-docs-1, railway-docs-12, railway-docs-15, railway-docs-17). However, config is presented as best done via a proprietary visual 'canvas' (YAML optional but canvas-first), and there's no explicit evidence of compatibility with external CI pipelines (e.g., GitHub Actions) or independent developer confirmation of a friction-free existing-workflow experience. missing for 10: evidence of CI-tool interoperability, independent/hands-on confirmation that no Railway-specific tooling is required, editor-specific integration details.
- [claimed-docs] “Connect your repo, Railway handles the rest. Auto-config, instant previews, no new tools to learn.”
- [claimed-docs] “Every pull request gets its own preview. No surprises after merge.”
- [claimed-docs] “Develop locally and deploy from your terminal with the Railway CLI.”
- [claimed-docs] “One-click deployable applications and starters for common use cases.”
- [claimed-docs] “Modify settings directly from the canvas. YAML optional.”
Edge compute — running code at the edge — regions, cold starts, runtime limitsEdge compute
Running code at the edge — regions, cold starts, runtime limits
Agent runtime
ai-native builderGive my coding agent a persistent runtime environment that checkpoints its state automatically while working
weight 2 · round to RailwayVercelnone0/10Vercel's execution environments are explicitly described as 'ephemeral' (vercel-docs-3, vercel-docs-17), the opposite of a persistent, auto-checkpointing runtime; no evidence describes state persistence or automatic checkpointing for agent workloads.
- [claimed-docs] “Run untrusted code in secure, ephemeral execution environments.”
- [claimed-docs] “Run untrusted or agent-generated code in isolated, ephemeral execution environments.”
- [claimed-docs] “Run production workloads in isolated containers on Vercel.”
Railway's cloud-agents feature explicitly provides a persistent runtime: the agent's machine 'stays running when you disconnect' and files persist on a dedicated disk, with coding-agent credentials carried over (railway-docs-22, 23, 24). However, there is no evidence of automatic state checkpointing/snapshotting of the agent's work — Railway's rollback feature (railway-docs-13) applies to deployment versions, not agent runtime state. Missing for 10: explicit automatic checkpoint/snapshot mechanism for agent state, evidence of restore-from-checkpoint after crash or disconnect, and independent corroboration of persistence reliability.
- [claimed-docs] “Railway prepares the environment and carries available coding-agent credentials from your machine. Your files stay on the agent's disk, and …”
- [claimed-docs] “Use Claude Desktop to work on a Railway cloud agent. Claude Code runs on the remote machine, with its development tools and persistent disk,…”
- [claimed-docs] “Give Codex Desktop a project on a Railway computer. The app connects over SSH, and Codex reads files, runs commands, and makes changes on yo…”
- [claimed-docs] “Rollback to any previous version instantly when something breaks.”
Placement latency
devops-leadDeploy my application to specific regions closer to my users
weight 2 · round to RailwayVercelnone0/10The evidence pack never mentions region selection, multi-region deployment, or edge network configuration for compute; middleware/CDN mentions (vercel-docs-20, vercel-docs-22) refer to on-demand code execution and image optimization, not choosing deployment regions. Since region control is a plausible and common capability for a deployment platform, absence of evidence yields 'none' rather than 'na'.
Railway's marketing docs mention 'Run your application closer to where your users are' (railway-docs-7), implying multi-region deployment, but there is no documentation on selecting specific regions, listing available regions, or configuring region-based deployment, and no independent/hands-on corroboration of this capability. Missing for 10: detailed region list/selection docs, technical configuration guidance, independent verification of region-based deployment working as described.
- [claimed-docs] “Run your application closer to where your users are.”
devops-leadRely on automatic compute placement near backend data to optimize latency
weight 2 · round to RailwayVercelnone0/10The evidence pack shows Vercel's edge/compute features (Edge Middleware, Fluid compute, CDN, ISR) but contains no mention of automatic compute placement based on backend/data location, region-aware routing, or latency-optimizing placement near a data store — this specific edge-compute capability is unevidenced. missing for 10: any documentation of automatic region/compute placement tied to backend data location, region-selection configuration, or latency-based routing near data stores.
- [claimed-docs] “Run server-side code on demand with Fluid compute, which scales concurrency for AI and I/O-heavy workloads.”
- [claimed-docs] “Run code before a request completes to rewrite, redirect, or personalize responses.”
- [claimed-docs] “Resize and convert images on demand and serve them from the CDN in modern formats.”
Railway's marketing states 'Run your application closer to where your users are' (docs-7), implying region selection for latency, but there is no evidence of automatic compute placement decisions based on backend data location, no documentation of an algorithm or feature that colocates compute with data stores. missing for 10: technical detail on automatic placement logic, evidence of data-aware region selection, and any independent corroboration of latency optimization near data.
- [claimed-docs] “Run your application closer to where your users are.”
Sandboxing
developerRun untrusted code in hardware-isolated, disposable sandboxes
weight 2 · round to VercelVercel's docs explicitly describe a Sandbox feature for running untrusted or agent-generated code in isolated, ephemeral execution environments, and separately for running production workloads in isolated containers, matching the disposable/isolated sandbox story closely. Missing for 10: explicit confirmation of hardware-level isolation (e.g., microVM/VM-based tech) and independent/hands-on validation beyond first-party docs.
- [claimed-docs] “Run untrusted code in secure, ephemeral execution environments.”
- [claimed-docs] “Run untrusted or agent-generated code in isolated, ephemeral execution environments.”
- [claimed-docs] “Run production workloads in isolated containers on Vercel.”
Railwaynone0/10Railway's evidence covers deployment, CI/CD, cloud agents with persistent disks, and AI integrations, but nothing addresses hardware-isolated, disposable sandboxes for running untrusted code — in fact cloud agents are described as persistent ('machine stays running when you disconnect'), the opposite of disposable isolation. Missing for 10: any mention of sandbox isolation technology (VM/hypervisor-level), disposability guarantees, or untrusted-code execution security model.
- [claimed-docs] “Railway prepares the environment and carries available coding-agent credentials from your machine. Your files stay on the agent's disk, and …”
Scaling
devops-leadDeploy instances that boot in under a second and scale to tens of thousands under load
weight 2 · round to VercelVercel's docs describe serverless/edge functions, Fluid compute for scaling concurrency, and isolated ephemeral execution environments that support rapid, elastic scaling for AI/I/O workloads, aligning with the edge-compute story's spirit. However, no evidence gives concrete sub-second boot benchmarks or explicit tens-of-thousands concurrent instance figures, and community reports of surprise $10k bills during undetected DDoS traffic (vercel-comm-12) hint at real-world scaling being uncontrolled/costly rather than a clean documented guarantee. Missing for 10: quantified cold-start/boot latency data, published large-scale load test results, and independent benchmarks validating claimed scale.
- [claimed-docs] “Run server-side code on demand with Fluid compute, which scales concurrency for AI and I/O-heavy workloads.”
- [claimed-docs] “Run production workloads in isolated containers on Vercel.”
- [claimed-docs] “Run untrusted or agent-generated code in isolated, ephemeral execution environments.”
- [claimed-docs] “Run code before a request completes to rewrite, redirect, or personalize responses.”
- [community] “"Waking up to a 10k vercel bill is pretty common, especially when a DDoS goes undetected."”
Railwaynone0/10Railway's docs mention general scaling (CPU/RAM/replicas, load balancing) and running closer to users, but there is no evidence of sub-second instance boot times or scaling to tens of thousands of instances under load, which is the specific edge-compute claim in the story. Community evidence even highlights platform-wide stability issues rather than proven massive-scale elasticity.
- [claimed-docs] “Scale CPU and RAM or add replicas with load balancing.”
- [claimed-docs] “Run your application closer to where your users are.”
- [community] “Sorry, I have a hard time blaming Google for this, when Railway seems to be having increasing trouble keeping the platform stable. Something…”
- [community] “This is bad. Even their own website is down at railway.com. Looks like total dependency on google cloud. Surprising for a company of their s…”
devops-leadRely on load-based autoscaling to absorb large traffic bursts automatically
weight 2 · round to VercelVercel's docs describe Fluid compute scaling concurrency for I/O-heavy workloads and isolated container-based production workloads, implying automatic capacity scaling for traffic bursts, and it offers bot/DDoS mitigation features (invisible CAPTCHA, custom firewall rules) that complement burst handling. However, there's no explicit 'autoscaling SLA' documentation, and community reports (e.g., surprise $10k bills tied to undetected DDoS traffic) suggest that while capacity does scale, cost/traffic-spike management can be unpredictable rather than a clean, bounded autoscaling guarantee. missing for 10: explicit autoscaling architecture docs/SLAs, independent load-test benchmarks, and clearer safeguards against runaway cost during bursts.
- [claimed-docs] “Run server-side code on demand with Fluid compute, which scales concurrency for AI and I/O-heavy workloads.”
- [claimed-docs] “Run production workloads in isolated containers on Vercel.”
- [claimed-docs] “Block attacks, scrapers, and unwanted traffic with custom rules, IP blocking, and managed rulesets.”
- [claimed-docs] “An invisible CAPTCHA that protects against sophisticated bots without challenges.”
- [community] “"Waking up to a 10k vercel bill is pretty common, especially when a DDoS goes undetected."”
Railwaynone0/10Docs mention manual scaling (adjusting CPU/RAM or adding replicas with load balancing) but there is no evidence of automatic, load-triggered autoscaling that reacts to traffic bursts without manual intervention.
- [claimed-docs] “Scale CPU and RAM or add replicas with load balancing.”
- [claimed-docs] “Private connections, public endpoints, SSL, and load balancing live from the moment you deploy.”
Serverless runtime
developerRun my code on a global edge network close to end users
weight 3 · round to VercelVercel's docs describe a global CDN with edge-executed middleware ('Run code before a request completes to rewrite, redirect, or personalize responses'), automatic image optimization served from the CDN, and Fluid compute scaling for I/O-heavy workloads, all consistent with edge network delivery close to end users. However, the evidence pack lacks explicit independent benchmarks or hands-on confirmation of edge latency/performance, and no community corroboration specifically addresses edge-network proximity. Missing for 10: independent latency benchmarks, explicit documentation of edge region coverage, and hands-on developer confirmation of edge execution behavior.
- [claimed-docs] “Run code before a request completes to rewrite, redirect, or personalize responses.”
- [claimed-docs] “Resize and convert images on demand and serve them from the CDN in modern formats.”
- [claimed-docs] “Run server-side code on demand with Fluid compute, which scales concurrency for AI and I/O-heavy workloads.”
- [claimed-docs] “Monitor traffic, function performance, and errors with framework-aware insights across your apps and AI workflows.”
Railwaydisputedcontradicted4/10Railway's marketing states only a single vague line — 'Run your application closer to where your users are' (railway-docs-7) — with no detail on edge regions, PoPs, or CDN architecture. Community reports of a major outage explicitly attribute it to 'total dependency on google cloud' and note the entire service (including the marketing site) went down together, which contradicts the premise of a distributed, resilient global edge network (railway-comm-4, railway-comm-6, railway-comm-1). missing for 10: documented edge-region list, latency/PoP architecture details, evidence of multi-region failover, and confirmation the claim survives independent scrutiny.
- [claimed-docs] “Run your application closer to where your users are.”
- [community] “This is bad. Even their own website is down at railway.com. Looks like total dependency on google cloud. Surprising for a company of their s…”
- [community] “Wait… railway runs on GCP? Didn't they make a whole thing about not 'building a cloud on top of another cloud'?”
- [community] “Sorry, I have a hard time blaming Google for this, when Railway seems to be having increasing trouble keeping the platform stable. Something…”
developerDeploy serverless functions and full-stack apps with no servers to manage
weight 3 · round to VercelVercel's docs demonstrate zero-config framework deployment, git-based deploys, serverless/fluid compute, isolated execution sandboxes, and full-stack support for 40+ frameworks with automatic scaling and no server management (vercel-docs-14, vercel-docs-19, vercel-docs-12, vercel-docs-17, vercel-gh-1). This is corroborated by independent commentary describing Vercel's smooth 'code and go' onboarding as a leading serverless platform experience (vercel-comm-3). Missing for 10: deeper independent hands-on benchmarks of serverless function cold-starts/scaling limits beyond community anecdotes.
- [claimed-docs] “Deploy Next.js with zero configuration, or bring one of 40+ supported frameworks.”
- [claimed-docs] “Run server-side code on demand with Fluid compute, which scales concurrency for AI and I/O-heavy workloads.”
- [claimed-docs] “Run production workloads in isolated containers on Vercel.”
- [claimed-docs] “Run untrusted or agent-generated code in isolated, ephemeral execution environments.”
- [github] “Get started by importing a project, choosing a template, or using the Vercel CLI. Then, git push to deploy.”
- [community] “A user predicted Vercel could become the dominant go-to platform for serverless frameworks, contrasting its smooth 'code and go' onboarding …”
Railway's docs strongly evidence full-stack app deployment with no server management (connect repo, auto-config, scaling, networking, previews), fitting the 'full-stack apps' half of the story. However there is no evidence of a serverless/FaaS functions offering (e.g., function-level deploys, event-triggered execution) — Railway's model is service/container-based rather than classic serverless functions. missing for 10: evidence of serverless function deployment/FaaS primitives, independent corroboration of zero-ops scaling under load.
- [claimed-docs] “Connect your repo, Railway handles the rest. Auto-config, instant previews, no new tools to learn.”
- [claimed-docs] “Railway is an all-in-one intelligent cloud provider that makes it easy to provision infrastructure, develop locally, and deploy to the cloud…”
- [claimed-docs] “Private connections, public endpoints, SSL, and load balancing live from the moment you deploy.”
- [claimed-docs] “Scale CPU and RAM or add replicas with load balancing.”
- [claimed-docs] “Every pull request gets its own preview. No surprises after merge.”
Workflows
developerDeploy durable, long-running workflows as code without manually wiring queues and retries
weight 2 · round to VercelVercel documents a Workflow SDK explicitly for building 'durable, observable applications and AI agents' on a fully managed platform, directly matching the story of deploying durable workflows as code without manually wiring queues/retries, and this is complemented by Fluid compute for scaling concurrency. Missing for 10: no independent/hands-on evidence of retry semantics or durability guarantees, no detail on how queuing is abstracted, and no community corroboration of real-world reliability.
- [claimed-docs] “Build durable, observable applications and AI agents with the Workflow SDK on a fully managed platform.”
- [claimed-docs] “Run server-side code on demand with Fluid compute, which scales concurrency for AI and I/O-heavy workloads.”
- [claimed-docs] “Monitor traffic, function performance, and errors with framework-aware insights across your apps and AI workflows.”
Railwaynone0/10Railway's evidence pack shows it as a deployment/hosting platform (repo-to-deploy, networking, scaling, environments, previews) with no mention of a durable execution engine, workflow-as-code framework, or built-in queue/retry orchestration primitives. The story describes a specific workflow-orchestration capability (like Temporal/Inngest) that Railway does not evidence.
- [claimed-docs] “Railway is an all-in-one intelligent cloud provider that makes it easy to provision infrastructure, develop locally, and deploy to the cloud…”
- [claimed-docs] “Scale CPU and RAM or add replicas with load balancing.”
- [claimed-docs] “Develop locally and deploy from your terminal with the Railway CLI.”
Networking security — network controls and isolation — private access, firewalls, encryptionNetworking security
Network controls and isolation — private access, firewalls, encryption
Access control
developerPut simple password protection on a deployed site without standing up a custom auth system
weight 2 · round to VercelVercel docs explicitly state you can 'Control who can open your preview and production URLs with Vercel Authentication, passwords, or trusted IPs' (vercel-docs-26), directly matching the story of simple password protection without building custom auth. Missing for 10: independent/hands-on corroboration of the password-protection feature working as described and details on any plan restrictions.
- [claimed-docs] “Control who can open your preview and production URLs with Vercel Authentication, passwords, or trusted IPs.”
Bot protection
developerProtect my app from automated bot traffic with invisible challenge-based protection
weight 1 · round to VercelVercel's docs explicitly describe an invisible CAPTCHA/bot check ('An invisible CAPTCHA that protects against sophisticated bots without challenges' and 'Protect sensitive routes from sophisticated bots with an invisible check instead of a CAPTCHA'), directly matching the story. This is complemented by broader firewall/rules-based bot blocking. Missing for 10: independent/hands-on verification of the invisible challenge's effectiveness and no third-party benchmarking of bypass rates.
- [claimed-docs] “An invisible CAPTCHA that protects against sophisticated bots without challenges.”
- [claimed-docs] “Protect sensitive routes from sophisticated bots with an invisible check instead of a CAPTCHA.”
- [claimed-docs] “Block attacks, scrapers, and unwanted traffic with custom rules, IP blocking, and managed rulesets.”
Railwaynone0/10No evidence in the pack mentions bot protection, challenge pages, CAPTCHA, or invisible bot-mitigation of any kind; Railway's docs focus on deployment, scaling, and networking basics like SSL/load balancing, not bot/WAF-style traffic protection. missing for 10: any mention of bot detection, challenge-based traffic filtering, or WAF/CDN-style bot mitigation features.
Ddos waf
devops-leadHave DDoS protection and a web application firewall applied to every request by default
weight 3 · round to VercelVerceldisputedcontradicted4/10Vercel's docs describe a firewall that can 'block attacks, scrapers, and unwanted traffic with custom rules, IP blocking, and managed rulesets' (vercel-docs-24) and bot-protection features (vercel-docs-11, vercel-docs-25), suggesting WAF-like capability, but these are configurable/opt-in rather than clearly stated as applied to every request 'by default'. A community report explicitly states that 'waking up to a 10k vercel bill is pretty common, especially when a DDoS goes undetected' (vercel-comm-12), directly contradicting the idea that DDoS protection is reliably applied automatically. missing for 10: explicit vendor claim of automatic, zero-config DDoS mitigation on every request, independent confirmation that the firewall/bot-protection is enabled by default rather than requiring rule configuration, and resolution of the community-reported undetected-DDoS billing incidents.
- [claimed-docs] “Block attacks, scrapers, and unwanted traffic with custom rules, IP blocking, and managed rulesets.”
- [claimed-docs] “An invisible CAPTCHA that protects against sophisticated bots without challenges.”
- [claimed-docs] “Protect sensitive routes from sophisticated bots with an invisible check instead of a CAPTCHA.”
- [community] “"Waking up to a 10k vercel bill is pretty common, especially when a DDoS goes undetected."”
Railwaynone0/10Evidence covers SSL, load balancing, and general networking but no mention of DDoS protection or a web application firewall being applied by default; the outage-related community items discuss general stability, not DDoS/WAF specifically. missing for 10: any mention of DDoS mitigation, WAF, or default request-level security filtering.
- [claimed-docs] “Private connections, public endpoints, SSL, and load balancing live from the moment you deploy.”
Domains
developerAttach custom domains to my deployed services
weight 2 · round to VercelVercel docs explicitly state you can 'Add a custom domain, manage DNS records, and get SSL certificates automatically,' directly matching the story of attaching custom domains to deployed services. This is first-party documentation with no contradicting evidence. Missing for 10: independent/hands-on corroboration of the custom domain workflow beyond vendor docs.
- [claimed-docs] “Add a custom domain, manage DNS records, and get SSL certificates automatically.”
Railwaynone0/10The evidence pack never explicitly mentions custom domain attachment; docs only reference generic 'public endpoints, SSL' (railway-docs-4) without confirming a custom-domain feature. Missing for 10: any documentation or community proof of attaching/verifying custom domains on deployed services.
- [claimed-docs] “Private connections, public endpoints, SSL, and load balancing live from the moment you deploy.”
developerProgrammatically provision and route custom domains for my own multi-tenant SaaS customers
weight 2 · round to VercelVercel docs mention adding custom domains with automatic DNS/SSL (vercel-docs-31) and an OpenAPI surface exists (vercel-probe-3), suggesting some programmatic domain management is possible, but there is no explicit documentation of a multi-tenant SaaS domain-provisioning API or workflow for routing customer-owned domains. Missing for 10: explicit Domains API docs for multi-tenant use cases, per-tenant provisioning examples, and independent confirmation of this workflow working at scale.
- [claimed-docs] “Add a custom domain, manage DNS records, and get SSL certificates automatically.”
- [probe] “PROBE openapi: HTTP 200 at https://vercel.com/openapi.json — contains "openapi" key”
Railwaynone0/10Railway's docs mention custom domains, SSL, and public endpoints being available at deploy time, but there is no evidence of a programmatic API/CLI capability for provisioning and routing custom domains on behalf of a multi-tenant SaaS's own customers, and a probe for an OpenAPI/domains API returned 404s.
- [claimed-docs] “Private connections, public endpoints, SSL, and load balancing live from the moment you deploy.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.railway.com/openapi.json, https://docs.railway.com/swagger.json, https://docs.railway.c…”
Env isolation
devops-leadIsolate non-production environments from accessing production services
weight 1 · round to VercelVercel lets teams manage separate environment variables per environment and gate preview/production URL access via authentication, passwords, or trusted IPs, which supports some separation between non-prod and prod environments. However, there's no explicit evidence of network-level isolation preventing a preview deployment from reaching production databases/services, and a community report notes that secure database connectivity beyond a password requires an enterprise sales conversation, undercutting the case for out-of-box isolation. Missing for 10: documented network segmentation or firewall rules between environments, default prevention of preview-to-production service calls, and independent verification that isolation works without enterprise upsell.
- [claimed-docs] “Manage local, preview, production, and custom environments and the variables each one uses.”
- [claimed-docs] “Control who can open your preview and production URLs with Vercel Authentication, passwords, or trusted IPs.”
- [claimed-docs] “Secure every internal agent, app, and deployment with your identity provider.”
- [community] “"if you want to connect Vercel securely to a database with more than a password, you need to 'contact sales' about 'enterprise'... needing t…”
Railwaynone0/10Evidence mentions 'unlimited environments' and private networking/endpoints generally, but there is no documentation or claim about network-level isolation preventing non-production environments from reaching production services (e.g., separate private networks, environment-scoped service discovery restrictions). Missing for 10: explicit environment-to-environment network isolation policy, private networking scoped per environment, access-control documentation preventing staging/dev from calling prod services.
- [claimed-docs] “Private connections, public endpoints, SSL, and load balancing live from the moment you deploy.”
- [claimed-docs] “Unlimited environments mean everyone can ship simultaneously.”
Identity
devops-leadSecure internal apps, deployments, and agents using my organization's identity provider
weight 2 · round to VercelVercel explicitly claims 'Secure every internal agent, app, and deployment with your identity provider' and separately offers Vercel Authentication/passwords/trusted IPs to gate preview and production URLs, directly matching the devops-lead's IdP-based security story. However, the evidence is a single thin marketing line with no detail on supported IdPs (SAML/OIDC/SSO providers), no docs on configuration steps, and no independent or hands-on corroboration that this works in practice. Missing for 10: detailed IdP integration docs (specific protocols/providers), setup/configuration guidance, and third-party validation of the feature working as described.
- [claimed-docs] “Secure every internal agent, app, and deployment with your identity provider.”
- [claimed-docs] “Control who can open your preview and production URLs with Vercel Authentication, passwords, or trusted IPs.”
Private networking
devops-leadKeep internal service-to-service traffic off the public internet without VPC complexity
weight 2 · round to RailwayVercelnone0/10The evidence pack contains no documentation of private networking, VPC peering, or mechanisms to keep service-to-service traffic off the public internet; a community comment even suggests secure database connectivity beyond a password requires an undocumented 'enterprise' sales conversation rather than a built-in feature. This is a fair axis for a cloud/deployment platform, but no capability is evidenced.
- [community] “"if you want to connect Vercel securely to a database with more than a password, you need to 'contact sales' about 'enterprise'... needing t…”
Railway's docs claim built-in "Private connections" alongside public endpoints, SSL, and load balancing "live from the moment you deploy," implying internal service traffic can stay off the public internet without manual VPC setup. However, the evidence pack gives only a single high-level marketing line with no architectural detail, no explicit VPC-avoidance framing, and no independent corroboration of how private networking actually isolates traffic. Missing for 10: detailed technical docs on private networking implementation, explicit no-VPC-needed messaging, and independent/hands-on verification of traffic isolation.
- [claimed-docs] “Private connections, public endpoints, SSL, and load balancing live from the moment you deploy.”
Protocols
developerServe HTTP, TCP, gRPC, and WebSocket traffic from the same deployed service without separate protocol configuration
weight 1 · round to RailwayVercelnone0/10Vercel's evidence is entirely about HTTP-based serverless functions, edge middleware, static hosting, and framework deployment; there is no mention of TCP, gRPC, or WebSocket protocol support from the same deployed service. Vercel's serverless model is known to be HTTP-request/response oriented, and no evidence pack item claims multi-protocol serving without separate configuration.
Railway's own docs explicitly state 'HTTP, TCP, gRPC, WebSockets handled automatically' alongside private connections, public endpoints, SSL, and load balancing available from deploy time, directly matching the story. Missing for 10: independent/hands-on verification of multi-protocol serving from a single service and technical detail on how protocol detection/config works under the hood.
- [claimed-docs] “HTTP, TCP, gRPC, WebSockets handled automatically.”
- [claimed-docs] “Private connections, public endpoints, SSL, and load balancing live from the moment you deploy.”
Tls certs
devops-leadGet free, automatically renewing TLS certificates for every domain including wildcards
weight 3 · round to VercelVercel's docs state that adding a custom domain automatically provides SSL certificates and DNS management, implying free, auto-renewing TLS, but the evidence never explicitly confirms wildcard domain certificate support or renewal mechanics. Missing for 10: explicit wildcard-domain TLS support, renewal automation details, and independent confirmation that certs are free/no manual step.
- [claimed-docs] “Add a custom domain, manage DNS records, and get SSL certificates automatically.”
Docs mention SSL is provided automatically for endpoints from the moment of deployment, implying free TLS certs, but there is no evidence about wildcard domain certificates or explicit auto-renewal guarantees. missing for 10: wildcard certificate support, explicit auto-renewal details, independent confirmation of custom domain TLS coverage.
- [claimed-docs] “Private connections, public endpoints, SSL, and load balancing live from the moment you deploy.”
Observability — seeing what the system is doing — logs, metrics, traces, alertsObservability
Seeing what the system is doing — logs, metrics, traces, alerts
Alerting
devops-leadSet up alerts that notify me via chat or email when specific conditions are met
weight 2 · round to RailwayVercel offers monitoring/observability (vercel-docs-30) and a Slack marketplace integration that notifies on deployment status and comments (vercel-intdir-6), plus third-party logging integrations like Better Stack (vercel-intdir-5), but there is no first-party evidence of configurable alert rules with custom conditions or native email notifications for observability thresholds. Missing for 10: documented native alert-rule/threshold configuration, email notification channel, and evidence these trigger on arbitrary monitoring conditions rather than just deployment events.
- [claimed-docs] “Monitor traffic, function performance, and errors with framework-aware insights across your apps and AI workflows.”
- [claimed-docs] “Get Slack messages for comments, deployment status, and new projects on Vercel.”
- [claimed-docs] “Better Stack - formerly Logtail”
Railway docs explicitly state it sends Slack, Discord, or email notifications the moment specified conditions are met, directly matching the story. missing for 10: no independent/hands-on corroboration of alert configuration UX, no detail on what conditions/metrics can trigger alerts.
- [claimed-docs] “Slack, Discord, or emails the moment conditions you specify are met.”
- [claimed-docs] “Create custom dashboards with metrics from any service.”
Metrics dashboards
devops-leadBuild custom dashboards combining metrics from any service
weight 2 · round to RailwayVercelnone0/10Vercel's docs mention its own monitoring/observability dashboard for traffic, function performance, and errors (vercel-docs-30) and marketplace integrations with monitoring tools like Better Stack (vercel-intdir-5), but there is no evidence of a capability to build custom dashboards combining metrics from arbitrary/any external services into one view.
Direct first-party claim confirms custom dashboards combining metrics from any service, but the pack offers no independent/hands-on corroboration or detail on dashboard flexibility (e.g., cross-project aggregation, widget types, sharing). missing for 10: independent verification, detail on dashboard customization scope, evidence of multi-service/cross-project metric combination in practice.
- [claimed-docs] “Create custom dashboards with metrics from any service.”
devops-leadTrack site performance and visitor behavior with built-in analytics
weight 1 · round to VercelVercel docs claim built-in monitoring of traffic, function performance, and errors with framework-aware insights (vercel-docs-30), which covers site performance observability; the in-browser toolbar also lets users inspect performance (vercel-docs-7). However, there's no explicit mention of visitor behavior analytics (e.g., page views, sessions, geography breakdowns) beyond generic 'traffic' monitoring, and no independent/hands-on corroboration of the analytics product's depth or dashboards. missing for 10: dedicated visitor-behavior analytics detail (e.g. Web Analytics feature specifics), independent verification of analytics accuracy/usefulness, and any devops-lead-specific alerting/dashboard evidence.
- [claimed-docs] “Monitor traffic, function performance, and errors with framework-aware insights across your apps and AI workflows.”
- [claimed-docs] “An in-browser toolbar to leave feedback, manage flags, preview drafts, and inspect performance.”
Railwaynone0/10Railway's docs show infrastructure-level metrics dashboards, logs, and alerting (railway-docs-8, railway-docs-9, railway-docs-10) but nothing about tracking visitor behavior or site-level analytics (page views, user sessions, traffic patterns) as a built-in feature — the evidence only covers service/CPU/RAM/log observability, not visitor analytics.
- [claimed-docs] “Create custom dashboards with metrics from any service.”
- [claimed-docs] “Slack, Discord, or emails the moment conditions you specify are met.”
- [claimed-docs] “All logs in one place. Spot issues without switching tools.”
Reliability sla
devops-leadCheck a public status page with historical incident postmortems before committing
weight 2 · round drawnVercelnone0/10No evidence pack item references a public status page or historical incident postmortem repository; the only related material is community criticism that Vercel's 2026 security incident disclosure was vague and lacked specifics, which does not constitute a status/postmortem page.
Railwaynone0/10No evidence pack item references a public status page or historical incident postmortems; only community complaints about an outage exist, with no mention of a status.railway.app or postmortem documentation. missing for 10: public status page, incident history, postmortem write-ups.
devops-leadReview a published uptime SLA with defined credits for downtime
weight 3 · round drawnVercelnone0/10No evidence pack item mentions an uptime SLA, uptime percentage guarantee, or service credits for downtime; only general platform features and community commentary on a security incident are present.
Railwaynone0/10No evidence in the pack of a published uptime SLA or defined downtime credits; docs focus on features like logs, alerts, and scaling, not contractual guarantees. Community evidence even describes a major outage with no mention of any credit/SLA process, reinforcing the absence.
- [community] “Sorry, I have a hard time blaming Google for this, when Railway seems to be having increasing trouble keeping the platform stable. Something…”
- [community] “This is bad. Even their own website is down at railway.com. Looks like total dependency on google cloud. Surprising for a company of their s…”
- [community] “Railway is back, but I'm not sure if I can trust keeping my projects there, so I'm going to migrate to another company.”
devops-leadThe guaranteed support response times and escalation paths for my plan tier
weight 2 · round drawnVercelnone0/10No evidence pack item mentions support SLAs, guaranteed response times, or escalation paths for any plan tier; only product features, community sentiment, and unrelated docs are provided.
Unified logging
developerView all my build, deploy, and runtime logs in one place
weight 3 · round to RailwayVercel's docs describe an observability feature that monitors traffic, function performance, and errors across apps and AI workflows (vercel-docs-30), and the platform inherently surfaces deployment/build status through its Git-integrated deploy flow (vercel-docs-1, vercel-docs-27). However, no evidence explicitly confirms a single unified view combining build logs, deploy logs, and runtime logs together. missing for 10: explicit documentation of a unified log viewer spanning build, deploy, and runtime stages, and independent/hands-on confirmation of this consolidated experience.
- [claimed-docs] “Monitor traffic, function performance, and errors with framework-aware insights across your apps and AI workflows.”
- [claimed-docs] “Connect your Git repository to deploy on every push, with automatic preview environments for testing changes before production.”
- [claimed-docs] “Connect GitHub, GitLab, or Bitbucket to deploy on every push, with a preview URL for every branch.”
Railway explicitly claims a unified log view ('All logs in one place. Spot issues without switching tools') plus supporting observability features like custom dashboards and metrics, matching the story directly. missing for 10: independent/hands-on verification of unified log UX, and detail on separating build vs deploy vs runtime log views.
- [claimed-docs] “All logs in one place. Spot issues without switching tools.”
- [claimed-docs] “Create custom dashboards with metrics from any service.”
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round drawnVercel exposes a public REST API (openapi.json) and a CLI covering deployments, domains, env vars, etc., suggesting broad but unconfirmed parity with the UI; no documentation explicitly claims full UI/API feature parity, and features like the in-browser toolbar, comments, and CMS draft preview are described as UI-specific experiences. missing for 10: explicit parity statement, evidence that toolbar/comments/CMS-preview features are API-accessible, independent confirmation of full API coverage.
- [probe] “PROBE openapi: HTTP 200 at https://vercel.com/openapi.json — contains "openapi" key”
- [probe] “official CLI documented at https://vercel.com/docs/cli”
- [github] “Get started by importing a project, choosing a template, or using the Vercel CLI. Then, git push to deploy.”
- [github] “To opt into the native binary and replace existing global vercel and vc commands, install the native package explicitly”
- [claimed-docs] “An in-browser toolbar to leave feedback, manage flags, preview drafts, and inspect performance.”
- [claimed-docs] “Let teams and invited collaborators comment on your preview and production environments.”
Railway ships a CLI and an MCP server that let AI assistants create projects, deploy templates, manage environments, pull variables, and redeploy services (railway-docs-20, railway-docs-19), showing partial programmatic parity with the UI, but there is no documented OpenAPI/GraphQL spec (probe for openapi paths returned 404s) and no claim that canvas-level configuration, dashboards, or alerting can be fully replicated via API. Missing for 10: explicit full API/UI parity documentation, discoverable OpenAPI/GraphQL schema, and evidence that canvas/dashboard/alert features are API-accessible.
- [claimed-docs] “Install the Railway CLI and configure agent support — skills, MCP, and authentication — in one command.”
- [claimed-docs] “It lets AI assistants create projects, deploy templates, manage environments, pull variables, and redeploy services.”
- [claimed-docs] “The Railway Agent is a chat-based AI assistant built into the Railway dashboard. It can operate the platform on your behalf: creating and co…”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.railway.com/openapi.json, https://docs.railway.com/swagger.json, https://docs.railway.c…”
ai-native userExport all of my data in open formats and leave
weight 3 · round drawnVercelnone0/10No 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. This is a reasonable axis for a PaaS holding deployment/config/data (project settings, env vars, analytics), but no such export capability is documented.
Railwaynone0/10Railway's docs cover migrating INTO Railway (e.g., from Heroku) and CLI/local dev workflows, but there is no evidence of any data export feature, open-format export of configs/logs/variables, or documented offboarding path for leaving the platform with your data intact.
- [claimed-docs] “Develop locally and deploy from your terminal with the Railway CLI.”
- [claimed-docs] “Migrate from Heroku”
ai-native userRead the product's source under an open license
weight 2 · round to VercelThere's a public GitHub repo (vercel/vercel) referenced for getting started with the CLI, suggesting some source is publicly visible, but no evidence confirms an explicit open-source license or that the core platform (not just the CLI) is open. missing for 10: explicit license documentation, confirmation that the full product/platform source (not just CLI) is publicly available, independent verification of licensing terms.
- [github] “Get started by importing a project, choosing a template, or using the Vercel CLI. Then, git push to deploy.”
ai-native userSelf-host the core product
weight 3 · round drawnVercelnone0/10Vercel 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. The evidence even shows community members switching to genuinely self-hostable alternatives like Dokploy specifically to leave Vercel, underscoring the absence of a self-host option.
- [community] “"Also checkout Dokploy. Incredible to leave Vercel." — implying satisfaction after switching away from Vercel to a self-hosted alternative.”
- [probe] “official CLI documented at https://vercel.com/docs/cli”
- [claimed-docs] “Deploy Next.js with zero configuration, or bring one of 40+ supported frameworks.”
Railwaynone0/10Railway is a managed cloud PaaS; nothing in the evidence pack mentions an open-source or self-hostable version of the core Railway platform — all docs describe using Railway's own hosted service. missing for 10: any open-source repo/license for the core platform, self-hosting instructions or Docker/K8s deployment guide for running Railway itself.
- [claimed-docs] “Railway is an all-in-one intelligent cloud provider that makes it easy to provision infrastructure, develop locally, and deploy to the cloud…”
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
Cost controls
devops-leadSet hard spending limits to control my cloud costs
weight 2 · round to RailwayVerceldisputedcontradicted3/10Vercel only documents 'budgets' as part of its AI Gateway feature for LLM usage (vercel-docs-2, vercel-docs-16), not a platform-wide hard spending cap for compute/bandwidth costs, and community reports explicitly describe surprise five-figure bills ('Waking up to a 10k vercel bill is pretty common, especially when a DDoS goes undetected') indicating no effective hard limit exists for overall cloud spend. Missing for 10: dedicated hard-cap/kill-switch billing controls for general project usage, first-party docs on enforceable spend limits, and independent confirmation that such limits actually stop overage.
- [claimed-docs] “Access hundreds of models through one endpoint with budgets, fallbacks, and monitoring.”
- [claimed-docs] “Call hundreds of models through one endpoint with the AI SDK, any OpenAI-compatible SDK, or cURL, with budgets, fallbacks, and usage monitor…”
- [community] “"Waking up to a 10k vercel bill is pretty common, especially when a DDoS goes undetected."”
A community tweet explicitly praises Railway for offering hard spending limits, confirming the capability exists and is well-received, but there is no first-party documentation detailing configuration options, scope (project vs org-level), or enforcement behavior. Missing for 10: official docs on setting/configuring hard spending limits, independent hands-on verification, and details on limit granularity.
- [claimed-docs] “really gotta commend @Railway for allowing hard spending limits, I have never, ever seen this with any cloud provider.”
devops-leadReceive migration credits when moving my production infrastructure to a new platform
weight 1 · round drawnVercelnone0/10No evidence in the pack mentions migration credits, competitive switching incentives, or pricing offers for moving infrastructure from another platform to Vercel; the pack covers deployment, security, and AI features only.
Railwaynone0/10Railway has migration guides (e.g., 'Migrate from Heroku', 'Compare to Render') but no evidence of any migration credit program, discount, or reimbursement offered to customers moving production infrastructure to the platform.
- [claimed-docs] “Migrate from Heroku”
- [claimed-docs] “Compare to Render”
Execution limits
devops-leadThe CPU and wall-clock execution time limits for functions so I can tell whether long-running or agentic workloads will fit
weight 3 · round drawnVercelnone0/10No evidence pack item specifies concrete CPU or wall-clock execution time limits for functions (e.g., seconds per plan tier). Docs mention Fluid compute, sandboxes, and workflows but never state numeric duration/CPU limits a devops-lead could use to size agentic workloads. Missing for 10: explicit maxDuration/timeout numbers per plan, CPU allocation limits, and any pricing-page or docs citation stating these limits.
- [claimed-docs] “Run server-side code on demand with Fluid compute, which scales concurrency for AI and I/O-heavy workloads.”
- [claimed-docs] “Run untrusted or agent-generated code in isolated, ephemeral execution environments.”
- [claimed-docs] “Run production workloads in isolated containers on Vercel.”
Railwaynone0/10Railway's evidence pack describes general CPU/RAM scaling (railway-docs-6) but contains no documentation of specific CPU or wall-clock execution time limits for functions/workloads, which is the core of this story. Missing for 10: any explicit stated time limits, timeout thresholds, or documentation addressing how long-running or agentic workloads are bounded.
- [claimed-docs] “Scale CPU and RAM or add replicas with load balancing.”
Overage fees
devops-leadThe exact overage fee schedule for exceeding plan usage limits (bandwidth, invocations, build minutes) before I get billed
weight 3 · round drawnVercelnone0/10The 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. A community comment even suggests unexpected surprise billing ("Waking up to a 10k vercel bill is pretty common"), reinforcing that no clear overage schedule evidence exists.
- [community] “"Waking up to a 10k vercel bill is pretty common, especially when a DDoS goes undetected."”
Railwaynone0/10The evidence pack contains no documentation of an overage fee schedule for bandwidth, invocations, or build minutes — only a community tweet praising hard spending limits, which is a cap mechanism, not a fee schedule disclosure. missing for 10: published overage rate/pricing table, per-resource overage unit costs, and billing documentation describing what happens when limits are exceeded.
- [claimed-docs] “really gotta commend @Railway for allowing hard spending limits, I have never, ever seen this with any cloud provider.”
devops-leadWhether pricing is per-seat with minimum seat counts that increase cost as my team grows
weight 2 · round drawnVercelnone0/10No evidence in the pack addresses Vercel's pricing model, seat-based billing, or minimum seat counts; all citations concern product features, integrations, or unrelated community sentiment/security incidents. This axis applies to any SaaS platform but is unaddressed here.
Usage billing
devops-leadPay only for active compute time rather than idle wall-clock time
weight 2 · round to VercelVercel's 'Fluid compute' feature is explicitly marketed as running server-side code 'on demand' with concurrency scaling for I/O and AI workloads, which aligns with paying only for active compute rather than idle time — a core value prop of this pricing model. However, there is no detailed documentation of the actual billing mechanics (e.g., how idle vs active CPU time is measured/charged) and community sentiment includes concerns about unpredictable large bills, suggesting real-world cost behavior isn't fully transparent. Missing for 10: detailed pricing/billing docs on active-vs-idle compute metering, third-party verification of actual cost savings vs traditional serverless, and clarification of how this applies across all function types.
- [claimed-docs] “Run server-side code on demand with Fluid compute, which scales concurrency for AI and I/O-heavy workloads.”
- [community] “"Waking up to a 10k vercel bill is pretty common, especially when a DDoS goes undetected."”
Railwaynone0/10The evidence pack contains no documentation or claims about usage-based/active-compute billing versus idle time; only a community tweet about 'hard spending limits' is present, which addresses spend caps, not billing granularity. Missing for 10: any doc on per-second/active-compute billing model, idle-scale-to-zero mechanics, or pricing page evidence.
- [claimed-docs] “really gotta commend @Railway for allowing hard spending limits, I have never, ever seen this with any cloud provider.”
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
ai-native userChoose where my data is stored (region/residency)
weight 2 · round to RailwayVercelnone0/10No evidence pack item mentions data residency, region selection, or storage location controls for Vercel deployments or data; the closest items are about environments, domains, and functions, not geographic data residency.
Railway docs mention running applications 'closer to where your users are' (railway-docs-7), implying some region choice for deployments, but there is no explicit documentation of selectable regions, data storage location controls, or compliance/residency certifications (e.g., GDPR, SOC2) that would let an AI-native user confirm where their data is stored. Missing for 10: explicit region list/selector for compute and storage, data residency guarantees, and compliance documentation.
- [claimed-docs] “Run your application closer to where your users are.”
ai-native userPrevent my data from being used to train AI models
weight 3 · round drawnVercelnone0/10No 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.
Railwaynone0/10No evidence pack items mention data usage for AI model training or any opt-out/privacy controls regarding AI training; this is a cloud infrastructure provider and the axis of preventing AI training on user data is applicable (as with any SaaS handling customer data/code) but wholly unaddressed. Missing for 10: any privacy policy statement on AI training, opt-out settings, or data usage terms.
ai-native userControl data retention and deletion
weight 2 · round drawnVercelnone0/10The evidence pack contains no mention of data retention policies, deletion controls, data lifecycle management, or privacy/GDPR-style deletion tooling for Vercel. While security-adjacent topics (identity, environment variables, incident disclosure) appear, none address user-controllable data retention/deletion.
Railwaynone0/10No evidence in the pack addresses data retention policies, deletion controls, or privacy settings for AI workflows on Railway; the only tangential item (railway-comm-8) is a community jab about backup security, not a documented retention/deletion control. missing for 10: documentation of data retention policy, explicit deletion/opt-out controls, AI-specific data handling disclosures.
- [community] “Isn't Railway the 'the API key to delete the backups is in the prod database, because that's where the backups live duh' guys?”
ai-native userOpt out of telemetry and usage tracking
weight 2 · round drawnVercelnone0/10No evidence pack item mentions telemetry, usage tracking, or an opt-out mechanism for Vercel's CLI, platform, or AI tools; nothing in the docs, GitHub, or community sources addresses this capability.
Storage data — storing and moving data — persistence, formats, durabilityStorage data
Storing and moving data — persistence, formats, durability
Cdn assets
developerServe static assets faster using a global CDN with edge caching
weight 2 · round to VercelVercel documents serving optimized images 'from the CDN' and offers ISR/edge middleware, implying CDN-backed static asset delivery, but the evidence pack lacks explicit documentation of a global edge network, cache-control/edge caching mechanics, or performance benchmarks/independent corroboration of CDN speed. Missing for 10: explicit global CDN architecture docs, edge cache configuration details, independent performance benchmarks confirming faster asset delivery.
- [claimed-docs] “Resize and convert images on demand and serve them from the CDN in modern formats.”
- [claimed-docs] “Regenerate static pages on a schedule or on demand without rebuilding your whole site.”
- [claimed-docs] “Deploy Next.js with zero configuration, or bring one of 40+ supported frameworks.”
Railwaynone0/10No evidence of a CDN or edge-caching feature for static assets; Railway's evidence covers deployment, scaling, monitoring, and AI agent tooling but nothing about a global CDN or edge caching. 'Run your application closer to where your users are' refers to regional deployment, not CDN/static asset caching.
- [claimed-docs] “Run your application closer to where your users are.”
Integrations
developerConnect my code to external services like databases, APIs, and storage through native bindings with minimal boilerplate instead of hand-wiring SDKs and credentials
weight 2 · round to VercelVercel's Marketplace lists native, first-party integrations (Neon Postgres, Pinecone, Shopify, Slack, Jira/Linear, etc.) that plug into a project with managed credentials, reducing manual SDK wiring, and Vercel documents environment/variable management across environments. However, a concrete community report states that connecting to a database with more than a password requires 'contact sales' for enterprise, indicating the native-binding security experience is limited for standard tiers, and there's no first-party technical deep-dive on how the binding/credential injection mechanism works beyond marketplace listings. Missing for 10: detailed docs on the binding mechanism itself, independent hands-on confirmation of minimal-boilerplate setup, and resolution of the enterprise-gating friction noted in community feedback.
- [claimed-docs] “A collection of first-party services you can easily add to your Vercel project.”
- [claimed-docs] “Neon is serverless Postgres built for the cloud, with autoscaling and instant branching.”
- [claimed-docs] “Access Perplexity's cutting edge LLMs”
- [claimed-docs] “Get Slack messages for comments, deployment status, and new projects on Vercel.”
- [claimed-docs] “Convert comments to Linear issues”
- [claimed-docs] “Manage local, preview, production, and custom environments and the variables each one uses.”
- [community] “"if you want to connect Vercel securely to a database with more than a password, you need to 'contact sales' about 'enterprise'... needing t…”
Railway offers private networking, one-click databases/starters, and infrastructure provisioning with auto-config, which reduces some manual wiring, but the evidence pack lacks specifics on native SDK-free bindings for external third-party services (e.g., managed connectors to Stripe, S3, external APIs) or credential-injection features beyond internal service linking. Missing for 10: concrete documentation of native bindings/connectors to external third-party services and APIs, evidence of automatic credential/env-var injection without manual SDK setup, and independent corroboration of this workflow in practice.
- [claimed-docs] “Connect your repo, Railway handles the rest. Auto-config, instant previews, no new tools to learn.”
- [claimed-docs] “Private connections, public endpoints, SSL, and load balancing live from the moment you deploy.”
- [claimed-docs] “One-click deployable applications and starters for common use cases.”
- [claimed-docs] “Railway is an all-in-one intelligent cloud provider that makes it easy to provision infrastructure, develop locally, and deploy to the cloud…”
Kv cache
developerUse a Redis-compatible key-value store for low-latency caching and job queues
weight 2 · round drawnVercelnone0/10The evidence pack lists many Vercel marketplace integrations (Neon Postgres, Shopify, Perplexity, Pinecone, etc.) but none mention a Redis-compatible key-value store, caching layer, or job-queue product like Upstash/Vercel KV. Storage/caching is a plausible axis for a deployment platform, but no evidence here demonstrates this capability.
Railwaynone0/10The evidence pack contains no mention of Redis, a key-value store, or caching/queue database offerings on Railway—only generic deployment, templates, and AI-agent features. While Railway as a cloud platform could plausibly offer this (axis applies), there is no documentation or community evidence confirming a Redis-compatible database is available.
Object storage
developerPersist user-generated uploads using built-in object storage
weight 2 · round drawnVercelnone0/10The evidence pack lists Vercel's marketplace integrations (Neon Postgres, Pinecone, Better Stack, etc.) and platform features (deployments, functions, image optimization) but nowhere mentions Vercel Blob or any built-in object storage product for persisting user uploads. Storage-as-a-service is a plausible axis for a hosting platform, but no documentation, marketplace listing, or community evidence confirms this capability.
- [claimed-docs] “A collection of first-party services you can easily add to your Vercel project.”
- [claimed-docs] “Neon is serverless Postgres built for the cloud, with autoscaling and instant branching.”
- [claimed-docs] “Power your AI products with Pinecone”
Relational db
developerProvision a fully-managed Postgres database with point-in-time recovery, replicas, and high availability
weight 3 · round to VercelVercel offers Postgres only via a third-party Marketplace partner (Neon), described as 'serverless Postgres... with autoscaling and instant branching' rather than a Vercel-native fully-managed service with explicit point-in-time recovery, replicas, or HA guarantees. Missing for 10: first-party documentation of PITR, replica configuration, and HA SLAs, and any confirmation these features are exposed through the Vercel-integrated product rather than left to Neon's own console.
- [claimed-docs] “Neon is serverless Postgres built for the cloud, with autoscaling and instant branching.”
- [claimed-docs] “A collection of first-party services you can easily add to your Vercel project.”
Railwaynone0/10The evidence pack contains no documentation of Railway provisioning managed Postgres with point-in-time recovery, replicas, or high availability — only generic claims about scaling CPU/RAM and adding replicas for services in general (railway-docs-6), with no database-specific backup/PITR/HA feature descriptions. A community comment even suggests backup handling has been criticized (railway-comm-8), but nothing confirms the capability exists as described.
- [claimed-docs] “Scale CPU and RAM or add replicas with load balancing.”
- [community] “Isn't Railway the 'the API key to delete the backups is in the prod database, because that's where the backups live duh' guys?”
developerQuery a serverless SQL database directly from my code with no connection management
weight 2 · round to VercelVercel's marketplace lists Neon as a serverless Postgres partner offering autoscaling and instant branching, which implies serverless SQL access without manual connection pooling, but this is a third-party integration rather than a first-party Vercel database product with explicit 'no connection management' messaging. A community comment also notes friction: securely connecting Vercel to a database beyond a password reportedly requires an enterprise sales conversation, undercutting the 'no connection management' simplicity claim. Missing for 10: first-party Vercel docs describing a native serverless SQL/Postgres offering with pooling handled transparently, code examples showing zero-config querying, and independent hands-on confirmation that connection management is truly abstracted.
- [claimed-docs] “Neon is serverless Postgres built for the cloud, with autoscaling and instant branching.”
- [community] “"if you want to connect Vercel securely to a database with more than a password, you need to 'contact sales' about 'enterprise'... needing t…”
Railwaynone0/10Railway's evidence pack shows it as a general deployment/hosting platform with infra provisioning, CLI, and observability features, but nothing describes a serverless SQL database with an HTTP/driverless query interface (no connection pooling/management) like Neon or PlanetScale offer. Railway databases are provisioned as long-running services requiring standard connection strings, so the specific 'no connection management' serverless query capability is unevidenced.
Not comparable on these axes
developerUse an in-browser toolbar to leave feedback, manage feature flags, and inspect performance directly on my live site
weight 1 · not comparableVercel's docs explicitly describe an in-browser toolbar for leaving feedback, managing feature flags, previewing drafts, and inspecting performance, directly matching the story, and this is reinforced by related features like comments on preview/production environments and framework-aware performance insights. missing for 10: independent/hands-on corroboration of the toolbar beyond first-party docs.
- [claimed-docs] “An in-browser toolbar to leave feedback, manage flags, preview drafts, and inspect performance.”
- [claimed-docs] “Let teams and invited collaborators comment on your preview and production environments.”
- [claimed-docs] “Monitor traffic, function performance, and errors with framework-aware insights across your apps and AI workflows.”
Railwayn/aThis story describes an in-browser feedback/feature-flag/performance widget embedded on a live website (a product like a customer feedback/observability toolbar), which is not a category fit for Railway, a cloud infrastructure/deployment platform. Railway's evidence covers deployment, scaling, logs, and dashboards but nothing about an embeddable end-user-facing toolbar for feedback or feature flags on a live site.
developerLet teammates and collaborators comment directly on preview and production environments
weight 1 · not comparableVercel docs explicitly state teams and invited collaborators can comment on preview and production environments, corroborated by marketplace integrations that convert those comments into GitHub/Jira/Linear issues, showing the feature is real and integrated into workflows. Missing for 10: independent/hands-on user testimonials specifically about the commenting feature's usability.
- [claimed-docs] “Let teams and invited collaborators comment on your preview and production environments.”
- [claimed-docs] “An in-browser toolbar to leave feedback, manage flags, preview drafts, and inspect performance.”
- [claimed-docs] “Convert comments to GitHub issues”
- [claimed-docs] “Convert comments to Jira issues”
- [claimed-docs] “Convert comments to Linear issues”
developerWrite code against standard runtime APIs so it runs unmodified across multiple edge platforms instead of being locked into proprietary storage/runtime APIs
weight 2 · not comparableVercelnone0/10The evidence pack contains no documentation of Vercel supporting standard, portable runtime/storage APIs (e.g., Web APIs, WinterCG standards) that would let code run unmodified on other edge platforms; all functions (Edge Middleware, Functions, KV/Blob storage, ISR) are described as Vercel-specific proprietary features. Community commentary even explicitly flags lock-in ('locked into the NextJs ecosystem') as a reason to avoid Vercel, reinforcing the absence of cross-platform portability. missing for 10: evidence of standard Web/Edge runtime API compliance, documentation of avoiding proprietary storage/runtime lock-in, cross-platform interoperability claims or benchmarks.
- [community] “"There is no serious reason to use Vercel, other than for those being locked into the NextJs ecosystem and demo projects."”
- [claimed-docs] “Run server-side code on demand with Fluid compute, which scales concurrency for AI and I/O-heavy workloads.”
- [claimed-docs] “Run code before a request completes to rewrite, redirect, or personalize responses.”
Railwayn/aRailway is a general-purpose PaaS/cloud provider for deploying containers and standard app runtimes, not an edge-compute platform (like Cloudflare Workers/Deno Deploy) with proprietary storage/runtime APIs that this story is contrasting against. Nothing in the evidence discusses edge-platform portability or standard runtime API compliance across edge providers, so this axis is a category mismatch for Railway's product type.
devops-leadVisualize and edit my entire infrastructure stack on a visual canvas without writing config files
weight 2 · not comparableVerceln/aVercel is a code-first deployment/hosting platform with a CLI and config files (vercel.json, git-based deploys); there is no evidence of a visual canvas for designing or editing infrastructure without config. This story targets an IaC-visualization product category, which is a wrong axis for a deployment platform like Vercel.
Railway's docs explicitly describe a visual canvas showing the entire stack, with settings editable directly on canvas and YAML marked optional, matching the story closely. Missing for 10: independent hands-on review/screenshots demonstrating full editing depth on canvas beyond marketing copy, and no community corroboration of the canvas editing experience specifically.
- [claimed-docs] “Craft on a visual canvas that makes your entire stack visible at a glance.”
- [claimed-docs] “Modify settings directly from the canvas. YAML optional.”
- [claimed-docs] “Connect your repo, Railway handles the rest. Auto-config, instant previews, no new tools to learn.”
ai-native builderRun AI model inference globally with a single call without managing GPUs or capacity planning
weight 3 · not comparableVercel AI Gateway lets builders call hundreds of models through one endpoint with budgets, fallbacks, and monitoring (a global, single-call inference layer), and Fluid compute scales concurrency for AI workloads without manual GPU management. However, this is a gateway/routing layer to third-party model providers rather than Vercel itself running GPU inference, and there's no evidence of Vercel-hosted GPU capacity planning being abstracted away for actual model hosting. Missing for 10: independent/hands-on verification of global latency and capacity claims, detail on GPU-backed inference infrastructure vs. pure routing, and confirmation this covers self-hosted/custom model inference, not just third-party API aggregation.
- [claimed-docs] “Access hundreds of models through one endpoint with budgets, fallbacks, and monitoring.”
- [claimed-docs] “Call hundreds of models through one endpoint with the AI SDK, any OpenAI-compatible SDK, or cURL, with budgets, fallbacks, and usage monitor…”
- [claimed-docs] “Run server-side code on demand with Fluid compute, which scales concurrency for AI and I/O-heavy workloads.”
- [claimed-docs] “Monitor traffic, function performance, and errors with framework-aware insights across your apps and AI workflows.”
ai-native builderAccess hundreds of AI models through a single unified gateway endpoint
weight 3 · not comparableVercel's AI Gateway is directly documented as accessing hundreds of models through one unified endpoint, supporting the AI SDK, OpenAI-compatible SDKs, or cURL, with budgets, fallbacks, and usage monitoring. Missing for 10: independent/hands-on corroboration of the gateway's model count and reliability claims beyond first-party docs.
- [claimed-docs] “Access hundreds of models through one endpoint with budgets, fallbacks, and monitoring.”
- [claimed-docs] “Call hundreds of models through one endpoint with the AI SDK, any OpenAI-compatible SDK, or cURL, with budgets, fallbacks, and usage monitor…”
Railwayn/aRailway is a deployment/infrastructure platform, not an AI model gateway; nothing in the evidence describes a unified endpoint for accessing hundreds of AI models. This story targets a fundamentally different product category (LLM gateway/router), making the axis a category error for Railway.
developerHandle persistent WebSocket connections from within edge/serverless functions for real-time apps
weight 2 · not comparableVercelnone0/10No evidence pack item describes WebSocket support in Vercel's serverless/edge functions; the functions described (Edge Middleware, Fluid compute, sandboxes) are documented as request/response or ephemeral execution models, not persistent connections. Absence of evidence for this applicable capability yields 'none'. missing for 10: any documentation of WebSocket/persistent-connection support in serverless or edge functions, any first-party guidance on real-time connection handling.
Railwayn/aRailway is a persistent-container/service hosting platform, not an edge/serverless-functions runtime (e.g., Cloudflare Workers, Vercel Edge Functions); the story specifically asks about WebSocket handling within short-lived edge/serverless function execution models, which is a different product category than what Railway offers.
developerRun unmodified Node.js code and npm packages in edge/serverless functions instead of a restricted runtime subset
weight 3 · not comparableDocs reference Fluid compute for running 'server-side code on demand' (vercel-docs-19) and 'production workloads in isolated containers' (vercel-docs-12), implying full Node.js runtime support beyond a restricted Edge subset, but no evidence explicitly confirms unmodified Node.js APIs or full npm package compatibility in edge/serverless functions. Missing for 10: explicit documentation contrasting Node.js runtime vs restricted Edge Runtime, npm package compatibility guarantees, and independent verification of unmodified Node.js execution.
- [claimed-docs] “Run server-side code on demand with Fluid compute, which scales concurrency for AI and I/O-heavy workloads.”
- [claimed-docs] “Run production workloads in isolated containers on Vercel.”
- [claimed-docs] “Run untrusted code in secure, ephemeral execution environments.”
- [claimed-docs] “Run untrusted or agent-generated code in isolated, ephemeral execution environments.”
Railwayn/aRailway is a general container/service deployment platform (build from repo, deploy full services with CPU/RAM scaling), not an edge/serverless-functions product with a restricted runtime that this story presupposes; no evidence describes an edge-function runtime at all, restricted or otherwise, so the axis is a category mismatch rather than an unmet capability.
- [claimed-docs] “Railway is an all-in-one intelligent cloud provider that makes it easy to provision infrastructure, develop locally, and deploy to the cloud…”
- [claimed-docs] “Scale CPU and RAM or add replicas with load balancing.”
- [claimed-docs] “Run your application closer to where your users are.”
developerWrite edge functions in languages other than JavaScript such as Python, Go, or Rust
weight 2 · not comparableVercelnone0/10The evidence pack contains no vendor documentation claiming edge functions can be written in Python, Go, or Rust; all edge/runtime references are JS/TS-focused. A community comment explicitly complains that Vercel (and Netlify) only offer 'JS/TS/Go, or WebAssembly gimmicks,' reinforcing that non-JS edge language support is not a real, documented capability.
- [community] “"I dislike how Vercel and Netlify build up on AWS and then we only get JS/TS/Go, or WebAssembly gimmicks." — complaint about limited languag…”
Railwayn/aRailway is a general-purpose cloud deployment/hosting platform for full applications and services, not an edge-function/edge-compute product with a language-restricted runtime; the story's premise (writing edge functions in specific languages) is a category error for this product type.
devops-leadAttached disk/storage auto-grows with usage and I'm billed only for bytes actually written rather than pre-provisioned capacity
weight 2 · not comparableVerceln/aVercel is a serverless/PaaS deployment platform with ephemeral functions and edge/static hosting rather than a provider of attached block storage volumes for compute instances; the evidence pack shows no concept of 'attached disks' at all, only marketplace-integrated databases (e.g., Neon) which are a separate axis. This 'auto-growing disk with per-byte billing' story is a category mismatch for Vercel's architecture.
Railwaynone0/10The evidence pack contains no mention of persistent volumes, disk auto-scaling behavior, or usage-based storage billing (only general platform, deployment, and AI-agent features). This is a fair question for a cloud infra provider, but nothing in the pack confirms auto-grow disks or byte-metered storage pricing.
developerResize and optimize images on demand via a built-in image CDN
weight 1 · not comparableVercel's docs explicitly describe on-demand image resizing/conversion served from the CDN in modern formats, directly matching the story's requirements. Missing for 10: independent/hands-on corroboration beyond first-party docs and detail on caching/format negotiation specifics.
- [claimed-docs] “Resize and convert images on demand and serve them from the CDN in modern formats.”