runsonwhat

Kenya Commercial Bank's tech stack

What does Kenya Commercial Bank use?

Kenya Commercial Bank (kcbgroup.com) uses at least 9 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, Cloudflare for content delivery and Amazon SES for email delivery. Last checked .

Industry
Banking
Size
5,001–10,000 employees
Based in
Nairobi, Kenya
Founded
2015
LinkedIn
Company page
Tools found
9
Categories
8
Layers
5 of 5
Last checked
Oct 2026

Kenya Commercial Bank'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

Data & Observability

2 tools, what they measure and store

Go-to-market

1 tool, how they find and keep customers

Company Ops

4 tools, what the team runs on day to day

Email Delivery

Dev Tools

Security & Compliance

Kenya Commercial Bank tech stack FAQ

What tools does Kenya Commercial Bank use?

We've found 9 tools at Kenya Commercial Bank (kcbgroup.com). Edge & Hosting: Cloudflare. Application: jQuery. Data & Observability: Google Analytics and Google Tag Manager. Company Ops: Microsoft 365, Amazon SES and Zscaler. Last checked October 2, 2026.

What email provider does Kenya Commercial Bank use?

Kenya Commercial Bank uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records and email records.

What analytics tools does Kenya Commercial Bank use?

Kenya Commercial Bank uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.

Does Kenya Commercial Bank use Microsoft 365?

Yes. We found Microsoft 365 at Kenya Commercial Bank through DNS verification records and email records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what Kenya Commercial Bank uses?

We read public traces only: Kenya Commercial Bank'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.