Access
Install
npm install -g netlify-cliShowcase


Verified integrations
Connections to other tracked products — hover a chip for the verbatim evidence quote behind it.
By theme — the product's score on each story themeBy theme
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Deploy workflow — the commit-to-production path — builds, previews, rollbacksDeploy workflowevidence →
The commit-to-production path — builds, previews, rollbacks
Dev experience — day-to-day developer experience — setup friction, docs, debugging, iteration speedDev experienceevidence →
Day-to-day developer experience — setup friction, docs, debugging, iteration speed
Edge compute — running code at the edge — regions, cold starts, runtime limitsEdge computeevidence →
Running code at the edge — regions, cold starts, runtime limits
Networking security — network controls and isolation — private access, firewalls, encryptionNetworking securityevidence →
Network controls and isolation — private access, firewalls, encryption
Observability — seeing what the system is doing — logs, metrics, traces, alertsObservabilityevidence →
Seeing what the system is doing — logs, metrics, traces, alerts
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limitsevidence →
Free-tier ceilings, usage caps, and rate limits before you have to pay
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Storage data — storing and moving data — persistence, formats, durabilityStorage dataevidence →
Storing and moving data — persistence, formats, durability
Story verdicts — every judged story with its evidenceStory verdicts
What’s free: 5 free · 0 paid · 0 enterprise · 37 not stated in evidence
Follow the green: where the map greys out is where Netlify stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
✓8/10
unlocks → Scoped API keys · MCP server · Machine-readable spec · Versioning policy · Full data export · The documented rate limits and concurrency caps for APIs and functions so I can plan for scale
Subscribe to events via webhooks
~3/10
Build against official SDKs
✓7/10
Issue scoped/least-privilege API credentials for an agent
—0/10
Connect an agent via an official MCP server
—0/10
Download a machine-readable API spec (OpenAPI or equivalent)
—0/10
Rely on versioned APIs with a documented deprecation policy
—0/10
Test against a sandbox environment without touching production data
~6/10
Explore an interactive API reference with runnable examples
—0/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
~6/10
unlocks → MCP client · AI insights
Operate the product with natural-language commands
~5/10
Plug MCP servers into this product so it can use their tools
—0/10
Get AI-generated insights and suggestions from my data inside the product
—–
Set up automations that run autonomously in the background
~4/10
The documented rate limits and concurrency caps for APIs and functions so I can plan for scale
—–
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Automation depth
Define rules that trigger actions automatically on events
~5/10
unlocks → Develop and test my app locally using a simulator that matches the production runtime · Deploy applications packaged as Docker containers · Define, deploy, and version my entire architecture with a single configuration file
Schedule recurring jobs or workflows
—–
Perform bulk operations across many items at once
~3/10
Version, review, and roll back my automations
✓7/10
Deploy workflow — the commit-to-production path — builds, previews, rollbacksDeploy workflow
The commit-to-production path — builds, previews, rollbacks
Cli tooling
Deployment strategies
Git integration
Define, deploy, and version my entire architecture with a single configuration file
—0/10
Deploy a project by uploading a folder of files directly, with no Git repo required and the new deployment kept private until I choose to publish it
✓8/10
Preview envs
Roll back a deployed service to any previous version in one click
✓8/10
Deploy one-click templates and starters for common use cases
~5/10
Dev experience — day-to-day developer experience — setup friction, docs, debugging, iteration speedDev experience
Day-to-day developer experience — setup friction, docs, debugging, iteration speed
Collaboration
Spin up unlimited isolated environments so my whole team can ship simultaneously
~6/10
Rely on the same core APIs and primitives from prototype through massive scale, without rearchitecting or migrating platforms as usage grows
~6/10
Manage team-level access, secrets, and environment variables centrally
~6/10
Tool continuity
Visualize and edit my entire infrastructure stack on a visual canvas without writing config files
n/an/a
Edge compute — running code at the edge — regions, cold starts, runtime limitsEdge compute
Running code at the edge — regions, cold starts, runtime limits
Give my coding agent a persistent runtime environment that checkpoints its state automatically while working
n/an/a
Ai inference
Placement latency
Handle persistent WebSocket connections from within edge/serverless functions for real-time apps
—0/10
Runtime compatibility
Run untrusted code in hardware-isolated, disposable sandboxes
—–
Scaling
Serverless runtime
Deploy durable, long-running workflows as code without manually wiring queues and retries
—0/10
Networking security — network controls and isolation — private access, firewalls, encryptionNetworking security
Network controls and isolation — private access, firewalls, encryption
Put simple password protection on a deployed site without standing up a custom auth system
~6/10
Protect my app from automated bot traffic with invisible challenge-based protection
—0/10
Have DDoS protection and a web application firewall applied to every request by default
!4/10
Domains
Isolate non-production environments from accessing production services
~3/10
Secure internal apps, deployments, and agents using my organization's identity provider
—0/10
Keep internal service-to-service traffic off the public internet without VPC complexity
n/an/a
Serve HTTP, TCP, gRPC, and WebSocket traffic from the same deployed service without separate protocol configuration
n/an/a
Get free, automatically renewing TLS certificates for every domain including wildcards
~6/10
Observability — seeing what the system is doing — logs, metrics, traces, alertsObservability
Seeing what the system is doing — logs, metrics, traces, alerts
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limits
Free-tier ceilings, usage caps, and rate limits before you have to pay
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Storage data — storing and moving data — persistence, formats, durabilityStorage data
Storing and moving data — persistence, formats, durability
Serve static assets faster using a global CDN with edge caching
—0/10
Connect my code to external services like databases, APIs, and storage through native bindings with minimal boilerplate instead of hand-wiring SDKs and credentials
~6/10
Use a Redis-compatible key-value store for low-latency caching and job queues
—0/10
Resize and optimize images on demand via a built-in image CDN
~6/10
Persist user-generated uploads using built-in object storage
~5/10
Sorted by importance (agentic first) (high → low) · 96/96 stories · click a row’s chevron for the rationale and evidence
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 8/10 | Tprobed | |
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | partial | 6/10 | Cclaimed | |
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | 0/10 | ||
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | 0/10 | ||
The documented rate limits and concurrency caps for APIs and functions so I can plan for scale G Api quality | developer | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | untested | none yet | |
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 7/10 | Tprobed | |
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Tprobed | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 4/10 | Cclaimed | |
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partialfree | 3/10 | Xcommunity | |
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | partial | 6/10 | Cclaimed | |
Get an automatic preview URL for every pull request C Preview envs | developer | Deploy workflow — the commit-to-production path — builds, previews, rollbacksDeploy workflow | 3 | full | 9/10 | Xcommunity | |
Automatically deploy my app on every Git push C Git integration | developer | Deploy workflow — the commit-to-production path — builds, previews, rollbacksDeploy workflow | 3 | full | 8/10 | Xcommunity | |
Deploy my app by simply connecting my repo without manual build configuration C Git integration | developer | Deploy workflow — the commit-to-production path — builds, previews, rollbacksDeploy workflow | 3 | full | 8/10 | Xcommunity | |
Deploy serverless functions and full-stack apps with no servers to manage C Serverless runtime | developer | Edge compute — running code at the edge — regions, cold starts, runtime limitsEdge compute | 3 | fullfree | 8/10 | Xcommunity | |
Roll back a deployed service to any previous version in one click C Rollback recovery | developer | Deploy workflow — the commit-to-production path — builds, previews, rollbacksDeploy workflow | 3 | full | 8/10 | Cclaimed | |
Access hundreds of AI models through a single unified gateway endpoint C Ai inference | ai-native builder | Edge compute — running code at the edge — regions, cold starts, runtime limitsEdge compute | 3 | partial | 6/10 | Cclaimed | |
Get free, automatically renewing TLS certificates for every domain including wildcards C Tls certs | devops-lead | Networking security — network controls and isolation — private access, firewalls, encryptionNetworking security | 3 | partialfree | 6/10 | Xcommunity | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | partialfree | 5/10 | Xcommunity | |
Run AI model inference globally with a single call without managing GPUs or capacity planning C Ai inference | ai-native builder | Edge compute — running code at the edge — regions, cold starts, runtime limitsEdge compute | 3 | partial | 5/10 | Cclaimed | |
Have DDoS protection and a web application firewall applied to every request by default C Ddos waf | devops-lead | Networking security — network controls and isolation — private access, firewalls, encryptionNetworking security | 3 | disputed | 4/10 | Dcontradicted | |
Provision a fully-managed Postgres database with point-in-time recovery, replicas, and high availability C Relational db | developer | Storage data — storing and moving data — persistence, formats, durabilityStorage data | 3 | partial | 3/10 | Cclaimed | |
Run my code on a global edge network close to end users C Serverless runtime | developer | Edge compute — running code at the edge — regions, cold starts, runtime limitsEdge compute | 3 | partial | 3/10 | Cclaimed | |
Run unmodified Node.js code and npm packages in edge/serverless functions instead of a restricted runtime subset C Runtime compatibility | developer | Edge compute — running code at the edge — regions, cold starts, runtime limitsEdge compute | 3 | none | 0/10 | ||
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | 0/10 | ||
The exact overage fee schedule for exceeding plan usage limits (bandwidth, invocations, build minutes) before I get billed G Overage fees | devops-lead | Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limits | 3 | none | 0/10 | ||
View all my build, deploy, and runtime logs in one place C Unified logging | developer | Observability — seeing what the system is doing — logs, metrics, traces, alertsObservability | 3 | none | 0/10 | ||
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | untested | none yet | |
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | none | untested | none yet | |
Review a published uptime SLA with defined credits for downtime G Reliability sla | devops-lead | Observability — seeing what the system is doing — logs, metrics, traces, alertsObservability | 3 | none | untested | none yet | |
The CPU and wall-clock execution time limits for functions so I can tell whether long-running or agentic workloads will fit C Execution limits | devops-lead | Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limits | 3 | none | untested | none yet | |
Deploy my project directly from the command line without using a web dashboard C Cli tooling | developer | Deploy workflow — the commit-to-production path — builds, previews, rollbacksDeploy workflow | 2 | full | 9/10 | Tprobed | |
Attach custom domains to my deployed services C Domains | developer | Networking security — network controls and isolation — private access, firewalls, encryptionNetworking security | 2 | fullfree | 8/10 | Xcommunity | |
Deploy a project by uploading a folder of files directly, with no Git repo required and the new deployment kept private until I choose to publish it P Manual deploy | developer | Deploy workflow — the commit-to-production path — builds, previews, rollbacksDeploy workflow | 2 | full | 8/10 | Cclaimed | |
Get ephemeral full-stack preview environments for every pull request C Preview envs | developer | Deploy workflow — the commit-to-production path — builds, previews, rollbacksDeploy workflow | 2 | full | 8/10 | Xcommunity | |
Query a serverless SQL database directly from my code with no connection management C Relational db | developer | Storage data — storing and moving data — persistence, formats, durabilityStorage data | 2 | full | 7/10 | Cclaimed | |
Connect my code to external services like databases, APIs, and storage through native bindings with minimal boilerplate instead of hand-wiring SDKs and credentials C Integrations | developer | Storage data — storing and moving data — persistence, formats, durabilityStorage data | 2 | partial | 6/10 | Cclaimed | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 6/10 | Tprobed | |
Keep using my existing Git, CI, editor, and framework workflows without adopting proprietary tooling C Tool continuity | developer | Dev experience — day-to-day developer experience — setup friction, docs, debugging, iteration speedDev experience | 2 | partial | 6/10 | Xcommunity | |
Manage team-level access, secrets, and environment variables centrally C Secrets management | devops-lead | Dev experience — day-to-day developer experience — setup friction, docs, debugging, iteration speedDev experience | 2 | partial | 6/10 | Cclaimed | |
Put simple password protection on a deployed site without standing up a custom auth system C Access control | developer | Networking security — network controls and isolation — private access, firewalls, encryptionNetworking security | 2 | partial | 6/10 | Cclaimed | |
Rely on the same core APIs and primitives from prototype through massive scale, without rearchitecting or migrating platforms as usage grows C Scaling continuity | developer | Dev experience — day-to-day developer experience — setup friction, docs, debugging, iteration speedDev experience | 2 | partial | 6/10 | Cclaimed | |
Scaffold and deploy a new project with a single CLI command C Cli tooling | developer | Deploy workflow — the commit-to-production path — builds, previews, rollbacksDeploy workflow | 2 | partial | 6/10 | Tprobed | |
Persist user-generated uploads using built-in object storage C Object storage | developer | Storage data — storing and moving data — persistence, formats, durabilityStorage data | 2 | partial | 5/10 | Cclaimed | |
Programmatically provision and route custom domains for my own multi-tenant SaaS customers C Domains | developer | Networking security — network controls and isolation — private access, firewalls, encryptionNetworking security | 2 | partial | 5/10 | Cclaimed | |
Develop and test my app locally using a simulator that matches the production runtime C Cli tooling | developer | Deploy workflow — the commit-to-production path — builds, previews, rollbacksDeploy workflow | 2 | disputed | 4/10 | Dcontradicted | |
Pay only for active compute time rather than idle wall-clock time G Usage billing | devops-lead | Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limits | 2 | partial | 3/10 | Cclaimed | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | partial | 3/10 | Tprobed | |
Rely on load-based autoscaling to absorb large traffic bursts automatically C Scaling | devops-lead | Edge compute — running code at the edge — regions, cold starts, runtime limitsEdge compute | 2 | partial | 3/10 | Xcommunity | |
Roll out new deployments incrementally to reduce blast radius C Deployment strategies | devops-lead | Deploy workflow — the commit-to-production path — builds, previews, rollbacksDeploy workflow | 2 | partial | 3/10 | Cclaimed | |
Attached disk/storage auto-grows with usage and I'm billed only for bytes actually written rather than pre-provisioned capacity P Usage billing | devops-lead | Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limits | 2 | none | 0/10 | ||
Build custom dashboards combining metrics from any service C Metrics dashboards | devops-lead | Observability — seeing what the system is doing — logs, metrics, traces, alertsObservability | 2 | none | 0/10 | ||
Define, deploy, and version my entire architecture with a single configuration file C Infra as code | devops-lead | Deploy workflow — the commit-to-production path — builds, previews, rollbacksDeploy workflow | 2 | none | 0/10 | ||
Deploy durable, long-running workflows as code without manually wiring queues and retries C Workflows | developer | Edge compute — running code at the edge — regions, cold starts, runtime limitsEdge compute | 2 | none | 0/10 | ||
Deploy instances that boot in under a second and scale to tens of thousands under load C Scaling | devops-lead | Edge compute — running code at the edge — regions, cold starts, runtime limitsEdge compute | 2 | none | 0/10 | ||
Handle persistent WebSocket connections from within edge/serverless functions for real-time apps C Realtime connections | developer | Edge compute — running code at the edge — regions, cold starts, runtime limitsEdge compute | 2 | none | 0/10 | ||
Secure internal apps, deployments, and agents using my organization's identity provider G Identity | devops-lead | Networking security — network controls and isolation — private access, firewalls, encryptionNetworking security | 2 | none | 0/10 | ||
Serve static assets faster using a global CDN with edge caching C Cdn assets | developer | Storage data — storing and moving data — persistence, formats, durabilityStorage data | 2 | none | 0/10 | ||
Set hard spending limits to control my cloud costs G Cost controls | devops-lead | Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limits | 2 | none | 0/10 | ||
The guaranteed support response times and escalation paths for my plan tier G Reliability sla | devops-lead | Observability — seeing what the system is doing — logs, metrics, traces, alertsObservability | 2 | none | 0/10 | ||
Use a Redis-compatible key-value store for low-latency caching and job queues C Kv cache | developer | Storage data — storing and moving data — persistence, formats, durabilityStorage data | 2 | none | 0/10 | ||
Whether pricing is per-seat with minimum seat counts that increase cost as my team grows G Overage fees | devops-lead | Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limits | 2 | none | 0/10 | ||
Write code against standard runtime APIs so it runs unmodified across multiple edge platforms instead of being locked into proprietary storage/runtime APIs C Tool continuity | developer | Dev experience — day-to-day developer experience — setup friction, docs, debugging, iteration speedDev experience | 2 | none | 0/10 | ||
Write edge functions in languages other than JavaScript such as Python, Go, or Rust C Runtime compatibility | developer | Edge compute — running code at the edge — regions, cold starts, runtime limitsEdge compute | 2 | none | 0/10 | ||
Check a public status page with historical incident postmortems before committing G Reliability sla | devops-lead | Observability — seeing what the system is doing — logs, metrics, traces, alertsObservability | 2 | none | untested | none yet | |
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Deploy applications packaged as Docker containers C Deployment strategies | developer | Deploy workflow — the commit-to-production path — builds, previews, rollbacksDeploy workflow | 2 | none | untested | none yet | |
Deploy my application to specific regions closer to my users C Placement latency | devops-lead | Edge compute — running code at the edge — regions, cold starts, runtime limitsEdge compute | 2 | none | untested | none yet | |
Give my coding agent a persistent runtime environment that checkpoints its state automatically while working C Agent runtime | ai-native builder | Edge compute — running code at the edge — regions, cold starts, runtime limitsEdge compute | 2 | n/a | untested | none yet | |
Keep internal service-to-service traffic off the public internet without VPC complexity C Private networking | devops-lead | Networking security — network controls and isolation — private access, firewalls, encryptionNetworking security | 2 | n/a | untested | none yet | |
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | none | untested | none yet | |
Rely on automatic compute placement near backend data to optimize latency C Placement latency | devops-lead | Edge compute — running code at the edge — regions, cold starts, runtime limitsEdge compute | 2 | none | untested | none yet | |
Run untrusted code in hardware-isolated, disposable sandboxes C Sandboxing | developer | Edge compute — running code at the edge — regions, cold starts, runtime limitsEdge compute | 2 | none | untested | none yet | |
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | none | untested | none yet | |
Set up alerts that notify me via chat or email when specific conditions are met C Alerting | devops-lead | Observability — seeing what the system is doing — logs, metrics, traces, alertsObservability | 2 | none | untested | none yet | |
Visualize and edit my entire infrastructure stack on a visual canvas without writing config files C Visual infra | devops-lead | Dev experience — day-to-day developer experience — setup friction, docs, debugging, iteration speedDev experience | 2 | n/a | untested | none yet | |
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | full | 7/10 | Xcommunity | |
Resize and optimize images on demand via a built-in image CDN C Media | developer | Storage data — storing and moving data — persistence, formats, durabilityStorage data | 1 | partial | 6/10 | Cclaimed | |
Spin up unlimited isolated environments so my whole team can ship simultaneously C Environments | developer | Dev experience — day-to-day developer experience — setup friction, docs, debugging, iteration speedDev experience | 1 | partial | 6/10 | Xcommunity | |
Track site performance and visitor behavior with built-in analytics C Metrics dashboards | devops-lead | Observability — seeing what the system is doing — logs, metrics, traces, alertsObservability | 1 | partial | 6/10 | Cclaimed | |
Deploy one-click templates and starters for common use cases C Templates | developer | Deploy workflow — the commit-to-production path — builds, previews, rollbacksDeploy workflow | 1 | partial | 5/10 | Cclaimed | |
Let teammates and collaborators comment directly on preview and production environments C Collaboration | developer | Dev experience — day-to-day developer experience — setup friction, docs, debugging, iteration speedDev experience | 1 | partial | 4/10 | Cclaimed | |
Isolate non-production environments from accessing production services C Env isolation | devops-lead | Networking security — network controls and isolation — private access, firewalls, encryptionNetworking security | 1 | partial | 3/10 | Cclaimed | |
Protect my app from automated bot traffic with invisible challenge-based protection C Bot protection | developer | Networking security — network controls and isolation — private access, firewalls, encryptionNetworking security | 1 | none | 0/10 | ||
Receive migration credits when moving my production infrastructure to a new platform C Cost controls | devops-lead | Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limits | 1 | none | untested | none yet | |
Serve HTTP, TCP, gRPC, and WebSocket traffic from the same deployed service without separate protocol configuration C Protocols | developer | Networking security — network controls and isolation — private access, firewalls, encryptionNetworking security | 1 | n/a | untested | none yet | |
Use an in-browser toolbar to leave feedback, manage feature flags, and inspect performance directly on my live site C Collaboration | developer | Dev experience — day-to-day developer experience — setup friction, docs, debugging, iteration speedDev experience | 1 | n/a | untested | none yet |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 73 stories with headroom
What would move Netlify’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Agenticness — how well agents can access and operate the productPlug MCP servers into this product so it can use their tools
nonemoves agent-readyimpact 45
Missing: any mention of MCP protocol/server support, or documentation of Netlify consuming third-party MCP tool servers.
Agenticness — how well agents can access and operate the productConnect an agent via an official MCP server
nonemoves agent-readyimpact 45
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.
Agenticness — how well agents can access and operate the productThe documented rate limits and concurrency caps for APIs and functions so I can plan for scale
nonemoves API qualityimpact 45
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.
Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payThe CPU and wall-clock execution time limits for functions so I can tell whether long-running or agentic workloads will fit
nonemoves PA Scoreimpact 30
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.
Edge compute — running code at the edge — regions, cold starts, runtime limitsRun unmodified Node.js code and npm packages in edge/serverless functions instead of a restricted runtime subset
nonemoves PA Scoreimpact 30
The evidence only generically mentions 'Build APIs with serverless functions' (netlify-docs-6) with no detail on Node.js runtime compatibility, npm package support, or contrast with a restricted runtime subset (e.g., edge functions).
Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payThe exact overage fee schedule for exceeding plan usage limits (bandwidth, invocations, build minutes) before I get billed
nonemoves PA Scoreimpact 30
Missing: a documented overage pricing table, per-unit fee schedule, or billing calculator referenced in official docs.
Openness — open source, data portability, and self-hosting storiesExport all of my data in open formats and leave
nonemoves PA Scoreimpact 30
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.
Openness — open source, data portability, and self-hosting storiesSelf-host the core product
nonemoves PA Scoreimpact 30
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.
Showing the top 8 of 73 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map7 surfaces · 48 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
netlify.com38 stories
- Run the product headlessly / in CI for automation
- Use an official CLI
- Build against official SDKs
- Set up automations that run autonomously in the background
- Test against a sandbox environment without touching production data
- Define rules that trigger actions automatically on events
- Version, review, and roll back my automations
- Deploy my project directly from the command line without using a web dashboard
- Scaffold and deploy a new project with a single CLI command
- Roll out new deployments incrementally to reduce blast radius
- Automatically deploy my app on every Git push
- Deploy my app by simply connecting my repo without manual build configuration
- Deploy a project by uploading a folder of files directly, with no Git repo required and the new deployment kept private until I choose to publish it
- Get ephemeral full-stack preview environments for every pull request
- Get an automatic preview URL for every pull request
- Roll back a deployed service to any previous version in one click
- Let teammates and collaborators comment directly on preview and production environments
- Spin up unlimited isolated environments so my whole team can ship simultaneously
- Rely on the same core APIs and primitives from prototype through massive scale, without rearchitecting or migrating platforms as usage grows
- Manage team-level access, secrets, and environment variables centrally
- Keep using my existing Git, CI, editor, and framework workflows without adopting proprietary tooling
- Run AI model inference globally with a single call without managing GPUs or capacity planning
- Access hundreds of AI models through a single unified gateway endpoint
- Rely on load-based autoscaling to absorb large traffic bursts automatically
- Run my code on a global edge network close to end users
- Deploy serverless functions and full-stack apps with no servers to manage
- Have DDoS protection and a web application firewall applied to every request by default
- Attach custom domains to my deployed services
- Programmatically provision and route custom domains for my own multi-tenant SaaS customers
- Isolate non-production environments from accessing production services
- Get free, automatically renewing TLS certificates for every domain including wildcards
- Do everything through the API that I can do in the UI
- Pay only for active compute time rather than idle wall-clock time
- Connect my code to external services like databases, APIs, and storage through native bindings with minimal boilerplate instead of hand-wiring SDKs and credentials
- Resize and optimize images on demand via a built-in image CDN
- Persist user-generated uploads using built-in object storage
- Provision a fully-managed Postgres database with point-in-time recovery, replicas, and high availability
- Query a serverless SQL database directly from my code with no connection management
docs.netlify.com31 stories
- Run the product headlessly / in CI for automation
- Use an official CLI
- Drive the product through a documented public API
- Build against official SDKs
- Set up automations that run autonomously in the background
- Delegate tasks to a built-in AI assistant inside the product
- Operate the product with natural-language commands
- Test against a sandbox environment without touching production data
- Perform bulk operations across many items at once
- Define rules that trigger actions automatically on events
- Deploy my project directly from the command line without using a web dashboard
- Scaffold and deploy a new project with a single CLI command
- Develop and test my app locally using a simulator that matches the production runtime
- Roll out new deployments incrementally to reduce blast radius
- Get ephemeral full-stack preview environments for every pull request
- Get an automatic preview URL for every pull request
- Let teammates and collaborators comment directly on preview and production environments
- Spin up unlimited isolated environments so my whole team can ship simultaneously
- Rely on the same core APIs and primitives from prototype through massive scale, without rearchitecting or migrating platforms as usage grows
- Manage team-level access, secrets, and environment variables centrally
- Keep using my existing Git, CI, editor, and framework workflows without adopting proprietary tooling
- Run AI model inference globally with a single call without managing GPUs or capacity planning
- Access hundreds of AI models through a single unified gateway endpoint
- Put simple password protection on a deployed site without standing up a custom auth system
- Have DDoS protection and a web application firewall applied to every request by default
- Attach custom domains to my deployed services
- Programmatically provision and route custom domains for my own multi-tenant SaaS customers
- Isolate non-production environments from accessing production services
- Track site performance and visitor behavior with built-in analytics
- Do everything through the API that I can do in the UI
- Connect my code to external services like databases, APIs, and storage through native bindings with minimal boilerplate instead of hand-wiring SDKs and credentials
Hacker News15 stories
- Subscribe to events via webhooks
- Define rules that trigger actions automatically on events
- Version, review, and roll back my automations
- Develop and test my app locally using a simulator that matches the production runtime
- Automatically deploy my app on every Git push
- Deploy my app by simply connecting my repo without manual build configuration
- Get ephemeral full-stack preview environments for every pull request
- Get an automatic preview URL for every pull request
- Spin up unlimited isolated environments so my whole team can ship simultaneously
- Keep using my existing Git, CI, editor, and framework workflows without adopting proprietary tooling
- Rely on load-based autoscaling to absorb large traffic bursts automatically
- Deploy serverless functions and full-stack apps with no servers to manage
- Have DDoS protection and a web application firewall applied to every request by default
- Attach custom domains to my deployed services
- Get free, automatically renewing TLS certificates for every domain including wildcards
CLI docs9 stories
- Run the product headlessly / in CI for automation
- Use an official CLI
- Drive the product through a documented public API
- Build against official SDKs
- Perform bulk operations across many items at once
- Deploy my project directly from the command line without using a web dashboard
- Scaffold and deploy a new project with a single CLI command
- Develop and test my app locally using a simulator that matches the production runtime
- Do everything through the API that I can do in the UI
Integrations docs6 stories
- Deploy one-click templates and starters for common use cases
- Rely on the same core APIs and primitives from prototype through massive scale, without rearchitecting or migrating platforms as usage grows
- Keep using my existing Git, CI, editor, and framework workflows without adopting proprietary tooling
- Run my code on a global edge network close to end users
- Connect my code to external services like databases, APIs, and storage through native bindings with minimal boilerplate instead of hand-wiring SDKs and credentials
- Query a serverless SQL database directly from my code with no connection management
llms.txt4 stories
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
9 of 23 testable claims verified · 3 contradicted → integrity 13/100
23 distinct capability claims found in Netlify’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
9
Verified
11
Unverified
3
Contradicted
26
Undersold
Verified (10)
“Automatically deploys the site on every git push”
“Every pull request gets an automatic preview URL”
Get an automatic preview URL for every pull requestfullproof ↗
“Deploy anonymously via CLI without an account using netlify deploy --allow-anonymous”
Deploy my project directly from the command line without using a web dashboardfullproof ↗
“Deploy anonymously via CLI without an account using netlify deploy --allow-anonymous”
“Build backend APIs using serverless functions”
Deploy serverless functions and full-stack apps with no servers to managefullproof ↗
“Automatic HTTPS certificates for deployed sites”
Get free, automatically renewing TLS certificates for every domain including wildcardspartialproof ↗
“Programmatically manage sites, deploys, and DNS via a REST API”
Drive the product through a documented public APIfullproof ↗
“Official CLI to deploy sites, run local dev servers, and manage projects from the terminal”
“Build extensions and integrations using an official SDK”
“Manage and attach custom domains for different project versions”
Unverified (11)
“Deploy a project folder directly with no login required, staying private until published”
Deploy a project by uploading a folder of files directly, with no Git repo required and the new deployment kept private until I choose to publish itfullproof ↗
“Roll back any deploy to a previous version with one click”
Roll back a deployed service to any previous version in one clickfullproof ↗
“Connect to AI models through a built-in AI Gateway”
Access hundreds of AI models through a single unified gateway endpointpartialproof ↗
“Centrally manage team access, secrets, and environment variables”
Manage team-level access, secrets, and environment variables centrallypartialproof ↗
“On-demand image resizing (e.g. to 800px wide) via built-in image CDN”
Resize and optimize images on demand via a built-in image CDNpartialproof ↗
“Store and access file uploads via a built-in object store API (getStore)”
Persist user-generated uploads using built-in object storagepartialproof ↗
“Deploy and iterate on a managed Postgres database (Netlify Database)”
Provision a fully-managed Postgres database with point-in-time recovery, replicas, and high availabilitypartialproof ↗
“Track deployment performance and visitor/team behavior analytics”
Track site performance and visitor behavior with built-in analyticspartialproof ↗
“Add simple password protection to a site without building custom auth”
Put simple password protection on a deployed site without standing up a custom auth systempartialproof ↗
“Share a customizable preview environment for collaborators to review content and code updates in real time”
Let teammates and collaborators comment directly on preview and production environmentspartialproof ↗
“Prompt AI agents from the dashboard to fix, update, and ship code using project context”
Delegate tasks to a built-in AI assistant inside the productpartialproof ↗
Contradicted (3)
“Built-in DDoS protection applied automatically”
Have DDoS protection and a web application firewall applied to every request by defaultdisputedproof ↗
“Official CLI to deploy sites, run local dev servers, and manage projects from the terminal”
Develop and test my app locally using a simulator that matches the production runtimedisputedproof ↗
“Connect external AI assistants to a Netlify account for deployment workflows”
Undersold (26)
Point an agent at llms.txt or agent-oriented docsfullproof ↗
Run the product headlessly / in CI for automationfullproof ↗
Set up automations that run autonomously in the backgroundpartialproof ↗
Operate the product with natural-language commandspartialproof ↗
Test against a sandbox environment without touching production datapartialproof ↗
Perform bulk operations across many items at oncepartialproof ↗
Define rules that trigger actions automatically on eventspartialproof ↗
Scaffold and deploy a new project with a single CLI commandpartialproof ↗
Roll out new deployments incrementally to reduce blast radiuspartialproof ↗
Deploy my app by simply connecting my repo without manual build configurationfullproof ↗
Get ephemeral full-stack preview environments for every pull requestfullproof ↗
Deploy one-click templates and starters for common use casespartialproof ↗
Spin up unlimited isolated environments so my whole team can ship simultaneouslypartialproof ↗
Rely on the same core APIs and primitives from prototype through massive scale, without rearchitecting or migrating platforms as usage growspartialproof ↗
Keep using my existing Git, CI, editor, and framework workflows without adopting proprietary toolingpartialproof ↗
Run AI model inference globally with a single call without managing GPUs or capacity planningpartialproof ↗
Rely on load-based autoscaling to absorb large traffic bursts automaticallypartialproof ↗
Run my code on a global edge network close to end userspartialproof ↗
Programmatically provision and route custom domains for my own multi-tenant SaaS customerspartialproof ↗
Isolate non-production environments from accessing production servicespartialproof ↗
Do everything through the API that I can do in the UIpartialproof ↗
Pay only for active compute time rather than idle wall-clock timepartialproof ↗
Connect my code to external services like databases, APIs, and storage through native bindings with minimal boilerplate instead of hand-wiring SDKs and credentialspartialproof ↗
Query a serverless SQL database directly from my code with no connection managementfullproof ↗
Claims outside our story set (1)
Real capability claims found in Netlify’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.
“Collect form leads with zero configuration”
source ↗
Business model
Free tier plus paid Personal/Pro flat subscriptions that grant monthly usage credits (deploys, bandwidth, compute); Enterprise custom.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
Agent surface uptime llms.txt 100% (30d, checked every 6h since Sep 8 '26)
