NECS's tech stack
What does NECS use?
NECS (necsu.nhs.uk) uses at least 12 tools we can see from public records, including Microsoft Azure for hosting, Microsoft 365 for email and documents, Google Analytics for analytics and WordPress for its website. Last checked .
- Industry
- Healthcare
- Size
- 1,001–5,000 employees
- Based in
- Durham, United Kingdom
- Founded
- 2013
- Company page
- Tools found
- 12
- Categories
- 8
- Layers
- 5 of 5
- Last checked
- Oct 2026
NECS'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
5 tools, what the product is built with
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
2 tools, how they find and keep customers
Website & CMS
Marketing
Company Ops
3 tools, what the team runs on day to day
Workspace
Security & Compliance
NECS tech stack FAQ
What tools does NECS use?
We've found 12 tools at NECS (necsu.nhs.uk). Edge & Hosting: Microsoft Azure. Application: jQuery, Google Fonts and Vimeo. Data & Observability: Google Analytics. Go-to-market: WordPress. Company Ops: Microsoft 365, Apple Business and reCAPTCHA. Last checked October 3, 2026.
What cloud does NECS run on?
NECS uses Microsoft Azure for hosting. We found Microsoft Azure through custom domain.
What email provider does NECS use?
NECS uses Microsoft 365 and Apple Business for email and documents. We found Microsoft 365 through DNS verification records.
What analytics tools does NECS use?
NECS uses Google Analytics for analytics. We found Google Analytics through website code.
What CMS does NECS use?
NECS uses WordPress for its website. We found WordPress through website code.
Does NECS use Microsoft 365?
Yes. We found Microsoft 365 at NECS through DNS verification records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what NECS uses?
We read public traces only: NECS'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.