スポーツブル's tech stack
What does スポーツブル use?
スポーツブル (sportsbull.jp) uses at least 14 tools we can see from public records, including Google Cloud for hosting, Microsoft 365 for email and documents, Google Analytics for analytics and Amazon CloudFront for content delivery. Last checked .
- Industry
- Software
- Size
- 11–50 employees
- Based in
- Nishishimbashi, Japan
- Founded
- 2015
- 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
5 tools, where the bytes are served from
Hosting & Cloud
Application
2 tools, what the product is built with
Frontend
Media & UI
Data & Observability
2 tools, what they measure and store
Go-to-market
2 tools, how they find and keep customers
Marketing
Ads & Pixels
Company Ops
3 tools, what the team runs on day to day
Security & Compliance
スポーツブル tech stack FAQ
What tools does スポーツブル use?
We've found 14 tools at スポーツブル (sportsbull.jp). Edge & Hosting: Amazon Route 53, Amazon CloudFront and Google Cloud. Application: YouTube and Next.js. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Google Ads. Company Ops: Microsoft 365, Google Workspace and GlobalSign. Last checked October 2, 2026.
What cloud does スポーツブル run on?
スポーツブル uses Google Cloud for hosting. We found Google Cloud through website code.
What email provider does スポーツブル use?
スポーツブル uses Microsoft 365 and Google Workspace for email and documents. We found Microsoft 365 through DNS verification records.
What analytics tools does スポーツブル use?
スポーツブル uses Google Analytics and Google Tag Manager 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.