runsonwhat

playdisplay's tech stack

What does playdisplay use?

playdisplay (playdisplay.com) uses at least 8 tools we can see from public records, including Google Workspace for email and documents, Google Analytics for analytics and WordPress for its website. Last checked .

“playdisplay проектирует пространства и впечатления, которые люди запоминают: современные музеи, интерактивные экспозиции, visitor centre, шоурумы и иммерсивные выставки. Превращаем идею, историю или бренд в опыт, который хочется пережить.”

Industry
Software
Size
11–50 employees
Based in
Nizhnyaya Purlovka, Russia
Founded
2011
LinkedIn
Company page
Tools found
8
Categories
6
Layers
4 of 5
Last checked
Oct 2026

playdisplay'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.

Application

4 tools, what the product is built with

Data & Observability

1 tool, what they measure and store

Go-to-market

2 tools, how they find and keep customers

Company Ops

1 tool, what the team runs on day to day

playdisplay tech stack FAQ

What tools does playdisplay use?

We've found 8 tools at playdisplay (playdisplay.com). Application: Google Fonts, YouTube and Vimeo. Data & Observability: Google Analytics. Go-to-market: WordPress. Company Ops: Google Workspace. Last checked October 6, 2026.

What email provider does playdisplay use?

playdisplay uses Google Workspace for email and documents. We found Google Workspace through email records.

What analytics tools does playdisplay use?

playdisplay uses Google Analytics for analytics. We found Google Analytics through website code.

What CMS does playdisplay use?

playdisplay uses WordPress for its website. We found WordPress through website code.

Does playdisplay use Google Analytics?

Yes. We found Google Analytics at playdisplay through website code. Google Analytics is used by 726,530 companies we track.

How does runsonwhat know what playdisplay uses?

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