runsonwhat

ZALORA's tech stack

What does ZALORA use?

ZALORA (zalora.co.id) uses at least 22 tools we can see from public records, including Microsoft 365 for email and documents, Zendesk for customer support, Google Analytics for analytics and Sentry for monitoring. Last checked .

Industry
Apparel & Fashion
Size
1–10 employees
Based in
Singapore
Founded
2012
LinkedIn
Company page
Tools found
22
Categories
12
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

Application

1 tool, what the product is built with

Data & Observability

6 tools, what they measure and store

Go-to-market

8 tools, how they find and keep customers

Company Ops

5 tools, what the team runs on day to day

ZALORA tech stack FAQ

What tools does ZALORA use?

We've found 22 tools at ZALORA (zalora.co.id). 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 Zendesk. 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 does ZALORA use for customer support?

ZALORA uses Zendesk for customer support. We found Zendesk through custom domain.

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 245,233 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.