runsonwhat

Eyeo's tech stack

What does Eyeo use?

Eyeo (eyeo.com) uses at least 29 tools we can see from public records, including WP Engine for hosting, Google Workspace for email and documents, HubSpot for sales and Scroll Viewport for customer support. Last checked .

Industry
Internet
Size
201–1,000 employees
Based in
Berlin Kreuzberg, Germany
Founded
2011
LinkedIn
Company page
Tools found
29
Categories
16
Oldest proven tool
Oct 2023
Last checked
Oct 2026

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

3 tools, where the bytes are served from

Application

4 tools, what the product is built with

Go-to-market

6 tools, how they find and keep customers

What changed at Eyeo

Using since

Dates come from the first certificate of the subdomain that points at the tool.

  1. Akamai

Eyeo tech stack FAQ

What tools does Eyeo use?

We've found 29 tools at Eyeo (eyeo.com). Edge & Hosting: Cloudflare, Akamai and WP Engine. Application: jQuery, Vimeo and Anthropic. Go-to-market: Meta Pixel, WordPress and HubSpot. Company Ops: Google Workspace, Apple Business and Atlassian. Last checked October 2, 2026.

What cloud does Eyeo run on?

Eyeo uses WP Engine for hosting. We found WP Engine through website code.

What CRM does Eyeo use?

Eyeo uses HubSpot for sales and CRM. We found HubSpot through email records.

What email provider does Eyeo use?

Eyeo uses Google Workspace and Apple Business for email and documents. We found Google Workspace through email records.

What does Eyeo use for customer support?

Eyeo uses Scroll Viewport for customer support. We found Scroll Viewport through custom domain.

What CMS does Eyeo use?

Eyeo uses WordPress for its website. We found WordPress through website code.

Does Eyeo use Cloudflare?

Yes. We found Cloudflare at Eyeo through website code. Cloudflare is used by 147,753 companies we track.

How does runsonwhat know what Eyeo uses?

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