AEON Hokkaido's tech stack
What does AEON Hokkaido use?
AEON Hokkaido (aeon-hokkaido.jp) uses at least 12 tools we can see from public records, including Google Workspace for email and documents, Google Analytics for analytics, WordPress for its website and Amazon CloudFront for content delivery. Last checked .
- Based in
- Japan
- Founded
- 1978
- Tools found
- 12
- Categories
- 9
- Layers
- 5 of 5
- Last checked
- Oct 2026
AEON Hokkaido'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
1 tool, where the bytes are served from
CDN & Edge
Application
2 tools, what the product is built with
Frontend
Media & UI
Data & Observability
2 tools, what they measure and store
Go-to-market
5 tools, how they find and keep customers
Website & CMS
Marketing
Ads & Pixels
Company Ops
2 tools, what the team runs on day to day
Email Delivery
Workspace
AEON Hokkaido tech stack FAQ
What tools does AEON Hokkaido use?
We've found 12 tools at AEON Hokkaido (aeon-hokkaido.jp). Edge & Hosting: Amazon CloudFront. Application: jQuery and YouTube. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Meta Pixel, Google Ads and WordPress. Company Ops: Google Workspace and SendGrid. Last checked October 3, 2026.
What email provider does AEON Hokkaido use?
AEON Hokkaido uses Google Workspace for email and documents. We found Google Workspace through email records.
What analytics tools does AEON Hokkaido use?
AEON Hokkaido uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
What CMS does AEON Hokkaido use?
AEON Hokkaido uses WordPress for its website. We found WordPress through website code.
Does AEON Hokkaido use Google Workspace?
Yes. We found Google Workspace at AEON Hokkaido through email records. Google Workspace is used by 126,364 companies we track.
How does runsonwhat know what AEON Hokkaido uses?
We read public traces only: AEON Hokkaido'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.