runsonwhat

Brigo's tech stack

What does Brigo use?

Brigo (brigo.com) uses at least 15 tools we can see from public records, including Microsoft 365 for email and documents, Zendesk for customer support, Google Analytics for analytics and WordPress for its website. Last checked .

Industry
Consumer Goods
Size
51–200 employees
Based in
Mölndal, Sweden
LinkedIn
Company page
Tools found
15
Categories
10
Layers
5 of 5
Last checked
Oct 2026

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

1 tool, where the bytes are served from

Application

4 tools, what the product is built with

Data & Observability

2 tools, what they measure and store

Go-to-market

6 tools, how they find and keep customers

Company Ops

2 tools, what the team runs on day to day

Security & Compliance

Brigo tech stack FAQ

What tools does Brigo use?

We've found 15 tools at Brigo (brigo.com). Edge & Hosting: Amazon CloudFront. Application: jQuery, Vimeo and GSAP. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: WordPress, Google Ads and Yoast SEO. Company Ops: Microsoft 365 and URIports. Last checked October 7, 2026.

What email provider does Brigo use?

Brigo uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records and email records.

What does Brigo use for customer support?

Brigo uses Zendesk for customer support. We found Zendesk through email records.

What analytics tools does Brigo use?

Brigo uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.

What CMS does Brigo use?

Brigo uses WordPress and Yoast SEO for its website. We found WordPress through website code.

Does Brigo use jQuery?

Yes. We found jQuery at Brigo through website code. jQuery is used by 761,882 companies we track.

How does runsonwhat know what Brigo uses?

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