Yam's tech stack
What does Yam use?
Yam (yam.com) uses at least 18 tools we can see from public records, including Microsoft Azure for hosting, Google Workspace for email and documents, Google Analytics for analytics and Cloudflare for content delivery. Last checked .
- Industry
- Internet
- Size
- 51–200 employees
- Based in
- Taiwan
- Founded
- 1998
- Company page
- Tools found
- 18
- Categories
- 9
- Layers
- 5 of 5
- Last checked
- Oct 2026
Yam'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
7 tools, how they find and keep customers
Company Ops
6 tools, what the team runs on day to day
Email Delivery
Workspace
Security & Compliance
Yam tech stack FAQ
What tools does Yam use?
We've found 18 tools at Yam (yam.com). Edge & Hosting: Cloudflare and Microsoft Azure. Application: jQuery. Data & Observability: Google Analytics and Microsoft Clarity. Go-to-market: Meta Pixel, Google Ad Manager and Microsoft Xandr. Company Ops: Google Workspace, SendGrid and Let's Encrypt. Last checked October 3, 2026.
What cloud does Yam run on?
Yam uses Microsoft Azure for hosting. We found Microsoft Azure through custom domain.
What email provider does Yam use?
Yam uses Google Workspace for email and documents. We found Google Workspace through email records.
What analytics tools does Yam use?
Yam uses Google Analytics and Microsoft Clarity for analytics. We found Google Analytics through website code.
Does Yam use Cloudflare?
Yes. We found Cloudflare at Yam through DNS records and website code. Cloudflare is used by 147,753 companies we track.
How does runsonwhat know what Yam uses?
We read public traces only: Yam'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.