スーパーマーケットいちい's tech stack
What does スーパーマーケットいちい use?
スーパーマーケットいちい (ichii-yume.co.jp) uses at least 10 tools we can see from public records, including Google Workspace for email and documents, Google Analytics for analytics, WordPress for its website and reCAPTCHA for security. Last checked .
“福島県北地区をメインに食料品を中心としたスーパーマーケット事業の他、ペットショップ事業、ファストフード事業など多くのチェーンを展開している企業です。”
- Size
- 1–10 employees
- Based in
- 福島県 白河市東庁舎, Japan
- Founded
- 1969
- Company page
- Tools found
- 10
- Categories
- 7
- Layers
- 4 of 5
- Last checked
- Oct 2026
スーパーマーケットいちい'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.
Application
2 tools, what the product is built with
Frontend
Media & UI
Data & Observability
2 tools, what they measure and store
Go-to-market
4 tools, how they find and keep customers
Website & CMS
Ads & Pixels
Company Ops
2 tools, what the team runs on day to day
Workspace
Security & Compliance
スーパーマーケットいちい tech stack FAQ
What tools does スーパーマーケットいちい use?
We've found 10 tools at スーパーマーケットいちい (ichii-yume.co.jp). Application: jQuery and Google Fonts. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Meta Pixel, Google Ads and WordPress. Company Ops: Google Workspace and reCAPTCHA. Last checked October 3, 2026.
What email provider does スーパーマーケットいちい use?
スーパーマーケットいちい uses Google Workspace for email and documents. We found Google Workspace through email records.
What analytics tools does スーパーマーケットいちい use?
スーパーマーケットいちい uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
What CMS does スーパーマーケットいちい use?
スーパーマーケットいちい uses WordPress and All in One SEO for its website. We found WordPress through website code.
Does スーパーマーケットいちい use Google Workspace?
Yes. We found Google Workspace at スーパーマーケットいちい through email records. Google Workspace is used by 126,364 companies we track.
How does runsonwhat know what スーパーマーケットいちい uses?
We read public traces only: スーパーマーケットいちい'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.