runsonwhat

Gjensidige Forsikring A/S's tech stack

What does Gjensidige Forsikring A/S use?

Gjensidige Forsikring A/S (gjensidige.dk) uses at least 16 tools we can see from public records, including Microsoft Azure for hosting, Microsoft 365 for email and documents, SendGrid for email delivery and Let's Encrypt for security. Last checked .

Industry
General Insurance
Size
1,001–5,000 employees
Based in
København SV, Denmark
Founded
1922
LinkedIn
Company page
Tools found
16
Categories
8
Layers
4 of 5
Last checked
Oct 2026

Gjensidige Forsikring A/S'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

Data & Observability

1 tool, what they measure and store

Data Pipeline

Go-to-market

1 tool, how they find and keep customers

Company Ops

13 tools, what the team runs on day to day

Gjensidige Forsikring A/S tech stack FAQ

What tools does Gjensidige Forsikring A/S use?

We've found 16 tools at Gjensidige Forsikring A/S (gjensidige.dk). Edge & Hosting: Microsoft Azure. Data & Observability: Tealium. Company Ops: Microsoft 365, SendGrid and Apple Business. Last checked October 4, 2026.

What cloud does Gjensidige Forsikring A/S run on?

Gjensidige Forsikring A/S uses Microsoft Azure for hosting. We found Microsoft Azure through custom domain, DNS records and website code.

What email provider does Gjensidige Forsikring A/S use?

Gjensidige Forsikring A/S uses Microsoft 365 and Apple Business for email and documents. We found Microsoft 365 through email records and DNS verification records.

Does Gjensidige Forsikring A/S use Microsoft 365?

Yes. We found Microsoft 365 at Gjensidige Forsikring A/S through email records and DNS verification records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what Gjensidige Forsikring A/S uses?

We read public traces only: Gjensidige Forsikring A/S'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.