Zenbu's tech stack
What does Zenbu use?
Zenbu (zenbu.dev) uses at least 8 tools we can see from public records, including Vercel for hosting, Google Workspace for email and documents, Discord for customer support and Vercel Analytics for analytics. Last checked .
“The browser for agentic development”
- Industry
- Engineering, Product and Design
- Size
- 1–10 employees
- Based in
- San Francisco, United States
- Tools found
- 8
- Categories
- 6
- Layers
- 5 of 5
- Last checked
- Oct 2026
Zenbu'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
1 tool, where the bytes are served from
Hosting & Cloud
Application
1 tool, 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
Support & Docs
Company Ops
4 tools, what the team runs on day to day
Workspace
Security & Compliance
Zenbu tech stack FAQ
What tools does Zenbu use?
We've found 8 tools at Zenbu (zenbu.dev). Edge & Hosting: Vercel. Application: Next.js. Data & Observability: Vercel Analytics. Go-to-market: Discord. Company Ops: Google Workspace, Let's Encrypt and Sectigo. Last checked October 2, 2026.
What cloud does Zenbu run on?
Zenbu uses Vercel for hosting. We found Vercel through DNS records.
What email provider does Zenbu use?
Zenbu uses Google Workspace for email and documents. We found Google Workspace through email records.
What does Zenbu use for customer support?
Zenbu uses Discord for customer support. We found Discord through website code.
What analytics tools does Zenbu use?
Zenbu uses Vercel Analytics for analytics. We found Vercel Analytics through website code.
Does Zenbu use Google Workspace?
Yes. We found Google Workspace at Zenbu through email records. Google Workspace is used by 347,642 companies we track.
How does runsonwhat know what Zenbu uses?
We read public traces only: Zenbu'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.