BuildBuddy's tech stack
What does BuildBuddy use?
BuildBuddy (buildbuddy.io) uses at least 8 tools we can see from public records, including GitHub Pages for hosting, Microsoft 365 for email and documents, Google Analytics for analytics and Fastly for content delivery. Last checked .
“BuildBuddy provides enterprise features for Bazel — the open source…”
- Industry
- Infrastructure
- Size
- 11–50 employees
- Based in
- San Francisco, United States
- Company page
- Tools found
- 8
- Categories
- 7
- Layers
- 5 of 5
- Last checked
- Oct 2026
BuildBuddy's stack, layer by layer
Each tool links to the other companies we've found using it. The label says what kind of public trace gave it away.
Edge & Hosting
2 tools, where the bytes are served from
Hosting & Cloud
CDN & Edge
Application
1 tool, what the product is built with
Search
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
1 tool, how they find and keep customers
Marketing
Company Ops
3 tools, what the team runs on day to day
Email Delivery
BuildBuddy tech stack FAQ
What tools does BuildBuddy use?
We've found 8 tools at BuildBuddy (buildbuddy.io). Edge & Hosting: Fastly and GitHub Pages. Application: Algolia. Data & Observability: Google Analytics. Company Ops: Microsoft 365, Google Workspace and SendGrid. Last checked October 2, 2026.
What cloud does BuildBuddy run on?
BuildBuddy uses GitHub Pages for hosting. We found GitHub Pages through custom domain and website code.
What email provider does BuildBuddy use?
BuildBuddy uses Microsoft 365 and Google Workspace for email and documents. We found Microsoft 365 through DNS verification records.
What analytics tools does BuildBuddy use?
BuildBuddy uses Google Analytics for analytics. We found Google Analytics through website code.
Does BuildBuddy use Microsoft 365?
Yes. We found Microsoft 365 at BuildBuddy through DNS verification records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what BuildBuddy uses?
We read public traces only: BuildBuddy's DNS and email records, certificate logs, the code its website loads, and published subprocessor lists. A tool is listed only when a direct record backs it up. DNS is rechecked weekly and the website monthly.
We read public traces only: DNS and email records, certificate logs, website code and published subprocessor lists. A tool is listed when a direct record backs it up, and dropped when a recheck no longer finds it. Is this your company? See how to opt out.