runsonwhat

Московская Биржа's tech stack

What does Московская Биржа use?

Московская Биржа (moex.com) uses at least 11 tools we can see from public records, including Microsoft 365 for email and documents, Google Tag Manager for analytics and Yandex Webmaster for marketing. Last checked .

Industry
Financial Services
Size
1,001–5,000 employees
Based in
Moscow, Russia
Founded
2011
LinkedIn
Company page
Tools found
11
Categories
6
Layers
4 of 5
Last checked
Oct 2026

Московская Биржа'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

Data & Observability

1 tool, what they measure and store

Go-to-market

5 tools, how they find and keep customers

Company Ops

2 tools, what the team runs on day to day

Collaboration

Московская Биржа tech stack FAQ

What tools does Московская Биржа use?

We've found 11 tools at Московская Биржа (moex.com). Application: React, Tailwind CSS and Next.js. Data & Observability: Google Tag Manager. Go-to-market: Meta Pixel, Yandex Webmaster and ADFOX. Company Ops: Microsoft 365 and Webex. Last checked October 3, 2026.

What email provider does Московская Биржа use?

Московская Биржа uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records.

What analytics tools does Московская Биржа use?

Московская Биржа uses Google Tag Manager for analytics. We found Google Tag Manager through website code.

What marketing software does Московская Биржа use?

Московская Биржа uses Yandex Webmaster for marketing. We found Yandex Webmaster through DNS verification records and website code.

Does Московская Биржа use Microsoft 365?

Yes. We found Microsoft 365 at Московская Биржа through DNS verification records. Microsoft 365 is used by 685,700 companies we track.

How does runsonwhat know what Московская Биржа uses?

We read public traces only: Московская Биржа'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.