株式会社スポーツフィールド's tech stack
What does 株式会社スポーツフィールド use?
株式会社スポーツフィールド (sports-f.co.jp) uses at least 14 tools we can see from public records, including Google Workspace for email and documents, Google Analytics for analytics, WordPress for its website and SendGrid for email delivery. Last checked .
- Size
- 1–10 employees
- Based in
- Tokyo, Japan
- Founded
- 2010
- Company page
- Tools found
- 14
- Categories
- 10
- 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
Application
4 tools, what the product is built with
Frontend
Data & Observability
2 tools, what they measure and store
Go-to-market
4 tools, how they find and keep customers
Website & CMS
Marketing
Ads & Pixels
Company Ops
3 tools, what the team runs on day to day
株式会社スポーツフィールド tech stack FAQ
What tools does 株式会社スポーツフィールド use?
We've found 14 tools at 株式会社スポーツフィールド (sports-f.co.jp). Edge & Hosting: Amazon Route 53. Application: jQuery, GSAP and Adobe Fonts. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Google Ads, WordPress and Yoast SEO. Company Ops: Google Workspace, SendGrid and GlobalSign. Last checked October 3, 2026.
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 and Google Tag Manager for analytics. We found Google Analytics through website code.
What CMS does 株式会社スポーツフィールド use?
株式会社スポーツフィールド uses WordPress and Yoast SEO for its website. We found WordPress 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.