Pera Museum's tech stack
What does Pera Museum use?
Pera Museum (peramuseum.org) uses at least 11 tools we can see from public records, including CookieScript for security, Google Analytics for analytics and Cloudflare for content delivery. Last checked .
- Industry
- Museums and Institutions
- Size
- 11–50 employees
- Based in
- Beyoğlu, Turkey
- Founded
- 2005
- Company page
- Tools found
- 11
- Categories
- 6
- Layers
- 5 of 5
- Last checked
- Nov 2026
Pera Museum's stack, layer by layer
Of 11 tools, 10 came from website code and 1 from DNS records. 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
CDN & Edge
Application
5 tools, what the product is built with
Data & Observability
2 tools, what they measure and store
Go-to-market
2 tools, how they find and keep customers
Ads & Pixels
Company Ops
1 tool, what the team runs on day to day
Security & Compliance
Pera Museum tech stack FAQ
What tools does Pera Museum use?
As of November 2026, runsonwhat has found 11 tools at Pera Museum (peramuseum.org) in public records. Edge & Hosting: Cloudflare. Application: jQuery, Google Fonts and Font Awesome. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Google Ads and Meta Pixel. Company Ops: CookieScript. Last checked November 2, 2026.
What analytics tools does Pera Museum use?
Pera Museum uses Google Analytics for analytics, alongside Google Tag Manager, according to runsonwhat (November 2026). runsonwhat found Google Analytics through Google Analytics code on peramuseum.org. Google Analytics is used by 905,620 companies runsonwhat tracks.
Does Pera Museum use jQuery?
Yes. runsonwhat found jQuery at Pera Museum through jQuery code on peramuseum.org. jQuery is a Frontend tool used by 929,437 companies runsonwhat tracks.
How does runsonwhat know what Pera Museum uses?
runsonwhat reads public records only. Of the 11 tools at Pera Museum, 10 were found through code on peramuseum.org, 1 through DNS records. A tool is listed only when a direct record backs it up; DNS is rechecked weekly and peramuseum.org about 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.