runsonwhat

Playa Games's tech stack

What does Playa Games use?

Playa Games (playa-games.com) uses at least 15 tools we can see from public records, including Hetzner for hosting, Microsoft 365 for email and documents, Mixpanel for analytics and Fastly for content delivery. Last checked .

Based in
Germany
Founded
2009
LinkedIn
Company page
Tools found
15
Categories
12
Layers
5 of 5
Last checked
Oct 2026

Playa Games'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

Data & Observability

1 tool, what they measure and store

Analytics

Go-to-market

3 tools, how they find and keep customers

Company Ops

8 tools, what the team runs on day to day

Email Delivery

Collaboration

Dev Tools

Finance & Legal

Security & Compliance

Playa Games tech stack FAQ

What tools does Playa Games use?

We've found 15 tools at Playa Games (playa-games.com). Edge & Hosting: Fastly and Hetzner. Application: jQuery. Data & Observability: Mixpanel. Go-to-market: Meta Pixel and Google Ad Manager. Company Ops: Microsoft 365, Google Workspace and Atlassian. Last checked October 3, 2026.

What cloud does Playa Games run on?

Playa Games uses Hetzner for hosting. We found Hetzner through DNS records.

What email provider does Playa Games use?

Playa Games uses Microsoft 365 and Google Workspace for email and documents. We found Microsoft 365 through DNS verification records.

What analytics tools does Playa Games use?

Playa Games uses Mixpanel for analytics. We found Mixpanel through DNS verification records.

Does Playa Games use Microsoft 365?

Yes. We found Microsoft 365 at Playa Games through DNS verification records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what Playa Games uses?

We read public traces only: Playa Games'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.