runsonwhat

Nevada State Bank's tech stack

What does Nevada State Bank use?

Nevada State Bank (nsbank.com) uses at least 16 tools we can see from public records, including IBM Cloud for hosting, Microsoft 365 for email and documents, Salesforce for sales and Salesforce Marketing Cloud for marketing. Last checked .

Industry
Financial Services
Based in
United States
Founded
1959
Tools found
16
Categories
10
Layers
3 of 5
Last checked
Oct 2026

Nevada State Bank'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

Go-to-market

4 tools, how they find and keep customers

Company Ops

11 tools, what the team runs on day to day

Nevada State Bank tech stack FAQ

What tools does Nevada State Bank use?

We've found 16 tools at Nevada State Bank (nsbank.com). Edge & Hosting: IBM Cloud. Go-to-market: Meta Pixel, Salesforce and Salesforce Marketing Cloud. Company Ops: Microsoft 365, SendGrid and Atlassian. Last checked October 3, 2026.

What cloud does Nevada State Bank run on?

Nevada State Bank uses IBM Cloud for hosting. We found IBM Cloud through DNS verification records.

What CRM does Nevada State Bank use?

Nevada State Bank uses Salesforce for sales and CRM. We found Salesforce through custom domain and email records.

What email provider does Nevada State Bank use?

Nevada State Bank uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records.

What marketing software does Nevada State Bank use?

Nevada State Bank uses Salesforce Marketing Cloud for marketing. We found Salesforce Marketing Cloud through DNS verification records.

Does Nevada State Bank use Microsoft 365?

Yes. We found Microsoft 365 at Nevada State Bank through DNS verification records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what Nevada State Bank uses?

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