runsonwhat

Helma Eigenheimbau's tech stack

What does Helma Eigenheimbau use?

Helma Eigenheimbau (helma.de) uses at least 9 tools we can see from public records, including Microsoft 365 for email and documents, WordPress for its website and reCAPTCHA for security. Last checked .

Industry
Construction
Size
201–1,000 employees
Based in
Lehrte, Germany
Founded
1980
LinkedIn
Company page
Re-check liveVisit helma.de
Tools found
9
Categories
5
Layers
3 of 5
Last checked
Oct 2026

Helma Eigenheimbau'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

5 tools, what the product is built with

Frontend

Media & UI

Go-to-market

1 tool, how they find and keep customers

Website & CMS

Company Ops

3 tools, what the team runs on day to day

Workspace

Security & Compliance

Companies like Helma Eigenheimbau also use

Tools common among companies with a similar stack that we haven't found at Helma Eigenheimbau.

Companies with a stack like Helma Eigenheimbau's

Ranked by shared tools, with rare tools counting more.

Helma Eigenheimbau tech stack FAQ

What tools does Helma Eigenheimbau use?

We've found 9 tools at Helma Eigenheimbau (helma.de). Application: jQuery, Google Fonts and Vimeo. Go-to-market: WordPress. Company Ops: Microsoft 365, reCAPTCHA and Hornetsecurity. Last checked October 3, 2026.

What email provider does Helma Eigenheimbau use?

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

What CMS does Helma Eigenheimbau use?

Helma Eigenheimbau uses WordPress for its website. We found WordPress through website code.

Does Helma Eigenheimbau use Microsoft 365?

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

How does runsonwhat know what Helma Eigenheimbau uses?

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