Traverse's tech stack
What does Traverse use?
Traverse (traverse.so) uses at least 7 tools we can see from public records, including Vercel for hosting, Google Workspace for email and documents and Vercel Analytics for analytics. Last checked .
“Traverse.so builds reinforcement learning environments and training data for frontier AI labs working on taste, judgment, and long-horizon agent work.”
- Industry
- B2B
- Size
- 1–10 employees
- Based in
- San Francisco, United States
- Founded
- 2025
- Company page
- Tools found
- 7
- Categories
- 7
- Layers
- 5 of 5
- Last checked
- Oct 2026
Traverse'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
2 tools, what the product is built with
Frontend
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
1 tool, how they find and keep customers
Marketing
Company Ops
1 tool, what the team runs on day to day
Workspace
Traverse tech stack FAQ
What tools does Traverse use?
We've found 7 tools at Traverse (traverse.so). Edge & Hosting: Vercel and Namecheap. Application: Next.js. Data & Observability: Vercel Analytics. Company Ops: Google Workspace. Last checked October 2, 2026.
What cloud does Traverse run on?
Traverse uses Vercel for hosting. We found Vercel through custom domain, DNS records and website code.
What email provider does Traverse use?
Traverse uses Google Workspace for email and documents. We found Google Workspace through email records.
What analytics tools does Traverse use?
Traverse uses Vercel Analytics for analytics. We found Vercel Analytics through website code.
Does Traverse use Google Workspace?
Yes. We found Google Workspace at Traverse through email records. Google Workspace is used by 126,364 companies we track.
How does runsonwhat know what Traverse uses?
We read public traces only: Traverse'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.