Het Groene Hart Ziekenhuis's tech stack
What does Het Groene Hart Ziekenhuis use?
Het Groene Hart Ziekenhuis (ghz.nl) uses at least 14 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, SendGrid for email delivery and Let's Encrypt for security. Last checked .
- Industry
- Healthcare
- Size
- 1,001–5,000 employees
- Based in
- Gouda, Netherlands
- Founded
- 1927
- Company page
- Tools found
- 14
- Categories
- 8
- Layers
- 4 of 5
- Last checked
- Oct 2026
Het Groene Hart Ziekenhuis'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
1 tool, what the product is built with
Media & UI
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
1 tool, how they find and keep customers
Ads & Pixels
Company Ops
11 tools, what the team runs on day to day
Workspace
Collaboration
Finance & Legal
Security & Compliance
Het Groene Hart Ziekenhuis tech stack FAQ
What tools does Het Groene Hart Ziekenhuis use?
We've found 14 tools at Het Groene Hart Ziekenhuis (ghz.nl). Application: YouTube. Data & Observability: Google Analytics. Go-to-market: Google Ads. Company Ops: Microsoft 365, SendGrid and Let's Encrypt. Last checked October 3, 2026.
What email provider does Het Groene Hart Ziekenhuis use?
Het Groene Hart Ziekenhuis uses Microsoft 365 for email and documents. We found Microsoft 365 through email records.
What analytics tools does Het Groene Hart Ziekenhuis use?
Het Groene Hart Ziekenhuis uses Google Analytics for analytics. We found Google Analytics through website code.
Does Het Groene Hart Ziekenhuis use Microsoft 365?
Yes. We found Microsoft 365 at Het Groene Hart Ziekenhuis through email records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what Het Groene Hart Ziekenhuis uses?
We read public traces only: Het Groene Hart Ziekenhuis'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.