looxloo's tech stack
What does looxloo use?
looxloo (looxloo.com) uses at least 18 tools we can see from public records, including Amazon Web Services for hosting, Channel.io for customer support, Google Analytics for analytics and Cafe24 for its website. Last checked .
- Industry
- Apparel & Fashion
- Size
- 201–1,000 employees
- Based in
- South Korea
- Company page
- Tools found
- 18
- Categories
- 10
- Layers
- 4 of 5
- Last checked
- Oct 2026
looxloo'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
4 tools, what the product is built with
Data & Observability
4 tools, what they measure and store
Go-to-market
8 tools, how they find and keep customers
Website & CMS
Marketing
Support & Docs
looxloo tech stack FAQ
What tools does looxloo use?
We've found 18 tools at looxloo (looxloo.com). Edge & Hosting: Cloudflare and Amazon Web Services. Application: jQuery, Google Fonts and React. Data & Observability: Google Analytics, Google Tag Manager and Microsoft Clarity. Go-to-market: Google Ads, Meta Pixel and X Ads. Last checked October 7, 2026.
What cloud does looxloo run on?
looxloo uses Amazon Web Services for hosting. We found Amazon Web Services through website code.
What does looxloo use for customer support?
looxloo uses Channel.io for customer support. We found Channel.io through website code.
What analytics tools does looxloo use?
looxloo uses Google Analytics, Google Tag Manager and Microsoft Clarity for analytics, among 4 tools in this category. We found Google Analytics through website code.
What CMS does looxloo use?
looxloo uses Cafe24 for its website. We found Cafe24 through website code.
Does looxloo use jQuery?
Yes. We found jQuery at looxloo through website code. jQuery is used by 761,724 companies we track.
How does runsonwhat know what looxloo uses?
We read public traces only: looxloo'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.