Wiesbadener Volksbank Eg's tech stack
What does Wiesbadener Volksbank Eg use?
Wiesbadener Volksbank Eg (wvb.de) uses at least 13 tools we can see from public records, including Microsoft 365 for email and documents, Inxmail for marketing, Bugsnag for monitoring and Mailjet for email delivery. Last checked .
- Industry
- Banking
- Size
- 201–1,000 employees
- Based in
- Wiesbaden, Germany
- Founded
- 1860
- Company page
- Tools found
- 13
- Categories
- 7
- Layers
- 4 of 5
- Last checked
- Oct 2026
Wiesbadener Volksbank Eg'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
Go-to-market
2 tools, how they find and keep customers
Company Ops
5 tools, what the team runs on day to day
Email Delivery
Workspace
Security & Compliance
Wiesbadener Volksbank Eg tech stack FAQ
What tools does Wiesbadener Volksbank Eg use?
We've found 13 tools at Wiesbadener Volksbank Eg (wvb.de). Application: Angular and Adobe Dynamic Media Classic. Data & Observability: Bugsnag, Akamai mPulse and Dynatrace. Go-to-market: Inxmail. Company Ops: Microsoft 365, Apple Business and Mailjet. Last checked October 7, 2026.
What email provider does Wiesbadener Volksbank Eg use?
Wiesbadener Volksbank Eg uses Microsoft 365 and Apple Business for email and documents. We found Microsoft 365 through DNS verification records.
What marketing software does Wiesbadener Volksbank Eg use?
Wiesbadener Volksbank Eg uses Inxmail for marketing. We found Inxmail through email records.
Does Wiesbadener Volksbank Eg use Microsoft 365?
Yes. We found Microsoft 365 at Wiesbadener Volksbank Eg through DNS verification records. Microsoft 365 is used by 692,920 companies we track.
How does runsonwhat know what Wiesbadener Volksbank Eg uses?
We read public traces only: Wiesbadener Volksbank Eg'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.