runsonwhat

Gußwerke Leipzig/Saarbrücken's tech stack

What does Gußwerke Leipzig/Saarbrücken use?

Gußwerke Leipzig/Saarbrücken (gusswerke.de) uses at least 8 tools we can see from public records, including Microsoft 365 for email and documents and Google Analytics for analytics. Last checked .

Industry
Automotive Supplier
Based in
Germany
Founded
2011
Re-check liveVisit gusswerke.de
Tools found
8
Categories
5
Layers
4 of 5
Last checked
Oct 2026

Gußwerke Leipzig/Saarbrücken'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

Media & UI

Data & Observability

2 tools, what they measure and store

Analytics

Go-to-market

2 tools, how they find and keep customers

Marketing

Ads & Pixels

Company Ops

2 tools, what the team runs on day to day

Workspace

Gußwerke Leipzig/Saarbrücken tech stack FAQ

What tools does Gußwerke Leipzig/Saarbrücken use?

We've found 8 tools at Gußwerke Leipzig/Saarbrücken (gusswerke.de). Application: YouTube and Vimeo. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Google Ads. Company Ops: Microsoft 365 and Google Workspace. Last checked October 2, 2026.

What email provider does Gußwerke Leipzig/Saarbrücken use?

Gußwerke Leipzig/Saarbrücken uses Microsoft 365 and Google Workspace for email and documents. We found Microsoft 365 through DNS verification records.

What analytics tools does Gußwerke Leipzig/Saarbrücken use?

Gußwerke Leipzig/Saarbrücken uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.

Does Gußwerke Leipzig/Saarbrücken use Microsoft 365?

Yes. We found Microsoft 365 at Gußwerke Leipzig/Saarbrücken through DNS verification records. Microsoft 365 is used by 319,377 companies we track.

How does runsonwhat know what Gußwerke Leipzig/Saarbrücken uses?

We read public traces only: Gußwerke Leipzig/Saarbrücken'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.