runsonwhat

Fresenius Medical Care's tech stack

What does Fresenius Medical Care use?

Fresenius Medical Care (freseniusmedicalcare.co.ma) uses at least 8 tools we can see from public records, including Amazon Web Services for hosting, Adobe Edge Delivery Services for its website, Cloudflare for content delivery and OneTrust for security. Last checked .

Industry
Healthcare
Size
10,000+ employees
Based in
Casablanca, Morocco
Founded
1996
LinkedIn
Company page
Tools found
8
Categories
7
Layers
5 of 5
Last checked
Oct 2026

Fresenius Medical Care'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

3 tools, where the bytes are served from

Application

1 tool, what the product is built with

Data & Observability

1 tool, what they measure and store

Data Pipeline

Go-to-market

2 tools, how they find and keep customers

Company Ops

1 tool, what the team runs on day to day

Security & Compliance

Fresenius Medical Care tech stack FAQ

What tools does Fresenius Medical Care use?

We've found 8 tools at Fresenius Medical Care (freseniusmedicalcare.co.ma). Edge & Hosting: Cloudflare, Amazon CloudFront and Amazon Web Services. Application: jQuery. Data & Observability: Tealium. Go-to-market: Adobe Edge Delivery Services. Company Ops: OneTrust. Last checked October 3, 2026.

What cloud does Fresenius Medical Care run on?

Fresenius Medical Care uses Amazon Web Services for hosting. We found Amazon Web Services through website code.

What CMS does Fresenius Medical Care use?

Fresenius Medical Care uses Adobe Edge Delivery Services for its website. We found Adobe Edge Delivery Services through website code.

Does Fresenius Medical Care use Cloudflare?

Yes. We found Cloudflare at Fresenius Medical Care through DNS records. Cloudflare is used by 147,753 companies we track.

How does runsonwhat know what Fresenius Medical Care uses?

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