runsonwhat

Stockholm Resilience Centre's tech stack

What does Stockholm Resilience Centre use?

Stockholm Resilience Centre (stockholmresilience.org) uses at least 8 tools we can see from public records, including Google Analytics for analytics. Last checked .

Industry
Research
Size
51–200 employees
Based in
Stockholm, Sweden
Founded
2007
LinkedIn
Company page
Re-check liveVisit stockholmresilience.org
Tools found
8
Categories
4
Layers
3 of 5
Last checked
Oct 2026

Stockholm Resilience Centre'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

Frontend

Media & UI

Data & Observability

3 tools, what they measure and store

Analytics

Go-to-market

1 tool, how they find and keep customers

Marketing

Companies like Stockholm Resilience Centre also use

Tools common among companies with a similar stack that we haven't found at Stockholm Resilience Centre.

Companies with a stack like Stockholm Resilience Centre's

Ranked by shared tools, with rare tools counting more.

More Research companies

Other Research companies we've checked.

Stockholm Resilience Centre tech stack FAQ

What tools does Stockholm Resilience Centre use?

We've found 8 tools at Stockholm Resilience Centre (stockholmresilience.org). Application: jQuery, Google Fonts and YouTube. Data & Observability: Google Analytics, Matomo and Piwik PRO. Last checked October 4, 2026.

What analytics tools does Stockholm Resilience Centre use?

Stockholm Resilience Centre uses Google Analytics, Matomo and Piwik PRO for analytics. We found Google Analytics through website code.

Does Stockholm Resilience Centre use Google Analytics?

Yes. We found Google Analytics at Stockholm Resilience Centre through website code. Google Analytics is used by 89,943 companies we track.

How does runsonwhat know what Stockholm Resilience Centre uses?

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