runsonwhat

NV Energy's tech stack

What does NV Energy use?

NV Energy (nvenergy.com) uses at least 17 tools we can see from public records, including Microsoft Azure for hosting, Microsoft 365 for email and documents, Google Tag Manager for analytics and Cloudflare for content delivery. Last checked .

Industry
Energy Supply
Size
1,001–5,000 employees
Based in
Las Vegas, United States
Founded
1999
LinkedIn
Company page
Tools found
17
Categories
11
Layers
5 of 5
Last checked
Oct 2026

NV Energy'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

Application

2 tools, what the product is built with

Data & Observability

1 tool, what they measure and store

Go-to-market

2 tools, how they find and keep customers

Company Ops

9 tools, what the team runs on day to day

NV Energy tech stack FAQ

What tools does NV Energy use?

We've found 17 tools at NV Energy (nvenergy.com). Edge & Hosting: Cloudflare, Microsoft Azure and IBM Cloud. Application: Google Fonts and Google Maps. Data & Observability: Google Tag Manager. Go-to-market: Meta Pixel. Company Ops: Microsoft 365, SendGrid and Apple Business. Last checked October 4, 2026.

What cloud does NV Energy run on?

NV Energy uses Microsoft Azure and IBM Cloud for hosting. We found Microsoft Azure through custom domain.

What email provider does NV Energy use?

NV Energy uses Microsoft 365 and Apple Business for email and documents. We found Microsoft 365 through DNS verification records and email records.

What analytics tools does NV Energy use?

NV Energy uses Google Tag Manager for analytics. We found Google Tag Manager through website code.

Does NV Energy use Microsoft 365?

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

How does runsonwhat know what NV Energy uses?

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