runsonwhat

CURA's tech stack

What does CURA use?

CURA (cura-ag.com) uses at least 10 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics and Amazon SES for email delivery. Last checked .

Based in
Germany
Founded
1995
LinkedIn
Company page
Re-check liveVisit cura-ag.com
Tools found
10
Categories
5
Layers
4 of 5
Last checked
Oct 2026

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

1 tool, what the product is built with

Frontend

Data & Observability

3 tools, what they measure and store

Analytics

Go-to-market

2 tools, how they find and keep customers

Ads & Pixels

Company Ops

4 tools, what the team runs on day to day

Email Delivery

Workspace

Companies like CURA also use

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

Companies with a stack like CURA's

Ranked by shared tools, with rare tools counting more.

CURA tech stack FAQ

What tools does CURA use?

We've found 10 tools at CURA (cura-ag.com). Application: jQuery. Data & Observability: Google Analytics, Google Tag Manager and Matomo. Go-to-market: Meta Pixel and Google Ads. Company Ops: Microsoft 365, Apple Business and Amazon SES. Last checked October 3, 2026.

What email provider does CURA use?

CURA uses Microsoft 365, Apple Business and Exclaimer for email and documents. We found Microsoft 365 through DNS verification records and email records.

What analytics tools does CURA use?

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

Does CURA use Microsoft 365?

Yes. We found Microsoft 365 at CURA through DNS verification records and email records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what CURA uses?

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