Diag's tech stack
What does Diag use?
Diag (diagnostyka.pl) uses at least 12 tools we can see from public records, including Google Cloud for hosting, Microsoft 365 for email and documents, Google Analytics for analytics and WordPress for its website. Last checked .
- Industry
- Healthcare
- Size
- 5,001–10,000 employees
- Based in
- Kraków, Poland
- Founded
- 1998
- Company page
- Tools found
- 12
- Categories
- 8
- Layers
- 5 of 5
- Last checked
- Oct 2026
Diag'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
Hosting & Cloud
Application
2 tools, what the product is built with
Frontend
Data & Observability
3 tools, what they measure and store
Go-to-market
5 tools, how they find and keep customers
Website & CMS
Marketing
Company Ops
1 tool, what the team runs on day to day
Workspace
Diag tech stack FAQ
What tools does Diag use?
We've found 12 tools at Diag (diagnostyka.pl). Edge & Hosting: Google Cloud. Application: Next.js. Data & Observability: Google Analytics, Google Tag Manager and Hotjar. Go-to-market: Meta Pixel, Google Ads and WordPress. Company Ops: Microsoft 365. Last checked October 3, 2026.
What cloud does Diag run on?
Diag uses Google Cloud for hosting. We found Google Cloud through website code.
What email provider does Diag use?
Diag uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records and email records.
What analytics tools does Diag use?
Diag uses Google Analytics, Google Tag Manager and Hotjar for analytics. We found Google Analytics through website code.
What CMS does Diag use?
Diag uses WordPress for its website. We found WordPress through website code.
Does Diag use Microsoft 365?
Yes. We found Microsoft 365 at Diag through DNS verification records and email records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what Diag uses?
We read public traces only: Diag'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.