Netlify vs Railway

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Railway
   Netlify✓fullprobed8/10

   A live probe confirms Netlify hosts an llms.txt at docs.netlify.com/llms.txt returning HTTP 200 with structured LLM-oriented documentation, directly satisfying the story. Missing for 10: no evidence of broader agent-oriented doc formats (e.g., per-page .md variants) or third-party confirmation that agents successfully consume it.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.netlify.com/llms.txt # LLM documentation for Netlify > Comprehensive documentation for the Netlify…”

   proof ↗⚑ flag

   Railway✓fullprobed9/10

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

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Netlify
   Netlify✓fullprobed8/10

   Netlify offers a documented CLI and REST API explicitly for automating workflows (deploy, dev servers, project management), plus anonymous/no-login deploy from CLI suitable for CI pipelines, and auto-deploy on push already implies CI-friendly headless operation. Missing for 10: no explicit CI-specific docs (e.g., GitHub Actions recipes) or independent confirmation of headless CI usage beyond docs/probes.

   • [claimed-docs] “Manage sites, deploys, DNS, and more programmatically with the Netlify REST API—ideal for automating workflows and integrating into your sys…”
   • [claimed-docs] “Deploy sites, run local dev servers, and manage your Netlify projects right from the terminal with this powerful command-line tool.”
   • [claimed-docs] “npm i -g netlify-cli netlify deploy --allow-anonymous”
   • [claimed-docs] “Auto-deploy on every push. Every PR gets a preview URL.”
   • [probe] “official CLI documented at https://docs.netlify.com/cli/get-started/”

   proof ↗⚑ flag

   Railway~partialprobed5/10

   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”

   proof ↗⚑ flag

3. ai-native userPlug MCP servers into this product so it can use their tools

   weight 3 · round to Railway
   Netlify—none0/10

   Netlify's docs mention AI Gateway for connecting to AI models and letting AI assistants connect to a Netlify account, but nothing describes Netlify itself acting as an MCP client that plugs in external MCP servers to use their tools. Missing for 10: any mention of MCP protocol/server support, or documentation of Netlify consuming third-party MCP tool servers.

   • [claimed-docs] “Share context & connect AI assistants to your Netlify account for seamless deployment workflows.”
   • [claimed-docs] “Connect to popular AI models within your project code and connect to them seamlessly without managing API keys.”
   • [claimed-docs] “Connect to AI models through AI Gateway”

   proof ↗⚑ flag

   Railway✓fullclaimed8/10

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

   proof ↗⚑ flag

4. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Railway
   Netlify—none0/10

   Docs mention connecting AI assistants and agents to Netlify (netlify-docs-21, netlify-docs-22) but never reference an official MCP server or the Model Context Protocol specifically, so there's no concrete evidence of an MCP server offering.

   • [claimed-docs] “Prompt AI agents to fix, update, and ship code using your unique project context directly from your Netlify dashboard.”
   • [claimed-docs] “Share context & connect AI assistants to your Netlify account for seamless deployment workflows.”

   proof ↗⚑ flag

   Railway✓fullclaimed8/10

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

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round to Railway
   Netlify✓fullprobed8/10

   Netlify ships a well-documented official CLI (netlify-cli) for deploys, local dev, and project management, confirmed by both docs and a live probe. missing for 10: independent hands-on community validation specifically of the CLI's AI-native/agentic use cases, and no evidence of AI-specific CLI commands beyond general deploy/dev tooling.

   • [claimed-docs] “npm i -g netlify-cli netlify deploy --allow-anonymous”
   • [claimed-docs] “Deploy sites, run local dev servers, and manage your Netlify projects right from the terminal with this powerful command-line tool.”
   • [probe] “official CLI documented at https://docs.netlify.com/cli/get-started/”

   proof ↗⚑ flag

   Railway✓fullprobed9/10

   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”

   proof ↗⚑ flag

6. ai-native userDrive the product through a documented public API

   weight 3 · round to Netlify
   Netlify✓fullprobed8/10

   Netlify documents a REST API for managing sites, deploys, DNS, etc. explicitly for 'automating workflows and integrating into your systems,' plus an official CLI wrapping it, and even an llms.txt for AI-native consumption. No formal OpenAPI spec was found at expected locations, slightly weakening machine-readability claims. missing for 10: discoverable OpenAPI/swagger spec, independent developer corroboration of API robustness.

   • [claimed-docs] “Manage sites, deploys, DNS, and more programmatically with the Netlify REST API—ideal for automating workflows and integrating into your sys…”
   • [claimed-docs] “Deploy sites, run local dev servers, and manage your Netlify projects right from the terminal with this powerful command-line tool.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.netlify.com/llms.txt # LLM documentation for Netlify > Comprehensive documentation for the Netlify…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.netlify.com/openapi.json, https://docs.netlify.com/swagger.json, https://docs.netlify.c…”
   • [probe] “official CLI documented at https://docs.netlify.com/cli/get-started/”

   proof ↗⚑ flag

   Railway~partialprobed6/10

   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…”

   proof ↗⚑ flag

7. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round drawn
   Netlify—none0/10

   Evidence shows Netlify manages access/secrets/env vars 'by team' and offers a REST API and CLI, but there is no mention of scoped or least-privilege API tokens/credentials specifically for AI agents — no granular permission scopes, no agent-specific credential issuance workflow.

   • [claimed-docs] “Manage access, secrets, and env vars by team”
   • [claimed-docs] “Manage sites, deploys, DNS, and more programmatically with the Netlify REST API—ideal for automating workflows and integrating into your sys…”
   • [claimed-docs] “Share context & connect AI assistants to your Netlify account for seamless deployment workflows.”

   proof ↗⚑ flag

   Railway—none0/10

   Evidence 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 …”

   proof ↗⚑ flag

8. ai-native userBuild against official SDKs

   weight 2 · round to Netlify
   Netlify✓fullprobed7/10

   Netlify provides an official SDK for building extensions/integrations, a REST API for programmatic control, and a CLI, plus an AI Gateway to connect AI models — all documented as first-party tooling that AI-native builders can target. Missing for 10: independent/hands-on corroboration of SDK usage by AI agents, and multi-language SDK examples beyond the extension SDK.

   • [claimed-docs] “Manage sites, deploys, DNS, and more programmatically with the Netlify REST API—ideal for automating workflows and integrating into your sys…”
   • [claimed-docs] “Deploy sites, run local dev servers, and manage your Netlify projects right from the terminal with this powerful command-line tool.”
   • [claimed-docs] “Build extensions and custom integrations with the Netlify SDK to enhance workflows, add UI components, and connect third-party services.”
   • [claimed-docs] “Connect to AI models through AI Gateway”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.netlify.com/llms.txt # LLM documentation for Netlify > Comprehensive documentation for the Netlify…”
   • [probe] “official CLI documented at https://docs.netlify.com/cli/get-started/”

   proof ↗⚑ flag

   Railway—none0/10

   Railway 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.”

   proof ↗⚑ flag

9. ai-native userSubscribe to events via webhooks

   weight 2 · round to Netlify
   Netlify~partialcommunity3/10

   The only evidence touching webhooks is a single community comment listing 'forms/webhooks' as a feature alongside other capabilities; there is no first-party doc describing a webhook subscription API, event types, or configuration for AI-native agentic workflows. Missing for 10: official docs on deploy/build event webhooks, subscription/configuration mechanism, and event payload schema.

   • [community] “Netlify is amazing: Free, good support, custom domains with SSL, forms/webhooks, zero-config Lambda functions, and simple redirect config - …”

   proof ↗⚑ flag

   Railway—none0/10

   The evidence mentions Slack/Discord/email alerts and an MCP server/agent integrations, but nowhere does it document a generic webhook subscription mechanism for external event consumption. No API or docs reference to 'webhooks' as a subscribable event feed is present.

   ⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round to Railway
   Netlify—none0/10

   Netlify's evidence covers AI Gateway for connecting to AI models, AI agents that fix/ship code, and analytics tracking, but there is no evidence of AI-generated insights or suggestions derived from a user's own data (e.g., analytics interpretation, usage recommendations) surfaced inside the product.

   ⚑ flag

   Railway~partialclaimed6/10

   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 …”

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to Railway
   Netlify~partialclaimed4/10

   Netlify supports event-driven automation (auto-deploy on every push, serverless functions, REST API for automating workflows) which can run without manual intervention, but there is no evidence of scheduled/cron jobs or persistent background agents that operate autonomously beyond deploy/build triggers. Missing for 10: explicit scheduled/cron function support, evidence of long-running or continuously monitoring background automations, and independent confirmation that such automations work reliably.

   • [claimed-docs] “Auto-deploy on every push. Every PR gets a preview URL.”
   • [claimed-docs] “Build APIs with serverless functions”
   • [claimed-docs] “Manage sites, deploys, DNS, and more programmatically with the Netlify REST API—ideal for automating workflows and integrating into your sys…”
   • [claimed-docs] “Prompt AI agents to fix, update, and ship code using your unique project context directly from your Netlify dashboard.”

   proof ↗⚑ flag

   Railway~partialclaimed6/10

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

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round to Railway
   Netlify~partialclaimed6/10

   Netlify's docs describe a built-in AI capability that lets users 'prompt AI agents to fix, update, and ship code using your unique project context directly from your Netlify dashboard' and connect AI assistants to the account for deployment workflows, indicating a delegated in-product AI assistant exists. However, evidence is limited to marketing-level docs with no detail on capabilities, limits, or hands-on/independent validation of how well it performs task delegation. Missing for 10: independent/community corroboration of the AI assistant working in practice, technical documentation of its scope and limitations, and concrete examples of delegated tasks being completed.

   • [claimed-docs] “Prompt AI agents to fix, update, and ship code using your unique project context directly from your Netlify dashboard.”
   • [claimed-docs] “Share context & connect AI assistants to your Netlify account for seamless deployment workflows.”
   • [claimed-docs] “Connect to popular AI models within your project code and connect to them seamlessly without managing API keys.”

   proof ↗⚑ flag

   Railway✓fullclaimed8/10

   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…”

   proof ↗⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round to Railway
   Netlify~partialprobed5/10

   Netlify offers AI-agent integration features (prompt AI agents to fix/update/ship code from the dashboard, connect AI assistants for deployment workflows) and an llms.txt for LLM-readable docs, suggesting some natural-language/agentic operation surface, but there's no evidence of a broad natural-language command interface (e.g., chat-driven CLI or conversational control of deploys, DNS, env vars). missing for 10: evidence of a general NL command interface across the product (not just AI agent code-fix prompts), independent/hands-on validation of the natural-language workflow actually working.

   • [claimed-docs] “Prompt AI agents to fix, update, and ship code using your unique project context directly from your Netlify dashboard.”
   • [claimed-docs] “Share context & connect AI assistants to your Netlify account for seamless deployment workflows.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.netlify.com/llms.txt # LLM documentation for Netlify > Comprehensive documentation for the Netlify…”

   proof ↗⚑ flag

   Railway✓fullclaimed8/10

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

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round drawn
   Netlify—none0/10

   There's a REST API and CLI documentation, but no evidence of an interactive API reference with runnable examples (e.g., API explorer, Swagger/OpenAPI UI, or embedded try-it console); the probe explicitly found no OpenAPI/swagger endpoints (404s across all candidates).

   • [claimed-docs] “Manage sites, deploys, DNS, and more programmatically with the Netlify REST API—ideal for automating workflows and integrating into your sys…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.netlify.com/openapi.json, https://docs.netlify.com/swagger.json, https://docs.netlify.c…”

   proof ↗⚑ flag

   Railway—none0/10

   No 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…”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   Netlify—none0/10

   Netlify documents a REST API and CLI but explicit probes for an OpenAPI/swagger spec at standard paths all returned 404, and no evidence pack item shows a downloadable machine-readable API spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.netlify.com/openapi.json, https://docs.netlify.com/swagger.json, https://docs.netlify.c…”
   • [claimed-docs] “Manage sites, deploys, DNS, and more programmatically with the Netlify REST API—ideal for automating workflows and integrating into your sys…”

   proof ↗⚑ flag

   Railway—none0/10

   The 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…”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round drawn
   Netlify~partialclaimed6/10

   Netlify's Deploy Previews and preview environments (per-PR preview URLs, shareable preview environments) provide isolated environments that don't touch production, and Netlify Database claims to let you 'safely iterate' on managed Postgres. However, none of this is framed specifically for AI-agent-driven testing or data isolation guarantees (e.g., branch databases, seeded test data), and there's no independent corroboration of preview data isolation. Missing for 10: explicit AI-agent-oriented sandbox/test-data isolation guarantees, database branching/reset mechanics, and independent verification that preview environments never touch production data.

   • [claimed-docs] “Auto-deploy on every push. Every PR gets a preview URL.”
   • [claimed-docs] “Share a customizable preview environment where you and key collaborators can preview content updates alongside code updates in real-time.”
   • [claimed-docs] “Review every change before it goes live with Deploy Previews”
   • [claimed-docs] “Deploy and safely iterate on managed Postgres with **Netlify Database**”

   proof ↗⚑ flag

   Railway~partialclaimed6/10

   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 …”

   proof ↗⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Netlify—none0/10

   There is evidence of a REST API and CLI, but no documentation of API versioning scheme or a deprecation policy; the probe explicitly found no OpenAPI spec at expected locations, and no evidence pack item mentions version numbers, sunset timelines, or changelog/deprecation notices.

   • [claimed-docs] “Manage sites, deploys, DNS, and more programmatically with the Netlify REST API—ideal for automating workflows and integrating into your sys…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.netlify.com/openapi.json, https://docs.netlify.com/swagger.json, https://docs.netlify.c…”

   proof ↗⚑ flag

   Railway—none0/10

   No 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…”

   proof ↗⚑ flag

5. developerThe documented rate limits and concurrency caps for APIs and functions so I can plan for scale

   weight 3 · round drawn
   Netlify—none0/10

   No evidence in the pack cites documented rate limits or concurrency caps for Netlify's APIs or serverless functions; billing/DDoS complaints (netlify-comm-1/2/3/15) discuss cost surprises, not documented limits/caps for capacity planning.

   ⚑ flag

   Railway—none0/10

   No 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…”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Netlify
   Netlify~partialprobed3/10

   Netlify's REST API and CLI are documented as generally 'ideal for automating workflows' across sites/deploys, which an AI-native user could script to perform bulk actions, but there is no explicit bulk-operation feature (e.g., batch deploy, bulk env-var update, multi-site actions) documented anywhere in the evidence. Missing for 10: any first-party bulk/batch endpoint or CLI command, documented multi-item automation examples, and independent confirmation of bulk workflows.

   • [claimed-docs] “Manage sites, deploys, DNS, and more programmatically with the Netlify REST API—ideal for automating workflows and integrating into your sys…”
   • [claimed-docs] “Deploy sites, run local dev servers, and manage your Netlify projects right from the terminal with this powerful command-line tool.”
   • [probe] “official CLI documented at https://docs.netlify.com/cli/get-started/”

   proof ↗⚑ flag

   Railway—none0/10

   Railway'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”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round drawn
   Netlify~partialcommunity5/10

   Netlify supports some automatic event-triggered actions (auto-deploy on push, PR previews, webhooks/forms, serverless functions triggered by requests, REST API for scripting workflows), but there is no documented general-purpose rules/trigger engine letting users define arbitrary custom event→action automations. Missing for 10: a dedicated automation/rules configuration UI or API for defining custom triggers-to-actions mappings beyond git push and forms, and independent evidence of such a system in use.

   • [claimed-docs] “Auto-deploy on every push. Every PR gets a preview URL.”
   • [claimed-docs] “Build APIs with serverless functions”
   • [claimed-docs] “Manage sites, deploys, DNS, and more programmatically with the Netlify REST API—ideal for automating workflows and integrating into your sys…”
   • [community] “Netlify is amazing: Free, good support, custom domains with SSL, forms/webhooks, zero-config Lambda functions, and simple redirect config - …”

   proof ↗⚑ flag

   Railway~partialclaimed5/10

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

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Netlify—none0/10

   No evidence of scheduled/cron functions or recurring workflow triggers; Netlify's evidence covers deploys, functions, forms, DB, and AI-assist features but nothing about scheduled/recurring job execution. missing for 10: scheduled functions/cron support, recurring workflow trigger docs, any mention of time-based automation.

   ⚑ flag

   Railway—none0/10

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

   ⚑ flag

4. ai-native userVersion, review, and roll back my automations

   weight 1 · round drawn
   Netlify✓fullcommunity7/10

   Netlify's deploy pipeline provides versioning via git-based deploys, review via Deploy Previews on every PR, and one-click rollback to any prior deploy, directly matching the version/review/rollback story for its core automation (site deploys); community feedback independently praises the PR preview workflow. Missing for 10: independent/hands-on confirmation of rollback specifically, and evidence extending versioning/rollback to other 'automations' like serverless functions or AI agent workflows beyond the site deploy itself.

   • [claimed-docs] “Roll back any deploy in one click”
   • [claimed-docs] “Review every change before it goes live with Deploy Previews”
   • [claimed-docs] “Auto-deploy on every push. Every PR gets a preview URL.”
   • [community] “I part run a non-profit site on Netlify and the experience is pretty great. The real killer bit for me has been their GitHub integration whe…”

   proof ↗⚑ flag

   Railway✓fullclaimed7/10

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

   proof ↗⚑ flag

Cli tooling

1. developerDeploy my project directly from the command line without using a web dashboard

   weight 2 · round to Netlify
   Netlify✓fullprobed9/10

   Netlify CLI docs explicitly support deploying from the terminal without dashboard, including anonymous/no-login deploys via `netlify deploy --allow-anonymous`, plus a full CLI reference for deploys, local dev, and site management. Missing for 10: independent hands-on confirmation of CLI deploy workflow beyond docs.

   • [claimed-docs] “Deploy directly from your working directory. No login required to start.”
   • [claimed-docs] “npm i -g netlify-cli netlify deploy --allow-anonymous”
   • [claimed-docs] “Deploy sites, run local dev servers, and manage your Netlify projects right from the terminal with this powerful command-line tool.”
   • [probe] “official CLI documented at https://docs.netlify.com/cli/get-started/”

   proof ↗⚑ flag

   Railway✓fullprobed8/10

   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”

   proof ↗⚑ flag

2. developerScaffold and deploy a new project with a single CLI command

   weight 2 · round to Netlify
   Netlify~partialprobed6/10

   Netlify CLI supports one-command deploy from a working directory without login (netlify deploy --allow-anonymous) and the CLI docs confirm deploying, running dev servers, and managing projects from the terminal, but there's no evidence of a 'scaffold' (project templating/initialization) step bundled into a single command. missing for 10: evidence of CLI-driven project scaffolding/templating, independent hands-on confirmation of the single-command flow working end-to-end.

   • [claimed-docs] “Deploy directly from your working directory. No login required to start.”
   • [claimed-docs] “npm i -g netlify-cli netlify deploy --allow-anonymous”
   • [claimed-docs] “Deploy sites, run local dev servers, and manage your Netlify projects right from the terminal with this powerful command-line tool.”
   • [probe] “official CLI documented at https://docs.netlify.com/cli/get-started/”

   proof ↗⚑ flag

   Railway~partialprobed5/10

   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”

   proof ↗⚑ flag

3. developerDevelop and test my app locally using a simulator that matches the production runtime

   weight 2 · round to Railway
   Netlify!disputedcontradicted4/10

   Netlify's CLI docs advertise 'run local dev servers' (netlify dev) as part of the CLI (netlify-docs-15, netlify-probe-3), which is the mechanism for simulating the production runtime locally, but a hands-on community report describes a concrete failure ('Unable to determine public folder for the dev server') with unclear config docs (netlify-comm-12), directly contradicting reliable parity with production. Missing for 10: detailed first-party documentation of how netlify dev emulates functions/redirects/edge runtime, and independent corroboration that this works smoothly in practice.

   • [claimed-docs] “Deploy sites, run local dev servers, and manage your Netlify projects right from the terminal with this powerful command-line tool.”
   • [probe] “official CLI documented at https://docs.netlify.com/cli/get-started/”
   • [community] “Netlify Dev gave an error: 'Unable to determine public folder for the dev server' with no clear docs on what to put in the [dev] section of …”

   proof ↗⚑ flag

   Railway~partialprobed3/10

   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”

   proof ↗⚑ flag

Deployment strategies

1. developerDeploy applications packaged as Docker containers

   weight 2 · round drawn
   Netlify—none0/10

   Netlify's evidence pack covers static site/JAMstack deploys, serverless functions, CLI, database, and integrations, but there is no mention of Docker container deployment or container registry support anywhere in the docs or community evidence.

   ⚑ flag

   Railway—none0/10

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

   ⚑ flag

2. devops-leadRoll out new deployments incrementally to reduce blast radius

   weight 2 · round to Netlify
   Netlify~partialclaimed3/10

   Netlify offers deploy previews for reviewing changes before going live and one-click rollback to a previous deploy, which reduce risk around releases, but there is no evidence of true incremental/staged rollout mechanisms like percentage-based traffic splitting or canary releases to limit blast radius. Missing for 10: canary/staged rollout support, percentage-based traffic shifting, gradual rollout automation, and any documentation framing deploys as incremental releases.

   • [claimed-docs] “Roll back any deploy in one click”
   • [claimed-docs] “Review every change before it goes live with Deploy Previews”
   • [claimed-docs] “Share a customizable preview environment where you and key collaborators can preview content updates alongside code updates in real-time.”

   proof ↗⚑ flag

   Railway—none0/10

   Evidence shows rollback, replicas/load balancing, and PR previews, but nothing describing incremental/canary/blue-green rollout strategies or traffic-shifting to limit blast radius during deploys.

   ⚑ flag

Git integration

1. developerAutomatically deploy my app on every Git push

   weight 3 · round drawn
   Netlify✓fullcommunity8/10

   Netlify's core value prop is documented auto-deploy on Git push with PR preview URLs, plus one-click rollback, corroborated by independent community reports praising GitHub integration and automated builds/deploys with PR preview builds working well in practice. Missing for 10: no first-party doc detail on configuring build settings/branch deploy rules, and some community friction with netlify.toml dev config shows minor rough edges.

   • [claimed-docs] “Auto-deploy on every push. Every PR gets a preview URL.”
   • [claimed-docs] “Roll back any deploy in one click”
   • [claimed-docs] “Review every change before it goes live with Deploy Previews”
   • [community] “Fantastic service. We've moved some of our SPA's out of our Heroku infrastructure and into Netlify. The GitHub/Slack integration, automated …”
   • [community] “I part run a non-profit site on Netlify and the experience is pretty great. The real killer bit for me has been their GitHub integration whe…”

   proof ↗⚑ flag

   Railway✓fullclaimed8/10

   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…”

   proof ↗⚑ flag

2. developerDeploy my app by simply connecting my repo without manual build configuration

   weight 3 · round drawn
   Netlify✓fullcommunity8/10

   Docs and community evidence confirm connect-repo auto-deploy with build detection, PR previews, and rollback, matching the zero-config repo-connect deploy workflow (netlify-docs-1, netlify-docs-25, netlify-docs-5). Community reviews corroborate the GitHub integration and automated builds working well in practice (netlify-comm-7, netlify-comm-10). Missing for 10: explicit documentation of automatic build-command/framework detection logic and independent hands-on confirmation that zero manual config is needed for varied frameworks.

   • [claimed-docs] “Auto-deploy on every push. Every PR gets a preview URL.”
   • [claimed-docs] “Review every change before it goes live with Deploy Previews”
   • [claimed-docs] “Roll back any deploy in one click”
   • [community] “Fantastic service. We've moved some of our SPA's out of our Heroku infrastructure and into Netlify. The GitHub/Slack integration, automated …”
   • [community] “I part run a non-profit site on Netlify and the experience is pretty great. The real killer bit for me has been their GitHub integration whe…”

   proof ↗⚑ flag

   Railway✓fullclaimed8/10

   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…”

   proof ↗⚑ flag

Infra as code

1. devops-leadDefine, deploy, and version my entire architecture with a single configuration file

   weight 2 · round to Railway
   Netlify—none0/10

   The evidence pack never documents netlify.toml (or any single manifest) as a way to declare an entire architecture (functions, redirects, headers, databases, DNS, envs) in one versioned file; the only reference to netlify.toml is a community complaint about unclear docs for its [dev] section (netlify-comm-12), not a confirmation of full-architecture-as-code capability. CLI and REST API docs (netlify-docs-14, netlify-docs-15) show operational tooling but not a single declarative config for the whole stack.

   • [community] “Netlify Dev gave an error: 'Unable to determine public folder for the dev server' with no clear docs on what to put in the [dev] section of …”
   • [claimed-docs] “Manage sites, deploys, DNS, and more programmatically with the Netlify REST API—ideal for automating workflows and integrating into your sys…”
   • [claimed-docs] “Deploy sites, run local dev servers, and manage your Netlify projects right from the terminal with this powerful command-line tool.”

   proof ↗⚑ flag

   Railway~partialclaimed4/10

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

   proof ↗⚑ flag

Manual deploy

1. 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 Netlify
   Netlify✓fullclaimed8/10

   Netlify's docs explicitly describe drag-and-drop folder deploys with no login/Git required (netlify-docs-2, netlify-docs-4) and CLI-based anonymous deploys (netlify-docs-3), plus explicit confirmation that new projects stay private until published (netlify-docs-4). Missing for 10: independent hands-on confirmation of the private-until-publish behavior and more detail on how/when publishing is triggered.

   • [claimed-docs] “Deploy directly from your working directory. No login required to start.”
   • [claimed-docs] “npm i -g netlify-cli netlify deploy --allow-anonymous”
   • [claimed-docs] “Drop your project folder and deploy in seconds. New projects stay private until you choose to publish.”

   proof ↗⚑ flag

   Railway—none0/10

   Evidence 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”

   proof ↗⚑ flag

Preview envs

1. developerGet ephemeral full-stack preview environments for every pull request

   weight 2 · round drawn
   Netlify✓fullcommunity8/10

   Netlify's Deploy Previews give every PR a full preview URL with backend features (functions, DB, env vars) tied to the branch, and this is corroborated by independent hands-on community testimony calling the PR preview integration a 'killer feature.' missing for 10: no explicit mention of ephemeral teardown/cleanup behavior or full-stack backend parity (e.g., preview-specific DB branching) in evidence.

   • [claimed-docs] “Auto-deploy on every push. Every PR gets a preview URL.”
   • [claimed-docs] “Review every change before it goes live with Deploy Previews”
   • [claimed-docs] “Share a customizable preview environment where you and key collaborators can preview content updates alongside code updates in real-time.”
   • [community] “I part run a non-profit site on Netlify and the experience is pretty great. The real killer bit for me has been their GitHub integration whe…”

   proof ↗⚑ flag

   Railway✓fullclaimed8/10

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

   proof ↗⚑ flag

2. developerGet an automatic preview URL for every pull request

   weight 3 · round to Netlify
   Netlify✓fullcommunity9/10

   Netlify's docs explicitly claim automatic Deploy Previews for every PR/push, and independent community testimony corroborates the GitHub PR preview builds as a standout feature. Missing for 10: no first-party technical deep-dive on preview URL configuration edge cases (e.g., monorepos) in this pack.

   • [claimed-docs] “Auto-deploy on every push. Every PR gets a preview URL.”
   • [claimed-docs] “Review every change before it goes live with Deploy Previews”
   • [claimed-docs] “Share a customizable preview environment where you and key collaborators can preview content updates alongside code updates in real-time.”
   • [community] “I part run a non-profit site on Netlify and the experience is pretty great. The real killer bit for me has been their GitHub integration whe…”

   proof ↗⚑ flag

   Railway✓fullclaimed8/10

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

   proof ↗⚑ flag

Rollback recovery

1. developerRoll back a deployed service to any previous version in one click

   weight 3 · round to Netlify
   Netlify✓fullclaimed8/10

   Netlify's own docs explicitly state one-click rollback to any previous deploy, directly matching the story, and this is corroborated by broader deploy-workflow evidence (deploy previews, auto-deploy per push). missing for 10: independent hands-on confirmation of the rollback feature specifically and details on any limitations (e.g., plan restrictions).

   • [claimed-docs] “Roll back any deploy in one click”
   • [claimed-docs] “Review every change before it goes live with Deploy Previews”
   • [claimed-docs] “Auto-deploy on every push. Every PR gets a preview URL.”

   proof ↗⚑ flag

   Railway~partialclaimed6/10

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

   proof ↗⚑ flag

Templates

1. developerDeploy one-click templates and starters for common use cases

   weight 1 · round to Railway
   Netlify~partialclaimed5/10

   Netlify's integrations directory shows starter templates for common use cases (Remix+Supabase, Angular bare-bones project, Clerk B2C auth template), indicating template-based quick deployment exists. However, none of the evidence explicitly describes a 'one-click deploy' button/flow or a dedicated templates gallery UI, and no independent/hands-on confirmation of the one-click experience is present. Missing for 10: explicit one-click 'Deploy to Netlify' button documentation, a dedicated templates marketplace/gallery, and community corroboration of the one-click flow working.

   • [claimed-docs] “The Remix Supabase starter demonstrates how to integrate Supabase into an Remix project deployed on Netlify.”
   • [claimed-docs] “This is a bare-bones Angular project that has everything you need to quickly deploy it to Netlify.”
   • [claimed-docs] “The Clerk B2C template on Netlify makes it simple to launch a production-ready B2C application with authentication and user management, that…”

   proof ↗⚑ flag

   Railway✓fullclaimed8/10

   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…”

   proof ↗⚑ flag

Environments

1. developerSpin up unlimited isolated environments so my whole team can ship simultaneously

   weight 1 · round to Railway
   Netlify~partialcommunity6/10

   Netlify supports Deploy Previews for every PR/branch and customizable preview environments for collaborators, which enables isolated environments per change so teams can work in parallel; community feedback corroborates PR preview builds as a standout feature. However, there's no explicit evidence of 'unlimited' environments, per-branch full-stack isolated dev environments (e.g., ephemeral backends/databases per branch), or scaling guarantees for large teams shipping simultaneously. missing for 10: explicit 'unlimited' environment claims, isolated backend/database-per-branch evidence, independent validation of scaling to large teams.

   • [claimed-docs] “Auto-deploy on every push. Every PR gets a preview URL.”
   • [claimed-docs] “Share a customizable preview environment where you and key collaborators can preview content updates alongside code updates in real-time.”
   • [claimed-docs] “Review every change before it goes live with Deploy Previews”
   • [community] “I part run a non-profit site on Netlify and the experience is pretty great. The real killer bit for me has been their GitHub integration whe…”

   proof ↗⚑ flag

   Railway✓fullclaimed8/10

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

   proof ↗⚑ flag

Scaling continuity

1. 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 Netlify
   Netlify~partialclaimed6/10

   Netlify's docs explicitly market a spectrum from zero-config prototype deploys (CLI deploy with no login) to enterprise-grade security 'at any scale' and templates claiming to scale to millions of users, implying the same core primitives (CLI, REST API, functions, database) work from small to large projects. However, there is no independent or hands-on evidence confirming large production deployments avoid rearchitecting, and cost-related community complaints about surprise scaling bills hint at friction once traffic grows. Missing for 10: case studies or technical benchmarks of large-scale production use on the same APIs, and independent confirmation that no migration/rearchitecture is needed at massive scale.

   • [claimed-docs] “Deploy directly from your working directory. No login required to start.”
   • [claimed-docs] “npm i -g netlify-cli netlify deploy --allow-anonymous”
   • [claimed-docs] “Secure your project at any scale—whether you need the security of a banking site with Netlify Advanced Security or simple password protectio…”
   • [claimed-docs] “The Clerk B2C template on Netlify makes it simple to launch a production-ready B2C application with authentication and user management, that…”
   • [claimed-docs] “Manage sites, deploys, DNS, and more programmatically with the Netlify REST API—ideal for automating workflows and integrating into your sys…”
   • [claimed-docs] “Deploy sites, run local dev servers, and manage your Netlify projects right from the terminal with this powerful command-line tool.”

   proof ↗⚑ flag

   Railway!disputedcontradicted4/10

   Railway'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.”

   proof ↗⚑ flag

Secrets management

1. devops-leadManage team-level access, secrets, and environment variables centrally

   weight 2 · round to Netlify
   Netlify~partialclaimed6/10

   Netlify explicitly claims team-level management of access, secrets, and env vars ([netlify-docs-8]), plus security/access controls at scale ([netlify-docs-18]) and a REST API/CLI for programmatic management ([netlify-docs-14], [netlify-docs-15]). However, there is no detailed documentation or independent/hands-on corroboration of the specifics (e.g., RBAC granularity, secret scoping, audit logs) beyond a single marketing line. Missing for 10: detailed docs on role-based permissions, audit logging, secret rotation, and independent verification of team-management workflows.

   • [claimed-docs] “Manage access, secrets, and env vars by team”
   • [claimed-docs] “Secure your project at any scale—whether you need the security of a banking site with Netlify Advanced Security or simple password protectio…”
   • [claimed-docs] “Manage sites, deploys, DNS, and more programmatically with the Netlify REST API—ideal for automating workflows and integrating into your sys…”
   • [claimed-docs] “Deploy sites, run local dev servers, and manage your Netlify projects right from the terminal with this powerful command-line tool.”

   proof ↗⚑ flag

   Railway~partialclaimed3/10

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

   proof ↗⚑ flag

Tool continuity

1. developerKeep using my existing Git, CI, editor, and framework workflows without adopting proprietary tooling

   weight 2 · round to Railway
   Netlify~partialcommunity6/10

   Netlify's evidence shows Git-based auto-deploys, PR previews, a CLI, REST API, and framework-agnostic integrations (Next.js, Gatsby, Remix, Svelte, Angular), supporting continued use of existing Git/framework workflows without lock-in, and community praise for GitHub integration/preview builds. However, there is no explicit evidence about compatibility with arbitrary existing CI pipelines (Netlify's own build system largely replaces CI) or editor-agnosticism, and one community report cites a CLI/dev-server config error suggesting friction. Missing for 10: explicit support for external CI systems, editor-agnostic workflow evidence, and resolution of CLI dev-server friction reports.

   • [claimed-docs] “Auto-deploy on every push. Every PR gets a preview URL.”
   • [claimed-docs] “Review every change before it goes live with Deploy Previews”
   • [claimed-docs] “Deploy sites, run local dev servers, and manage your Netlify projects right from the terminal with this powerful command-line tool.”
   • [claimed-docs] “Manage sites, deploys, DNS, and more programmatically with the Netlify REST API—ideal for automating workflows and integrating into your sys…”
   • [claimed-docs] “React CMS and visual editor for Next.js, Gatsby, and Remix”
   • [claimed-docs] “Versatile, open source framework for building web applications using Svelte components.”
   • [claimed-docs] “This is a bare-bones Angular project that has everything you need to quickly deploy it to Netlify.”
   • [community] “Fantastic service. We've moved some of our SPA's out of our Heroku infrastructure and into Netlify. The GitHub/Slack integration, automated …”
   • [community] “I part run a non-profit site on Netlify and the experience is pretty great. The real killer bit for me has been their GitHub integration whe…”
   • [community] “Netlify Dev gave an error: 'Unable to determine public folder for the dev server' with no clear docs on what to put in the [dev] section of …”

   proof ↗⚑ flag

   Railway~partialclaimed7/10

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

   proof ↗⚑ flag

Placement latency

1. devops-leadDeploy my application to specific regions closer to my users

   weight 2 · round to Railway
   Netlify—none0/10

   The evidence pack contains no mention of region selection, multi-region deployment, or edge location control for Netlify sites/functions—no docs or community reports address deploying to specific geographic regions closer to users. Missing for 10: any documentation of region-specific deployment configuration, edge function region pinning, or geographic deployment controls.

   ⚑ flag

   Railway~partialclaimed3/10

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

   proof ↗⚑ flag

2. devops-leadRely on automatic compute placement near backend data to optimize latency

   weight 2 · round to Railway
   Netlify—none0/10

   No evidence describes automatic compute placement near backend data or latency-optimizing region selection for functions/edge compute; only generic serverless functions and database integration mentions appear (netlify-docs-6, netlify-docs-13, netlify-intdir-5) without any placement/latency logic.

   ⚑ flag

   Railway~partialclaimed3/10

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

   proof ↗⚑ flag

Sandboxing

1. developerRun untrusted code in hardware-isolated, disposable sandboxes

   weight 2 · round drawn
   Netlify—none0/10

   Evidence covers deploys, serverless functions, previews, and integrations but contains no mention of hardware-isolated sandboxes, VM-level isolation, or disposable sandbox execution for running untrusted code; this is a legitimate edge-compute question for a platform like Netlify but no supporting evidence exists.

   ⚑ flag

   Railway—none0/10

   Railway'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 …”

   proof ↗⚑ flag

Scaling

1. devops-leadDeploy instances that boot in under a second and scale to tens of thousands under load

   weight 2 · round drawn
   Netlify—none0/10

   Netlify's docs mention serverless functions, automatic HTTPS/DDoS protection, and scaling for teams, but there is no evidence of specific boot-time (sub-second cold start) or explicit scale metrics (tens of thousands of concurrent instances) claims. Community evidence even highlights uncontrolled scaling causing massive surprise DDoS bills, which is orthogonal to the performance claim itself. missing for 10: cold-start latency data, explicit scale/throughput benchmarks, autoscaling architecture details.

   • [claimed-docs] “Build APIs with serverless functions”
   • [claimed-docs] “Automatic HTTPS and DDoS protection”
   • [community] “Netlify just sent me a $104k bill for a simple static site after a DDoS; they offered a discount to 5%, still $5k.”
   • [community] “This is a known issue... Netlify's response boils down to, 'if you're hosting a small site that gets DDoS'd, don't.'”

   proof ↗⚑ flag

   Railway—none0/10

   Railway'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…”

   proof ↗⚑ flag

2. devops-leadRely on load-based autoscaling to absorb large traffic bursts automatically

   weight 2 · round to Netlify
   Netlify~partialcommunity3/10

   Netlify's docs mention 'Automatic HTTPS and DDoS protection' and serverless functions, implying some infrastructure elasticity, but there is no explicit claim or documentation of load-based autoscaling for traffic bursts. Community reports (e.g., a $104k bill after a DDoS) suggest that while traffic was absorbed, the cost and reliability experience for large bursts was problematic, undermining confidence in seamless autoscaling. missing for 10: explicit autoscaling architecture docs, capacity/burst guarantees, independent benchmark or case study showing successful large-scale traffic absorption.

   • [claimed-docs] “Automatic HTTPS and DDoS protection”
   • [community] “Netlify just sent me a $104k bill for a simple static site after a DDoS; they offered a discount to 5%, still $5k.”
   • [community] “This is a known issue... Netlify's response boils down to, 'if you're hosting a small site that gets DDoS'd, don't.'”

   proof ↗⚑ flag

   Railway—none0/10

   Docs 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.”

   proof ↗⚑ flag

Serverless runtime

1. developerRun my code on a global edge network close to end users

   weight 3 · round to Netlify
   Netlify~partialclaimed3/10

   Evidence only indirectly implies Netlify Edge Functions exist via a third-party integration blurb ('Turso... brings your data close to your edge functions') rather than first-party documentation describing a global edge-compute network for running developer code. Serverless functions (netlify-docs-6) are mentioned but that's origin/regional compute, not edge. Missing for 10: first-party docs on Edge Functions architecture/global PoPs, performance benchmarks, or independent hands-on confirmation of edge execution.

   • [claimed-docs] “Turso is the Edge database that brings your data close to your edge functions. Develop locally and deploy globally with the developer experi…”
   • [claimed-docs] “Build APIs with serverless functions”

   proof ↗⚑ flag

   Railway!disputedcontradicted4/10

   Railway'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…”

   proof ↗⚑ flag

2. developerDeploy serverless functions and full-stack apps with no servers to manage

   weight 3 · round to Netlify
   Netlify✓fullcommunity8/10

   Netlify's docs explicitly support serverless functions (netlify-docs-6), instant databases/file storage (netlify-docs-23, netlify-docs-13, netlify-docs-12), auto-deploys with no server management (netlify-docs-1,2,4), plus HTTPS/DDoS protection and rollback, matching the 'no servers to manage' full-stack story. Community evidence corroborates real-world use for SPA and function-based deploys (netlify-comm-7, netlify-comm-8). missing for 10: independent hands-on validation of serverless function scaling/limits and more detail on full-stack (SSR) app support beyond marketing copy.

   • [claimed-docs] “Build APIs with serverless functions”
   • [claimed-docs] “Add instant databases and file storage”
   • [claimed-docs] “Deploy and safely iterate on managed Postgres with **Netlify Database**”
   • [claimed-docs] “const uploads = getStore("file-uploads");”
   • [claimed-docs] “Auto-deploy on every push. Every PR gets a preview URL.”
   • [claimed-docs] “Drop your project folder and deploy in seconds. New projects stay private until you choose to publish.”
   • [claimed-docs] “Automatic HTTPS and DDoS protection”
   • [community] “Fantastic service. We've moved some of our SPA's out of our Heroku infrastructure and into Netlify. The GitHub/Slack integration, automated …”
   • [community] “Netlify is amazing: Free, good support, custom domains with SSL, forms/webhooks, zero-config Lambda functions, and simple redirect config - …”

   proof ↗⚑ flag

   Railway~partialclaimed6/10

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

   proof ↗⚑ flag

Workflows

1. developerDeploy durable, long-running workflows as code without manually wiring queues and retries

   weight 2 · round drawn
   Netlify—none0/10

   Netlify's evidence covers serverless functions, edge functions, databases, storage, and CI/CD deploy previews, but there is no mention of a durable/long-running workflow orchestration primitive (e.g., background jobs with built-in retries, queues, or workflow-as-code) comparable to Vercel's workflow/queue offerings. Functions are described as short-lived serverless invocations, not durable workflows.

   • [claimed-docs] “Build APIs with serverless functions”
   • [claimed-docs] “Add instant databases and file storage”
   • [claimed-docs] “Deploy and safely iterate on managed Postgres with **Netlify Database**”

   proof ↗⚑ flag

   Railway—none0/10

   Railway'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.”

   proof ↗⚑ flag

Access control

1. developerPut simple password protection on a deployed site without standing up a custom auth system

   weight 2 · round to Netlify
   Netlify~partialclaimed6/10

   Docs explicitly mention 'simple password protection for a personal portfolio site' as a built-in security option distinct from Advanced Security, directly matching the story. However, there's no detailed documentation snippet showing setup steps, no independent/hands-on confirmation of this feature working, and no mention of limitations (e.g., plan tier requirements). Missing for 10: setup documentation detail, independent verification, plan/tier restrictions.

   • [claimed-docs] “Secure your project at any scale—whether you need the security of a banking site with Netlify Advanced Security or simple password protectio…”

   proof ↗⚑ flag

   Railway—none0/10

   No evidence pack item mentions password protection, basic auth, or any simple access-gating feature for deployed sites; only general deployment, networking, and AI-agent features are documented.

   ⚑ flag

Bot protection

1. developerProtect my app from automated bot traffic with invisible challenge-based protection

   weight 1 · round drawn
   Netlify—none0/10

   Evidence shows generic 'Automatic HTTPS and DDoS protection' and 'Advanced Security' mentions but nothing about invisible challenge-based bot protection (e.g., CAPTCHA-free bot challenges, proof-of-work verification). No documentation or hands-on evidence confirms this specific capability.

   • [claimed-docs] “Automatic HTTPS and DDoS protection”
   • [claimed-docs] “Secure your project at any scale—whether you need the security of a banking site with Netlify Advanced Security or simple password protectio…”

   proof ↗⚑ flag

   Railway—none0/10

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

   ⚑ flag

Ddos waf

1. devops-leadHave DDoS protection and a web application firewall applied to every request by default

   weight 3 · round to Netlify
   Netlify!disputedcontradicted4/10

   Netlify's docs claim automatic DDoS protection and offer 'Advanced Security' for WAF-like protections, but there's no evidence that a WAF is applied to every request by default (Advanced Security appears to be a separate, presumably paid, tier). Concrete hands-on community evidence directly contradicts the DDoS protection claim: a user was billed ~$104k after a DDoS attack on a simple static site, and Netlify's official response was reportedly 'if you're hosting a small site that gets DDoS'd, don't,' indicating the protection does not shield customers from cost/impact as implied. missing for 10: evidence of a WAF applied by default to all requests, and evidence that DDoS protection actually blocks/absorbs attacks without cost exposure.

   • [claimed-docs] “Automatic HTTPS and DDoS protection”
   • [claimed-docs] “Secure your project at any scale—whether you need the security of a banking site with Netlify Advanced Security or simple password protectio…”
   • [community] “Netlify just sent me a $104k bill for a simple static site after a DDoS; they offered a discount to 5%, still $5k.”
   • [community] “This is a known issue... Netlify's response boils down to, 'if you're hosting a small site that gets DDoS'd, don't.'”

   proof ↗⚑ flag

   Railway—none0/10

   Evidence 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.”

   proof ↗⚑ flag

Domains

1. developerAttach custom domains to my deployed services

   weight 2 · round to Netlify
   Netlify✓fullcommunity8/10

   Netlify docs explicitly describe custom domain management, including adding unique custom domains per project version, plus automatic HTTPS, and community reviews corroborate 'custom domains with SSL' as a delivered feature. Missing for 10: independent hands-on walkthrough of the domain-attachment flow and DNS configuration details beyond a single doc line.

   • [claimed-docs] “Simplify domain management for your projects and add unique custom domains for different versions of your project.”
   • [claimed-docs] “Automatic HTTPS and DDoS protection”
   • [community] “Netlify is amazing: Free, good support, custom domains with SSL, forms/webhooks, zero-config Lambda functions, and simple redirect config - …”

   proof ↗⚑ flag

   Railway—none0/10

   The 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.”

   proof ↗⚑ flag

2. developerProgrammatically provision and route custom domains for my own multi-tenant SaaS customers

   weight 2 · round to Netlify
   Netlify~partialclaimed5/10

   Netlify's REST API explicitly supports managing sites, deploys, and DNS programmatically, and docs mention adding unique custom domains per project version, which could underpin per-tenant domain routing. However, there's no explicit documentation or example showing multi-tenant SaaS customer domain provisioning workflows (e.g., bulk domain API endpoints, automated SSL issuance per tenant, ownership verification flows). Missing for 10: explicit multi-tenant custom domain API docs, tenant-scoped domain automation examples, and independent/hands-on confirmation of this specific use case.

   • [claimed-docs] “Manage sites, deploys, DNS, and more programmatically with the Netlify REST API—ideal for automating workflows and integrating into your sys…”
   • [claimed-docs] “Simplify domain management for your projects and add unique custom domains for different versions of your project.”
   • [claimed-docs] “Automatic HTTPS and DDoS protection”

   proof ↗⚑ flag

   Railway—none0/10

   Railway'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…”

   proof ↗⚑ flag

Env isolation

1. devops-leadIsolate non-production environments from accessing production services

   weight 1 · round to Netlify
   Netlify~partialclaimed3/10

   Netlify offers per-team env var/secrets management and separate preview environments for PRs, which provide some separation between non-prod and prod configs, but there is no documented network-level isolation (e.g., VPC/firewall rules preventing preview deploys from reaching production backends). missing for 10: explicit network/service-level isolation controls, documented access restrictions from preview/staging to production APIs, independent verification of isolation guarantees.

   • [claimed-docs] “Manage access, secrets, and env vars by team”
   • [claimed-docs] “Share a customizable preview environment where you and key collaborators can preview content updates alongside code updates in real-time.”

   proof ↗⚑ flag

   Railway—none0/10

   Evidence 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.”

   proof ↗⚑ flag

Identity

1. devops-leadSecure internal apps, deployments, and agents using my organization's identity provider

   weight 2 · round drawn
   Netlify—none0/10

   The evidence pack mentions team-based access/secrets management and generic 'Advanced Security' or password protection, but contains no mention of SSO, SAML, OIDC, or integration with an external identity provider (e.g., Okta, Azure AD) for securing apps, deployments, or agents. This is a reasonable axis for an enterprise deployment platform, but no supporting evidence exists.

   • [claimed-docs] “Manage access, secrets, and env vars by team”
   • [claimed-docs] “Secure your project at any scale—whether you need the security of a banking site with Netlify Advanced Security or simple password protectio…”

   proof ↗⚑ flag

   Railway—none0/10

   No evidence in the pack mentions SSO, SAML, OIDC, or any identity-provider integration for securing internal apps, deployments, or agents; coverage is limited to deployment, scaling, monitoring, and AI-agent features unrelated to IdP-based access control.

   ⚑ flag

Tls certs

1. devops-leadGet free, automatically renewing TLS certificates for every domain including wildcards

   weight 3 · round to Netlify
   Netlify~partialcommunity6/10

   Netlify's docs explicitly promise 'Automatic HTTPS' as a core platform feature, and community reviews confirm 'custom domains with SSL' works in practice, supporting the free/auto-renewing TLS claim. However, there is no explicit documentation confirming wildcard domain certificate support, and one community anecdote (netlify-comm-6) mentions a customer hitting cert errors that required manual support intervention rather than fully automatic resolution. missing for 10: explicit wildcard-domain TLS documentation, independent verification of automatic renewal behavior at scale.

   • [claimed-docs] “Automatic HTTPS and DDoS protection”
   • [community] “Netlify service is ridiculously awesome. I host my site there for free and had some cert errors; I messaged support and they had it fixed in…”
   • [community] “Netlify is amazing: Free, good support, custom domains with SSL, forms/webhooks, zero-config Lambda functions, and simple redirect config - …”

   proof ↗⚑ flag

   Railway~partialclaimed3/10

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

   proof ↗⚑ flag

Alerting

1. devops-leadSet up alerts that notify me via chat or email when specific conditions are met

   weight 2 · round to Railway
   Netlify—none0/10

   No evidence pack items mention configurable alerting/notification rules for conditions (e.g., deploy failures, performance thresholds) delivered via chat or email; only analytics tracking and generic Discord community links are mentioned, not an alerting system.

   ⚑ flag

   Railway✓fullclaimed7/10

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

   proof ↗⚑ flag

Metrics dashboards

1. devops-leadBuild custom dashboards combining metrics from any service

   weight 2 · round to Railway
   Netlify—none0/10

   Netlify provides its own analytics on deploys/traffic (netlify-docs-17) and a REST API for automation, but there is no evidence of custom dashboarding that combines metrics from arbitrary external services (e.g., no Grafana/Datadog-style dashboard builder or multi-source metrics aggregation). This is a fair ask for a devops-facing platform, but nothing in the evidence shows it.

   • [claimed-docs] “Track your project's performance with every deployment and understand your Netlify team's behavior and the behavior of visitors to your site…”
   • [claimed-docs] “Manage sites, deploys, DNS, and more programmatically with the Netlify REST API—ideal for automating workflows and integrating into your sys…”

   proof ↗⚑ flag

   Railway~partialclaimed6/10

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

   proof ↗⚑ flag

2. devops-leadTrack site performance and visitor behavior with built-in analytics

   weight 1 · round to Netlify
   Netlify~partialclaimed6/10

   netlify-docs-17 explicitly claims tracking of project performance and visitor/team behavior analytics, directly matching the story, but there is no further first-party detail on dashboards, metrics depth, or independent/hands-on corroboration of the analytics feature itself. Missing for 10: detailed documentation of specific analytics metrics/dashboards, independent hands-on validation, and confirmation of real-time or historical performance tracking capabilities.

   • [claimed-docs] “Track your project's performance with every deployment and understand your Netlify team's behavior and the behavior of visitors to your site…”

   proof ↗⚑ flag

   Railway—none0/10

   Railway'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.”

   proof ↗⚑ flag

Reliability sla

1. devops-leadCheck a public status page with historical incident postmortems before committing

   weight 2 · round drawn
   Netlify—none0/10

   No evidence pack item references a public status page, uptime history, or postmortem archive for Netlify; only product docs and unrelated community sentiment are present.

   ⚑ flag

   Railway—none0/10

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

   ⚑ flag

2. devops-leadReview a published uptime SLA with defined credits for downtime

   weight 3 · round drawn
   Netlify—none0/10

   No evidence pack item references an SLA document, uptime guarantee, or downtime credit policy; only general reliability/DDoS billing complaints appear, which are off-topic to a published SLA. Missing for 10: a published SLA page, defined uptime percentage, and credit schedule for downtime.

   ⚑ flag

   Railway—none0/10

   No 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.”

   proof ↗⚑ flag

3. devops-leadThe guaranteed support response times and escalation paths for my plan tier

   weight 2 · round drawn
   Netlify—none0/10

   No evidence in the pack documents SLA-backed support response times or escalation paths per plan tier; only anecdotal community reports of ad-hoc support turnaround (e.g., a cert fix within 48 hrs) exist, not guaranteed contractual response times or escalation processes.

   • [community] “Netlify service is ridiculously awesome. I host my site there for free and had some cert errors; I messaged support and they had it fixed in…”

   proof ↗⚑ flag

   Railway—none0/10

   No evidence describes SLA-backed support response times, escalation paths, or plan-tier support guarantees; evidence only covers product features, community outage complaints, and AI tooling.

   ⚑ flag

Unified logging

1. developerView all my build, deploy, and runtime logs in one place

   weight 3 · round to Railway
   Netlify—none0/10

   The evidence pack references analytics and performance tracking (netlify-docs-17) but never describes a unified view combining build, deploy, and runtime logs; no docs or community evidence confirm a consolidated logging dashboard. missing for 10: explicit docs on build logs, deploy logs, and function/runtime logs being viewable together, any UI screenshot or dashboard reference, community confirmation of log consolidation.

   • [claimed-docs] “Track your project's performance with every deployment and understand your Netlify team's behavior and the behavior of visitors to your site…”

   proof ↗⚑ flag

   Railway✓fullclaimed7/10

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

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Netlify
   Netlify~partialprobed6/10

   Netlify documents a REST API for managing sites, deploys, DNS, etc. plus a CLI that wraps much of the same functionality, suggesting broad API/UI parity for core deployment workflows. However, there's no evidence of a public OpenAPI spec (probe returned 404s for all candidates), and no confirmation that newer dashboard-only features (e.g., AI agent prompting from dashboard, Netlify Database management, image resizing, forms/lead collection) are fully exposed via API. missing for 10: OpenAPI/spec discoverability, explicit API coverage for newer UI-only features like AI agent prompting and Database management, independent confirmation of full API-UI parity.

   • [claimed-docs] “Manage sites, deploys, DNS, and more programmatically with the Netlify REST API—ideal for automating workflows and integrating into your sys…”
   • [claimed-docs] “Deploy sites, run local dev servers, and manage your Netlify projects right from the terminal with this powerful command-line tool.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.netlify.com/openapi.json, https://docs.netlify.com/swagger.json, https://docs.netlify.c…”
   • [probe] “official CLI documented at https://docs.netlify.com/cli/get-started/”
   • [claimed-docs] “Prompt AI agents to fix, update, and ship code using your unique project context directly from your Netlify dashboard.”
   • [claimed-docs] “Deploy and safely iterate on managed Postgres with **Netlify Database**”

   proof ↗⚑ flag

   Railway~partialprobed4/10

   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…”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round drawn
   Netlify—none0/10

   Evidence shows Netlify's REST API and CLI for managing sites/deploys/DNS, but nothing documents an explicit data-export feature or open-format guarantee for Netlify Database contents, Forms submissions, Blobs/file storage, or env vars that would let a user fully extract their data and leave.

   ⚑ flag

   Railway—none0/10

   Railway'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”

   proof ↗⚑ flag

3. ai-native userRead the product's source under an open license

   weight 2 · round drawn
   Netlify—none0/10

   Netlify is a proprietary SaaS platform; no evidence indicates its core source code is available under an open license (CLI is separately open-source but the platform itself is not, and no license is cited).

   ⚑ flag

   Railway—none0/10

   No evidence that Railway's source code is open-licensed or publicly available; Railway is a closed proprietary cloud platform with only docs/CLI/API references, none pointing to an open-source repo or license.

   ⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round drawn
   Netlify—none0/10

   Netlify is a proprietary, fully-managed hosting/deploy platform; no evidence of an open-source self-hostable core or self-hosting instructions exists in the evidence pack, and one community comment even frames Netlify as the alternative to self-hosting. This is an applicable axis (many dev-tool platforms could offer OSS self-hosted editions) but no evidence supports it, so it is 'none' not 'na'.

   • [community] “I would choose Heroku or Netlify because I don't want to self host it. I want someone else to manage all those bits for me.”

   proof ↗⚑ flag

   Railway—none0/10

   Railway 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…”

   proof ↗⚑ flag

Cost controls

1. devops-leadSet hard spending limits to control my cloud costs

   weight 2 · round to Railway
   Netlify—none0/10

   No documentation anywhere mentions a hard spend-limit or budget-cap feature; instead community reports (netlify-comm-1, netlify-comm-2, netlify-comm-15) describe customers receiving unexpectedly massive bills after traffic spikes/DDoS with no cap in place, and Netlify's response was to suggest not hosting small sites rather than offering a spending limit.

   • [community] “Netlify just sent me a $104k bill for a simple static site after a DDoS; they offered a discount to 5%, still $5k.”
   • [community] “This is a known issue... Netlify's response boils down to, 'if you're hosting a small site that gets DDoS'd, don't.'”
   • [community] “Waking up to a 10k Vercel bill is pretty common, especially when a DDoS goes undetected - similar cost-overrun complaints apply across Netli…”

   proof ↗⚑ flag

   Railway~partialclaimed5/10

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

   proof ↗⚑ flag

2. devops-leadReceive migration credits when moving my production infrastructure to a new platform

   weight 1 · round drawn
   Netlify—none0/10

   No evidence of a migration-credits program or any incentive for moving production infrastructure from another platform; evidence only covers general product features and unrelated billing complaints.

   ⚑ flag

   Railway—none0/10

   Railway 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”

   proof ↗⚑ flag

Execution limits

1. 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 drawn
   Netlify—none0/10

   No evidence pack item specifies actual CPU or wall-clock execution time limits for Netlify Functions; docs only mention 'serverless functions' generically without documenting timeout/CPU constraints.

   ⚑ flag

   Railway—none0/10

   Railway'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.”

   proof ↗⚑ flag

Overage fees

1. devops-leadThe exact overage fee schedule for exceeding plan usage limits (bandwidth, invocations, build minutes) before I get billed

   weight 3 · round drawn
   Netlify—none0/10

   No evidence pack item documents an explicit overage fee schedule for bandwidth, invocations, or build minutes; the only related evidence is community reports of unexpected surprise bills (e.g., a $104k DDoS bill) rather than any published fee table. missing for 10: a documented overage pricing table, per-unit fee schedule, or billing calculator referenced in official docs.

   • [community] “Netlify just sent me a $104k bill for a simple static site after a DDoS; they offered a discount to 5%, still $5k.”
   • [community] “This is a known issue... Netlify's response boils down to, 'if you're hosting a small site that gets DDoS'd, don't.'”
   • [community] “Waking up to a 10k Vercel bill is pretty common, especially when a DDoS goes undetected - similar cost-overrun complaints apply across Netli…”

   proof ↗⚑ flag

   Railway—none0/10

   The 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.”

   proof ↗⚑ flag

2. devops-leadWhether pricing is per-seat with minimum seat counts that increase cost as my team grows

   weight 2 · round drawn
   Netlify—none0/10

   The evidence pack contains no official pricing-page or plan documentation describing seat-based tiers or minimum seat counts; the only related signal is a community complaint that Netlify 'tried charging per user on a documentation site repo,' which is anecdotal and not a documented pricing structure. Another community comment (netlify-comm-13) explicitly states pricing information is hard to find at all, reinforcing that no clear evidence exists to confirm or deny a per-seat minimum-seat pricing model.

   • [community] “Netlify has implemented all these customer-hostile billing changes. I migrated my company's site off of Netlify when they tried charging per…”
   • [community] “I could not find pricing anywhere for Netlify, and the 'ROI calculator' pushed me to enter name/email/phone just to learn the basics - still…”

   proof ↗⚑ flag

   Railway—none0/10

   No evidence pack items discuss Railway's pricing model, seat-based pricing, or per-seat minimums; all docs focus on features and AI agent tooling. Absence of any pricing/seat-cost evidence for an applicable axis means this cannot be verified.

   ⚑ flag

Usage billing

1. devops-leadPay only for active compute time rather than idle wall-clock time

   weight 2 · round to Netlify
   Netlify~partialclaimed3/10

   Netlify's serverless Functions (netlify-docs-6) imply pay-per-invocation compute rather than idle wall-clock billing, but there is no explicit pricing documentation stating that compute is billed only for active execution time versus idle time. Community billing complaints focus on bandwidth/DDoS overages, not on compute-vs-idle billing specifically, so they don't directly contradict this claim but do show unpredictable costs. Missing for 10: explicit pricing docs on function/compute billing granularity, independent confirmation that idle time is never charged.

   • [claimed-docs] “Build APIs with serverless functions”

   proof ↗⚑ flag

   Railway—none0/10

   The 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.”

   proof ↗⚑ flag

2. devops-leadAttached disk/storage auto-grows with usage and I'm billed only for bytes actually written rather than pre-provisioned capacity

   weight 2 · round drawn
   Netlify—none0/10

   Netlify does offer storage-adjacent products (Blobs, 'Netlify Database' managed Postgres) that could in principle have auto-grow/pay-per-byte billing, so the axis is not entirely foreign to the product category. However, the evidence pack contains no documentation about disk auto-scaling behavior or a bytes-written billing model for these storage features—only generic marketing mentions ('Add instant databases and file storage', 'Deploy and safely iterate on managed Postgres'). Community evidence instead highlights unpredictable, capacity-unrelated billing surprises (bandwidth/DDoS overage bills), which is off-topic to this specific disk-storage billing claim.

   • [claimed-docs] “Deploy and safely iterate on managed Postgres with **Netlify Database**”
   • [claimed-docs] “Add instant databases and file storage”

   proof ↗⚑ flag

   Railway—none0/10

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

   ⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round to Railway
   Netlify—none0/10

   No evidence in the pack mentions data residency, region selection, or storage location controls for Netlify projects/data; the only geographic-adjacent items are about CDN/DDoS protection, not user-selectable data residency. missing for 10: any documentation of region/residency selection, data storage location controls, or compliance certifications (e.g., GDPR data locality) that would let a user choose where data is stored.

   ⚑ flag

   Railway~partialclaimed3/10

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

   proof ↗⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round drawn
   Netlify—none0/10

   No evidence in the pack addresses AI-training data opt-out or data-usage policies for AI model training; Netlify's docs mention AI Gateway/model connections but nothing about preventing customer data from being used to train models.

   ⚑ flag

   Railway—none0/10

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

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Netlify—none0/10

   No evidence in the pack addresses data retention policies, deletion controls, or AI-specific data handling settings for Netlify; the evidence covers deployment, hosting, integrations, and unrelated billing complaints.

   ⚑ flag

   Railway—none0/10

   No 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?”

   proof ↗⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Netlify—none0/10

   No evidence in the pack addresses telemetry/usage tracking opt-out settings for Netlify's CLI, dashboard, or AI features; nothing documents a privacy control of this kind.

   ⚑ flag

   Railway—none0/10

   No evidence pack item addresses telemetry, usage tracking, or an opt-out mechanism for Railway's CLI, dashboard, or AI features; the axis is applicable (a dev platform could ship telemetry opt-out) but nothing documents it.

   ⚑ flag

Cdn assets

1. developerServe static assets faster using a global CDN with edge caching

   weight 2 · round drawn
   Netlify—none0/10

   The evidence pack contains no explicit claim about a global CDN or edge caching for static assets — mentions are limited to HTTPS/DDoS protection, deploy previews, and edge functions used by third-party integrations, none of which document CDN-based asset delivery speed. Missing for 10: explicit CDN/edge-caching documentation, performance benchmarks, or first-party claims about global asset distribution.

   • [claimed-docs] “Automatic HTTPS and DDoS protection”

   proof ↗⚑ flag

   Railway—none0/10

   No 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.”

   proof ↗⚑ flag

Integrations

1. 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 Netlify
   Netlify~partialclaimed6/10

   Netlify provides native bindings for common services—managed Postgres via Netlify Database, Blob Storage (getStore for file uploads), AI Gateway for connecting to AI models without managing API keys, and an integrations directory with pre-built connectors (Turso, Supabase, Algolia, etc.)—reducing boilerplate for common data/API needs. However, these are curated first-party primitives rather than a general-purpose native binding system for arbitrary external services, and there's no independent/hands-on evidence validating ease-of-use claims. Missing for 10: broader native binding coverage beyond Netlify's own curated services, independent developer corroboration of 'minimal boilerplate' claims, and detail on credential/secret management specifics for third-party bindings.

   • [claimed-docs] “Deploy and safely iterate on managed Postgres with **Netlify Database**”
   • [claimed-docs] “const uploads = getStore("file-uploads");”
   • [claimed-docs] “Add instant databases and file storage”
   • [claimed-docs] “Connect to popular AI models within your project code and connect to them seamlessly without managing API keys.”
   • [claimed-docs] “Turso is the Edge database that brings your data close to your edge functions. Develop locally and deploy globally with the developer experi…”
   • [claimed-docs] “The Remix Supabase starter demonstrates how to integrate Supabase into an Remix project deployed on Netlify.”
   • [claimed-docs] “The Clerk B2C template on Netlify makes it simple to launch a production-ready B2C application with authentication and user management, that…”

   proof ↗⚑ flag

   Railway~partialclaimed4/10

   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…”

   proof ↗⚑ flag

Kv cache

1. developerUse a Redis-compatible key-value store for low-latency caching and job queues

   weight 2 · round drawn
   Netlify—none0/10

   Netlify offers Netlify DB (Postgres), Blobs/file storage, and integrations like Turso, but there is no evidence of a Redis-compatible key-value store for caching or job queues; this is an applicable storage axis given Netlify's data offerings, so absence of evidence yields none.

   • [claimed-docs] “Deploy and safely iterate on managed Postgres with **Netlify Database**”
   • [claimed-docs] “Add instant databases and file storage”
   • [claimed-docs] “const uploads = getStore("file-uploads");”
   • [claimed-docs] “Turso is the Edge database that brings your data close to your edge functions. Develop locally and deploy globally with the developer experi…”

   proof ↗⚑ flag

   Railway—none0/10

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

   ⚑ flag

Object storage

1. developerPersist user-generated uploads using built-in object storage

   weight 2 · round to Netlify
   Netlify~partialclaimed5/10

   Netlify docs reference built-in storage capability directly relevant to persisting uploads — `getStore("file-uploads")` (Netlify Blobs) and 'Add instant databases and file storage' — showing a code-level API for storing user-generated files without external services. However, evidence is thin: no detail on durability, size limits, access control, or hands-on/independent confirmation of reliability for uploads at scale. missing for 10: deeper docs on Blobs API scope/limits, real-world usage examples, independent/community validation of the storage feature.

   • [claimed-docs] “const uploads = getStore("file-uploads");”
   • [claimed-docs] “Add instant databases and file storage”

   proof ↗⚑ flag

   Railway—none0/10

   No evidence pack items mention object storage, file/blob storage, S3-compatible storage, or persistent volumes for user uploads; the evidence covers deployment, scaling, observability, and AI agent tooling only.

   ⚑ flag

Relational db

1. developerProvision a fully-managed Postgres database with point-in-time recovery, replicas, and high availability

   weight 3 · round to Netlify
   Netlify~partialclaimed3/10

   Netlify docs mention a managed 'Netlify Database' offering for Postgres, but there is no evidence describing point-in-time recovery, replicas, or high-availability configurations. Missing for 10: explicit documentation of PITR, read replicas, HA/failover architecture, and any independent corroboration of these features.

   • [claimed-docs] “Deploy and safely iterate on managed Postgres with **Netlify Database**”
   • [claimed-docs] “Add instant databases and file storage”

   proof ↗⚑ flag

   Railway—none0/10

   The 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?”

   proof ↗⚑ flag

2. developerQuery a serverless SQL database directly from my code with no connection management

   weight 2 · round to Netlify
   Netlify✓fullclaimed7/10

   Netlify Database offers managed Postgres deployable directly with 'no connection management' framing implied by serverless integration (netlify-docs-13, netlify-docs-23), and Turso edge SQLite integration also supports serverless SQL querying (netlify-intdir-5). Missing for 10: independent hands-on verification of connection pooling/no-connection-management behavior, and detailed API/SDK docs showing query syntax from code.

   • [claimed-docs] “Deploy and safely iterate on managed Postgres with **Netlify Database**”
   • [claimed-docs] “Add instant databases and file storage”
   • [claimed-docs] “Turso is the Edge database that brings your data close to your edge functions. Develop locally and deploy globally with the developer experi…”

   proof ↗⚑ flag

   Railway—none0/10

   Railway'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.

   ⚑ flag