Seguros Unimed's tech stack
What does Seguros Unimed use?
Seguros Unimed (segurosunimed.com.br) uses at least 16 tools we can see from public records, including Google Cloud for hosting, Microsoft 365 for email and documents, HubSpot for sales and Akamai for content delivery. Last checked .
- Industry
- Insurance
- Size
- 1,001–5,000 employees
- Based in
- São Paulo, Brazil
- Founded
- 1989
- Company page
- Tools found
- 16
- Categories
- 10
- Layers
- 4 of 5
- Last checked
- Oct 2026
Seguros Unimed'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
Hosting & Cloud
CDN & Edge
Application
1 tool, what the product is built with
Backend & Database
Go-to-market
2 tools, how they find and keep customers
Marketing
Sales & CRM
Company Ops
10 tools, what the team runs on day to day
Email Delivery
Collaboration
Dev Tools
Security & Compliance
Seguros Unimed tech stack FAQ
What tools does Seguros Unimed use?
We've found 16 tools at Seguros Unimed (segurosunimed.com.br). Edge & Hosting: Google Cloud, Akamai and Oracle Cloud. Application: MongoDB Atlas. Go-to-market: HubSpot. Company Ops: Microsoft 365, Google Workspace and SendGrid. Last checked October 3, 2026.
What cloud does Seguros Unimed run on?
Seguros Unimed uses Google Cloud and Oracle Cloud for hosting. We found Google Cloud through custom domain.
What CRM does Seguros Unimed use?
Seguros Unimed uses HubSpot for sales and CRM. We found HubSpot through email records.
What email provider does Seguros Unimed use?
Seguros Unimed uses Microsoft 365, Google Workspace and Apple Business for email and documents. We found Microsoft 365 through DNS verification records.
Does Seguros Unimed use Microsoft 365?
Yes. We found Microsoft 365 at Seguros Unimed through DNS verification records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what Seguros Unimed uses?
We read public traces only: Seguros Unimed'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.