runsonwhat

Sageworks Banking Solutions's tech stack

What does Sageworks Banking Solutions use?

Sageworks Banking Solutions (sageworksanalyst.com) uses at least 10 tools we can see from public records, including Amazon Web Services for hosting, Microsoft 365 for email and documents, New Relic for monitoring and DigiCert for security. Last checked .

Industry
Software
Size
51–200 employees
Based in
Raleigh, United States
Founded
1998
LinkedIn
Company page
Tools found
10
Categories
7
Layers
4 of 5
Last checked
Oct 2026

Sageworks Banking Solutions'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

2 tools, what the product is built with

Data & Observability

1 tool, what they measure and store

Company Ops

5 tools, what the team runs on day to day

Sageworks Banking Solutions tech stack FAQ

What tools does Sageworks Banking Solutions use?

We've found 10 tools at Sageworks Banking Solutions (sageworksanalyst.com). Edge & Hosting: Amazon Web Services and Amazon Route 53. Application: jQuery and Font Awesome. Data & Observability: New Relic. Company Ops: Microsoft 365, Google Workspace and DigiCert. Last checked October 5, 2026.

What cloud does Sageworks Banking Solutions run on?

Sageworks Banking Solutions uses Amazon Web Services for hosting. We found Amazon Web Services through custom domain and website code.

What email provider does Sageworks Banking Solutions use?

Sageworks Banking Solutions uses Microsoft 365 and Google Workspace for email and documents. We found Microsoft 365 through email records.

Does Sageworks Banking Solutions use Microsoft 365?

Yes. We found Microsoft 365 at Sageworks Banking Solutions through email records. Microsoft 365 is used by 682,847 companies we track.

How does runsonwhat know what Sageworks Banking Solutions uses?

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