StartupBus's tech stack
What does StartupBus use?
StartupBus (startupbus.com) uses at least 11 tools we can see from public records, including GitHub Pages for hosting, Google Workspace for email and documents, Google Analytics for analytics and Fastly for content delivery. Last checked .
- Industry
- Internet
- Size
- 11–50 employees
- Based in
- San Francisco, United States
- Founded
- 2010
- Company page
- Tools found
- 11
- Categories
- 8
- Layers
- 5 of 5
- Last checked
- Oct 2026
StartupBus'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
3 tools, where the bytes are served from
Application
4 tools, what the product is built with
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
1 tool, how they find and keep customers
Ads & Pixels
Company Ops
2 tools, what the team runs on day to day
Workspace
Security & Compliance
StartupBus tech stack FAQ
What tools does StartupBus use?
We've found 11 tools at StartupBus (startupbus.com). Edge & Hosting: GoDaddy, Fastly and GitHub Pages. Application: Google Fonts, Vimeo and YouTube. Data & Observability: Google Analytics. Go-to-market: Meta Pixel. Company Ops: Google Workspace and Detectify. Last checked October 4, 2026.
What cloud does StartupBus run on?
StartupBus uses GitHub Pages for hosting. We found GitHub Pages through custom domain, DNS records and website code.
What email provider does StartupBus use?
StartupBus uses Google Workspace for email and documents. We found Google Workspace through email records.
What analytics tools does StartupBus use?
StartupBus uses Google Analytics for analytics. We found Google Analytics through website code.
Does StartupBus use Google Workspace?
Yes. We found Google Workspace at StartupBus through email records. Google Workspace is used by 126,364 companies we track.
How does runsonwhat know what StartupBus uses?
We read public traces only: StartupBus'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.