runsonwhat

Pair Networks's tech stack

What does Pair Networks use?

Pair Networks (pair.com) uses at least 18 tools we can see from public records, including Zendesk for customer support, Google Analytics for analytics, WordPress for its website and Sorry for monitoring. Last checked .

Industry
Internet
Size
51–200 employees
Based in
Pittsburgh, United States
Founded
1996
LinkedIn
Company page
Tools found
18
Categories
11
Layers
5 of 5
Last checked
Oct 2026

Pair Networks'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

5 tools, what the product is built with

Data & Observability

4 tools, what they measure and store

Go-to-market

7 tools, how they find and keep customers

Company Ops

1 tool, what the team runs on day to day

Security & Compliance

Pair Networks tech stack FAQ

What tools does Pair Networks use?

We've found 18 tools at Pair Networks (pair.com). Edge & Hosting: Cloudflare. Application: jQuery, Google Fonts and Font Awesome. Data & Observability: Google Analytics, Google Tag Manager and Crazy Egg. Go-to-market: WordPress, Google Ads and Meta Pixel. Company Ops: reCAPTCHA. Last checked October 3, 2026.

What does Pair Networks use for customer support?

Pair Networks uses Zendesk for customer support. We found Zendesk through email records and website code.

What analytics tools does Pair Networks use?

Pair Networks uses Google Analytics, Google Tag Manager and Crazy Egg for analytics. We found Google Analytics through website code.

What CMS does Pair Networks use?

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

Does Pair Networks use Cloudflare?

Yes. We found Cloudflare at Pair Networks through custom domain, DNS records and website code. Cloudflare is used by 309,463 companies we track.

How does runsonwhat know what Pair Networks uses?

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