runsonwhat

Wernsing Feinkost's tech stack

What does Wernsing Feinkost use?

Wernsing Feinkost (wernsing.de) uses at least 14 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, LinkedIn for marketing and Cookiebot for security. Last checked .

Industry
Food
Based in
Germany
Founded
1962
Tools found
14
Categories
9
Layers
4 of 5
Last checked
Oct 2026

Wernsing Feinkost'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

3 tools, what the product is built with

Data & Observability

1 tool, what they measure and store

Go-to-market

4 tools, how they find and keep customers

Company Ops

6 tools, what the team runs on day to day

Wernsing Feinkost tech stack FAQ

What tools does Wernsing Feinkost use?

We've found 14 tools at Wernsing Feinkost (wernsing.de). Application: jQuery, Vimeo and YouTube. Data & Observability: Google Analytics. Go-to-market: Google Ads, LinkedIn and Perspective. Company Ops: Microsoft 365, Apple Business and Atlassian. Last checked October 3, 2026.

What email provider does Wernsing Feinkost use?

Wernsing Feinkost uses Microsoft 365 and Apple Business for email and documents. We found Microsoft 365 through DNS verification records and email records.

What analytics tools does Wernsing Feinkost use?

Wernsing Feinkost uses Google Analytics for analytics. We found Google Analytics through website code.

What marketing software does Wernsing Feinkost use?

Wernsing Feinkost uses LinkedIn and Perspective for marketing. We found LinkedIn through DNS verification records.

Does Wernsing Feinkost use Microsoft 365?

Yes. We found Microsoft 365 at Wernsing Feinkost through DNS verification records and email records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what Wernsing Feinkost uses?

We read public traces only: Wernsing Feinkost'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.