Historie der CG Gruppe's tech stack
What does Historie der CG Gruppe use?
Historie der CG Gruppe (cg-gruppe.de) uses at least 10 tools we can see from public records, including IONOS for hosting, Google Analytics for analytics and WordPress for its website. Last checked .
- Industry
- Real Estate
- Size
- 1–10 employees
- Based in
- Berlin, Germany
- Founded
- 1995
- Company page
- Tools found
- 10
- Categories
- 6
- Layers
- 4 of 5
- Last checked
- Oct 2026
Historie der CG Gruppe'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
5 tools, what the product is built with
Frontend
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
3 tools, how they find and keep customers
Website & CMS
Marketing
Historie der CG Gruppe tech stack FAQ
What tools does Historie der CG Gruppe use?
We've found 10 tools at Historie der CG Gruppe (cg-gruppe.de). Edge & Hosting: IONOS. Application: jQuery, Vimeo and YouTube. Data & Observability: Google Analytics. Go-to-market: WordPress and Rank Math. Last checked October 3, 2026.
What cloud does Historie der CG Gruppe run on?
Historie der CG Gruppe uses IONOS for hosting. We found IONOS through email records.
What analytics tools does Historie der CG Gruppe use?
Historie der CG Gruppe uses Google Analytics for analytics. We found Google Analytics through website code.
What CMS does Historie der CG Gruppe use?
Historie der CG Gruppe uses WordPress and Rank Math for its website. We found WordPress through website code.
Does Historie der CG Gruppe use Google Analytics?
Yes. We found Google Analytics at Historie der CG Gruppe through website code. Google Analytics is used by 89,943 companies we track.
How does runsonwhat know what Historie der CG Gruppe uses?
We read public traces only: Historie der CG Gruppe'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.