runsonwhat

Paul Gerhardt Diakonie's tech stack

What does Paul Gerhardt Diakonie use?

Paul Gerhardt Diakonie (pgdiakonie.de) uses at least 12 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics and Cookiebot for security. Last checked .

Industry
Healthcare
Size
5,001–10,000 employees
Based in
Berlin, Germany
Founded
1929
LinkedIn
Company page
Tools found
12
Categories
6
Layers
4 of 5
Last checked
Oct 2026

Paul Gerhardt Diakonie'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

3 tools, what they measure and store

Go-to-market

4 tools, how they find and keep customers

Company Ops

2 tools, what the team runs on day to day

Security & Compliance

Paul Gerhardt Diakonie tech stack FAQ

What tools does Paul Gerhardt Diakonie use?

We've found 12 tools at Paul Gerhardt Diakonie (pgdiakonie.de). Application: jQuery, YouTube and Google Maps. Data & Observability: Google Analytics, Google Tag Manager and Matomo. Go-to-market: Meta Pixel, Google Ads and LinkedIn Insight Tag. Company Ops: Microsoft 365 and Cookiebot. Last checked October 3, 2026.

What email provider does Paul Gerhardt Diakonie use?

Paul Gerhardt Diakonie uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records.

What analytics tools does Paul Gerhardt Diakonie use?

Paul Gerhardt Diakonie uses Google Analytics, Google Tag Manager and Matomo for analytics. We found Google Analytics through website code.

Does Paul Gerhardt Diakonie use Microsoft 365?

Yes. We found Microsoft 365 at Paul Gerhardt Diakonie through DNS verification records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what Paul Gerhardt Diakonie uses?

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