GOODSMILE RACING's tech stack
What does GOODSMILE RACING use?
GOODSMILE RACING (goodsmileracing.com) uses at least 8 tools we can see from public records, including Google Workspace for email and documents, Google Analytics for analytics, WordPress for its website and Amazon CloudFront for content delivery. Last checked .
- Based in
- Japan
- Founded
- 2009
- Tools found
- 8
- Categories
- 8
- Layers
- 5 of 5
- Last checked
- Oct 2026
GOODSMILE RACING'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
CDN & Edge
Application
1 tool, what the product is built with
Frontend
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
2 tools, how they find and keep customers
Website & CMS
Marketing
Company Ops
2 tools, what the team runs on day to day
Email Delivery
Workspace
GOODSMILE RACING tech stack FAQ
What tools does GOODSMILE RACING use?
We've found 8 tools at GOODSMILE RACING (goodsmileracing.com). Edge & Hosting: Amazon Route 53 and Amazon CloudFront. Application: jQuery. Data & Observability: Google Analytics. Go-to-market: WordPress. Company Ops: Google Workspace and SendGrid. Last checked October 3, 2026.
What email provider does GOODSMILE RACING use?
GOODSMILE RACING uses Google Workspace for email and documents. We found Google Workspace through email records.
What analytics tools does GOODSMILE RACING use?
GOODSMILE RACING uses Google Analytics for analytics. We found Google Analytics through website code.
What CMS does GOODSMILE RACING use?
GOODSMILE RACING uses WordPress for its website. We found WordPress through website code.
Does GOODSMILE RACING use Google Workspace?
Yes. We found Google Workspace at GOODSMILE RACING through email records. Google Workspace is used by 126,364 companies we track.
How does runsonwhat know what GOODSMILE RACING uses?
We read public traces only: GOODSMILE RACING'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.