Commerzbank's tech stack
What does Commerzbank use?
Commerzbank (commerzbank.de) uses at least 15 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, SAS Customer Intelligence 360 for marketing and Dynatrace for monitoring. Last checked .
- Industry
- Financial Services
- Size
- 201–1,000 employees
- Based in
- Frankfurt, Germany
- Founded
- 2002
- Company page
- Tools found
- 15
- Categories
- 8
- Layers
- 4 of 5
- Last checked
- Oct 2026
Commerzbank'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.
Application
2 tools, what the product is built with
Frontend
Media & UI
Data & Observability
4 tools, what they measure and store
Analytics
Go-to-market
5 tools, how they find and keep customers
Company Ops
4 tools, what the team runs on day to day
Workspace
Security & Compliance
Commerzbank tech stack FAQ
What tools does Commerzbank use?
We've found 15 tools at Commerzbank (commerzbank.de). Application: Vimeo and Next.js. Data & Observability: Google Analytics, Dynatrace and Bugsnag. Go-to-market: Google Ads, Meta Pixel and TikTok Pixel. Company Ops: Microsoft 365, Apple Business and GlobalSign. Last checked October 2, 2026.
What email provider does Commerzbank use?
Commerzbank uses Microsoft 365 and Apple Business for email and documents. We found Microsoft 365 through email records.
What analytics tools does Commerzbank use?
Commerzbank uses Google Analytics for analytics. We found Google Analytics through website code.
What marketing software does Commerzbank use?
Commerzbank uses SAS Customer Intelligence 360 for marketing. We found SAS Customer Intelligence 360 through custom domain.
Does Commerzbank use Microsoft 365?
Yes. We found Microsoft 365 at Commerzbank through email records. Microsoft 365 is used by 328,140 companies we track.
How does runsonwhat know what Commerzbank uses?
We read public traces only: Commerzbank'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.