京都銀行's tech stack
What does 京都銀行 use?
京都銀行 (kyotobank.co.jp) uses at least 16 tools we can see from public records, including Amazon Web Services for hosting, Microsoft 365 for email and documents, Google Analytics for analytics and Akamai for content delivery. Last checked .
- Industry
- Financial Services
- Size
- 1,001–5,000 employees
- Based in
- Kyoto, Japan
- Founded
- 1941
- Company page
- Tools found
- 16
- 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
3 tools, where the bytes are served from
Application
3 tools, what the product is built with
Frontend
Media & UI
Data & Observability
2 tools, what they measure and store
Go-to-market
5 tools, how they find and keep customers
Company Ops
3 tools, what the team runs on day to day
Email Delivery
Workspace
京都銀行 tech stack FAQ
What tools does 京都銀行 use?
We've found 16 tools at 京都銀行 (kyotobank.co.jp). Edge & Hosting: Amazon Route 53, Amazon Web Services and Akamai. Application: jQuery, Vimeo and YouTube. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Meta Pixel, Google Ads and Microsoft Ads. Company Ops: Microsoft 365, SendGrid and Amazon SES. Last checked October 2, 2026.
What cloud does 京都銀行 run on?
京都銀行 uses Amazon Web Services for hosting. We found Amazon Web Services through website code.
What email provider does 京都銀行 use?
京都銀行 uses Microsoft 365 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.