runsonwhat

Wehack Utd's tech stack

What does Wehack Utd use?

Wehack Utd (wehackutd.com) uses at least 8 tools we can see from public records, including Vercel for hosting, Google Analytics for analytics and Clerk for sign-in. Last checked .

Industry
Software
Size
11–50 employees
Based in
Richardson, United States
Founded
2019
LinkedIn
Company page
Re-check liveVisit wehackutd.com
Tools found
8
Categories
6
Layers
3 of 5
Last checked
Oct 2026

Wehack Utd'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

2 tools, where the bytes are served from

Hosting & Cloud

DNS

Application

4 tools, what the product is built with

Frontend

Auth & Identity

Media & UI

Data & Observability

2 tools, what they measure and store

Analytics

Companies like Wehack Utd also use

Tools common among companies with a similar stack that we haven't found at Wehack Utd.

Companies with a stack like Wehack Utd's

Ranked by shared tools, with rare tools counting more.

More Software companies

Other Software companies we've checked.

Wehack Utd tech stack FAQ

What tools does Wehack Utd use?

We've found 8 tools at Wehack Utd (wehackutd.com). Edge & Hosting: GoDaddy and Vercel. Application: Google Fonts, Adobe Fonts and Next.js. Data & Observability: Google Analytics and Vercel Analytics. Last checked October 6, 2026.

What cloud does Wehack Utd run on?

Wehack Utd uses Vercel for hosting. We found Vercel through custom domain, DNS verification records, DNS records and website code.

What analytics tools does Wehack Utd use?

Wehack Utd uses Google Analytics and Vercel Analytics for analytics. We found Google Analytics through website code.

Does Wehack Utd use Google Analytics?

Yes. We found Google Analytics at Wehack Utd through website code. Google Analytics is used by 554,765 companies we track.

How does runsonwhat know what Wehack Utd uses?

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