Travelzoo's tech stack
What does Travelzoo use?
Travelzoo (travelzoo.com) uses at least 14 tools we can see from public records, including Microsoft Azure for hosting, Microsoft 365 for email and documents, Zendesk for customer support and Akamai for content delivery. Last checked .
- Industry
- Tourism
- Size
- 201–1,000 employees
- Based in
- New York, United Kingdom
- Founded
- 1998
- Company page
- Tools found
- 14
- Categories
- 9
- Layers
- 4 of 5
- Last checked
- Oct 2026
Travelzoo'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
3 tools, where the bytes are served from
Hosting & Cloud
CDN & Edge
Application
1 tool, what the product is built with
Backend & Database
Go-to-market
4 tools, how they find and keep customers
Company Ops
6 tools, what the team runs on day to day
Email Delivery
Security & Compliance
Travelzoo tech stack FAQ
What tools does Travelzoo use?
We've found 14 tools at Travelzoo (travelzoo.com). Edge & Hosting: Microsoft Azure, Amazon Web Services and Akamai. Application: Twilio. Go-to-market: Meta Pixel, Zendesk and Pinterest. Company Ops: Microsoft 365, Google Workspace and Apple Business. Last checked October 3, 2026.
What cloud does Travelzoo run on?
Travelzoo uses Microsoft Azure and Amazon Web Services for hosting. We found Microsoft Azure through custom domain.
What email provider does Travelzoo use?
Travelzoo uses Microsoft 365, Google Workspace and Apple Business for email and documents. We found Microsoft 365 through email records and DNS verification records.
What does Travelzoo use for customer support?
Travelzoo uses Zendesk for customer support. We found Zendesk through email records.
Does Travelzoo use Microsoft 365?
Yes. We found Microsoft 365 at Travelzoo through email records and DNS verification records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what Travelzoo uses?
We read public traces only: Travelzoo'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.