runsonwhat

CaRMS's tech stack

What does CaRMS use?

CaRMS (carms.ca) uses at least 30 tools we can see from public records, including Microsoft 365 for email and documents, HubSpot for sales, Zendesk for customer support and Google Analytics for analytics. Last checked .

Based in
Canada
Founded
1969
LinkedIn
Company page
Tools found
30
Categories
14
Layers
5 of 5
Last checked
Oct 2026

CaRMS'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

Data & Observability

3 tools, what they measure and store

Go-to-market

8 tools, how they find and keep customers

Company Ops

10 tools, what the team runs on day to day

CaRMS tech stack FAQ

What tools does CaRMS use?

We've found 30 tools at CaRMS (carms.ca). Edge & Hosting: Amazon Route 53. Application: jQuery, Google Fonts and Vimeo. Data & Observability: Google Analytics, Google Tag Manager and Hotjar. Go-to-market: Google Ads, WordPress and HubSpot. Company Ops: Microsoft 365, SendGrid and Atlassian. Last checked October 3, 2026.

What CRM does CaRMS use?

CaRMS uses HubSpot for sales and CRM. We found HubSpot through email records.

What email provider does CaRMS use?

CaRMS uses Microsoft 365 and Exclaimer for email and documents. We found Microsoft 365 through email records.

What does CaRMS use for customer support?

CaRMS uses Zendesk for customer support. We found Zendesk through email records.

What analytics tools does CaRMS use?

CaRMS uses Google Analytics, Google Tag Manager and Hotjar for analytics. We found Google Analytics through website code.

What CMS does CaRMS use?

CaRMS uses WordPress, Yoast SEO and HubSpot CMS for its website. We found WordPress through website code.

Does CaRMS use Microsoft 365?

Yes. We found Microsoft 365 at CaRMS through email records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what CaRMS uses?

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