Infrastructure · dated research package
Companies and websites using Fly.io
100 reviewed Fly.io company accounts. Evidence includes company-declared application infrastructure; public application endpoints; public websites. Claims apply only to the recorded property, product or workload.
Find sites built with Fly.io using the source classes below. This Fly.io customer/user list is a dated research cohort; inclusion does not establish a current paid customer relationship.
What the Fly.io list establishes
- Deliverable cohort
- 100 reviewed company accounts
- Package checked
- Source retrieval and observation dates
- A full-cohort source-check range is not summarized on this page. The dated package retains row-level source checks and historical publication limits. The package-check date records offline acceptance, not a source refresh.
- Interpretation
- 100 reviewed Fly.io company accounts. Evidence includes company-declared application infrastructure; public application endpoints; public websites. Claims apply only to the recorded property, product or workload.
Sources and methodology
The package review checks technology attribution, organization or site identity, duplicates and public-source support. Source classes can overlap; counts below use the scope named in each row and are not market-share estimates.
| Source class | Count | What it supports |
|---|---|---|
| Company-declared application infrastructure | 42 | A currently accessible first-party provider or security document names Fly.io and a service role |
| Public application endpoints | 10 | Reviewed public evidence within the recorded property or workload; execution and payment remain unverified. |
| Public websites | 46 | An own-domain website page returned Fly.io-specific HTTP headers |
| Corporate blogs | 2 | The company's blog hostname returned Fly.io-specific HTTP headers |
No public sample is offered for this package. Ask to review the delivery scope before buying.
Limitations of this cohort
- Public sources do not verify paid subscriptions, organization-wide deployment or purchasing intent.
- Source retrieval dates record access; they do not make an older statement or historical deployment current.
- Published contact channels do not establish outreach permission, mailbox deliverability or purchasing authority.
- Supplier and historical disclosures retain their source and age limits; they are not proof of continued use.
- The cohort is not complete coverage. Public signals and vendor statements do not prove current paid use, runtime execution, buying intent, deliverability or outreach permission.
- Source-fetch dates do not refresh historical customer stories or retained observations. Recheck a company's present use before acting.
Request the Fly.io package
The dated export contains 100 reviewed company accounts, organization or website identity, technology attribution, and recorded source and scope information.
Enquire about the dated 100-account Fly.io dataset. Confirm included company fields, source attribution and scope before private delivery.
Delivery is arranged by email. Confirm the dated cohort, price, file formats, license and any promised contact fields before payment. This offer is for the named 100 reviewed company accounts; it does not promise 250 rows or the older catalog's larger inventory.
Enquire about this package