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.
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.
Fly.io source composition | Source class | Count | Scope |
|---|
| 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 |
|---|
Contexts in the Fly.io research: Qualitative declared compute jobs, compared with website/blog response scope. WhosBuilt review of the saved accepted report and approved examples; no source refresh.
Accepted report describes the retained list. Qualitative roles show presence, not prevalence. Counts refer only to the named recorded classifications; no source-by-context intersections are released. The displayed date is the package date. Source dates remain as recorded in the package; no source was refreshed for this analysis.
- 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.
Source access dates do not refresh historical statements. Static signals do not prove execution, payment or buying intent. Published contacts do not establish deliverability or outreach permission.