runsonwhat

eo光's tech stack

What does eo光 use?

eo光 (eonet.jp) uses at least 22 tools we can see from public records, including Microsoft Azure for hosting, Google Tag Manager for analytics and Cloudflare for content delivery. Last checked .

Based in
Japan
Tools found
22
Categories
8
Layers
4 of 5
Last checked
Oct 2026

eo光'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

2 tools, what the product is built with

Data & Observability

4 tools, what they measure and store

eo光 tech stack FAQ

What tools does eo光 use?

As of October 2026, runsonwhat has found 22 tools at eo光 (eonet.jp) in public records. Edge & Hosting: Cloudflare and Microsoft Azure. Application: jQuery and Google Fonts. Data & Observability: Google Tag Manager, Microsoft Clarity and Matomo. Go-to-market: Google Ads, Meta Pixel and Microsoft Ads. Last checked October 20, 2026.

What cloud does eo光 run on?

eo光 uses Microsoft Azure for hosting and cloud infrastructure, according to runsonwhat (October 2026). runsonwhat found Microsoft Azure through a subdomain that points at Microsoft Azure. Microsoft Azure is used by 46,579 companies runsonwhat tracks.

What analytics tools does eo光 use?

eo光 uses Google Tag Manager for analytics, alongside Microsoft Clarity and Matomo, according to runsonwhat (October 2026). runsonwhat found Google Tag Manager through Google Tag Manager code on eonet.jp. Google Tag Manager is used by 500,509 companies runsonwhat tracks.

Does eo光 use jQuery?

Yes. runsonwhat found jQuery at eo光 through jQuery code on eonet.jp. jQuery is a Frontend tool used by 913,502 companies runsonwhat tracks.

Which companies have a tech stack similar to eo光's?

The companies with the stacks most like eo光's are 株式会社臨海, auフィナンシャルサービス株式会社, 株式会社ROBOT PAYMENT and 北日本銀行, according to runsonwhat (October 2026). Each shares 9 to 17 tools with eo光, and rare tools count for more than common ones like Google Workspace, so the match reflects real stack choices.

How does runsonwhat know what eo光 uses?

runsonwhat reads public records only. Of the 22 tools at eo光, 19 were found through code on eonet.jp, 1 through DNS records, 1 through subdomains that point at the vendor and 1 through website configuration files. A tool is listed only when a direct record backs it up; DNS is rechecked weekly and eonet.jp about 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.