The Centre for Health's tech stack
What does The Centre for Health use?
The Centre for Health (thecentreforhealth.co.nz) uses at least 11 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, Duda for its website and Cookiebot for security. Last checked .
- Based in
- New Zealand
- Tools found
- 11
- Categories
- 9
- Layers
- 4 of 5
- Last checked
- Oct 2026
The Centre for Health'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
Data & Observability
2 tools, what they measure and store
Go-to-market
3 tools, how they find and keep customers
Company Ops
3 tools, what the team runs on day to day
Security & Compliance
The Centre for Health tech stack FAQ
What tools does The Centre for Health use?
We've found 11 tools at The Centre for Health (thecentreforhealth.co.nz). Application: jQuery and Font Awesome. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Google Ads and Duda. Company Ops: Microsoft 365, Google Workspace and Cookiebot. Last checked October 4, 2026.
What email provider does The Centre for Health use?
The Centre for Health uses Microsoft 365 and Google Workspace for email and documents. We found Microsoft 365 through DNS verification records and email records.
What analytics tools does The Centre for Health use?
The Centre for Health uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
What CMS does The Centre for Health use?
The Centre for Health uses Duda for its website. We found Duda through custom domain.
Does The Centre for Health use Microsoft 365?
Yes. We found Microsoft 365 at The Centre for Health through DNS verification records and email records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what The Centre for Health uses?
We read public traces only: The Centre for Health'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.