runsonwhat

Bayerische Landesgartenschau's tech stack

What does Bayerische Landesgartenschau use?

Bayerische Landesgartenschau (lgs.de) uses at least 7 tools we can see from public records, including Hetzner for hosting, Microsoft 365 for email and documents, WordPress for its website and Eye-Able for security. Last checked .

Based in
Germany
Tools found
7
Categories
6
Layers
4 of 5
Last checked
Oct 2026

Bayerische Landesgartenschau'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

3 tools, what the product is built with

Go-to-market

1 tool, how they find and keep customers

Website & CMS

Company Ops

2 tools, what the team runs on day to day

Security & Compliance

Bayerische Landesgartenschau tech stack FAQ

What tools does Bayerische Landesgartenschau use?

We've found 7 tools at Bayerische Landesgartenschau (lgs.de). Edge & Hosting: Hetzner. Application: jQuery, Vimeo and Font Awesome. Go-to-market: WordPress. Company Ops: Microsoft 365 and Eye-Able. Last checked October 4, 2026.

What cloud does Bayerische Landesgartenschau run on?

Bayerische Landesgartenschau uses Hetzner for hosting. We found Hetzner through DNS records.

What email provider does Bayerische Landesgartenschau use?

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

What CMS does Bayerische Landesgartenschau use?

Bayerische Landesgartenschau uses WordPress for its website. We found WordPress through website code.

Does Bayerische Landesgartenschau use Microsoft 365?

Yes. We found Microsoft 365 at Bayerische Landesgartenschau through DNS verification records and email records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what Bayerische Landesgartenschau uses?

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