redBus's tech stack
What does redBus use?
redBus (redbus.in) uses at least 15 tools we can see from public records, including Amazon Web Services for hosting, Google Workspace for email and documents, Google Analytics for analytics and Branch for marketing. Last checked .
- Based in
- India
- Founded
- 2006
- Tools found
- 15
- Categories
- 11
- Layers
- 5 of 5
- Last checked
- Oct 2026
redBus'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
4 tools, where the bytes are served from
Hosting & Cloud
CDN & Edge
Application
2 tools, what the product is built with
Frontend
Data & Observability
2 tools, what they measure and store
Go-to-market
4 tools, how they find and keep customers
Ads & Pixels
Company Ops
3 tools, what the team runs on day to day
redBus tech stack FAQ
What tools does redBus use?
We've found 15 tools at redBus (redbus.in). Edge & Hosting: Amazon Route 53, Amazon CloudFront and Amazon Web Services. Application: React. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Google Ads, Microsoft Ads and Branch. Company Ops: Google Workspace, Amazon SES and Zoom. Last checked October 2, 2026.
What cloud does redBus run on?
redBus uses Amazon Web Services for hosting. We found Amazon Web Services through custom domain.
What email provider does redBus use?
redBus uses Google Workspace for email and documents. We found Google Workspace through email records.
What analytics tools does redBus use?
redBus uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
What marketing software does redBus use?
redBus uses Branch for marketing. We found Branch through website code.
Does redBus use Google Workspace?
Yes. We found Google Workspace at redBus through email records. Google Workspace is used by 126,364 companies we track.
How does runsonwhat know what redBus uses?
We read public traces only: redBus'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.