runsonwhat

Diakonhjemmet Sykehus's tech stack

What does Diakonhjemmet Sykehus use?

Diakonhjemmet Sykehus (diakonhjemmetsykehus.no) uses at least 4 tools we can see from public records, including Matomo for analytics, Cloudflare for content delivery and dmarcian for security. Last checked .

Industry
Healthcare
Size
1,001–5,000 employees
Based in
Oslo, Norway
Founded
1890
LinkedIn
Company page
Re-check liveVisit diakonhjemmetsykehus.no
Tools found
4
Categories
4
Layers
3 of 5
Last checked
Oct 2026

Diakonhjemmet Sykehus'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

CDN & Edge

Data & Observability

2 tools, what they measure and store

Analytics

Flags & Experiments

Company Ops

1 tool, what the team runs on day to day

Security & Compliance

Companies like Diakonhjemmet Sykehus also use

Tools common among companies with a similar stack that we haven't found at Diakonhjemmet Sykehus.

Companies with a stack like Diakonhjemmet Sykehus's

Ranked by shared tools, with rare tools counting more.

More Healthcare companies

Other Healthcare companies we've checked.

Diakonhjemmet Sykehus tech stack FAQ

What tools does Diakonhjemmet Sykehus use?

We've found 4 tools at Diakonhjemmet Sykehus (diakonhjemmetsykehus.no). Edge & Hosting: Cloudflare. Data & Observability: Matomo and Optimizely. Company Ops: dmarcian. Last checked October 3, 2026.

What analytics tools does Diakonhjemmet Sykehus use?

Diakonhjemmet Sykehus uses Matomo for analytics. We found Matomo through website code.

Does Diakonhjemmet Sykehus use Cloudflare?

Yes. We found Cloudflare at Diakonhjemmet Sykehus through website code. Cloudflare is used by 147,753 companies we track.

How does runsonwhat know what Diakonhjemmet Sykehus uses?

We read public traces only: Diakonhjemmet Sykehus'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.