Morrisons's tech stack
What does Morrisons use?
Morrisons (morrisons.com) uses at least 22 tools we can see from public records, including Google Workspace for email and documents, Google Analytics for analytics, Contentful for its website and Auth0 for sign-in. Last checked .
- Industry
- Retail
- Size
- 10,000+ employees
- Based in
- Leeds, United Kingdom
- Founded
- 1899
- Company page
- Tools found
- 22
- Categories
- 10
- Layers
- 5 of 5
- Last checked
- Oct 2026
Morrisons'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
CDN & Edge
Application
2 tools, what the product is built with
Frontend
Auth & Identity
Data & Observability
2 tools, what they measure and store
Go-to-market
11 tools, how they find and keep customers
Company Ops
6 tools, what the team runs on day to day
Dev Tools
Security & Compliance
Morrisons tech stack FAQ
What tools does Morrisons use?
We've found 22 tools at Morrisons (morrisons.com). Edge & Hosting: Amazon CloudFront. Application: Next.js and Auth0. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Meta Pixel, Google Ads and Microsoft Ads. Company Ops: Google Workspace, Apple Business and Proofpoint. Last checked October 4, 2026.
What email provider does Morrisons use?
Morrisons uses Google Workspace and Apple Business for email and documents. We found Google Workspace through email records.
What analytics tools does Morrisons use?
Morrisons uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
What CMS does Morrisons use?
Morrisons uses Contentful for its website. We found Contentful through website code.
Does Morrisons use Google Workspace?
Yes. We found Google Workspace at Morrisons through email records. Google Workspace is used by 126,364 companies we track.
How does runsonwhat know what Morrisons uses?
We read public traces only: Morrisons'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.