BVG's tech stack
What does BVG use?
BVG (bvg.de) uses at least 13 tools we can see from public records, including Microsoft 365 for email and documents, Zendesk for customer support, Google Analytics for analytics and Instapage for its website. Last checked .
- Industry
- Passenger Transport
- Size
- 10,000+ employees
- Based in
- Germany
- Founded
- 1929
- Tools found
- 13
- Categories
- 10
- Layers
- 5 of 5
- Last checked
- Oct 2026
BVG'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
Frontend
Data & Observability
2 tools, what they measure and store
Go-to-market
4 tools, how they find and keep customers
Website & CMS
Marketing
Ads & Pixels
Support & Docs
Company Ops
5 tools, what the team runs on day to day
Email Delivery
Workspace
Dev Tools
BVG tech stack FAQ
What tools does BVG use?
We've found 13 tools at BVG (bvg.de). Edge & Hosting: Amazon CloudFront. Application: Next.js. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Google Ads, Zendesk and Instapage. Company Ops: Microsoft 365, Atlassian and Mailchimp Transactional. Last checked October 2, 2026.
What email provider does BVG use?
BVG uses Microsoft 365 for email and documents. We found Microsoft 365 through email records.
What does BVG use for customer support?
BVG uses Zendesk for customer support. We found Zendesk through email records.
What analytics tools does BVG use?
BVG uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
What CMS does BVG use?
BVG uses Instapage for its website. We found Instapage through custom domain.
Does BVG use Microsoft 365?
Yes. We found Microsoft 365 at BVG through email records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what BVG uses?
We read public traces only: BVG'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.