runsonwhat

Heideförster e.K.'s tech stack

What does Heideförster e.K. use?

Heideförster e.K. (heidefoerster.de) uses at least 8 tools we can see from public records, including IONOS for hosting, Wix for its website, POWR for marketing and Sentry for monitoring. Last checked .

Based in
Oldendorf (Luhe), Germany
Re-check liveVisit heidefoerster.de
Tools found
8
Categories
6
Layers
4 of 5
Last checked
Oct 2026

Heideförster e.K.'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

CDN & Edge

Application

1 tool, what the product is built with

AI

Data & Observability

1 tool, what they measure and store

Monitoring

Go-to-market

4 tools, how they find and keep customers

Website & CMS

Marketing

Companies like Heideförster e.K. also use

Tools common among companies with a similar stack that we haven't found at Heideförster e.K..

Companies with a stack like Heideförster e.K.'s

Ranked by shared tools, with rare tools counting more.

Heideförster e.K. tech stack FAQ

What tools does Heideförster e.K. use?

We've found 8 tools at Heideförster e.K. (heidefoerster.de). Edge & Hosting: Fastly and IONOS. Data & Observability: Sentry. Go-to-market: Wix and POWR. Last checked October 4, 2026.

What cloud does Heideförster e.K. run on?

Heideförster e.K. uses IONOS for hosting. We found IONOS through email records.

What CMS does Heideförster e.K. use?

Heideförster e.K. uses Wix for its website. We found Wix through custom domain and website code.

What marketing software does Heideförster e.K. use?

Heideförster e.K. uses POWR for marketing. We found POWR through website code.

Does Heideförster e.K. use Wix?

Yes. We found Wix at Heideförster e.K. through custom domain and website code. Wix is used by 12,418 companies we track.

How does runsonwhat know what Heideförster e.K. uses?

We read public traces only: Heideförster e.K.'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.