ISPGR's tech stack
What does ISPGR use?
ISPGR (ispgr.org) uses at least 9 tools we can see from public records, including Google Workspace for email and documents, Google Analytics for analytics, WordPress for its website and Brevo for marketing. Last checked .
- Industry
- Non-profit Organization Management
- Size
- 201–1,000 employees
- Based in
- Victoria, Canada
- Company page
- Tools found
- 9
- Categories
- 7
- Layers
- 4 of 5
- Last checked
- Oct 2026
ISPGR'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.
Application
3 tools, what the product is built with
Frontend
Media & UI
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
3 tools, how they find and keep customers
Website & CMS
Marketing
Company Ops
2 tools, what the team runs on day to day
Email Delivery
Workspace
ISPGR tech stack FAQ
What tools does ISPGR use?
We've found 9 tools at ISPGR (ispgr.org). Application: jQuery, Google Fonts and GSAP. Data & Observability: Google Analytics. Go-to-market: WordPress, Yoast SEO and Brevo. Company Ops: Google Workspace and SendGrid. Last checked October 8, 2026.
What email provider does ISPGR use?
ISPGR uses Google Workspace for email and documents. We found Google Workspace through email records and website code.
What analytics tools does ISPGR use?
ISPGR uses Google Analytics for analytics. We found Google Analytics through website code.
What CMS does ISPGR use?
ISPGR uses WordPress and Yoast SEO for its website. We found WordPress through website code.
What marketing software does ISPGR use?
ISPGR uses Brevo for marketing. We found Brevo through DNS verification records.
Does ISPGR use jQuery?
Yes. We found jQuery at ISPGR through website code. jQuery is used by 762,178 companies we track.
How does runsonwhat know what ISPGR uses?
We read public traces only: ISPGR'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.