runsonwhat

SEAT's tech stack

What does SEAT use?

SEAT (seat.com) uses at least 19 tools we can see from public records, including Microsoft 365 for email and documents, LiveChat for customer support, Google Analytics for analytics and Akamai for content delivery. Last checked .

Industry
Automotive
Size
10,000+ employees
Based in
Spain
Founded
1950
LinkedIn
Company page
Tools found
19
Categories
9
Layers
5 of 5
Last checked
Oct 2026

SEAT'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

2 tools, where the bytes are served from

Application

3 tools, what the product is built with

Data & Observability

6 tools, what they measure and store

Go-to-market

4 tools, how they find and keep customers

Company Ops

4 tools, what the team runs on day to day

SEAT tech stack FAQ

What tools does SEAT use?

We've found 19 tools at SEAT (seat.com). Edge & Hosting: Akamai and Fastly. Application: Vimeo, YouTube and Google Maps. Data & Observability: Google Analytics, Google Tag Manager and Microsoft Clarity. Go-to-market: Meta Pixel, Google Ads and Spotify Ads. Company Ops: Microsoft 365, OneTrust and QuoVadis. Last checked October 4, 2026.

What email provider does SEAT use?

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

What does SEAT use for customer support?

SEAT uses LiveChat for customer support. We found LiveChat through website code.

What analytics tools does SEAT use?

SEAT uses Google Analytics, Google Tag Manager and Microsoft Clarity for analytics, among 4 tools in this category. We found Google Analytics through website code.

Does SEAT use Microsoft 365?

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

How does runsonwhat know what SEAT uses?

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