Diakonie-Klinikum Schwäbisch Hall's tech stack
What does Diakonie-Klinikum Schwäbisch Hall use?
Diakonie-Klinikum Schwäbisch Hall (diak-klinikum.de) uses at least 5 tools we can see from public records, including Microsoft 365 for email and documents and Google Analytics for analytics. Last checked .
- Industry
- Hospitals and Rehabilitation
- Size
- 1,001–5,000 employees
- Based in
- Schwäbisch Hall, Germany
- Founded
- 1886
- Company page
- Tools found
- 5
- Categories
- 3
- Layers
- 3 of 5
- Last checked
- Oct 2026
Diakonie-Klinikum Schwäbisch Hall'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.
Data & Observability
2 tools, what they measure and store
Go-to-market
1 tool, how they find and keep customers
Ads & Pixels
Company Ops
2 tools, what the team runs on day to day
Workspace
Diakonie-Klinikum Schwäbisch Hall tech stack FAQ
What tools does Diakonie-Klinikum Schwäbisch Hall use?
We've found 5 tools at Diakonie-Klinikum Schwäbisch Hall (diak-klinikum.de). Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Google Ads. Company Ops: Microsoft 365 and Apple Business. Last checked October 3, 2026.
What email provider does Diakonie-Klinikum Schwäbisch Hall use?
Diakonie-Klinikum Schwäbisch Hall uses Microsoft 365 and Apple Business for email and documents. We found Microsoft 365 through DNS verification records.
What analytics tools does Diakonie-Klinikum Schwäbisch Hall use?
Diakonie-Klinikum Schwäbisch Hall uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
Does Diakonie-Klinikum Schwäbisch Hall use Microsoft 365?
Yes. We found Microsoft 365 at Diakonie-Klinikum Schwäbisch Hall through DNS verification records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what Diakonie-Klinikum Schwäbisch Hall uses?
We read public traces only: Diakonie-Klinikum Schwäbisch Hall'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.