CRG's tech stack
What does CRG use?
CRG (securityresponse.ca) uses at least 9 tools we can see from public records, including WP Engine for hosting, Microsoft 365 for email and documents, Google Analytics for analytics and WordPress for its website. Last checked .
- Industry
- Security and Investigations
- Size
- 51–200 employees
- Based in
- Denver, United States
- Founded
- 1970
- Company page
- Tools found
- 9
- Categories
- 8
- Layers
- 5 of 5
- Last checked
- Oct 2026
CRG'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
2 tools, what the product is built with
Frontend
Media & UI
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
2 tools, how they find and keep customers
Website & CMS
Company Ops
2 tools, what the team runs on day to day
Workspace
Security & Compliance
CRG tech stack FAQ
What tools does CRG use?
We've found 9 tools at CRG (securityresponse.ca). Edge & Hosting: WP Engine and Gandi. Application: jQuery and Google Fonts. Data & Observability: Google Analytics. Go-to-market: WordPress and Yoast SEO. Company Ops: Microsoft 365 and reCAPTCHA. Last checked October 8, 2026.
What cloud does CRG run on?
CRG uses WP Engine for hosting. We found WP Engine through website code.
What email provider does CRG use?
CRG uses Microsoft 365 for email and documents. We found Microsoft 365 through email records and website code.
What analytics tools does CRG use?
CRG uses Google Analytics for analytics. We found Google Analytics through website code.
What CMS does CRG use?
CRG uses WordPress and Yoast SEO for its website. We found WordPress through website code.
Does CRG use jQuery?
Yes. We found jQuery at CRG through website code. jQuery is used by 762,178 companies we track.
How does runsonwhat know what CRG uses?
We read public traces only: CRG'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.