Charité – Universitätsmedizin Berlin's tech stack
What does Charité – Universitätsmedizin Berlin use?
Charité – Universitätsmedizin Berlin (charite.de) uses at least 7 tools we can see from public records, including Apple Business for email and documents, Brevo for marketing and Let's Encrypt for security. Last checked .
- Industry
- Healthcare
- Size
- 10,000+ employees
- Based in
- Berlin, Germany
- Company page
- Tools found
- 7
- Categories
- 5
- Layers
- 3 of 5
- Last checked
- Oct 2026
Charité – Universitätsmedizin Berlin'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
Go-to-market
2 tools, how they find and keep customers
Marketing
Company Ops
4 tools, what the team runs on day to day
Workspace
Dev Tools
Security & Compliance
Charité – Universitätsmedizin Berlin tech stack FAQ
What tools does Charité – Universitätsmedizin Berlin use?
We've found 7 tools at Charité – Universitätsmedizin Berlin (charite.de). Application: jQuery. Go-to-market: Brevo. Company Ops: Apple Business, Atlassian and Let's Encrypt. Last checked October 3, 2026.
What email provider does Charité – Universitätsmedizin Berlin use?
Charité – Universitätsmedizin Berlin uses Apple Business for email and documents. We found Apple Business through DNS verification records.
What marketing software does Charité – Universitätsmedizin Berlin use?
Charité – Universitätsmedizin Berlin uses Brevo for marketing. We found Brevo through DNS verification records.
Does Charité – Universitätsmedizin Berlin use jQuery?
Yes. We found jQuery at Charité – Universitätsmedizin Berlin through website code. jQuery is used by 67,244 companies we track.
How does runsonwhat know what Charité – Universitätsmedizin Berlin uses?
We read public traces only: Charité – Universitätsmedizin Berlin'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.