runsonwhat

BridgeBase's tech stack

What does BridgeBase use?

BridgeBase (bridgebase.dev) uses at least 9 tools we can see from public records, including Amazon Web Services for hosting, Google Workspace for email and documents, Discord for customer support and Google Analytics for analytics. Last checked .

Tools found
9
Categories
8
Layers
5 of 5
Last checked
Oct 2026

BridgeBase'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

1 tool, what the product is built with

Data & Observability

2 tools, what they measure and store

Go-to-market

2 tools, how they find and keep customers

Company Ops

1 tool, what the team runs on day to day

BridgeBase tech stack FAQ

What tools does BridgeBase use?

We've found 9 tools at BridgeBase (bridgebase.dev). Edge & Hosting: Cloudflare, Amazon Web Services and Fastly. Application: Next.js. Data & Observability: Google Analytics and Better Stack. Go-to-market: Discord. Company Ops: Google Workspace. Last checked October 2, 2026.

What cloud does BridgeBase run on?

BridgeBase uses Amazon Web Services for hosting. We found Amazon Web Services through custom domain.

What email provider does BridgeBase use?

BridgeBase uses Google Workspace for email and documents. We found Google Workspace through email records.

What does BridgeBase use for customer support?

BridgeBase uses Discord for customer support. We found Discord through website code.

What analytics tools does BridgeBase use?

BridgeBase uses Google Analytics for analytics. We found Google Analytics through website code.

Does BridgeBase use Cloudflare?

Yes. We found Cloudflare at BridgeBase through DNS records and website code. Cloudflare is used by 352,341 companies we track.

How does runsonwhat know what BridgeBase uses?

We read public traces only: BridgeBase'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.