Pocket Worlds's tech stack
What does Pocket Worlds use?
Pocket Worlds (pocketworlds.com) uses at least 8 tools we can see from public records, including Vercel for hosting, Google Workspace for email and documents, Intercom for customer support and Resend for email delivery. Last checked .
“Our platform enables creators to build experiences, games, and worlds…”
- Industry
- Social
- Size
- 51–200 employees
- Based in
- Austin, United States
- Founded
- 2015
- Company page
- Tools found
- 8
- Categories
- 8
- Layers
- 4 of 5
- Last checked
- Oct 2026
Pocket Worlds'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
Media & UI
Go-to-market
2 tools, how they find and keep customers
Marketing
Support & Docs
Company Ops
2 tools, what the team runs on day to day
Email Delivery
Workspace
Pocket Worlds tech stack FAQ
What tools does Pocket Worlds use?
We've found 8 tools at Pocket Worlds (pocketworlds.com). Edge & Hosting: Vercel and Namecheap. Application: Google Fonts and Anthropic. Go-to-market: Intercom. Company Ops: Google Workspace and Resend. Last checked October 2, 2026.
What cloud does Pocket Worlds run on?
Pocket Worlds uses Vercel for hosting. We found Vercel through custom domain, DNS records and website code.
What email provider does Pocket Worlds use?
Pocket Worlds uses Google Workspace for email and documents. We found Google Workspace through email records.
What does Pocket Worlds use for customer support?
Pocket Worlds uses Intercom for customer support. We found Intercom through email records.
Does Pocket Worlds use Google Workspace?
Yes. We found Google Workspace at Pocket Worlds through email records. Google Workspace is used by 126,364 companies we track.
How does runsonwhat know what Pocket Worlds uses?
We read public traces only: Pocket Worlds'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.