runsonwhat

Läbesruum's tech stack

What does Läbesruum use?

Läbesruum (laebesruum.ch) uses at least 10 tools we can see from public records, including WP Engine for hosting, Microsoft 365 for email and documents, Google Analytics for analytics and WordPress for its website. Last checked .

Industry
Cleaning
Size
51–200 employees
Based in
Winterthur, Switzerland
Founded
1990
LinkedIn
Company page
Tools found
10
Categories
8
Layers
4 of 5
Last checked
Oct 2026

Läbesruum'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

Data & Observability

2 tools, what they measure and store

Go-to-market

3 tools, how they find and keep customers

Company Ops

4 tools, what the team runs on day to day

Email Delivery

Security & Compliance

Läbesruum tech stack FAQ

What tools does Läbesruum use?

We've found 10 tools at Läbesruum (laebesruum.ch). Edge & Hosting: WP Engine. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Google Ads and WordPress. Company Ops: Microsoft 365, SendGrid and Apple Business. Last checked October 4, 2026.

What cloud does Läbesruum run on?

Läbesruum uses WP Engine for hosting. We found WP Engine through custom domain.

What email provider does Läbesruum use?

Läbesruum uses Microsoft 365 and Apple Business for email and documents. We found Microsoft 365 through email records.

What analytics tools does Läbesruum use?

Läbesruum uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.

What CMS does Läbesruum use?

Läbesruum uses WordPress for its website. We found WordPress through website code.

Does Läbesruum use Microsoft 365?

Yes. We found Microsoft 365 at Läbesruum through email records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what Läbesruum uses?

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