Pgx Testing's tech stack
What does Pgx Testing use?
Pgx Testing (pgxt.com) uses at least 10 tools we can see from public records, including Google Cloud for hosting, Google Workspace for email and documents, Google Analytics for analytics and Bugsnag for monitoring. Last checked .
- Industry
- Health, Wellness and Fitness
- Size
- 11–50 employees
- Based in
- San Antonio, United States
- Founded
- 2012
- Company page
- Tools found
- 10
- Categories
- 9
- Layers
- 5 of 5
- Last checked
- Oct 2026
Pgx Testing'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
DNS
Application
4 tools, what the product is built with
Data & Observability
2 tools, what they measure and store
Monitoring
Analytics
Go-to-market
1 tool, how they find and keep customers
Marketing
Company Ops
1 tool, what the team runs on day to day
Workspace
Pgx Testing tech stack FAQ
What tools does Pgx Testing use?
We've found 10 tools at Pgx Testing (pgxt.com). Edge & Hosting: GoDaddy and Google Cloud. Application: jQuery, YouTube and Firebase. Data & Observability: Google Analytics and Bugsnag. Company Ops: Google Workspace. Last checked October 6, 2026.
What cloud does Pgx Testing run on?
Pgx Testing uses Google Cloud for hosting. We found Google Cloud through custom domain.
What email provider does Pgx Testing use?
Pgx Testing uses Google Workspace for email and documents. We found Google Workspace through email records.
What analytics tools does Pgx Testing use?
Pgx Testing uses Google Analytics for analytics. We found Google Analytics through website code.
Does Pgx Testing use jQuery?
Yes. We found jQuery at Pgx Testing through website code. jQuery is used by 597,140 companies we track.
How does runsonwhat know what Pgx Testing uses?
We read public traces only: Pgx Testing'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.