runsonwhat

InterRisk's tech stack

What does InterRisk use?

InterRisk (interrisk.de) uses at least 11 tools we can see from public records, including Microsoft 365 for email and documents, Microsoft Clarity for analytics and Cookiebot for security. Last checked .

Industry
Insurance
Based in
Germany
Founded
1990
LinkedIn
Company page
Re-check liveVisit interrisk.de
Tools found
11
Categories
6
Layers
4 of 5
Last checked
Oct 2026

InterRisk'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

Media & UI

Data & Observability

2 tools, what they measure and store

Analytics

Go-to-market

1 tool, how they find and keep customers

Marketing

Company Ops

5 tools, what the team runs on day to day

Workspace

Collaboration

Security & Compliance

Companies like InterRisk also use

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

Companies with a stack like InterRisk's

Ranked by shared tools, with rare tools counting more.

More Insurance companies

Other Insurance companies we've checked.

InterRisk tech stack FAQ

What tools does InterRisk use?

We've found 11 tools at InterRisk (interrisk.de). Application: Vimeo, YouTube and Font Awesome. Data & Observability: Microsoft Clarity and etracker. Company Ops: Microsoft 365, Apple Business and Cookiebot. Last checked October 4, 2026.

What email provider does InterRisk use?

InterRisk uses Microsoft 365 and Apple Business for email and documents. We found Microsoft 365 through email records.

What analytics tools does InterRisk use?

InterRisk uses Microsoft Clarity and etracker for analytics. We found Microsoft Clarity through website code.

Does InterRisk use Microsoft 365?

Yes. We found Microsoft 365 at InterRisk through email records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what InterRisk uses?

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