runsonwhat

Turm Kaffee's tech stack

What does Turm Kaffee use?

Turm Kaffee (turmkaffee.ch) uses at least 16 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, Shopify for its website and Klaviyo for marketing. Last checked .

Industry
Food & Beverages
Size
11–50 employees
Based in
Sankt Gallen, Switzerland
LinkedIn
Company page
Tools found
16
Categories
8
Layers
4 of 5
Last checked
Oct 2026

Turm Kaffee'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

6 tools, what the product is built with

Data & Observability

2 tools, what they measure and store

Go-to-market

5 tools, how they find and keep customers

Company Ops

3 tools, what the team runs on day to day

Turm Kaffee tech stack FAQ

What tools does Turm Kaffee use?

We've found 16 tools at Turm Kaffee (turmkaffee.ch). Application: jQuery, Google Fonts and Vimeo. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Meta Pixel, Google Ads and LinkedIn Insight Tag. Company Ops: Microsoft 365, reCAPTCHA and Cookiebot. Last checked October 4, 2026.

What email provider does Turm Kaffee use?

Turm Kaffee uses Microsoft 365 for email and documents. We found Microsoft 365 through email records.

What analytics tools does Turm Kaffee use?

Turm Kaffee uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.

What CMS does Turm Kaffee use?

Turm Kaffee uses Shopify for its website. We found Shopify through DNS records.

What marketing software does Turm Kaffee use?

Turm Kaffee uses Klaviyo for marketing. We found Klaviyo through DNS verification records.

Does Turm Kaffee use Microsoft 365?

Yes. We found Microsoft 365 at Turm Kaffee through email records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what Turm Kaffee uses?

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