ヤヱガキグループ - 酒造・発酵・バイオテクノロジー -'s tech stack
What does ヤヱガキグループ - 酒造・発酵・バイオテクノロジー - use?
ヤヱガキグループ - 酒造・発酵・バイオテクノロジー - (yaegaki.co.jp) uses at least 7 tools we can see from public records, including Google Analytics for analytics, WordPress for its website and reCAPTCHA for security. Last checked .
“自然の力を、誰かが待ち望む力へ。私たちヤヱガキグループは、独自の発酵技術によって、人や社会への貢献を続けてきました。まだ見ぬ「発酵」の力を引き出し、世の中の期待を超える未来づくりを目指していきます。”
- Based in
- Japan
- Founded
- 1963
- Tools found
- 7
- Categories
- 5
- 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
3 tools, what the product is built with
Frontend
Media & UI
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
2 tools, how they find and keep customers
Website & CMS
Company Ops
1 tool, what the team runs on day to day
Security & Compliance
ヤヱガキグループ - 酒造・発酵・バイオテクノロジー - tech stack FAQ
What tools does ヤヱガキグループ - 酒造・発酵・バイオテクノロジー - use?
We've found 7 tools at ヤヱガキグループ - 酒造・発酵・バイオテクノロジー - (yaegaki.co.jp). Application: jQuery, Google Fonts and GSAP. Data & Observability: Google Analytics. Go-to-market: WordPress and All in One SEO. Company Ops: reCAPTCHA. Last checked October 3, 2026.
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 Analytics?
Yes. We found Google Analytics at ヤヱガキグループ - 酒造・発酵・バイオテクノロジー - through website code. Google Analytics is used by 89,943 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.