runsonwhat

Gima's tech stack

What does Gima use?

Gima (gima-ziegel.de) uses at least 12 tools we can see from public records, including IONOS for hosting, Microsoft 365 for email and documents, Google Analytics for analytics and WordPress for its website. Last checked .

Industry
Building Materials
Size
201–1,000 employees
Based in
Marklkofen, Germany
Founded
1903
LinkedIn
Company page
Tools found
12
Categories
8
Layers
5 of 5
Last checked
Oct 2026

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

2 tools, where the bytes are served from

Hosting & Cloud

Application

1 tool, what the product is built with

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

Gima tech stack FAQ

What tools does Gima use?

We've found 12 tools at Gima (gima-ziegel.de). Edge & Hosting: Cloudflare and IONOS. Application: jQuery. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Google Ads, WordPress and Yoast SEO. Company Ops: Microsoft 365, reCAPTCHA and Cloudflare Turnstile. Last checked October 4, 2026.

What cloud does Gima run on?

Gima uses IONOS for hosting. We found IONOS through email records.

What email provider does Gima use?

Gima uses Microsoft 365 for email and documents. We found Microsoft 365 through email records.

What analytics tools does Gima use?

Gima uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.

What CMS does Gima use?

Gima uses WordPress and Yoast SEO for its website. We found WordPress through website code.

Does Gima use Microsoft 365?

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

How does runsonwhat know what Gima uses?

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