Fly.io Sub-processors

Last updated: 2026-10-24

Fly.io uses the following sub-processors to assist in providing our services.

Sub–processor Location Activity
Anthropic United States AI-assisted log analysis, support responses, and signup classification
AWS United States Account management, backup storage, engineering support
CacheNetworks United States Hosting provider
ClickHouse United States Audit log storage for control plane API requests
Customer.io United States Newsletters and transactional email
DataPacket United Kingdom Hosting provider
Depot United States Customer software builds
Discord United States Customer support communication
Discourse United States Customer support communication
Dropbox Sign United States Agreement signing (DPA, BAA, NDA)
Google United States Productivity suite and cloud infrastructure
Help Scout United States Customer support communication
Honeycomb United States Tracing and observability
HubSpot United States Customer relationship management
incident.io United Kingdom Incident response and on-call management
IPinfo United States Signup IP geolocation and risk scoring
Latitude United States Hosting provider
LaunchDarkly United States Feature rollout management
Mailgun United States Transactional email
Metronome United States Billing
NetActuate United States Hosting provider
OpenAI United States Incident summary generation
OpenRouter United States AI model routing for internal tooling
PeopleDataLabs United States Signup risk scoring
Plain United Kingdom Customer support communication
PostHog Germany Product analytics
RudderStack United States Product analytics
Sentry United States Error reporting
Slab United States Knowledge management
Slack United States Customer support communication
Snowflake United States Customer relationship management
Stripe United States Payment processing, fraud and abuse prevention
Tigris United States Object storage for Sprites
Timescale United States Time-series metrics storage
Vultr United States Hosting provider

AI vendors

Anthropic, OpenAI and OpenRouter are used only by Fly.io’s internal tooling, under our AI usage policy. We never send the contents of your volumes, or the bodies of requests to your applications, to an AI vendor. OpenRouter routes a request to a third-party model provider; our policy limits its internal use to providers whose terms prohibit training on the content, and OpenRouter itself does not train on inputs or outputs.

During support and abuse investigations, the data that can be processed is account and organization metadata, support ticket text, and platform log lines, which include whatever your application writes to stdout. For Managed Postgres, our support tooling can also process a cluster’s Postgres logs and, when a Fly.io operator runs a read-only diagnostic query during an investigation, the results of that query.

Changes

Additions to and removals from this list are recorded here. Under section 6.3 of our Data Processing Agreement, a new or replacement sub-processor is listed here at least 30 days before it processes customer personal data, this page is the notice of that appointment, and objections on data protection grounds may be sent to compliance@fly.io within 10 days of the listing.

  • 2026-10-24: Added ClickHouse and OpenRouter. Neither processes customer personal data before 2026-11-23.
  • 2026-09-24: Added Dropbox Sign, incident.io, and Vultr.
  • 2026-05-18: Removed Equinix and OVH.