TriEye's tech stack
What does TriEye use?
TriEye (trieye.tech) uses at least 13 tools we can see from public records, including Amazon Web Services for hosting, Google Workspace for email and documents, Google Analytics for analytics and WordPress for its website. Last checked .
- Industry
- Semiconductors
- Size
- 51–200 employees
- Based in
- Tel Aviv-Yafo, Israel
- Founded
- 2017
- Company page
- Tools found
- 13
- Categories
- 9
- Layers
- 5 of 5
- Last checked
- Oct 2026
TriEye'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
5 tools, what the product is built with
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
3 tools, how they find and keep customers
Website & CMS
Marketing
Company Ops
1 tool, what the team runs on day to day
Workspace
TriEye tech stack FAQ
What tools does TriEye use?
We've found 13 tools at TriEye (trieye.tech). Edge & Hosting: Cloudflare, Amazon Web Services and Amazon Route 53. Application: jQuery, Google Fonts and Font Awesome. Data & Observability: Google Analytics. Go-to-market: WordPress and Yoast SEO. Company Ops: Google Workspace. Last checked October 8, 2026.
What cloud does TriEye run on?
TriEye uses Amazon Web Services for hosting. We found Amazon Web Services through website code.
What email provider does TriEye use?
TriEye uses Google Workspace for email and documents. We found Google Workspace through email records and website code.
What analytics tools does TriEye use?
TriEye uses Google Analytics for analytics. We found Google Analytics through website code.
What CMS does TriEye use?
TriEye uses WordPress and Yoast SEO for its website. We found WordPress through website code.
Does TriEye use jQuery?
Yes. We found jQuery at TriEye through website code. jQuery is used by 762,082 companies we track.
How does runsonwhat know what TriEye uses?
We read public traces only: TriEye'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.