Voronoi's tech stack
What does Voronoi use?
Voronoi (voronoi.io) uses at least 7 tools we can see from public records, including Google Cloud for hosting, Google Workspace for email and documents, Google Analytics for analytics and WordPress for its website. Last checked .
- Based in
- South Korea
- Founded
- 2015
- Company page
- Tools found
- 7
- Categories
- 6
- Layers
- 5 of 5
- Last checked
- Oct 2026
Voronoi'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
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
Website & CMS
Company Ops
2 tools, what the team runs on day to day
Workspace
Security & Compliance
Voronoi tech stack FAQ
What tools does Voronoi use?
We've found 7 tools at Voronoi (voronoi.io). Edge & Hosting: Google Cloud and Amazon Web Services. Application: jQuery. Data & Observability: Google Analytics. Go-to-market: WordPress. Company Ops: Google Workspace and Cookiebot. Last checked October 4, 2026.
What cloud does Voronoi run on?
Voronoi uses Google Cloud and Amazon Web Services for hosting. We found Google Cloud through custom domain.
What email provider does Voronoi use?
Voronoi uses Google Workspace for email and documents. We found Google Workspace through email records.
What analytics tools does Voronoi use?
Voronoi uses Google Analytics for analytics. We found Google Analytics through website code.
What CMS does Voronoi use?
Voronoi uses WordPress for its website. We found WordPress through website code.
Does Voronoi use Google Workspace?
Yes. We found Google Workspace at Voronoi through email records. Google Workspace is used by 126,364 companies we track.
How does runsonwhat know what Voronoi uses?
We read public traces only: Voronoi'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.