← All company lists

Developer infrastructure · October 2026 research

Companies and websites using GitLab CI

Find companies and properties to review for GitLab CI services and integrations.

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

Choose the GitLab CI list

61 reviewed company accounts

Package dated

61 reviewed GitLab CI company accounts. Software delivery disclosures, supplier stories and public repository pipeline configuration. Claims apply 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 61-account GitLab CI 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.

Agoda

agoda.com

supplier case study · Source checked 2026-10-04

Agoda DevOps teams; no claim about other Booking Holdings businesses. Current payment and runtime unverified.

Airwallex

airwallex.com

supplier case study · Source checked 2026-10-04

Software delivery pipelines described in the supplier story. Current payment and runtime unverified.

Alteryx

alteryx.com

historical supplier case study · Source checked 2026-10-04

Engineering build migration described in an older supplier story. Current payment and runtime unverified.

Baserow

baserow.io

first party public configuration · Source checked 2026-10-05

Baserow develop-branch CI configuration; supports manually controlled jobs as well as rule-driven pipelines; default branch and runtime unverified. Current payment and runtime unverified.

What we found in this list

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

Pipeline configuration has its own scope

Retained repository scopes include manually controlled jobs as well as rule-driven pipelines. Supplier stories describe software delivery at named teams and products.

For CI migration work, inspect the pipeline configuration and team boundary before assuming that jobs execute automatically or across the whole organization.

Selected dated research cohort; present runtime, paid use, organization-wide deployment and outreach permission remain unverified. Descriptions and supplier claims apply only to their recorded scope and source date.

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

How this list was checked

Original cohort dated 2026-10-05. Retained source-check dates span 2026-10-04 to 2026-10-05 UTC; missing original check or review times remain unknown. Recovery revision reviewed 2026-10-11. Recovery is not a source refresh or a current adoption date. Historical publication dates and account scopes remain attached to delivered rows.

61 reviewed GitLab CI company accounts. Software delivery disclosures, supplier stories and public repository pipeline configuration. Claims apply to the recorded property, product or workload.

GitLab CI source composition
Source classCountScope
supplier case studyNot separately countedSupplier-reported relationship at the original source date; present use remains unverified.
historical supplier case studyNot separately countedSupplier-reported relationship at the original source date; present use remains unverified.
first party public configurationNot separately countedSaved public configuration or resource reference; execution and organization-wide adoption are unverified.
first party operating disclosureNot separately countedSaved scoped organization disclosure; authorization or a publication is not independent runtime proof.
first party engineering disclosureNot separately countedSaved scoped organization disclosure; authorization or a publication is not independent runtime proof.
historical first party engineering disclosureNot separately countedSaved scoped organization disclosure; authorization or a publication is not independent runtime proof.
first party public pipeline recordNot separately countedSaved scoped organization disclosure; authorization or a publication is not independent runtime proof.

Pipeline configuration has its own scope: Qualitative synthesis of retained accepted workload scopes; presence only, with no prevalence or market-share claim. WhosBuilt analysis of saved accepted fields for the dated October research cohort; no source refresh.

Original cohort and source dates are retained. The October 11 revision review does not establish adoption or continued deployment on that date. Missing dates and historical statements retain their original limitations.

  • Public sources do not confirm current paid subscriptions, live runtime, organization-wide deployment or purchasing intent.
  • Source retrieval dates record access; they do not make older statements or historical deployments current.
  • Some accounts have no retained contact. Published routes retain their purpose restrictions and grant no outreach permission or deliverability guarantee.

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 GitLab CI list

61 reviewed company accounts

Package dated

61 reviewed GitLab CI company accounts. Software delivery disclosures, supplier stories and public repository pipeline configuration. Claims apply 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.