← All company lists

Developer infrastructure · October 2026 research

Companies and websites using GitHub Actions

Find companies and properties to review for GitHub Actions services and integrations.

The research date describes the saved package. Inclusion does not confirm present use or a paid subscription.

Choose the GitHub Actions list

100 reviewed company accounts

Package dated

100 reviewed GitHub Actions company accounts. GitHub Actions workflow configuration in company-owned public repositories. Evidence applies to the recorded website, product or workload and its source date; current paid use and whole-organization deployment remain unverified. Claims apply only to the recorded property, product or workload.

Price and delivery by enquiry

Enquire about this packageDownload the contact-free CSV preview

What is included

Enquire about the dated 100-account GitHub Actions dataset. Confirm included company fields, source attribution and scope before private delivery.

Organization or website identity
Technology attribution
Recorded source and check dates
Property or workload scope

Reviewed contact-free examples

These approved examples illustrate the 2026-10-05 package. They are not a representative sample of all customers.

Supabase

supabase.com

Website configuration signal · Signal observed 2026-10-05

Restricted to the attributed property or product. Paid use and company-wide deployment unverified.

Docker

docker.com

Website configuration signal · Signal observed 2026-10-05

Restricted to the attributed property or product. Paid use and company-wide deployment unverified.

Stripe

stripe.com

Website configuration signal · Signal observed 2026-10-05

Attributed website or workload only. Paid use and company-wide deployment unverified.

Plausible Analytics

plausible.io

Website configuration signal · Signal observed 2026-10-05

Restricted to the attributed property or product. Paid use and company-wide deployment unverified.

What we found in this list

WhosBuilt analysis of the saved October 2026 package. Findings describe this selected cohort, not market share.

Contexts in the GitHub Actions research

This cohort favors commercial developer products with public repositories. Selected workflows include documentation builds and repository maintenance, so public workflow configuration does not establish a private production-delivery pipeline.

Selected research cohort. Published configuration, declarations and supplier reports do not verify current runtime, paid use or buying intent. Source ages and property boundaries remain as recorded.

Package 2026-10-05 · reviewed company accounts · WhosBuilt saved-record analysis

How this list was checked

Reviewed public sample source-check dates: 2026-10-05 UTC. This range covers the visible examples, not every account. Full-cohort source and historical publication dates remain attached to the delivered rows; package acceptance is not a source refresh.

100 reviewed GitHub Actions company accounts. GitHub Actions workflow configuration in company-owned public repositories. Evidence applies to the recorded website, product or workload and its source date; current paid use and whole-organization deployment remain unverified. Claims apply only to the recorded property, product or workload.

GitHub Actions source composition
Source classCountScope
Company-owned public repository workflow configurations100Published configuration or resource reference; execution, paid use and organization-wide coverage are unverified.

Contexts in the GitHub Actions research: Report cohort-selection characteristic; public-repository use context rather than execution proof. 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.

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.

Choose the GitHub Actions list

100 reviewed company accounts

Package dated

100 reviewed GitHub Actions company accounts. GitHub Actions workflow configuration in company-owned public repositories. Evidence applies to the recorded website, product or workload and its source date; current paid use and whole-organization deployment remain unverified. Claims apply only to the recorded property, product or workload.

Price and delivery by enquiry

Enquire about this packageDownload the contact-free CSV preview

Paid files are licensed for internal use; no resale or redistribution.