株式会社リスキル's tech stack
What does 株式会社リスキル use?
株式会社リスキル (recurrent.jp) uses at least 13 tools we can see from public records, including Heroku for hosting, Google Workspace for email and documents, Google Analytics for analytics and SendGrid for email delivery. Last checked .
- Industry
- Corporate Education
- Size
- 51–200 employees
- Based in
- Japan
- Founded
- 2022
- Company page
- Tools found
- 13
- 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
Hosting & Cloud
Application
2 tools, what the product is built with
Media & UI
Data & Observability
3 tools, what they measure and store
Go-to-market
5 tools, how they find and keep customers
Company Ops
2 tools, what the team runs on day to day
Email Delivery
Workspace
株式会社リスキル tech stack FAQ
What tools does 株式会社リスキル use?
We've found 13 tools at 株式会社リスキル (recurrent.jp). Edge & Hosting: Heroku. Application: YouTube and Font Awesome. Data & Observability: Google Analytics, Google Tag Manager and Microsoft Clarity. Go-to-market: Meta Pixel, Google Ads and Microsoft Ads. Company Ops: Google Workspace and SendGrid. Last checked October 4, 2026.
What cloud does 株式会社リスキル run on?
株式会社リスキル uses Heroku for hosting. We found Heroku through custom domain and website code.
What email provider does 株式会社リスキル use?
株式会社リスキル uses Google Workspace for email and documents. We found Google Workspace through email 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 Google Workspace?
Yes. We found Google Workspace at 株式会社リスキル through email records. Google Workspace is used by 126,364 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.