Amaya Inc.'s tech stack
What does Amaya Inc. use?
Amaya Inc. (amaya.com) uses at least 14 tools we can see from public records, including Amazon Web Services for hosting, Dealfront for sales, Google Analytics for analytics and Cloudflare for content delivery. Last checked .
- Industry
- Online Gambling
- Based in
- Canada
- Founded
- 2004
- Company page
- Tools found
- 14
- Categories
- 9
- Layers
- 5 of 5
- Last checked
- Oct 2026
Amaya 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
3 tools, where the bytes are served from
Application
2 tools, what the product is built with
Frontend
Media & UI
Data & Observability
2 tools, what they measure and store
Go-to-market
4 tools, how they find and keep customers
Sales & CRM
Company Ops
3 tools, what the team runs on day to day
Security & Compliance
Amaya Inc. tech stack FAQ
What tools does Amaya Inc. use?
We've found 14 tools at Amaya Inc. (amaya.com). Edge & Hosting: Cloudflare, Amazon Web Services and Amazon Route 53. Application: Vimeo and Nuxt. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Google Ads, LinkedIn Insight Tag and Microsoft Xandr. Company Ops: Cookiebot, Cisco Secure Email and Acquia Optimize. Last checked October 3, 2026.
What cloud does Amaya Inc. run on?
Amaya Inc. uses Amazon Web Services for hosting. We found Amazon Web Services through custom domain.
What CRM does Amaya Inc. use?
Amaya Inc. uses Dealfront for sales and CRM. We found Dealfront through website code.
What analytics tools does Amaya Inc. use?
Amaya Inc. uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
Does Amaya Inc. use Cloudflare?
Yes. We found Cloudflare at Amaya Inc. through website code. Cloudflare is used by 308,484 companies we track.
How does runsonwhat know what Amaya Inc. uses?
We read public traces only: Amaya 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.