runsonwhat

Kubex's tech stack

What does Kubex use?

Kubex (densify.com) uses at least 24 tools we can see from public records, including Kinsta for hosting, Google Analytics for analytics, WordPress for its website and Pardot for marketing. Last checked .

Industry
Software
Based in
Canada
Founded
1999
LinkedIn
Company page
Tools found
24
Categories
13
Layers
5 of 5
Last checked
Oct 2026

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

7 tools, what the product is built with

Data & Observability

3 tools, what they measure and store

Go-to-market

7 tools, how they find and keep customers

Company Ops

5 tools, what the team runs on day to day

Kubex tech stack FAQ

What tools does Kubex use?

We've found 24 tools at Kubex (densify.com). Edge & Hosting: Cloudflare and Kinsta. Application: jQuery, Google Fonts and Vimeo. Data & Observability: Google Analytics, Google Tag Manager and Microsoft Clarity. Go-to-market: Meta Pixel, WordPress and Yoast SEO. Company Ops: SendGrid, Atlassian and Mimecast. Last checked October 3, 2026.

What cloud does Kubex run on?

Kubex uses Kinsta for hosting. We found Kinsta through website code.

What analytics tools does Kubex use?

Kubex uses Google Analytics, Google Tag Manager and Microsoft Clarity for analytics. We found Google Analytics through website code.

What CMS does Kubex use?

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

What marketing software does Kubex use?

Kubex uses Pardot and G2 for marketing. We found Pardot through email records and website code.

Does Kubex use Cloudflare?

Yes. We found Cloudflare at Kubex through DNS records and website code. Cloudflare is used by 147,753 companies we track.

How does runsonwhat know what Kubex uses?

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