WFS, Inc.'s tech stack
What does WFS, Inc. use?
WFS, Inc. (wfs.games) uses at least 9 tools we can see from public records, including Google Workspace for email and documents, Zendesk for customer support, Google Tag Manager for analytics and Amazon CloudFront for content delivery. Last checked .
- Industry
- Video Games
- Size
- 201–1,000 employees
- Based in
- Roppongi, Japan
- Founded
- 2014
- Company page
- Tools found
- 9
- Categories
- 9
- Layers
- 5 of 5
- Last checked
- Oct 2026
WFS, Inc.'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
CDN & Edge
Application
1 tool, what the product is built with
Frontend
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
3 tools, how they find and keep customers
Company Ops
2 tools, what the team runs on day to day
Email Delivery
Workspace
WFS, Inc. tech stack FAQ
What tools does WFS, Inc. use?
We've found 9 tools at WFS, Inc. (wfs.games). Edge & Hosting: Amazon Route 53 and Amazon CloudFront. Application: jQuery. Data & Observability: Google Tag Manager. Go-to-market: Meta Pixel and Zendesk. Company Ops: Google Workspace and Amazon SES. Last checked October 3, 2026.
What email provider does WFS, Inc. use?
WFS, Inc. uses Google Workspace for email and documents. We found Google Workspace through email records.
What does WFS, Inc. use for customer support?
WFS, Inc. uses Zendesk for customer support. We found Zendesk through email records.
What analytics tools does WFS, Inc. use?
WFS, Inc. uses Google Tag Manager for analytics. We found Google Tag Manager through website code.
Does WFS, Inc. use Google Workspace?
Yes. We found Google Workspace at WFS, Inc. through email records. Google Workspace is used by 126,364 companies we track.
How does runsonwhat know what WFS, Inc. uses?
We read public traces only: WFS, Inc.'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.