The Hellenium Project's tech stack
What does The Hellenium Project use?
The Hellenium Project (hellenium.com) uses at least 8 tools we can see from public records, including IONOS for hosting, tawk.to for customer support, Google Analytics for analytics and Cookiebot for security. Last checked .
- Industry
- Banking
- Size
- 51–200 employees
- Based in
- Greece
- Company page
- Tools found
- 8
- Categories
- 7
- Layers
- 5 of 5
- Last checked
- Oct 2026
The Hellenium Project'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
Frontend
Media & UI
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
2 tools, how they find and keep customers
Marketing
Support & Docs
Company Ops
1 tool, what the team runs on day to day
Security & Compliance
The Hellenium Project tech stack FAQ
What tools does The Hellenium Project use?
We've found 8 tools at The Hellenium Project (hellenium.com). Edge & Hosting: IONOS. Application: jQuery, Google Fonts and Font Awesome. Data & Observability: Google Analytics. Go-to-market: tawk.to. Company Ops: Cookiebot. Last checked October 6, 2026.
What cloud does The Hellenium Project run on?
The Hellenium Project uses IONOS for hosting. We found IONOS through email records.
What does The Hellenium Project use for customer support?
The Hellenium Project uses tawk.to for customer support. We found tawk.to through website code.
What analytics tools does The Hellenium Project use?
The Hellenium Project uses Google Analytics for analytics. We found Google Analytics through website code.
Does The Hellenium Project use jQuery?
Yes. We found jQuery at The Hellenium Project through website code. jQuery is used by 574,683 companies we track.
How does runsonwhat know what The Hellenium Project uses?
We read public traces only: The Hellenium Project'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.