HSBC's tech stack
What does HSBC use?
HSBC (hsbc.com) uses at least 21 tools we can see from public records, including Amazon Web Services for hosting, Google Workspace for email and documents, Pendo for analytics and Akamai for content delivery. Last checked .
- Industry
- Financial Services
- Size
- 10,000+ employees
- Based in
- United Kingdom
- Founded
- 1865
- Company page
- Tools found
- 21
- Categories
- 13
- Layers
- 5 of 5
- Last checked
- Oct 2026
HSBC'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
Hosting & Cloud
CDN & Edge
Application
2 tools, what the product is built with
Backend & Database
Media & UI
Data & Observability
2 tools, what they measure and store
Analytics
Data Pipeline
Go-to-market
3 tools, how they find and keep customers
Marketing
Ads & Pixels
Company Ops
12 tools, what the team runs on day to day
Workspace
Dev Tools
Finance & Legal
Security & Compliance
HSBC tech stack FAQ
What tools does HSBC use?
We've found 21 tools at HSBC (hsbc.com). Edge & Hosting: Amazon Web Services and Akamai. Application: MongoDB Atlas and Brightcove. Data & Observability: Tealium and Pendo. Go-to-market: Meta Pixel and LinkedIn Insight Tag. Company Ops: Google Workspace, Atlassian and Proofpoint. Last checked October 2, 2026.
What cloud does HSBC run on?
HSBC uses Amazon Web Services for hosting. We found Amazon Web Services through website code.
What email provider does HSBC use?
HSBC uses Google Workspace for email and documents. We found Google Workspace through email records.
What analytics tools does HSBC use?
HSBC uses Pendo for analytics. We found Pendo through DNS verification records.
Does HSBC use Google Workspace?
Yes. We found Google Workspace at HSBC through email records. Google Workspace is used by 384,919 companies we track.
How does runsonwhat know what HSBC uses?
We read public traces only: HSBC'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.