Aarhus Universitetshospital - Til patienter og pårørende's tech stack
What does Aarhus Universitetshospital - Til patienter og pårørende use?
Aarhus Universitetshospital - Til patienter og pårørende (auh.dk) uses at least 6 tools we can see from public records, including Mailchimp for marketing, Mailchimp Transactional for email delivery and Cookiebot for security. Last checked .
- Industry
- Healthcare
- Size
- 10,000+ employees
- Based in
- Aarhus, Denmark
- Company page
- Tools found
- 6
- Categories
- 5
- Layers
- 3 of 5
- Last checked
- Oct 2026
Aarhus Universitetshospital - Til patienter og pårørende'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
2 tools, what the product is built with
Frontend
Search
Go-to-market
2 tools, how they find and keep customers
Company Ops
2 tools, what the team runs on day to day
Email Delivery
Security & Compliance
Aarhus Universitetshospital - Til patienter og pårørende tech stack FAQ
What tools does Aarhus Universitetshospital - Til patienter og pårørende use?
We've found 6 tools at Aarhus Universitetshospital - Til patienter og pårørende (auh.dk). Application: jQuery and Cludo. Go-to-market: Mailchimp. Company Ops: Mailchimp Transactional and Cookiebot. Last checked October 3, 2026.
What marketing software does Aarhus Universitetshospital - Til patienter og pårørende use?
Aarhus Universitetshospital - Til patienter og pårørende uses Mailchimp for marketing. We found Mailchimp through email records.
Does Aarhus Universitetshospital - Til patienter og pårørende use jQuery?
Yes. We found jQuery at Aarhus Universitetshospital - Til patienter og pårørende through website code. jQuery is used by 67,244 companies we track.
How does runsonwhat know what Aarhus Universitetshospital - Til patienter og pårørende uses?
We read public traces only: Aarhus Universitetshospital - Til patienter og pårørende'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.