EM Microelectronic's tech stack
What does EM Microelectronic use?
EM Microelectronic (emmicroelectronic.com) uses at least 12 tools we can see from public records, including Microsoft Azure for hosting, Google Analytics for analytics, Akamai mPulse for monitoring and Akamai for content delivery. Last checked .
- Industry
- Semiconductor
- Size
- 201–1,000 employees
- Based in
- Marin-Epagnier, Switzerland
- Founded
- 1975
- Company page
- Tools found
- 12
- Categories
- 9
- Layers
- 5 of 5
- Last checked
- Oct 2026
EM Microelectronic'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
4 tools, what they measure and store
Go-to-market
1 tool, how they find and keep customers
Ads & Pixels
Company Ops
4 tools, what the team runs on day to day
EM Microelectronic tech stack FAQ
What tools does EM Microelectronic use?
We've found 12 tools at EM Microelectronic (emmicroelectronic.com). Edge & Hosting: Microsoft Azure and Akamai. Application: jQuery. Data & Observability: Google Analytics, Google Tag Manager and Hotjar. Go-to-market: Google Ads. Company Ops: Atlassian, Adobe and Red Sift OnDMARC. Last checked October 3, 2026.
What cloud does EM Microelectronic run on?
EM Microelectronic uses Microsoft Azure for hosting. We found Microsoft Azure through DNS records and website code.
What analytics tools does EM Microelectronic use?
EM Microelectronic uses Google Analytics, Google Tag Manager and Hotjar for analytics. We found Google Analytics through website code.
Does EM Microelectronic use jQuery?
Yes. We found jQuery at EM Microelectronic through website code. jQuery is used by 583,189 companies we track.
How does runsonwhat know what EM Microelectronic uses?
We read public traces only: EM Microelectronic'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.