Fira Roboworld Cup's tech stack
What does Fira Roboworld Cup use?
Fira Roboworld Cup (firaworldcup.org) uses at least 12 tools we can see from public records, including Vercel for hosting, Google Workspace for email and documents, WordPress for its website and Cloudflare for content delivery. Last checked .
- Industry
- Research
- Size
- 10,000+ employees
- Based in
- Taipei, Taiwan
- Founded
- 1996
- Company page
- Tools found
- 12
- Categories
- 7
- Layers
- 4 of 5
- Last checked
- Oct 2026
Fira Roboworld Cup'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
CDN & Edge
Application
7 tools, what the product is built with
Go-to-market
2 tools, how they find and keep customers
Website & CMS
Marketing
Company Ops
1 tool, what the team runs on day to day
Workspace
Fira Roboworld Cup tech stack FAQ
What tools does Fira Roboworld Cup use?
We've found 12 tools at Fira Roboworld Cup (firaworldcup.org). Edge & Hosting: Cloudflare and Vercel. Application: jQuery, Google Fonts and Vimeo. Go-to-market: WordPress. Company Ops: Google Workspace. Last checked October 3, 2026.
What cloud does Fira Roboworld Cup run on?
Fira Roboworld Cup uses Vercel for hosting. We found Vercel through DNS verification records.
What email provider does Fira Roboworld Cup use?
Fira Roboworld Cup uses Google Workspace for email and documents. We found Google Workspace through DNS verification records and email records.
What CMS does Fira Roboworld Cup use?
Fira Roboworld Cup uses WordPress for its website. We found WordPress through website code.
Does Fira Roboworld Cup use Cloudflare?
Yes. We found Cloudflare at Fira Roboworld Cup through DNS records and website code. Cloudflare is used by 147,753 companies we track.
How does runsonwhat know what Fira Roboworld Cup uses?
We read public traces only: Fira Roboworld Cup'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.