runsonwhat

Bridge.audio's tech stack

What does Bridge.audio use?

Bridge.audio (bridge.audio) uses at least 26 tools we can see from public records, including OVHcloud for hosting, Google Workspace for email and documents, HubSpot for sales and Discord for customer support. Last checked .

Industry
Internet
Size
1–10 employees
Based in
Paris, France
LinkedIn
Company page
Re-check liveVisit bridge.audio
Tools found
26
Categories
16
Layers
5 of 5
Last checked
Oct 2026

Bridge.audio'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

4 tools, what the product is built with

AI

Payments & Billing

Media & UI

Data & Observability

3 tools, what they measure and store

Analytics

Go-to-market

10 tools, how they find and keep customers

Website & CMS

Marketing

Ads & Pixels

Sales & CRM

Support & Docs

Company Ops

7 tools, what the team runs on day to day

Email Delivery

Workspace

Collaboration

Dev Tools

Security & Compliance

Companies like Bridge.audio also use

Tools common among companies with a similar stack that we haven't found at Bridge.audio.

Companies with a stack like Bridge.audio's

Ranked by shared tools, with rare tools counting more.

Bridge.audio tech stack FAQ

What tools does Bridge.audio use?

As of October 2026, runsonwhat has found 26 tools at Bridge.audio (bridge.audio) in public records. Edge & Hosting: Cloudflare and OVHcloud. Application: GSAP, Lottie and Stripe. Data & Observability: Google Analytics, Google Tag Manager and Segment. Go-to-market: Google Ads, Meta Pixel and LinkedIn Insight Tag. Company Ops: Google Workspace, SendGrid and Atlassian. Last checked October 4, 2026.

What cloud does Bridge.audio run on?

Bridge.audio uses OVHcloud for hosting and cloud infrastructure, according to runsonwhat (October 2026). runsonwhat found OVHcloud through DNS records that point at OVHcloud and code on bridge.audio. OVHcloud is used by 26,536 companies runsonwhat tracks.

What CRM does Bridge.audio use?

Bridge.audio uses HubSpot for its CRM, alongside lemlist, according to runsonwhat (October 2026). runsonwhat found HubSpot through a subdomain that points at HubSpot and email records. HubSpot is used by 90,591 companies runsonwhat tracks.

What email provider does Bridge.audio use?

Bridge.audio uses Google Workspace for email and office software, according to runsonwhat (October 2026). runsonwhat found Google Workspace through email records that authorize Google Workspace and code on bridge.audio. Google Workspace is used by 393,472 companies runsonwhat tracks.

What does Bridge.audio use for customer support?

Bridge.audio uses Discord for customer support and documentation, according to runsonwhat (October 2026). runsonwhat found Discord through Discord code on bridge.audio. Discord is used by 3,650 companies runsonwhat tracks.

What payment provider does Bridge.audio use?

Bridge.audio uses Stripe for payments and billing, according to runsonwhat (October 2026). runsonwhat found Stripe through a DNS verification record for Stripe and code on bridge.audio. Stripe is used by 25,596 companies runsonwhat tracks.

Does Bridge.audio use Cloudflare?

Yes. runsonwhat found Cloudflare at Bridge.audio through Cloudflare code on bridge.audio. Cloudflare is a CDN & Edge tool used by 685,952 companies runsonwhat tracks.

Which companies have a tech stack similar to Bridge.audio's?

The companies with the stacks most like Bridge.audio's are MCPJam, Speechmatics, Jitter and Straion FlexCo, according to runsonwhat (October 2026). Each shares 8 to 13 tools with Bridge.audio, and rare tools count for more than common ones like Google Workspace, so the match reflects real stack choices.

How does runsonwhat know what Bridge.audio uses?

runsonwhat reads public records only. Of the 26 tools at Bridge.audio, 10 were found through code on bridge.audio, 7 through DNS records, 6 through email records, 2 through subdomains that point at the vendor and 1 through website configuration files. A tool is listed only when a direct record backs it up; DNS is rechecked weekly and bridge.audio about 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.