Methodology
Evidence before assertion.
WeBazel is deliberately stricter than a logo wall. Every sentence is scoped to what a public source actually establishes, with dates kept visible.
01 · Publication bar
A claim must match a source.
A company appears only after a reviewer can point to a public source that directly supports the wording on its profile. A source may prove use by a company, team, product, repository, or engineer; those scopes are not interchangeable.
- First-party engineering publications and explicit company talks are preferred.
- Secondary lists are discovery aids, not sole proof.
- Attendance, sponsorship, or a speaker affiliation alone does not prove adoption.
02 · Evidence types
Different receipts prove different things.
Internal use
A company source explicitly describes Bazel in its own build, test, release, or deployment workflow.
Conference talk
An identified employee presents a company-specific Bazel implementation at an official event.
Engineer report
An engineer with public company affiliation describes a concrete Bazel build, repository, migration, or workflow. The claim remains limited to exactly that reported scope.
Open-source use
An organization-owned repository demonstrably builds or tests with Bazel. The claim stays repository-scoped.
Hiring signal
A dated job listing asks for Bazel work. The relevant passage is captured because listings disappear.
Community contribution
A company-affiliated engineer contributes to Bazel. This proves participation, never company-wide use by itself.
Vendor product
First-party product or service documentation proves the vendor relationship described by the claim. It does not, by itself, prove the vendor uses Bazel for every internal build.
03 · Confidence levels
How confidently does each source support its claim?
The confidence level reflects how directly one source supports its precisely worded claim—not company-wide breadth, importance, or whether the evidence is current. Evidence type, claim scope, and the Scheduled, Published, Historical, or Unavailable status remain separate dimensions. Editors can override the normal level when the source itself is materially stronger or weaker.
Direct organizational evidence: a first-party engineering publication describing concrete internal use; an official company-adoption talk by identified employees; or first-party documentation establishing the claimed vendor product.
Strong scoped evidence: a company-owned repository or verified engineer report documenting a concrete build, test, migration, or remote-execution workflow.
Substantive supporting evidence: an official users-list entry, public Bazel tooling owned by the organization, or a talk about upstream/project work rather than the company's adoption.
An indirect organizational signal: a corporate-domain contribution or a specific hiring statement describing an intended Bazel migration or ongoing maintenance work.
A lead only: a generic job requirement, speaker affiliation, sponsorship, attendance, or weak secondary mention. These sources never justify an internal-adoption claim on their own.
04 · Time and history
Public evidence has a date.
An old article does not automatically prove current usage. Profiles say when something was publicly evidenced, and acquired, closed, or former users remain visible as historical records rather than quietly disappearing.
When a job listing or another ephemeral source is removed, its reviewed capture and checksum remain available. The citation is marked as unavailable or historical, and its wording is limited to what the dated listing established rather than being presented as evidence of current use.
Accepted conference sessions may appear before the event as upcoming evidence. They stay visibly marked as scheduled and are rechecked after the event for cancellations, program changes, slides, and recordings.
05 · Ranking
Financial size is the default.
The default order compares cited USD snapshots: market capitalization for listed companies, disclosed valuations for private companies, and clearly labeled transaction values. A parent company's market cap is not used as a subsidiary's value by default; unclear or undisclosed standalone values stay empty and sort last rather than being treated as zero. Google is the narrow exception: as Alphabet's principal operating company and the identity most directly tied to Bazel, its profile uses Alphabet's market cap, explicitly labeled as group value. The optional Featured order balances prominence, evidence quality, recency, and industry and geographic diversity.
The separate Bazel-like tools catalog covers Pants and Pants 2, Buck and Buck2, BuildXL, Soong, reclient, Goma, Siso, JustBuild, and the BuildGrid, BuildStream, and RECC ecosystem, plus Horde, Unreal Build Accelerator, Ya Make, and Please. Evidence is tagged to the specific tool, so organizations can remain in the Bazel directory while also appearing in this adjacent-tool catalog. Bazel-like organizations are hidden from the default directory view and their values are excluded from the headline Bazel-company total, even when a public valuation is available.
Subsidiaries, acquired brands, and successor organizations can keep separate evidence profiles. Financial-group metadata records those relationships without assigning the parent's value to each profile, and the headline combined value counts related organizations only once when they have their own defensible values.
06 · Corrections
Evidence can be challenged.
Each profile exposes its sources so claims can be independently checked. A future public repository will provide the correction channel; until then, unverified leads stay outside the published dataset.