runsonwhat

kontrabande Verlag's tech stack

What does kontrabande Verlag use?

kontrabande Verlag (kontrabande.de) uses at least 7 tools we can see from public records, including HubSpot for sales, Matomo for analytics and Metricool for marketing. Last checked .

Based in
Germany
LinkedIn
Company page
Re-check liveVisit kontrabande.de
Tools found
7
Categories
6
Layers
3 of 5
Last checked
Oct 2026

kontrabande Verlag'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

Frontend

Media & UI

Data & Observability

1 tool, what they measure and store

Analytics

Go-to-market

3 tools, how they find and keep customers

Marketing

Ads & Pixels

Sales & CRM

Companies like kontrabande Verlag also use

Tools common among companies with a similar stack that we haven't found at kontrabande Verlag.

Companies with a stack like kontrabande Verlag's

Ranked by shared tools, with rare tools counting more.

kontrabande Verlag tech stack FAQ

What tools does kontrabande Verlag use?

We've found 7 tools at kontrabande Verlag (kontrabande.de). Application: jQuery, Google Fonts and Mapbox. Data & Observability: Matomo. Go-to-market: Meta Pixel, HubSpot and Metricool. Last checked October 4, 2026.

What CRM does kontrabande Verlag use?

kontrabande Verlag uses HubSpot for sales and CRM. We found HubSpot through email records and website code.

What analytics tools does kontrabande Verlag use?

kontrabande Verlag uses Matomo for analytics. We found Matomo through website code.

What marketing software does kontrabande Verlag use?

kontrabande Verlag uses Metricool for marketing. We found Metricool through website code.

Does kontrabande Verlag use jQuery?

Yes. We found jQuery at kontrabande Verlag through website code. jQuery is used by 67,244 companies we track.

How does runsonwhat know what kontrabande Verlag uses?

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