Vivox's tech stack
What does Vivox use?
Vivox (vivox.com) uses at least 10 tools we can see from public records, including Google Workspace for email and documents, Zendesk for customer support, Amplitude for analytics and Sanity for its website. Last checked .
- Industry
- Video Games
- Based in
- San Francisco, United States
- Founded
- 2004
- Company page
- Tools found
- 10
- Categories
- 10
- Layers
- 5 of 5
- Last checked
- Oct 2026
Vivox'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
CDN & Edge
Application
1 tool, what the product is built with
Frontend
Data & Observability
2 tools, what they measure and store
Monitoring
Analytics
Go-to-market
3 tools, how they find and keep customers
Company Ops
3 tools, what the team runs on day to day
Vivox tech stack FAQ
What tools does Vivox use?
We've found 10 tools at Vivox (vivox.com). Edge & Hosting: Amazon CloudFront. Application: Next.js. Data & Observability: Sentry and Amplitude. Go-to-market: Zendesk and Sanity. Company Ops: Google Workspace, SendGrid and OneTrust. Last checked October 2, 2026.
What email provider does Vivox use?
Vivox uses Google Workspace for email and documents. We found Google Workspace through email records.
What does Vivox use for customer support?
Vivox uses Zendesk for customer support. We found Zendesk through custom domain and email records.
What analytics tools does Vivox use?
Vivox uses Amplitude for analytics. We found Amplitude through website code.
What CMS does Vivox use?
Vivox uses Sanity for its website. We found Sanity through website code.
Does Vivox use Google Workspace?
Yes. We found Google Workspace at Vivox through email records. Google Workspace is used by 126,364 companies we track.
How does runsonwhat know what Vivox uses?
We read public traces only: Vivox'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.