runsonwhat

Musik Produktiv's tech stack

What does Musik Produktiv use?

Musik Produktiv (musik-produktiv.de) uses at least 15 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, Mailchimp for marketing and Bunny.net for content delivery. Last checked .

Based in
Walldorf, Germany
Founded
1974
Tools found
15
Categories
8
Layers
5 of 5
Last checked
Oct 2026

Musik Produktiv'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

2 tools, where the bytes are served from

Application

1 tool, what the product is built with

Media & UI

Data & Observability

2 tools, what they measure and store

Go-to-market

5 tools, how they find and keep customers

Company Ops

5 tools, what the team runs on day to day

Musik Produktiv tech stack FAQ

What tools does Musik Produktiv use?

We've found 15 tools at Musik Produktiv (musik-produktiv.de). Edge & Hosting: Bunny.net and smoxy. Application: Three.js. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Meta Pixel, Google Ads and Mailchimp. Company Ops: Microsoft 365, SendGrid and Apple Business. Last checked October 2, 2026.

What email provider does Musik Produktiv use?

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

What analytics tools does Musik Produktiv use?

Musik Produktiv uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.

What marketing software does Musik Produktiv use?

Musik Produktiv uses Mailchimp for marketing. We found Mailchimp through email records.

Does Musik Produktiv use Microsoft 365?

Yes. We found Microsoft 365 at Musik Produktiv through DNS verification records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what Musik Produktiv uses?

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