創味食品's tech stack
What does 創味食品 use?
創味食品 (somi.co.jp) uses at least 11 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, WordPress for its website and reCAPTCHA for security. Last checked .
- Industry
- Food Production
- Size
- 201–1,000 employees
- Based in
- Kyoto, Japan
- Founded
- 1950
- Company page
- Tools found
- 11
- Categories
- 8
- 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
3 tools, what they measure and store
Go-to-market
3 tools, how they find and keep customers
Company Ops
3 tools, what the team runs on day to day
Workspace
Security & Compliance
創味食品 tech stack FAQ
What tools does 創味食品 use?
We've found 11 tools at 創味食品 (somi.co.jp). Application: jQuery and Google Fonts. Data & Observability: Google Analytics, Google Tag Manager and Microsoft Clarity. Go-to-market: Google Ads and WordPress. Company Ops: Microsoft 365, Google Workspace and reCAPTCHA. Last checked October 3, 2026.
What email provider does 創味食品 use?
創味食品 uses Microsoft 365 and Google Workspace for email and documents. We found Microsoft 365 through DNS verification records and email records.
What analytics tools does 創味食品 use?
創味食品 uses Google Analytics, Google Tag Manager and Microsoft Clarity for analytics. We found Google Analytics through website code.
What CMS does 創味食品 use?
創味食品 uses WordPress for its website. We found WordPress through website code.
Does 創味食品 use Microsoft 365?
Yes. We found Microsoft 365 at 創味食品 through DNS verification records and email records. Microsoft 365 is used by 245,233 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.