Wimdu's tech stack
What does Wimdu use?
Wimdu (wimdu.com) uses at least 11 tools we can see from public records, including Google Workspace for email and documents, Zendesk for customer support, Google Analytics for analytics and SAP Emarsys for marketing. Last checked .
- Industry
- Tourism
- Size
- 201–1,000 employees
- Based in
- Berlin, Germany
- Founded
- 2011
- Company page
- Tools found
- 11
- Categories
- 9
- Layers
- 5 of 5
- Last checked
- Oct 2026
Wimdu'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
CDN & Edge
Application
1 tool, what the product is built with
Frontend
Data & Observability
2 tools, what they measure and store
Go-to-market
4 tools, how they find and keep customers
Ads & Pixels
Support & Docs
Company Ops
3 tools, what the team runs on day to day
Wimdu tech stack FAQ
What tools does Wimdu use?
We've found 11 tools at Wimdu (wimdu.com). Edge & Hosting: Cloudflare. Application: React. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Zendesk, Google Ad Manager and SAP Emarsys. Company Ops: Google Workspace, SendGrid and Valimail. Last checked October 3, 2026.
What email provider does Wimdu use?
Wimdu uses Google Workspace for email and documents. We found Google Workspace through email records and website code.
What does Wimdu use for customer support?
Wimdu uses Zendesk for customer support. We found Zendesk through email records and website code.
What analytics tools does Wimdu use?
Wimdu uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
What marketing software does Wimdu use?
Wimdu uses SAP Emarsys for marketing. We found SAP Emarsys through custom domain.
Does Wimdu use Cloudflare?
Yes. We found Cloudflare at Wimdu through DNS records and website code. Cloudflare is used by 307,941 companies we track.
How does runsonwhat know what Wimdu uses?
We read public traces only: Wimdu'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.