DevilishGames's tech stack
What does DevilishGames use?
DevilishGames (devilishgames.com) uses at least 12 tools we can see from public records, including OVHcloud for hosting, Google Analytics for analytics, WordPress for its website and CookieYes for security. Last checked .
- Based in
- Spain
- Founded
- 1998
- Company page
- Tools found
- 12
- Categories
- 7
- Layers
- 5 of 5
- Last checked
- Oct 2026
DevilishGames'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
1 tool, where the bytes are served from
Hosting & Cloud
Application
6 tools, what the product is built with
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
3 tools, how they find and keep customers
Website & CMS
Ads & Pixels
Company Ops
1 tool, what the team runs on day to day
Security & Compliance
DevilishGames tech stack FAQ
What tools does DevilishGames use?
We've found 12 tools at DevilishGames (devilishgames.com). Edge & Hosting: OVHcloud. Application: jQuery, Google Fonts and Font Awesome. Data & Observability: Google Analytics. Go-to-market: WordPress, Yoast SEO and Google Ad Manager. Company Ops: CookieYes. Last checked October 2, 2026.
What cloud does DevilishGames run on?
DevilishGames uses OVHcloud for hosting. We found OVHcloud through DNS records and website code.
What analytics tools does DevilishGames use?
DevilishGames uses Google Analytics for analytics. We found Google Analytics through website code.
What CMS does DevilishGames use?
DevilishGames uses WordPress and Yoast SEO for its website. We found WordPress through website code.
Does DevilishGames use jQuery?
Yes. We found jQuery at DevilishGames through website code. jQuery is used by 378,812 companies we track.
How does runsonwhat know what DevilishGames uses?
We read public traces only: DevilishGames'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.