Fumiplagas's tech stack
What does Fumiplagas use?
Fumiplagas (fumiplagas.net) uses at least 9 tools we can see from public records, including Vercel for hosting, Google Workspace for email and documents, WhatsApp Business for customer support and WordPress for its website. Last checked .
- Industry
- Utilities
- Size
- 1–10 employees
- Based in
- Mexico
- Company page
- Tools found
- 9
- Categories
- 9
- Layers
- 4 of 5
- Last checked
- Oct 2026
Fumiplagas'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
1 tool, what the product is built with
Frontend
Go-to-market
3 tools, how they find and keep customers
Website & CMS
Marketing
Support & Docs
Company Ops
3 tools, what the team runs on day to day
Fumiplagas tech stack FAQ
What tools does Fumiplagas use?
We've found 9 tools at Fumiplagas (fumiplagas.net). Edge & Hosting: Cloudflare and Vercel. Application: Next.js. Go-to-market: WordPress and WhatsApp Business. Company Ops: Google Workspace, reCAPTCHA and Resend. Last checked October 4, 2026.
What cloud does Fumiplagas run on?
Fumiplagas uses Vercel for hosting. We found Vercel through custom domain, DNS verification records, DNS records and website code.
What email provider does Fumiplagas use?
Fumiplagas uses Google Workspace for email and documents. We found Google Workspace through email records.
What does Fumiplagas use for customer support?
Fumiplagas uses WhatsApp Business for customer support. We found WhatsApp Business through website code.
What CMS does Fumiplagas use?
Fumiplagas uses WordPress for its website. We found WordPress through website code.
Does Fumiplagas use Cloudflare?
Yes. We found Cloudflare at Fumiplagas through DNS records. Cloudflare is used by 147,753 companies we track.
How does runsonwhat know what Fumiplagas uses?
We read public traces only: Fumiplagas'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.