SaaS Ranking
Menu

Fly.io: what they publish

fly.io · Cloud hosting · checked 2026-10-12

39/100EBand E

Rank 12 of 35 in Cloud hosting, where the median is 35.

Public transparency score, not a product or security rating. Latest check: 2026-10-12. How the score works.

Evidence at a glance

Choose a check to see its source, date and scope.

Not found means not found at the addresses we checked. Not measured means we could not complete the check.

Start a vendor reviewDownload evidence (CSV)

Overview

4 days since the newest dated result, 4 since the oldest. 12 of 12 criteria have a measured result in the last 30 days. Failed checks and undated results are excluded.

Evidence freshness is a statement about our measurement and is kept apart from the transparency score, which is frozen at v1. How good our own measurement is.

Transparency labelsaas-ranking.com

Fly.io

fly.io · Cloud hosting

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
E 39of 100 Rank 12 of 35

Published commitments4 of 9 found

Measured behaviour0 of 3 found

Checked 2026-10-12. Every line links the page we found it on. A cross means we found nothing at the addresses we checked, not that the vendor has no such document. A transparency score, not a product rating.

Downloads include all checks, source URLs, dates and the snapshot ID for your procurement file. We do not issue badges.

The label is the whole measurement in one object: every criterion with its weight, the band, and the date. Public transparency score, not a product or security rating.

Every line in it links the page we found the result on, or lists the addresses we checked. A cross means we found nothing there, not that Fly.io has no such document.

Where Fly.io sits in Cloud hosting

  1. A1 3%
  2. B2 6%
  3. C2 6%
  4. D6 17%
  5. E14 40%
  6. F10 29%
35 vendors with a score; 2 more without a score because we could measure too little. Bands have fixed thresholds, see how the score works.

The band of Fly.io is marked. Vendors without a score are the ones where we could measure too few criteria to rank them – a gap on our side, counted separately.

What Fly.io states

The exact figures and names we read off the pages linked below, with the sentence they stand in. This is what they publish, not what we verified about their systems.

Gaps, heaviest first

✗

Data processing agreement (DPA)

weight 3 of 3

No data processing agreement found.

Checked 8 addresses on 2026-10-12.

Show the 8 addresses we checked
  1. https://fly.io/legal/dpa – reached, no match (HTTP 404)
  2. https://fly.io/dpa – reached, no match (HTTP 404)
  3. https://fly.io/legal/data-processing-agreement – reached, no match (HTTP 404)
  4. https://fly.io/data-processing-agreement – reached, no match (HTTP 404)
  5. https://fly.io/legal/data-processing-addendum – reached, no match (HTTP 404)
  6. https://fly.io/legal/gdpr – reached, no match (HTTP 404)
  7. https://fly.io/trust/dpa – reached, no match (HTTP 404)
  8. https://fly.io/privacy/dpa – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Across the market: Data processing agreement in Cloud hosting: 9 of 35 companies

✗

Status page with incident history

weight 2 of 3

We found this behind a sign-in, so it is not published openly.

Seen at https://fly.io/app/sign-in?return_to=%2Fstatus · checked 2026-10-12

Show the 3 addresses we checked
  1. https://status.fly.io/ – reached, no match (HTTP 200)
  2. https://fly.io/status – found, but behind a sign-in
  3. https://fly.io.statuspage.io/ – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

Across the market: Status page with history in Cloud hosting: 17 of 36 companies

✗

HTTPS enforced with HSTS

weight 2 of 3

No enforced HTTPS with HSTS found.

Checked 2 addresses on 2026-10-12.

Show the 2 addresses we checked
  1. http://fly.io/ – redirects to https://fly.io/
  2. https://fly.io/ – no HSTS header

Is this wrong? Send us the URL

Across the market: HTTPS enforced with HSTS in Cloud hosting: 26 of 37 companies

✗weight 2 of 3

Third-party requests seen on the first load, before any interaction.

  • Third-party hosts we saw on the first load 3 googletagmanager.com, stripe.com, stripe.network.
    Show the 3 exact wordings

    www.googletagmanager.com

    Read at https://fly.io/

    js.stripe.com, m.stripe.com

    Read at https://fly.io/

    m.stripe.network

    Read at https://fly.io/

Checked 1 address on 2026-10-12.

Show the 1 address we checked
  1. https://fly.io/ – third-party requests before any interaction: js.stripe.com, m.stripe.com, m.stripe.network, www.googletagmanager.com

Is this wrong? Send us the URL

Across the market: No third-party tracking before consent in Cloud hosting: 5 of 37 companies

✗

Notice before subprocessors change

weight 2 of 3

No commitment to give notice before subprocessors change found.

Checked 8 addresses on 2026-10-12.

Show the 8 addresses we checked
  1. https://fly.io/legal/subprocessors – reached, no match (HTTP 404)
  2. https://fly.io/subprocessors – reached, no match (HTTP 404)
  3. https://fly.io/sub-processors – reached, no match (HTTP 404)
  4. https://fly.io/legal/dpa – reached, no match (HTTP 404)
  5. https://fly.io/dpa – reached, no match (HTTP 404)
  6. https://fly.io/legal/data-processing-agreement – reached, no match (HTTP 404)
  7. https://fly.io/trust/subprocessors – reached, no match (HTTP 404)
  8. https://fly.io/legal/sub-processors – reached, no match (HTTP 200)

Is this wrong? Send us the URL

Across the market: Notice before subprocessors change in Cloud hosting: 9 of 35 companies

✗

Uptime SLA with a figure

weight 1 of 3

No uptime figure found.

Checked 6 addresses on 2026-10-12.

Show the 6 addresses we checked
  1. https://fly.io/legal/sla – reached, no match (HTTP 404)
  2. https://fly.io/sla – reached, no match (HTTP 404)
  3. https://fly.io/legal/service-level-agreement – reached, no match (HTTP 404)
  4. https://fly.io/trust/sla – reached, no match (HTTP 404)
  5. https://fly.io/uptime – reached, no match (HTTP 404)
  6. https://fly.io/legal/uptime-sla – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Across the market: Uptime SLA with a figure in Cloud hosting: 8 of 35 companies

✗

security.txt (RFC 9116)

weight 1 of 3

No security.txt found.

Checked 1 address on 2026-10-12.

Show the 1 address we checked
  1. https://fly.io/.well-known/security.txt – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Across the market: security.txt (RFC 9116) in Cloud hosting: 17 of 35 companies

✗

Named privacy contact (DPO or privacy address)

weight 1 of 3

No named privacy contact found.

Checked 7 addresses on 2026-10-12.

Show the 7 addresses we checked
  1. https://fly.io/legal/privacy – reached, no match (HTTP 404)
  2. https://fly.io/privacy – reached, no match (HTTP 404)
  3. https://fly.io/privacy-policy – reached, no match (HTTP 404)
  4. https://fly.io/legal/privacy-policy – reached, no match (HTTP 200)
  5. https://fly.io/legal/privacy-notice – reached, no match (HTTP 404)
  6. https://fly.io/trust/privacy – reached, no match (HTTP 404)
  7. https://fly.io/datenschutz – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Across the market: Named privacy contact in Cloud hosting: 20 of 35 companies

Evidence

The full source lists sit behind these two groups, so that the answer above stays readable.

Published, with a source 4
✓

Subprocessors: the published list

weight 3 of 3

The actual list is published, not just a promise to keep one.

Source: https://fly.io/legal/sub-processors/ · checked 2026-10-12

Across the market: Subprocessor list in Cloud hosting: 3 of 35 companies

✓

Data location: where they say data is hosted

weight 3 of 3

The hosting location is stated on a public page.

  • Locations named next to the hosting wording European Union, United States. This does not establish the company’s headquarters.
    Show the 2 exact wordings

    Our PostHog instance is hosted in the European Union (PostHog Cloud EU), and we serve its code from our own servers.

    Read at https://fly.io/legal/privacy-policy/

    e personal information on our servers, you are consenting to our storage of that information on our servers, which are in the United States.

    Read at https://fly.io/legal/privacy-policy/

Source: https://fly.io/legal/privacy-policy/ · checked 2026-10-12

Across the market: Data location stated in Cloud hosting: 11 of 35 companies

✓

Public pricing with figures

weight 2 of 3

Actual numbers on a public page.

Source: https://fly.io/pricing/ · checked 2026-10-12

Across the market: Public pricing in Cloud hosting: 27 of 35 companies

✓

Certifications named (SOC 2, ISO 27001)

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

  • Named on that page ISO/IEC 27001 (not counted: the sentence does not carry it), SOC 2 Type II. The sentence we kept does not carry this finding on its own, so it counts in no list and no figure.
    Show the 2 exact wordings

    Yeah, We’re SOC 2 Type 2 We're certified , our hardware runs in ISO 27001 datacenters, we do BAAs, and we answer security questionnaires.

    Read at https://fly.io/security/

    Yeah, We’re SOC 2 Type 2 We're certified , our hardware runs in ISO 27001 datacenters, we do BAAs, and we answer secu

    Read at https://fly.io/security/

Source: https://fly.io/security/ · checked 2026-10-12

Across the market: Certifications named in Cloud hosting: 16 of 36 companies

History

100 0 2026-10-05: 48 of 1002026-10-12: 39 of 100 2026-10-05 2026-10-12
Score over the last 2 runs we measured Fly.io in: 48 (2026-10-05), 39 (2026-10-12).

Prepare your vendor review

A source is a starting point. Check the product, plan, legal entity and date before treating it as evidence for your purchase. These questions do not change the transparency score.

Fly.io

4 found · 8 not found · 0 not measured across 12 public checks.

12 of 12 criteria have a measured result from the last 30 days. Oldest dated result: 2026-10-12.

Investigate 8 open evidence questions
  1. Data processing agreement

    Please share the current data processing agreement for the product and plan we are considering, including its annexes and signing process.

    Inspect this check
  2. Status page with history

    Where can we review incident history for the service we will use, and how do we subscribe to incident updates?

    Inspect this check
  3. Uptime SLA with a figure

    Which availability commitment applies to our plan? Please include the measurement window, exclusions and credit claim process.

    Inspect this check
  4. HTTPS enforced with HSTS

    How is HTTPS enforced on the product and sign-in domains we will use? Please distinguish those domains from the public website.

    Inspect this check
  5. No third-party tracking before consent

    Which third-party requests occur before a visitor makes a choice, and for what purpose? Please distinguish the public website from the product.

    Inspect this check
  6. security.txt (RFC 9116)

    Where should we report a vulnerability, and what acknowledgement and follow-up process should we expect?

    Inspect this check
  7. Notice before subprocessors change

    How will you notify us before a subprocessor changes, with how much notice, and what response options apply to our contract?

    Inspect this check
  8. Named privacy contact

    Which privacy contact handles requests for our account, and what escalation path should we use?

    Inspect this check

Compare

A shortlist holds up to six vendors across categories and lives entirely in the address of its page: share the link, bookmark it, put it in a ticket. Nothing is stored, so we do not know it exists.

Compared with

Each comparison lists only the criteria where the two differ, with the source for every one. All comparisons.