株式会社EduLab's tech stack
What does 株式会社EduLab use?
株式会社EduLab (edulab-inc.com) uses at least 11 tools we can see from public records, including Google Workspace for email and documents, Salesforce for sales, Google Analytics for analytics and WordPress for its website. Last checked .
- Based in
- Japan
- Founded
- 2015
- Tools found
- 11
- Categories
- 10
- Layers
- 5 of 5
- Last checked
- Oct 2026
株式会社EduLab'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
3 tools, what the product is built with
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
Workspace
Security & Compliance
株式会社EduLab tech stack FAQ
What tools does 株式会社EduLab use?
We've found 11 tools at 株式会社EduLab (edulab-inc.com). Edge & Hosting: Amazon CloudFront. Application: jQuery, Google Fonts and Anthropic. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: WordPress and Salesforce. Company Ops: Google Workspace and GlobalSign. Last checked October 3, 2026.
What CRM does 株式会社EduLab use?
株式会社EduLab uses Salesforce for sales and CRM. We found Salesforce through email records.
What email provider does 株式会社EduLab use?
株式会社EduLab uses Google Workspace for email and documents. We found Google Workspace through email records.
What analytics tools does 株式会社EduLab use?
株式会社EduLab uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
What CMS does 株式会社EduLab use?
株式会社EduLab uses WordPress for its website. We found WordPress through website code.
Does 株式会社EduLab use Google Workspace?
Yes. We found Google Workspace at 株式会社EduLab through email records. Google Workspace is used by 126,364 companies we track.
How does runsonwhat know what 株式会社EduLab uses?
We read public traces only: 株式会社EduLab'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.