グローリー株式会社's tech stack
What does グローリー株式会社 use?
グローリー株式会社 (glory.co.jp) uses at least 12 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, Amazon CloudFront for content delivery and Valimail for security. Last checked .
- Industry
- Machinery
- Size
- 1,001–5,000 employees
- Based in
- Himeji, Japan
- Founded
- 1918
- Company page
- Tools found
- 12
- Categories
- 7
- Layers
- 5 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.
Edge & Hosting
1 tool, where the bytes are served from
CDN & Edge
Application
1 tool, what the product is built with
Frontend
Data & Observability
3 tools, what they measure and store
Go-to-market
4 tools, how they find and keep customers
Marketing
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 12 tools at グローリー株式会社 (glory.co.jp). Edge & Hosting: Amazon CloudFront. Application: jQuery. Data & Observability: Google Analytics, Google Tag Manager and Microsoft Clarity. Go-to-market: Meta Pixel, Google Ads and Microsoft Ads. Company Ops: Microsoft 365, Valimail and OneTrust. Last checked October 3, 2026.
What email provider does グローリー株式会社 use?
グローリー株式会社 uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records.
What analytics tools does グローリー株式会社 use?
グローリー株式会社 uses Google Analytics, Google Tag Manager and Microsoft Clarity for analytics. We found Google Analytics through website code.
Does グローリー株式会社 use Microsoft 365?
Yes. We found Microsoft 365 at グローリー株式会社 through DNS verification 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.