KAB 熊本朝日放送's tech stack
What does KAB 熊本朝日放送 use?
KAB 熊本朝日放送 (kab.co.jp) uses at least 10 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 .
- Industry
- Public Relations and Communications
- Size
- 51–200 employees
- Based in
- Nihongi, Japan
- Founded
- 1989
- Company page
- Tools found
- 10
- Categories
- 8
- Layers
- 5 of 5
- Last checked
- Oct 2026
KAB 熊本朝日放送'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
1 tool, 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
2 tools, what the team runs on day to day
Email Delivery
Workspace
KAB 熊本朝日放送 tech stack FAQ
What tools does KAB 熊本朝日放送 use?
We've found 10 tools at KAB 熊本朝日放送 (kab.co.jp). Edge & Hosting: Amazon CloudFront. Application: jQuery. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Meta Pixel, Google Ads and WordPress. Company Ops: Google Workspace and Amazon SES. Last checked October 2, 2026.
What email provider does KAB 熊本朝日放送 use?
KAB 熊本朝日放送 uses Google Workspace for email and documents. We found Google Workspace through email records.
What analytics tools does KAB 熊本朝日放送 use?
KAB 熊本朝日放送 uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
What CMS does KAB 熊本朝日放送 use?
KAB 熊本朝日放送 uses WordPress for its website. We found WordPress through website code.
Does KAB 熊本朝日放送 use Google Workspace?
Yes. We found Google Workspace at KAB 熊本朝日放送 through email records. Google Workspace is used by 126,364 companies we track.
How does runsonwhat know what KAB 熊本朝日放送 uses?
We read public traces only: KAB 熊本朝日放送'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.