runsonwhat

株式会社東京技研's tech stack

What does 株式会社東京技研 use?

株式会社東京技研 (tokyogiken.com) uses at least 7 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics and WordPress for its website. Last checked .

Based in
Japan
Founded
1968
Re-check liveVisit tokyogiken.com
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

Workspace

Companies like 株式会社東京技研 also use

Tools common among companies with a similar stack that we haven't found at 株式会社東京技研.

Companies with a stack like 株式会社東京技研's

Ranked by shared tools, with rare tools counting more.

株式会社東京技研 tech stack FAQ

What tools does 株式会社東京技研 use?

We've found 7 tools at 株式会社東京技研 (tokyogiken.com). Application: jQuery, Adobe Fonts and Three.js. Data & Observability: Google Analytics. Go-to-market: WordPress and All in One SEO. Company Ops: Microsoft 365. Last checked October 3, 2026.

What email provider does 株式会社東京技研 use?

株式会社東京技研 uses Microsoft 365 for email and documents. We found Microsoft 365 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 Microsoft 365?

Yes. We found Microsoft 365 at 株式会社東京技研 through 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.