runsonwhat

RBC 琉球放送's tech stack

What does RBC 琉球放送 use?

RBC 琉球放送 (rbc.co.jp) uses at least 27 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, WordPress for its website and Amazon CloudFront for content delivery. Last checked .

Size
51–200 employees
Based in
Naha, Japan
Founded
1960
LinkedIn
Company page
Tools found
27
Categories
9
Layers
5 of 5
Last checked
Oct 2026

RBC 琉球放送'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

Application

3 tools, what the product is built with

Data & Observability

3 tools, what they measure and store

Company Ops

3 tools, what the team runs on day to day

RBC 琉球放送 tech stack FAQ

What tools does RBC 琉球放送 use?

We've found 27 tools at RBC 琉球放送 (rbc.co.jp). Edge & Hosting: Amazon Route 53 and Amazon CloudFront. Application: jQuery, Google Fonts and Font Awesome. Data & Observability: Google Analytics, Google Tag Manager and Microsoft Clarity. Go-to-market: Google Ads, WordPress and Google Ad Manager. Company Ops: Microsoft 365, Google Workspace and Apple Business. Last checked October 3, 2026.

What email provider does RBC 琉球放送 use?

RBC 琉球放送 uses Microsoft 365, Google Workspace and Apple Business for email and documents. We found Microsoft 365 through DNS verification records.

What analytics tools does RBC 琉球放送 use?

RBC 琉球放送 uses Google Analytics, Google Tag Manager and Microsoft Clarity for analytics. We found Google Analytics through website code.

What CMS does RBC 琉球放送 use?

RBC 琉球放送 uses WordPress for its website. We found WordPress through website code.

Does RBC 琉球放送 use Microsoft 365?

Yes. We found Microsoft 365 at RBC 琉球放送 through DNS verification records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what RBC 琉球放送 uses?

We read public traces only: RBC 琉球放送'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.