Finwave (ex Finance Evolution)'s tech stack
What does Finwave (ex Finance Evolution) use?
Finwave (ex Finance Evolution) (finance-evolution.it) uses at least 7 tools we can see from public records, including Microsoft Azure for hosting, Google Analytics for analytics and reCAPTCHA for security. Last checked .
- Industry
- Software
- Size
- 201–1,000 employees
- Based in
- Cinisello Balsamo, Italy
- Founded
- 2007
- Company page
- Tools found
- 7
- Categories
- 5
- Layers
- 4 of 5
- Last checked
- Oct 2026
Finwave (ex Finance Evolution)'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
Application
2 tools, what the product is built with
Media & UI
Data & Observability
1 tool, what they measure and store
Analytics
Company Ops
3 tools, what the team runs on day to day
Dev Tools
Security & Compliance
Finwave (ex Finance Evolution) tech stack FAQ
What tools does Finwave (ex Finance Evolution) use?
We've found 7 tools at Finwave (ex Finance Evolution) (finance-evolution.it). Edge & Hosting: Microsoft Azure. Application: Google Fonts and Google Maps. Data & Observability: Google Analytics. Company Ops: reCAPTCHA, Atlassian and CookieScript. Last checked October 6, 2026.
What cloud does Finwave (ex Finance Evolution) run on?
Finwave (ex Finance Evolution) uses Microsoft Azure for hosting. We found Microsoft Azure through custom domain.
What analytics tools does Finwave (ex Finance Evolution) use?
Finwave (ex Finance Evolution) uses Google Analytics for analytics. We found Google Analytics through website code.
Does Finwave (ex Finance Evolution) use Google Analytics?
Yes. We found Google Analytics at Finwave (ex Finance Evolution) through website code. Google Analytics is used by 725,138 companies we track.
How does runsonwhat know what Finwave (ex Finance Evolution) uses?
We read public traces only: Finwave (ex Finance Evolution)'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.