← All company lists

Infrastructure · October 2026 research

Companies and websites using Heroku

Find companies and properties to review for Heroku services and integrations.

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

Choose the Heroku list

100 reviewed company accounts

Package dated

100 reviewed Heroku company accounts. Evidence includes first-party web declaration; first-party pdf declaration; current public http provider header. 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 Heroku 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-04 package. They are not a representative sample of all customers.

Zapier

zapier.com

Direct public signal · Source fetched 2026-10-04

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

Tallyfor

tallyfor.com

Direct public signal · Source fetched 2026-10-04

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

Lexstream

lexstream.io

Direct public signal · Source fetched 2026-10-04

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

Clear Fashion

clear-fashion.com

Direct public signal · Source fetched 2026-10-04

Attributed website or workload only. 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 Heroku research

The disclosed Heroku roles include Redis queues, real-time messaging and datastore backups, alongside website and registered-user database hosting. A component-specific footprint can be useful even when the main application runs elsewhere.

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-04 · reviewed company accounts · WhosBuilt saved-record analysis

How this list was checked

Reviewed public sample source-check dates: 2026-10-04 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 Heroku company accounts. Evidence includes first-party web declaration; first-party pdf declaration; current public http provider header. Claims apply only to the recorded property, product or workload.

Heroku source composition
Source classCountScope
First-party web declaration72Reviewed public evidence within the recorded property or workload; execution and payment remain unverified.
First-party PDF declaration10Reviewed public evidence within the recorded property or workload; execution and payment remain unverified.
Current public HTTP provider header15Reviewed public evidence within the recorded property or workload; execution and payment remain unverified.
Current public DNS CNAME configuration3Reviewed public evidence within the recorded property or workload; execution and payment remain unverified.

Contexts in the Heroku research: Report-described component roles; no claim that every accepted account uses these roles. 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.
  • Published configuration does not establish browser execution or successful service operation.
  • Domain DNS observations do not establish the organization’s wider hosting or procurement relationship.

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 Heroku list

100 reviewed company accounts

Package dated

100 reviewed Heroku company accounts. Evidence includes first-party web declaration; first-party pdf declaration; current public http provider header. 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.