27
Reviewed scope
operating brand/group identities
Data platforms · October 2026 research
Review 27 operating brand/group identities supported by company-published ClickHouse workflow statements. The research includes dated and undated disclosures. Provider designations, supplier affiliations, query interfaces and product-architecture mentions alone do not qualify as operator workflows.
Research dated 2026-10-25. Original source dates and website scope stay with the records.
27 operating brand/group identities
Research dated
Contact-free research examples · CSV
Review 27 operating brand/group identities supported by company-published ClickHouse workflow statements. The research includes dated and undated disclosures. Provider designations, supplier affiliations, query interfaces and product-architecture mentions alone do not qualify as operator workflows.
Download the 3-row CSV preview27
operating brand/group identities
Sources were checked on 24–25 October 2026. Publication, revision and check dates stay separate; none establishes current runtime.
Research summary and contact-free examples only. Full-file commercial delivery and source reproduction rights remain unresolved.
CSV columns: name · domain · sourceClass · checkedOn · scope
These approved examples illustrate the 2026-10-25 research. They are not a representative sample of all customers.
cloudflare.com
Company engineering article · dated · 2026-10-25
A company engineering article describes storing data across ClickHouse clusters. The primary page was published in May 2026 and revised in July 2026; current runtime and paid status were not verified.
mux.com
Company engineering article · dated · 2026-10-25
A company engineering article describes ClickHouse for Mux Data video analytics and usage aggregation. Publication metadata is December 2024 and revision metadata December 2025; current runtime and paid status were not verified.
withorb.com
Company engineering article · undated · 2026-10-25
An undated company article describes ClickHouse for usage-event storage and SQL metric calculations. Current runtime, paid status and whole-company adoption were not verified.
WhosBuilt analysis of the saved October 2026 research. Findings describe this selected cohort, not market share.
15 of 27
15 of the 27 accepted operator-workflow claims have a reviewed page-publication date. The other 12 have no established publication date; revision and check dates are kept separate.
Historical and undated operator disclosures are included. Paid status, whole-company adoption and verified current independence remain unestablished.
Research 2026-10-25 · accepted operator-workflow claims · WhosBuilt saved-record analysis
A company naming a hosting provider or supporting a ClickHouse-compatible interface does not, by itself, establish that company operating a ClickHouse workload.
Historical and undated operator disclosures are included. Paid status, whole-company adoption and verified current independence remain unestablished.
Research 2026-10-25 · operator admission rule · WhosBuilt saved-record analysis
Source checks span 2026-10-24–2026-10-25. Retained observations and examples keep their original dates.
Review 27 operating brand/group identities supported by company-published ClickHouse workflow statements. The research includes dated and undated disclosures. Provider designations, supplier affiliations, query interfaces and product-architecture mentions alone do not qualify as operator workflows.
| Source class | Count | Scope |
|---|---|---|
| Company engineering article · dated | Not separately counted | operating brand/group identities |
| Company engineering article · undated | Not separately counted | operating brand/group identities |
Publication dates: operating brand/group identities Sources were checked on 24–25 October 2026. Publication, revision and check dates stay separate; none establishes current runtime.
Operator workflow admission: operating brand/group identities Sources were checked on 24–25 October 2026. Publication, revision and check dates stay separate; none establishes current runtime.
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.