runsonwhat

The Francis Crick Institute's tech stack

What does The Francis Crick Institute use?

The Francis Crick Institute (crick.ac.uk) uses at least 21 tools we can see from public records, including Microsoft 365 for email and documents, ServiceNow for customer support, Amazon CloudFront for content delivery and SendGrid for email delivery. Last checked .

Industry
Research
Size
1,001–5,000 employees
Based in
London, United Kingdom
Founded
2011
LinkedIn
Company page
Tools found
21
Categories
10
Layers
4 of 5
Last checked
Oct 2026

The Francis Crick Institute'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

Application

1 tool, what the product is built with

Go-to-market

2 tools, how they find and keep customers

Company Ops

17 tools, what the team runs on day to day

The Francis Crick Institute tech stack FAQ

What tools does The Francis Crick Institute use?

We've found 21 tools at The Francis Crick Institute (crick.ac.uk). Edge & Hosting: Amazon CloudFront. Application: Anthropic. Go-to-market: ServiceNow. Company Ops: Microsoft 365, SendGrid and Apple Business. Last checked October 3, 2026.

What email provider does The Francis Crick Institute use?

The Francis Crick Institute uses Microsoft 365 and Apple Business for email and documents. We found Microsoft 365 through DNS verification records and email records.

What does The Francis Crick Institute use for customer support?

The Francis Crick Institute uses ServiceNow for customer support. We found ServiceNow through email records.

Does The Francis Crick Institute use Microsoft 365?

Yes. We found Microsoft 365 at The Francis Crick Institute through DNS verification records and email records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what The Francis Crick Institute uses?

We read public traces only: The Francis Crick Institute'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.