runsonwhat

J.M. Finn's tech stack

What does J.M. Finn use?

J.M. Finn (jmfinn.com) uses at least 22 tools we can see from public records, including Netlify for hosting, Microsoft 365 for email and documents, Google Analytics for analytics and web-vitals for monitoring. Last checked .

Industry
Investment Management
Size
201–1,000 employees
Based in
London, United Kingdom
Founded
1946
LinkedIn
Company page
Tools found
22
Categories
11
Layers
5 of 5
Last checked
Oct 2026

J.M. Finn'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.

Edge & Hosting

1 tool, where the bytes are served from

Hosting & Cloud

Application

2 tools, what the product is built with

Go-to-market

5 tools, how they find and keep customers

Company Ops

8 tools, what the team runs on day to day

J.M. Finn tech stack FAQ

What tools does J.M. Finn use?

We've found 22 tools at J.M. Finn (jmfinn.com). Edge & Hosting: Netlify. Application: OpenAI and Gatsby. Data & Observability: Google Analytics, Google Tag Manager and Microsoft Clarity. Go-to-market: Meta Pixel, Google Ads and LinkedIn Insight Tag. Company Ops: Microsoft 365, GlobalSign and Exclaimer. Last checked October 4, 2026.

What cloud does J.M. Finn run on?

J.M. Finn uses Netlify for hosting. We found Netlify through custom domain and website code.

What email provider does J.M. Finn use?

J.M. Finn uses Microsoft 365 and Exclaimer for email and documents. We found Microsoft 365 through DNS verification records and email records.

What analytics tools does J.M. Finn use?

J.M. Finn uses Google Analytics, Google Tag Manager and Microsoft Clarity for analytics, among 5 tools in this category. We found Google Analytics through website code.

Does J.M. Finn use Microsoft 365?

Yes. We found Microsoft 365 at J.M. Finn through DNS verification records and email records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what J.M. Finn uses?

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