runsonwhat

Säbu's tech stack

What does Säbu use?

Säbu (saebu.de) uses at least 9 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics and Mailtrap for email delivery. Last checked .

Industry
Construction
Size
1–10 employees
Based in
Morsbach, Germany
Founded
1924
LinkedIn
Company page
Re-check liveVisit saebu.de
Tools found
9
Categories
6
Layers
4 of 5
Last checked
Oct 2026

Säbu'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

2 tools, what the product is built with

Media & UI

Data & Observability

2 tools, what they measure and store

Analytics

Go-to-market

2 tools, how they find and keep customers

Marketing

Ads & Pixels

Company Ops

3 tools, what the team runs on day to day

Email Delivery

Workspace

Companies like Säbu also use

Tools common among companies with a similar stack that we haven't found at Säbu.

Companies with a stack like Säbu's

Ranked by shared tools, with rare tools counting more.

Säbu tech stack FAQ

What tools does Säbu use?

We've found 9 tools at Säbu (saebu.de). Application: Vimeo and YouTube. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Google Ads. Company Ops: Microsoft 365, Exclaimer and Mailtrap. Last checked October 3, 2026.

What email provider does Säbu use?

Säbu uses Microsoft 365 and Exclaimer for email and documents. We found Microsoft 365 through DNS verification records and email records.

What analytics tools does Säbu use?

Säbu uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.

Does Säbu use Microsoft 365?

Yes. We found Microsoft 365 at Säbu through DNS verification records and email records. Microsoft 365 is used by 284,338 companies we track.

How does runsonwhat know what Säbu uses?

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