Access
Install
curl -L https://fly.io/install.sh | shVendor-official, but review any script before piping it to a shell.
Showcase


Verified integrations
Connections to other tracked products — hover a chip for the verbatim evidence quote behind it.
By theme — the product's score on each story themeBy theme
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Deploy workflow — the commit-to-production path — builds, previews, rollbacksDeploy workflowevidence →
The commit-to-production path — builds, previews, rollbacks
Dev experience — day-to-day developer experience — setup friction, docs, debugging, iteration speedDev experienceevidence →
Day-to-day developer experience — setup friction, docs, debugging, iteration speed
Edge compute — running code at the edge — regions, cold starts, runtime limitsEdge computeevidence →
Running code at the edge — regions, cold starts, runtime limits
Networking security — network controls and isolation — private access, firewalls, encryptionNetworking securityevidence →
Network controls and isolation — private access, firewalls, encryption
Observability — seeing what the system is doing — logs, metrics, traces, alertsObservabilityevidence →
Seeing what the system is doing — logs, metrics, traces, alerts
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limitsevidence →
Free-tier ceilings, usage caps, and rate limits before you have to pay
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Storage data — storing and moving data — persistence, formats, durabilityStorage dataevidence →
Storing and moving data — persistence, formats, durability
Story verdicts — every judged story with its evidenceStory verdicts
What’s free: 0 free · 1 paid · 0 enterprise · 27 not stated in evidence
Follow the green: where the map greys out is where Fly.io 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
~6/10
unlocks → Webhooks · Official SDKs · 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
—0/10
Build against official SDKs
—0/10
Issue scoped/least-privilege API credentials for an agent
✓7/10
Connect an agent via an official MCP server
~5/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
~7/10
Explore an interactive API reference with runnable examples
—0/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
n/an/a
Operate the product with natural-language commands
~4/10
Plug MCP servers into this product so it can use their tools
n/an/a
Get AI-generated insights and suggestions from my data inside the product
n/an/a
Set up automations that run autonomously in the background
~5/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
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
~6/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
~4/10
Preview envs
Roll back a deployed service to any previous version in one click
~4/10
Deploy one-click templates and starters for common use cases
—0/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
~5/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
✓7/10
Ai inference
Placement latency
Handle persistent WebSocket connections from within edge/serverless functions for real-time apps
~4/10
Runtime compatibility
Run untrusted code in hardware-isolated, disposable sandboxes
✓7/10
Scaling
Serverless runtime
Deploy durable, long-running workflows as code without manually wiring queues and retries
—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
—0/10
Protect my app from automated bot traffic with invisible challenge-based protection
n/an/a
Have DDoS protection and a web application firewall applied to every request by default
—–
Domains
Isolate non-production environments from accessing production services
—–
Secure internal apps, deployments, and agents using my organization's identity provider
—–
Keep internal service-to-service traffic off the public internet without VPC complexity
~4/10
Serve HTTP, TCP, gRPC, and WebSocket traffic from the same deployed service without separate protocol configuration
—–
Get free, automatically renewing TLS certificates for every domain including wildcards
—–
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
~4/10
Use a Redis-compatible key-value store for low-latency caching and job queues
—–
Resize and optimize images on demand via a built-in image CDN
n/an/a
Persist user-generated uploads using built-in object storage
—0/10
Sorted by importance (agentic first) (high → low) · 96/96 stories · click a row’s chevron for the rationale and evidence
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | partial | 6/10 | Tprobed | |
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | partial | 5/10 | Cclaimed | |
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | n/a | 0/10 | ||
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | n/a | untested | none yet | |
The documented rate limits and concurrency caps for APIs and functions so I can plan for scale G Api quality | developer | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | untested | none yet | |
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 | |
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 | |
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 | full | 7/10 | Cclaimed | |
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 | partial | 6/10 | Tprobed | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Xcommunity | |
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 | 4/10 | Cclaimed | |
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
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 | ||
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 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 | n/a | 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 | 7/10 | Cclaimed | |
Run my code on a global edge network close to end users C Serverless runtime | developer | Edge compute — running code at the edge — regions, cold starts, runtime limitsEdge compute | 3 | full | 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 | disputed | 5/10 | Dcontradicted | |
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 | partial | 4/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 | partial | 4/10 | Tprobed | |
Run unmodified Node.js code and npm packages in edge/serverless functions instead of a restricted runtime subset C Runtime compatibility | developer | Edge compute — running code at the edge — regions, cold starts, runtime limitsEdge compute | 3 | partial | 4/10 | Cclaimed | |
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 | disputed | 3/10 | Dcontradicted | |
Automatically deploy my app on every Git push C Git integration | developer | Deploy workflow — the commit-to-production path — builds, previews, rollbacksDeploy workflow | 3 | none | 0/10 | ||
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | none | 0/10 | ||
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 | 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 CPU and wall-clock execution time limits for functions so I can tell whether long-running or agentic workloads will fit C Execution limits | devops-lead | Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limits | 3 | none | 0/10 | ||
The exact overage fee schedule for exceeding plan usage limits (bandwidth, invocations, build minutes) before I get billed G Overage fees | devops-lead | Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limits | 3 | none | 0/10 | ||
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 | ||
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 | n/a | untested | none yet | |
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 | |
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 | none | untested | none yet | |
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 | none | untested | none yet | |
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 | 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 | n/a | 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 | |
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 | |
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 | full | 7/10 | Cclaimed | |
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 | full | 7/10 | Cclaimed | |
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 | full | 7/10 | Cclaimed | |
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 | fullpaid | 7/10 | Cclaimed | |
Run untrusted code in hardware-isolated, disposable sandboxes C Sandboxing | developer | Edge compute — running code at the edge — regions, cold starts, runtime limitsEdge compute | 2 | full | 7/10 | Cclaimed | |
Scaffold and deploy a new project with a single CLI command C Cli tooling | developer | Deploy workflow — the commit-to-production path — builds, previews, rollbacksDeploy workflow | 2 | full | 7/10 | Xcommunity | |
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 | full | 7/10 | Cclaimed | |
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | partial | 6/10 | Cclaimed | |
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 | 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 | 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 | |
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 | full | 6/10 | Cclaimed | |
Deploy applications packaged as Docker containers C Deployment strategies | developer | Deploy workflow — the commit-to-production path — builds, previews, rollbacksDeploy workflow | 2 | disputed | 5/10 | Dcontradicted | |
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 | disputed | 5/10 | Dcontradicted | |
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 | 5/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 | 4/10 | Cclaimed | |
Deploy a project by uploading a folder of files directly, with no Git repo required and the new deployment kept private until I choose to publish it P Manual deploy | developer | Deploy workflow — the commit-to-production path — builds, previews, rollbacksDeploy workflow | 2 | partial | 4/10 | Cclaimed | |
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 | partial | 4/10 | Cclaimed | |
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 | partial | 4/10 | Cclaimed | |
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 | partial | 4/10 | Cclaimed | |
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 | 4/10 | Xcommunity | |
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 | Cclaimed | |
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 | 0/10 | ||
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 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 | ||
Persist user-generated uploads using built-in object storage C Object storage | developer | Storage data — storing and moving data — persistence, formats, durabilityStorage data | 2 | none | 0/10 | ||
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 | none | 0/10 | ||
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 | none | 0/10 | ||
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 | none | 0/10 | ||
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 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 | ||
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 | ||
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 | ||
Attach custom domains to my deployed services C Domains | developer | Networking security — network controls and isolation — private access, firewalls, encryptionNetworking security | 2 | none | untested | none yet | |
Build custom dashboards combining metrics from any service C Metrics dashboards | devops-lead | Observability — seeing what the system is doing — logs, metrics, traces, alertsObservability | 2 | none | untested | none yet | |
Develop and test my app locally using a simulator that matches the production runtime C Cli tooling | developer | Deploy workflow — the commit-to-production path — builds, previews, rollbacksDeploy workflow | 2 | none | untested | none yet | |
Get ephemeral full-stack preview environments for every pull request C Preview envs | developer | Deploy workflow — the commit-to-production path — builds, previews, rollbacksDeploy workflow | 2 | none | untested | none yet | |
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
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 | 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 | |
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 | untested | none yet | |
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 | 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 | |
Use a Redis-compatible key-value store for low-latency caching and job queues C Kv cache | developer | Storage data — storing and moving data — persistence, formats, durabilityStorage data | 2 | none | untested | none yet | |
Visualize and edit my entire infrastructure stack on a visual canvas without writing config files C Visual infra | devops-lead | Dev experience — day-to-day developer experience — setup friction, docs, debugging, iteration speedDev experience | 2 | n/a | untested | none yet | |
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 | |
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | partial | 4/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 | none | 0/10 | ||
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 | none | untested | none yet | |
Let teammates and collaborators comment directly on preview and production environments C Collaboration | developer | Dev experience — day-to-day developer experience — setup friction, docs, debugging, iteration speedDev experience | 1 | n/a | untested | none yet | |
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 | n/a | untested | none yet | |
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 | |
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 | n/a | untested | none yet | |
Serve HTTP, TCP, gRPC, and WebSocket traffic from the same deployed service without separate protocol configuration C Protocols | developer | Networking security — network controls and isolation — private access, firewalls, encryptionNetworking security | 1 | none | untested | none yet | |
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 | 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 68 stories with headroom
What would move Fly.io’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 productThe documented rate limits and concurrency caps for APIs and functions so I can plan for scale
nonemoves API qualityimpact 45
No evidence pack items document specific rate limits, concurrency caps, or throughput quotas for Fly.io's APIs, Machines, or MCP/Sprite offerings; docs focus on scaling primitives and pricing model, not documented numeric limits/caps for planning capacity.
Edge compute — running code at the edge — regions, cold starts, runtime limitsRun AI model inference globally with a single call without managing GPUs or capacity planning
nonemoves PA Scoreimpact 30
The evidence pack documents Fly Machines/Sprites as general-purpose global compute VMs, agent sandboxes, and Postgres, but contains no mention of a managed AI inference/model-serving API, GPU provisioning, or 'single call' inference capability abstracting away GPU/capacity management.
Networking security — network controls and isolation — private access, firewalls, encryptionGet free, automatically renewing TLS certificates for every domain including wildcards
nonemoves PA Scoreimpact 30
No evidence in the pack mentions TLS certificate provisioning, automatic renewal, or wildcard domain support; the docs excerpts focus on Machines, Sprites, MCP servers, and pricing, not certificate management.
Automation depth — how much of the product can run unattendedDefine rules that trigger actions automatically on events
nonemoves PA Scoreimpact 30
Fly.io's evidence only shows infrastructure-level triggers like Machine restart policies (restart on process exit) — not a general-purpose rules/automation engine for reacting to arbitrary events.
Networking security — network controls and isolation — private access, firewalls, encryptionHave DDoS protection and a web application firewall applied to every request by default
nonemoves PA Scoreimpact 30
No evidence pack item mentions DDoS protection or a web application firewall being applied by default (or at all); docs cover secrets, scaling, and Machine isolation but never security perimeter features like WAF/DDoS mitigation.
Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payThe CPU and wall-clock execution time limits for functions so I can tell whether long-running or agentic workloads will fit
nonemoves PA Scoreimpact 30
Missing: any documented CPU quota, timeout, or wall-clock limit per Machine/Sprite invocation, and any comparison table or pricing-limits doc addressing execution duration.
Deploy workflow — the commit-to-production path — builds, previews, rollbacksAutomatically deploy my app on every Git push
nonemoves PA Scoreimpact 30
Missing: any mention of Git-triggered CI/CD, GitHub App integration, or auto-deploy hooks.
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
Evidence shows only generic pay-as-you-go pricing claims (compute/storage/bandwidth billed by usage) but no documented overage fee schedule, no specifics on invocation or build-minute overage costs, and no billing rate table.
Showing the top 8 of 68 — 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 map6 surfaces · 41 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
fly.io36 stories
- Point an agent at llms.txt or agent-oriented docs
- Run the product headlessly / in CI for automation
- Use an official CLI
- Drive the product through a documented public API
- Issue scoped/least-privilege API credentials for an agent
- Set up automations that run autonomously in the background
- Operate the product with natural-language commands
- Test against a sandbox environment without touching production data
- Perform bulk operations across many items at once
- Version, review, and roll back my automations
- Deploy my project directly from the command line without using a web dashboard
- Deploy applications packaged as Docker containers
- Define, deploy, and version my entire architecture with a single configuration file
- Roll back a deployed service to any previous version in one click
- 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
- Write code against standard runtime APIs so it runs unmodified across multiple edge platforms instead of being locked into proprietary storage/runtime APIs
- Give my coding agent a persistent runtime environment that checkpoints its state automatically while working
- Deploy my application to specific regions closer to my users
- Rely on automatic compute placement near backend data to optimize latency
- Handle persistent WebSocket connections from within edge/serverless functions for real-time apps
- Run unmodified Node.js code and npm packages in edge/serverless functions instead of a restricted runtime subset
- Write edge functions in languages other than JavaScript such as Python, Go, or Rust
- Run untrusted code in hardware-isolated, disposable sandboxes
- Deploy instances that boot in under a second and scale to tens of thousands under load
- Rely on load-based autoscaling to absorb large traffic bursts automatically
- Run my code on a global edge network close to end users
- Deploy serverless functions and full-stack apps with no servers to manage
- Keep internal service-to-service traffic off the public internet without VPC complexity
- Do everything through the API that I can do in the UI
- Pay only for active compute time rather than idle wall-clock time
- Attached disk/storage auto-grows with usage and I'm billed only for bytes actually written rather than pre-provisioned capacity
- Choose where my data is stored (region/residency)
- Connect my code to external services like databases, APIs, and storage through native bindings with minimal boilerplate instead of hand-wiring SDKs and credentials
docs29 stories
- Run the product headlessly / in CI for automation
- Connect an agent via an official MCP server
- Use an official CLI
- Drive the product through a documented public API
- Operate the product with natural-language commands
- Deploy my project directly from the command line without using a web dashboard
- Scaffold and deploy a new project with a single CLI command
- Deploy applications packaged as Docker containers
- Deploy my app by simply connecting my repo without manual build configuration
- Define, deploy, and version my entire architecture with a single configuration file
- Deploy a project by uploading a folder of files directly, with no Git repo required and the new deployment kept private until I choose to publish it
- Roll back a deployed service to any previous version in one click
- 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
- Keep using my existing Git, CI, editor, and framework workflows without adopting proprietary tooling
- Write code against standard runtime APIs so it runs unmodified across multiple edge platforms instead of being locked into proprietary storage/runtime APIs
- Deploy my application to specific regions closer to my users
- Rely on automatic compute placement near backend data to optimize latency
- Handle persistent WebSocket connections from within edge/serverless functions for real-time apps
- Run unmodified Node.js code and npm packages in edge/serverless functions instead of a restricted runtime subset
- Write edge functions in languages other than JavaScript such as Python, Go, or Rust
- Run untrusted code in hardware-isolated, disposable sandboxes
- Deploy instances that boot in under a second and scale to tens of thousands under load
- Run my code on a global edge network close to end users
- Deploy serverless functions and full-stack apps with no servers to manage
- Do everything through the API that I can do in the UI
- Choose where my data is stored (region/residency)
- Connect my code to external services like databases, APIs, and storage through native bindings with minimal boilerplate instead of hand-wiring SDKs and credentials
- Provision a fully-managed Postgres database with point-in-time recovery, replicas, and high availability
Hacker News10 stories
- Set up automations that run autonomously in the background
- Scaffold and deploy a new project with a single CLI command
- Deploy applications packaged as Docker containers
- Deploy my app by simply connecting my repo without manual build configuration
- Spin up unlimited isolated environments so my whole team can ship simultaneously
- Deploy instances that boot in under a second and scale to tens of thousands under load
- Rely on load-based autoscaling to absorb large traffic bursts automatically
- Run my code on a global edge network close to end users
- Deploy serverless functions and full-stack apps with no servers to manage
- Provision a fully-managed Postgres database with point-in-time recovery, replicas, and high availability
Laravel bytes docs5 stories
- Deploy applications packaged as Docker containers
- Keep using my existing Git, CI, editor, and framework workflows without adopting proprietary tooling
- Write code against standard runtime APIs so it runs unmodified across multiple edge platforms instead of being locked into proprietary storage/runtime APIs
- Run unmodified Node.js code and npm packages in edge/serverless functions instead of a restricted runtime subset
- Write edge functions in languages other than JavaScript such as Python, Go, or Rust
OpenAPI spec2 stories
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
3 of 12 testable claims verified · 2 contradicted → integrity 0/100
13 distinct capability claims found in Fly.io’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
3
Verified
7
Unverified
2
Contradicted
27
Undersold
Verified (3)
“Scaffold and deploy a new app via flyctl install + fly launch commands”
Scaffold and deploy a new project with a single CLI commandfullproof ↗
“Scaffold and deploy a new app via flyctl install + fly launch commands”
Deploy my project directly from the command line without using a web dashboardfullproof ↗
“Roll back a Sprite to any previous checkpoint within seconds”
Roll back a deployed service to any previous version in one clickpartialproof ↗
Unverified (10)
“Each AI agent gets a dedicated Linux VM (Sprite) that auto-checkpoints its state while working, so coding harnesses resume exactly where they left off”
Give my coding agent a persistent runtime environment that checkpoints its state automatically while workingfullproof ↗
“Sprites can sleep when idle and wake instantly with full memory of previous state”
Give my coding agent a persistent runtime environment that checkpoints its state automatically while workingfullproof ↗
“Sprites can sleep when idle and wake instantly with full memory of previous state”
Pay only for active compute time rather than idle wall-clock timefullproof ↗
“Run each MCP server in its own isolated Sprite with persistent disk and egress policy, billed per tool call”
Run untrusted code in hardware-isolated, disposable sandboxesfullproof ↗
“Execute untrusted/agent code in hardware-isolated, disposable VMs with a clean per-request baseline and locked egress”
Run untrusted code in hardware-isolated, disposable sandboxesfullproof ↗
“Attached disk auto-grows up to 100GB per Sprite and billing is based only on bytes actually written”
Attached disk/storage auto-grows with usage and I'm billed only for bytes actually written rather than pre-provisioned capacityfullproof ↗
“Connect a third-party service once at the org level and every Sprite can access it without individual tokens”
Manage team-level access, secrets, and environment variables centrallypartialproof ↗
“Grant fine-grained access by Sprite name, label, or specific endpoint to enforce least privilege”
Issue scoped/least-privilege API credentials for an agentfullproof ↗
“Rotate a shared credential once to update all Sprites, or revoke access for a single Sprite without affecting others”
Manage team-level access, secrets, and environment variables centrallypartialproof ↗
“Use the same core primitives and API from prototype to massive scale, with no rearchitecting or platform migration needed”
Rely on the same core APIs and primitives from prototype through massive scale, without rearchitecting or migrating platforms as usage growspartialproof ↗
Contradicted (2)
“Run each MCP server in its own isolated Sprite with persistent disk and egress policy, billed per tool call”
Plug MCP servers into this product so it can use their toolsn/aproof ↗
“Fly Machines are hardware-isolated VMs that boot in under a second and scale out to tens of thousands of instances under load”
Deploy instances that boot in under a second and scale to tens of thousands under loaddisputedproof ↗
Undersold (27)
Point an agent at llms.txt or agent-oriented docsfullproof ↗
Run the product headlessly / in CI for automationpartialproof ↗
Drive the product through a documented public APIpartialproof ↗
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 ↗
Deploy my app by simply connecting my repo without manual build configurationpartialproof ↗
Define, deploy, and version my entire architecture with a single configuration filepartialproof ↗
Deploy a project by uploading a folder of files directly, with no Git repo required and the new deployment kept private until I choose to publish itpartialproof ↗
Spin up unlimited isolated environments so my whole team can ship simultaneouslypartialproof ↗
Keep using my existing Git, CI, editor, and framework workflows without adopting proprietary toolingpartialproof ↗
Write code against standard runtime APIs so it runs unmodified across multiple edge platforms instead of being locked into proprietary storage/runtime APIsfullproof ↗
Deploy my application to specific regions closer to my usersfullproof ↗
Rely on automatic compute placement near backend data to optimize latencypartialproof ↗
Handle persistent WebSocket connections from within edge/serverless functions for real-time appspartialproof ↗
Run unmodified Node.js code and npm packages in edge/serverless functions instead of a restricted runtime subsetpartialproof ↗
Write edge functions in languages other than JavaScript such as Python, Go, or Rustfullproof ↗
Rely on load-based autoscaling to absorb large traffic bursts automaticallypartialproof ↗
Run my code on a global edge network close to end usersfullproof ↗
Keep internal service-to-service traffic off the public internet without VPC complexitypartialproof ↗
Do everything through the API that I can do in the UIpartialproof ↗
Choose where my data is stored (region/residency)partialproof ↗
Connect my code to external services like databases, APIs, and storage through native bindings with minimal boilerplate instead of hand-wiring SDKs and credentialspartialproof ↗
Claims outside our story set (1)
Real capability claims found in Fly.io’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.
“Every Sprite gets its own HTTPS URL so apps built by an agent go live in place with no migration step”
source ↗
Business model
Usage-based pay-as-you-go billing for compute, storage and egress, prorated by the second; only minor free allowances, no broad free tier.
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)
