Stripe
stripe.com
Repository configuration · changed within 730 days · Source checked 2026-10-12
Bitrise configuration in a company repository at a pinned public default-branch revision; file last changed 2026-10-09. Builds and paid use unverified.
← All company lists
Developer infrastructure · October 2026 research
Companies and websites using Bitrise
Find companies and properties to review for Bitrise services and integrations.
The research date describes the saved package. Inclusion does not confirm present use or a paid subscription.
Choose the Bitrise list
54 reviewed company accounts
Package dated
54 reviewed company accounts: 20 publish Bitrise configuration in a company-owned public repository and 34 describe a Bitrise setup they built or ran in a company article or page. Two of those articles describe a completed move away from Bitrise. Current builds, payment and company-wide use are unverified.
Price and delivery by enquiry
Enquire about this packageDownload the contact-free CSV previewWhat is included
Enquire about the dated 54-account Bitrise CSV/JSON package, with repository configuration and company articles kept separate. Confirm company fields, recorded dates and scope before private delivery. The public preview contains four approved rows with contacts removed.
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-12 package. They are not a representative sample of all customers.
Mozilla Corporation
mozilla.org
Repository configuration · changed within 730 days · Source checked 2026-10-12
Bitrise configuration in a company repository at a pinned public default-branch revision; file last changed 2026-10-08. Builds and paid use unverified.
Paysafe
paysafe.com
Repository configuration · changed within 730 days · Source checked 2026-10-12
Bitrise configuration in a company repository at a pinned public default-branch revision; file last changed 2026-10-06. Builds and paid use unverified.
Sailthru
sailthru.com
Repository configuration · changed within 730 days · Source checked 2026-10-12
Bitrise configuration in a company repository at a pinned public default-branch revision; file last changed 2026-09-30. Builds and paid use unverified.
What we found in this list
WhosBuilt analysis of the saved October 2026 package. Findings describe this selected cohort, not market share.
34 / 54 · 63%
Company articles supply most of the 54 accounts
34 of 54 accepted accounts (63%) come from company-authored articles or pages about a Bitrise setup they built or ran. The other 20 publish Bitrise configuration in a public company repository.
Check the article date and the named team or app before treating an article record as current mobile CI work.
An article describes the team, app or project it names at publication. It does not show current builds or company-wide use.
Package 2026-10-12 · accepted company accounts · WhosBuilt saved-record analysis
21 / 32 · 65.6%
Most dated articles describe 2017–2021 setups
21 of 32 dated company articles (65.6%) were published between 2017 and 2021, 4 in 2022 and 7 between 2023 and 2025. Two dated articles describe completed migrations away from Bitrise.
Retrieval on 2026-10-12 does not make an older article current. The two former-use records stay in the list as implementation history, not as current Bitrise customers.
Package 2026-10-12 · dated company articles · WhosBuilt saved-record analysis
13 / 20 changed within 730 days
13 of 20 configuration files changed in the last two years
13 of the 20 repository records have a Bitrise file last changed within 730 days of the 2026-10-12 check, 7 of them in 2026. The other 7 were last changed between 2020 and 2022.
A recent file change does not confirm an enabled pipeline or a paid plan. An older last-change date does not show that builds stopped.
Package 2026-10-12 · repository configuration records · WhosBuilt saved-record analysis
3 / 20 repository records
Three repository records test the companies' own Bitrise steps
3 of the 20 repository records belong to companies that maintain Bitrise steps (a Flutter step, an upload step and an APK metadata step) and test them with their own Bitrise workflow.
A step test workflow does not identify the CI provider used by these companies' clients or for their private apps.
Package 2026-10-12 · repository configuration records · WhosBuilt saved-record analysis
How this list was checked
Sources checked on 2026-10-12, 02:43–06:31 UTC. Configuration files were last changed between 2020-06-02 and 2026-10-09. Company articles are dated 2017-12-21 to 2025-10-08, and two have no established publication date. Check times record retrieval, not current use.
54 reviewed company accounts: 20 publish Bitrise configuration in a company-owned public repository and 34 describe a Bitrise setup they built or ran in a company article or page. Two of those articles describe a completed move away from Bitrise. Current builds, payment and company-wide use are unverified.
| Source class | Count | Scope |
|---|---|---|
| Repository configuration · changed within 730 days | 13 | A Bitrise YAML file at a checked public default-branch revision, last changed within 730 days of the check. A file change does not confirm enabled builds. |
| Repository configuration · older file history | 7 | The same configuration check, with the file last changed between 2020 and 2022. Treat these records as dated history. |
| Company article or page · dated | 32 | The company describes a Bitrise setup it built or ran for a named team, app or project at the publication date. Two of these articles describe a completed migration away from Bitrise. |
| Company article or page · undated | 2 | A company-authored description without an established publication date: one has conflicting date markers and one has none. |
Company articles supply most of the 54 accounts: Denominator: all 54 accepted accounts; each account has one source class. Count accepted accounts by source class: public repository configuration or company-authored implementation article. WhosBuilt analysis of accepted fields in the dated October 12 cohort; no source refresh.
Most dated articles describe 2017–2021 setups: Denominator: the 32 accepted company articles with a reviewed publication date. Two undated articles are excluded from the year counts. Group reviewed publication dates by year. WhosBuilt analysis of accepted fields in the dated October 12 cohort; no source refresh.
13 of 20 configuration files changed in the last two years: Denominator: the 20 accepted repository configuration records. Compare the last commit that changed the configuration file at the checked revision with the check date. Repository pushes that did not touch the file do not count. WhosBuilt analysis of accepted fields in the dated October 12 cohort; no source refresh.
Three repository records test the companies' own Bitrise steps: Denominator: the 20 accepted repository configuration records. Reviewed repository purpose for each accepted configuration record. WhosBuilt analysis of accepted fields in the dated October 12 cohort; no source refresh.
- One configuration file or company document supports each account. Other repositories, private apps and later changes were not checked.
- Public files and articles do not confirm current builds, a paid plan, company-wide use or buying intent. Agency articles count the agency that did the work; its clients are not added as accounts.
- The cohort came from public repository searches and company engineering articles, so it leans toward teams that publish their tooling. Counts describe this list, not Bitrise's customer base.
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 Bitrise list
54 reviewed company accounts
Package dated
54 reviewed company accounts: 20 publish Bitrise configuration in a company-owned public repository and 34 describe a Bitrise setup they built or ran in a company article or page. Two of those articles describe a completed move away from Bitrise. Current builds, payment and company-wide use are unverified.
Price and delivery by enquiry
Enquire about this packageDownload the contact-free CSV previewPaid files are licensed for internal use; no resale or redistribution.