株式会社KMS's tech stack
What does 株式会社KMS use?
株式会社KMS (kms3.com) uses at least 11 tools we can see from public records, including Google Cloud for hosting, Microsoft 365 for email and documents, Google Analytics for analytics and WordPress for its website. Last checked .
- Based in
- Japan
- Founded
- 2015
- Tools found
- 11
- Categories
- 8
- Layers
- 5 of 5
- Last checked
- Oct 2026
株式会社KMS'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.
Edge & Hosting
2 tools, where the bytes are served from
Hosting & Cloud
Application
2 tools, what the product is built with
Frontend
Media & UI
Data & Observability
2 tools, what they measure and store
Go-to-market
3 tools, how they find and keep customers
Company Ops
2 tools, what the team runs on day to day
株式会社KMS tech stack FAQ
What tools does 株式会社KMS use?
We've found 11 tools at 株式会社KMS (kms3.com). Edge & Hosting: Google Cloud and Microsoft Azure. Application: jQuery and Google Fonts. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: WordPress and Google Ads. Company Ops: Microsoft 365 and Google Workspace. Last checked October 4, 2026.
What cloud does 株式会社KMS run on?
株式会社KMS uses Google Cloud and Microsoft Azure for hosting. We found Google Cloud through custom domain.
What email provider does 株式会社KMS use?
株式会社KMS uses Microsoft 365 and Google Workspace for email and documents. We found Microsoft 365 through DNS verification records.
What analytics tools does 株式会社KMS use?
株式会社KMS uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
What CMS does 株式会社KMS use?
株式会社KMS uses WordPress for its website. We found WordPress through website code.
Does 株式会社KMS use Microsoft 365?
Yes. We found Microsoft 365 at 株式会社KMS through DNS verification records. Microsoft 365 is used by 398,121 companies we track.
How does runsonwhat know what 株式会社KMS uses?
We read public traces only: 株式会社KMS'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.