runsonwhat

CNRS Nucléaire & Particules's tech stack

What does CNRS Nucléaire & Particules use?

CNRS Nucléaire & Particules (in2p3.fr) uses at least 7 tools we can see from public records, including Matomo for analytics and Let's Encrypt for security. Last checked .

Industry
Research
Size
201–1,000 employees
Based in
Orsay, France
Founded
2020
LinkedIn
Company page
Re-check liveVisit in2p3.fr
Tools found
7
Categories
5
Layers
4 of 5
Last checked
Oct 2026

CNRS Nucléaire & Particules'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

3 tools, what the product is built with

Frontend

Media & UI

Data & Observability

1 tool, what they measure and store

Analytics

Go-to-market

1 tool, how they find and keep customers

Marketing

Company Ops

2 tools, what the team runs on day to day

Security & Compliance

Companies like CNRS Nucléaire & Particules also use

Tools common among companies with a similar stack that we haven't found at CNRS Nucléaire & Particules.

Companies with a stack like CNRS Nucléaire & Particules's

Ranked by shared tools, with rare tools counting more.

More Research companies

Other Research companies we've checked.

CNRS Nucléaire & Particules tech stack FAQ

What tools does CNRS Nucléaire & Particules use?

We've found 7 tools at CNRS Nucléaire & Particules (in2p3.fr). Application: jQuery, YouTube and Font Awesome. Data & Observability: Matomo. Company Ops: Let's Encrypt and Axeptio. Last checked October 4, 2026.

What analytics tools does CNRS Nucléaire & Particules use?

CNRS Nucléaire & Particules uses Matomo for analytics. We found Matomo through website code.

Does CNRS Nucléaire & Particules use jQuery?

Yes. We found jQuery at CNRS Nucléaire & Particules through website code. jQuery is used by 67,244 companies we track.

How does runsonwhat know what CNRS Nucléaire & Particules uses?

We read public traces only: CNRS Nucléaire & Particules'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.