runsonwhat

Labrix's tech stack

What does Labrix use?

Labrix (labrix.com) uses at least 13 tools we can see from public records, including Google Workspace for email and documents, Google Analytics for analytics and Termly for security. Last checked .

Industry
Health, Wellness and Fitness
Size
11–50 employees
Based in
Clackamas, United States
Founded
2004
LinkedIn
Company page
Re-check liveVisit labrix.com
Tools found
13
Categories
8
Layers
5 of 5
Last checked
Oct 2026

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

DNS

Application

6 tools, what the product is built with

Frontend

Media & UI

Data & Observability

2 tools, what they measure and store

Analytics

Go-to-market

2 tools, how they find and keep customers

Marketing

Ads & Pixels

Company Ops

2 tools, what the team runs on day to day

Workspace

Security & Compliance

Companies like Labrix also use

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

Companies with a stack like Labrix's

Ranked by shared tools, with rare tools counting more.

Labrix tech stack FAQ

What tools does Labrix use?

We've found 13 tools at Labrix (labrix.com). Edge & Hosting: GoDaddy. Application: jQuery, Font Awesome and YouTube. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Google Ads. Company Ops: Google Workspace and Termly. Last checked October 6, 2026.

What email provider does Labrix use?

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

What analytics tools does Labrix use?

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

Does Labrix use jQuery?

Yes. We found jQuery at Labrix through website code. jQuery is used by 584,456 companies we track.

How does runsonwhat know what Labrix uses?

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