runsonwhat

EA Principals's tech stack

What does EA Principals use?

EA Principals (performancearchitectures.com) uses at least 12 tools we can see from public records, including Zendesk for customer support, Google Analytics for analytics, WordPress for its website and Cloudflare for content delivery. Last checked .

Industry
IT Services
Size
11–50 employees
Based in
Colorado Springs, United States
LinkedIn
Company page
Tools found
12
Categories
9
Layers
5 of 5
Last checked
Oct 2026

EA Principals'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

Application

4 tools, what the product is built with

Data & Observability

1 tool, what they measure and store

Go-to-market

4 tools, how they find and keep customers

Company Ops

1 tool, what the team runs on day to day

Security & Compliance

EA Principals tech stack FAQ

What tools does EA Principals use?

We've found 12 tools at EA Principals (performancearchitectures.com). Edge & Hosting: Cloudflare and GoDaddy. Application: jQuery, Font Awesome and YouTube. Data & Observability: Google Analytics. Go-to-market: WordPress, Google Ads and WooCommerce. Company Ops: reCAPTCHA. Last checked October 7, 2026.

What does EA Principals use for customer support?

EA Principals uses Zendesk for customer support. We found Zendesk through website code.

What analytics tools does EA Principals use?

EA Principals uses Google Analytics for analytics. We found Google Analytics through website code.

What CMS does EA Principals use?

EA Principals uses WordPress and WooCommerce for its website. We found WordPress through website code.

Does EA Principals use jQuery?

Yes. We found jQuery at EA Principals through website code. jQuery is used by 761,474 companies we track.

How does runsonwhat know what EA Principals uses?

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