Developer infrastructure · October 2026 research
Find companies and properties to review for Google Cloud Build services and integrations.
The research date describes the saved research. Inclusion does not confirm present use or a paid subscription.
8 reviewed company accounts
Research dated
8 reviewed company accounts: 6 publish Cloud Build configuration in a company-owned public repository and 2 describe their own Cloud Build use on a company page. Current builds, payment and company-wide use are unverified.
Download the contact-free examples (CSV)This page publishes the source mix, findings and four contact-free examples from the 8-account Google Cloud Build cohort. The full account file is not offered.
These approved examples illustrate the 2026-10-12 research. They are not a representative sample of all customers.
promptdriven.ai
Repository configuration · changed within 730 days · Source checked 2026-10-12
Cloud Build recipe that rebuilds the company's CI test image for tests configured to run on Cloud Batch. File last changed 2026-09-08. Builds and Cloud Batch runs unverified.
clickhouse.com
Repository configuration · changed within 730 days · Source checked 2026-10-12
Build, push and Cloud Run deployment recipe for the Hacker News ingestion job of the public ClickHouse playground. File last changed 2025-12-24. Builds unverified.
ubilabs.com
Repository configuration · changed within 730 days · Source checked 2026-10-12
Build configuration in a nested ci folder for the Climate from Space Electron builder image. File last changed 2025-06-12. Builds unverified.
vizzuality.com
Repository configuration · older file history · Source checked 2026-10-12
Build, push and GKE deployment configuration for the Soils Revealed platform. File last changed 2023-06-30. Builds unverified.
WhosBuilt analysis of the saved October 2026 research. Findings describe this selected cohort, not market share.
4 / 6 repository records
4 of the 6 repository records keep their Cloud Build file in a nested folder or under a dot-prefixed name. Each was tied to Cloud Build by a README instruction, a gcloud command, or a Makefile or workflow reference.
A search for a root cloudbuild.yaml alone would miss these four. The path context does not confirm that a trigger or build ran.
Research 2026-10-12 · repository configuration records · WhosBuilt saved-record analysis
2 reviewed examples
In two reviewed records, the Cloud Build file builds or deploys an image for work configured to run on another service: Prompt Driven's tests on Cloud Batch and ClickHouse's ingestion job on Cloud Run.
These pipeline stages come from static files. Successful builds and enabled triggers are unverified.
Research 2026-10-12 · reviewed configuration examples · WhosBuilt saved-record analysis
1 record added on review
Review of saved sources added one record, from Tarosky, bringing the list to 8. Its recipe builds the company's own Go tool image and pushes it only from a gated branch. The file last changed on 2019-10-31, in a commit labelled as a prototype.
The record is dated history for one internal tool. It says nothing about current Cloud Build use for the company's applications or clients.
Research 2026-10-12 · accepted company accounts · WhosBuilt saved-record analysis
Sources checked on 2026-10-12, 02:45–02:59 UTC. Configuration files were last changed between 2019-10-31 and 2026-09-08. One company article is dated 2021-03-15 and one company page has no established publication date. Check times record retrieval, not current use.
8 reviewed company accounts: 6 publish Cloud Build configuration in a company-owned public repository and 2 describe their own Cloud Build use on a company page. Current builds, payment and company-wide use are unverified.
| Source class | Count | Scope |
|---|---|---|
| Repository configuration · changed within 730 days | 3 | A Cloud Build YAML file at a checked public default-branch revision, last changed within 730 days of the check. A file change does not confirm enabled triggers or builds. |
| Repository configuration · older file history | 3 | The same configuration check, with the file last changed between 2019 and 2023. Treat these records as dated history. |
| Company engineering article · dated | 1 | A 2021 article about automating the company's own blog builds and publication with Cloud Build. |
| Company page · undated | 1 | A company self-description of Cloud Build deployments with no established publication date and no repository file. |
Four of six configuration files are not a root cloudbuild.yaml: Denominator: the 6 accepted repository configuration records, including the record added on review. Classify each accepted configuration path at the checked revision. WhosBuilt analysis of accepted fields in the dated October 12 cohort; no source refresh.
Two recipes build images for work on another service: Selected examples from the accepted repository records; not a classification of every record. Read the stated role of each service in the two accepted configuration files. WhosBuilt analysis of accepted fields in the dated October 12 cohort; no source refresh.
The added record is a 2019 recipe for the company's own tool: One promoted record among 8 accepted accounts; no new sources were collected. Purpose check of the pinned recipe: an own image build plus branch-gated publication. A generic compatibility example would not qualify. WhosBuilt analysis of accepted fields in the dated October 12 cohort; no source refresh.
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.