runsonwhat

EV.com's tech stack

What does EV.com use?

EV.com (ev.com) uses at least 17 tools we can see from public records, including Amazon Web Services for hosting, Microsoft 365 for email and documents, Google Analytics for analytics and Amazon CloudFront for content delivery. Last checked .

“Discover the perfect blend of innovation and sustainability with new & used electric cars for sale on EV.com. Drive into the future today”

Industry
Online Marketplace
Based in
New York, United States
Founded
1994
LinkedIn
Company page
Tools found
17
Categories
10
Layers
5 of 5
Last checked
Oct 2026

EV.com'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

3 tools, where the bytes are served from

Data & Observability

1 tool, what they measure and store

Go-to-market

4 tools, how they find and keep customers

Company Ops

2 tools, what the team runs on day to day

Email Delivery

EV.com tech stack FAQ

What tools does EV.com use?

We've found 17 tools at EV.com (ev.com). Edge & Hosting: Amazon Web Services, Amazon Route 53 and Amazon CloudFront. Application: Google Fonts, YouTube and React. Data & Observability: Google Analytics. Go-to-market: Google Ads, Meta Pixel and Pinterest. Company Ops: Microsoft 365 and SendGrid. Last checked October 4, 2026.

What cloud does EV.com run on?

EV.com uses Amazon Web Services for hosting. We found Amazon Web Services through website code.

What email provider does EV.com use?

EV.com uses Microsoft 365 for email and documents. We found Microsoft 365 through email records and website code.

What analytics tools does EV.com use?

EV.com uses Google Analytics for analytics. We found Google Analytics through website code.

Does EV.com use Microsoft 365?

Yes. We found Microsoft 365 at EV.com through email records and website code. Microsoft 365 is used by 462,187 companies we track.

How does runsonwhat know what EV.com uses?

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