runsonwhat

Blaser's tech stack

What does Blaser use?

Blaser (blaser.de) uses at least 13 tools we can see from public records, including IONOS for hosting, Microsoft 365 for email and documents, Google Analytics for analytics and PayPal for payments. Last checked .

Based in
Germany
Founded
1957
Tools found
13
Categories
7
Layers
5 of 5
Last checked
Oct 2026

Blaser'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

1 tool, where the bytes are served from

Hosting & Cloud

Application

4 tools, what the product is built with

Data & Observability

3 tools, what they measure and store

Go-to-market

3 tools, how they find and keep customers

Company Ops

2 tools, what the team runs on day to day

Security & Compliance

Blaser tech stack FAQ

What tools does Blaser use?

We've found 13 tools at Blaser (blaser.de). Edge & Hosting: IONOS. Application: Google Maps, Adobe Fonts and PayPal. Data & Observability: Google Analytics, Google Tag Manager and Hotjar. Go-to-market: Google Ads, Meta Pixel and Microsoft Ads. Company Ops: Microsoft 365 and Cookiebot. Last checked October 2, 2026.

What cloud does Blaser run on?

Blaser uses IONOS for hosting. We found IONOS through website code.

What email provider does Blaser use?

Blaser uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records and email records.

What payment provider does Blaser use?

Blaser uses PayPal for payments. We found PayPal through website code.

What analytics tools does Blaser use?

Blaser uses Google Analytics, Google Tag Manager and Hotjar for analytics. We found Google Analytics through website code.

Does Blaser use Microsoft 365?

Yes. We found Microsoft 365 at Blaser through DNS verification records and email records. Microsoft 365 is used by 370,926 companies we track.

How does runsonwhat know what Blaser uses?

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