ZALORA's tech stack
What does ZALORA use?
ZALORA (zalora.com.hk) uses at least 20 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, Sentry for monitoring and Amazon CloudFront for content delivery. Last checked .
- Industry
- Airlines/aviation
- Size
- 1–10 employees
- Based in
- Union City, Singapore
- Founded
- 2012
- Company page
- Tools found
- 20
- Categories
- 11
- Layers
- 5 of 5
- Last checked
- Oct 2026
ZALORA'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
CDN & Edge
Application
1 tool, what the product is built with
Frontend
Data & Observability
6 tools, what they measure and store
Monitoring
Flags & Experiments
Go-to-market
6 tools, how they find and keep customers
Company Ops
5 tools, what the team runs on day to day
Email Delivery
Security & Compliance
ZALORA tech stack FAQ
What tools does ZALORA use?
We've found 20 tools at ZALORA (zalora.com.hk). Edge & Hosting: Amazon Route 53 and Amazon CloudFront. Application: Next.js. Data & Observability: Google Analytics, Google Tag Manager and Sentry. Go-to-market: Meta Pixel, Google Ads and Microsoft Ads. Company Ops: Microsoft 365, Google Workspace and SendGrid. Last checked October 4, 2026.
What email provider does ZALORA use?
ZALORA uses Microsoft 365 and Google Workspace for email and documents. We found Microsoft 365 through DNS verification records.
What analytics tools does ZALORA use?
ZALORA uses Google Analytics, Google Tag Manager and Segment for analytics, among 4 tools in this category. We found Google Analytics through website code.
Does ZALORA use Microsoft 365?
Yes. We found Microsoft 365 at ZALORA through DNS verification records. Microsoft 365 is used by 269,769 companies we track.
How does runsonwhat know what ZALORA uses?
We read public traces only: ZALORA'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.