Gambling.com's tech stack
What does Gambling.com use?
Gambling.com (gambling.com) uses at least 12 tools we can see from public records, including Vercel for hosting, Microsoft 365 for email and documents, Cloudflare for content delivery and SendGrid for email delivery. Last checked .
“Gambling.com is an independent comparison and review platform helping players worldwide find licensed online casinos and betting sites, backed by expert reviews, bonus guides, and responsible gambling advice.”
- Based in
- Dublin 2, Ireland
- Founded
- 2006
- Company page
- Tools found
- 12
- Categories
- 8
- Layers
- 4 of 5
- Last checked
- Oct 2026
Gambling.com'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
Hosting & Cloud
CDN & Edge
Application
3 tools, what the product is built with
Go-to-market
2 tools, how they find and keep customers
Company Ops
4 tools, what the team runs on day to day
Email Delivery
Workspace
Security & Compliance
Gambling.com tech stack FAQ
What tools does Gambling.com use?
We've found 12 tools at Gambling.com (gambling.com). Edge & Hosting: Cloudflare, Vercel and Amazon Web Services. Application: Tailwind CSS and Vue.js. Company Ops: Microsoft 365, SendGrid and EasyDMARC. Last checked October 4, 2026.
What cloud does Gambling.com run on?
Gambling.com uses Vercel and Amazon Web Services for hosting. We found Vercel through DNS verification records.
What email provider does Gambling.com use?
Gambling.com uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records and email records.
Does Gambling.com use Microsoft 365?
Yes. We found Microsoft 365 at Gambling.com through DNS verification records and email records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what Gambling.com uses?
We read public traces only: Gambling.com'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.