runsonwhat

Arriva TrainCare's tech stack

What does Arriva TrainCare use?

Arriva TrainCare (arrivatc.com) uses at least 6 tools we can see from public records, including Microsoft 365 for email and documents, WordPress for its website and SendGrid for email delivery. Last checked .

Industry
Transportation/trucking/railroad
Size
51–200 employees
Based in
Crewe, United Kingdom
Founded
2011
LinkedIn
Company page
Re-check liveVisit arrivatc.com
Tools found
6
Categories
6
Layers
3 of 5
Last checked
Oct 2026

Arriva TrainCare'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

2 tools, what the product is built with

Frontend

Media & UI

Go-to-market

1 tool, how they find and keep customers

Website & CMS

Company Ops

3 tools, what the team runs on day to day

Email Delivery

Workspace

Collaboration

Companies like Arriva TrainCare also use

Tools common among companies with a similar stack that we haven't found at Arriva TrainCare.

Companies with a stack like Arriva TrainCare's

Ranked by shared tools, with rare tools counting more.

Arriva TrainCare tech stack FAQ

What tools does Arriva TrainCare use?

We've found 6 tools at Arriva TrainCare (arrivatc.com). Application: jQuery and YouTube. Go-to-market: WordPress. Company Ops: Microsoft 365, SendGrid and Nintex. Last checked October 3, 2026.

What email provider does Arriva TrainCare use?

Arriva TrainCare uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records and email records.

What CMS does Arriva TrainCare use?

Arriva TrainCare uses WordPress for its website. We found WordPress through website code.

Does Arriva TrainCare use Microsoft 365?

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

How does runsonwhat know what Arriva TrainCare uses?

We read public traces only: Arriva TrainCare'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.