Walibi's tech stack
What does Walibi use?
Walibi (walibi.com) uses at least 11 tools we can see from public records, including Amazon Web Services for hosting, Microsoft 365 for email and documents, Google Analytics for analytics and Amazon CloudFront for content delivery. Last checked .
- Industry
- Leisure, Travel & Tourism
- Size
- 1,001–5,000 employees
- Based in
- Wavre, Belgium
- Founded
- 1989
- Company page
- Tools found
- 11
- Categories
- 9
- Layers
- 5 of 5
- Last checked
- Oct 2026
Walibi'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
2 tools, where the bytes are served from
Hosting & Cloud
CDN & Edge
Application
1 tool, what the product is built with
Frontend
Data & Observability
2 tools, what they measure and store
Go-to-market
2 tools, how they find and keep customers
Marketing
Ads & Pixels
Company Ops
4 tools, what the team runs on day to day
Walibi tech stack FAQ
What tools does Walibi use?
We've found 11 tools at Walibi (walibi.com). Edge & Hosting: Amazon Web Services and Amazon CloudFront. Application: jQuery. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Google Ads. Company Ops: Microsoft 365, GlobalSign and Mailjet. Last checked October 2, 2026.
What cloud does Walibi run on?
Walibi uses Amazon Web Services for hosting. We found Amazon Web Services through website code.
What email provider does Walibi use?
Walibi uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records, email records and website code.
What analytics tools does Walibi use?
Walibi uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
Does Walibi use Microsoft 365?
Yes. We found Microsoft 365 at Walibi through DNS verification records, email records and website code. Microsoft 365 is used by 685,701 companies we track.
How does runsonwhat know what Walibi uses?
We read public traces only: Walibi'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.