Getränkewelt's tech stack
What does Getränkewelt use?
Getränkewelt (getraenkewelt.org) uses at least 11 tools we can see from public records, including IONOS for hosting, Google Analytics for analytics, WordPress for its website and Cookiebot for security. Last checked .
- Based in
- Germany
- Tools found
- 11
- Categories
- 8
- Layers
- 5 of 5
- Last checked
- Oct 2026
Getränkewelt'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
1 tool, where the bytes are served from
Hosting & Cloud
Application
2 tools, what the product is built with
Frontend
Media & UI
Data & Observability
2 tools, what they measure and store
Go-to-market
4 tools, how they find and keep customers
Website & CMS
Marketing
Ads & Pixels
Company Ops
2 tools, what the team runs on day to day
Security & Compliance
Getränkewelt tech stack FAQ
What tools does Getränkewelt use?
We've found 11 tools at Getränkewelt (getraenkewelt.org). Edge & Hosting: IONOS. Application: jQuery and Three.js. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Meta Pixel, Google Ads and WordPress. Company Ops: Cookiebot and Usercentrics. Last checked October 3, 2026.
What cloud does Getränkewelt run on?
Getränkewelt uses IONOS for hosting. We found IONOS through email records.
What analytics tools does Getränkewelt use?
Getränkewelt uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
What CMS does Getränkewelt use?
Getränkewelt uses WordPress for its website. We found WordPress through website code.
Does Getränkewelt use Google Analytics?
Yes. We found Google Analytics at Getränkewelt through website code. Google Analytics is used by 89,943 companies we track.
How does runsonwhat know what Getränkewelt uses?
We read public traces only: Getränkewelt'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.