runsonwhat

スーパーマーケット オオゼキ's tech stack

What does スーパーマーケット オオゼキ use?

スーパーマーケット オオゼキ (ozeki-net.co.jp) uses at least 7 tools we can see from public records, including Google Workspace for email and documents, Google Analytics for analytics and WordPress for its website. Last checked .

“スーパーマーケット オオゼキは地域に密着した経営で、生鮮食料品、一般食料品、酒類、日用雑貨など選りすぐりの商品を販売しております。”

Industry
Retail
Size
1,001–5,000 employees
Based in
Kitazawa, Japan
Founded
1975
LinkedIn
Company page
Tools found
7
Categories
6
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

Data & Observability

1 tool, what they measure and store

Go-to-market

3 tools, how they find and keep customers

Company Ops

1 tool, what the team runs on day to day

スーパーマーケット オオゼキ tech stack FAQ

What tools does スーパーマーケット オオゼキ use?

We've found 7 tools at スーパーマーケット オオゼキ (ozeki-net.co.jp). Application: jQuery and Google Fonts. Data & Observability: Google Analytics. Go-to-market: WordPress and All in One SEO. Company Ops: Google Workspace. Last checked October 2, 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 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.