runsonwhat

WageProof's tech stack

What does WageProof use?

WageProof (wageproof.com) uses at least 14 tools we can see from public records, including Vercel for hosting, Google Workspace for email and documents, Google Analytics for analytics and Sentry for monitoring. Last checked .

“Defensible reasonable compensation reports for S-Corp owners, built on the IRS’s three approaches and Bureau of Labor Statistics wage data.”

Industry
Software
Size
1–10 employees
Based in
United States
Founded
2026
LinkedIn
Company page
Tools found
14
Categories
11
Layers
5 of 5
Last checked
Oct 2026

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

Application

3 tools, what the product is built with

Data & Observability

2 tools, what they measure and store

Go-to-market

2 tools, how they find and keep customers

Company Ops

5 tools, what the team runs on day to day

WageProof tech stack FAQ

What tools does WageProof use?

We've found 14 tools at WageProof (wageproof.com). Edge & Hosting: Cloudflare and Vercel. Application: Next.js and Tailwind CSS. Data & Observability: Google Analytics and Sentry. Go-to-market: Google Ads. Company Ops: Google Workspace, Let's Encrypt and Sectigo. Last checked October 4, 2026.

What cloud does WageProof run on?

WageProof uses Vercel for hosting. We found Vercel through DNS records.

What email provider does WageProof use?

WageProof uses Google Workspace for email and documents. We found Google Workspace through email records.

What analytics tools does WageProof use?

WageProof uses Google Analytics for analytics. We found Google Analytics through website code.

Does WageProof use Cloudflare?

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

How does runsonwhat know what WageProof uses?

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