Eye4Me's tech stack
What does Eye4Me use?
Eye4Me (eye4me.com) uses at least 14 tools we can see from public records, including Vercel for hosting, Microsoft 365 for email and documents, Google Analytics for analytics and Clerk for sign-in. Last checked .
- Company page
- Tools found
- 14
- Categories
- 12
- Layers
- 5 of 5
- Last checked
- Oct 2026
Eye4Me'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
Frontend
Auth & Identity
Backend & Database
Media & UI
Data & Observability
4 tools, what they measure and store
Flags & Experiments
Go-to-market
1 tool, how they find and keep customers
Marketing
Company Ops
2 tools, what the team runs on day to day
Workspace
Security & Compliance
Eye4Me tech stack FAQ
What tools does Eye4Me use?
We've found 14 tools at Eye4Me (eye4me.com). Edge & Hosting: Cloudflare, Amazon Route 53 and Vercel. Application: YouTube, Next.js and Supabase. Data & Observability: Google Analytics, Google Tag Manager and Vercel Analytics. Company Ops: Microsoft 365 and Cloudflare Turnstile. Last checked October 2, 2026.
What cloud does Eye4Me run on?
Eye4Me uses Vercel for hosting. We found Vercel through custom domain, DNS records and website code.
What email provider does Eye4Me use?
Eye4Me uses Microsoft 365 for email and documents. We found Microsoft 365 through email records.
What analytics tools does Eye4Me use?
Eye4Me uses Google Analytics, Google Tag Manager and Vercel Analytics for analytics. We found Google Analytics through website code.
Does Eye4Me use Microsoft 365?
Yes. We found Microsoft 365 at Eye4Me through email records. Microsoft 365 is used by 326,338 companies we track.
How does runsonwhat know what Eye4Me uses?
We read public traces only: Eye4Me'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.