runsonwhat

Hospital Rio Grande's tech stack

What does Hospital Rio Grande use?

Hospital Rio Grande (hospitalriogrande.com.br) uses at least 9 tools we can see from public records, including Amazon Web Services for hosting, Google Workspace for email and documents, Google Analytics for analytics and Cloudflare for content delivery. Last checked .

Industry
Healthcare
Size
1,001–5,000 employees
Based in
Natal, Brazil
Founded
2018
LinkedIn
Company page
Tools found
9
Categories
5
Layers
4 of 5
Last checked
Oct 2026

Hospital Rio Grande'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

5 tools, what the product is built with

Data & Observability

1 tool, what they measure and store

Company Ops

1 tool, what the team runs on day to day

Hospital Rio Grande tech stack FAQ

What tools does Hospital Rio Grande use?

We've found 9 tools at Hospital Rio Grande (hospitalriogrande.com.br). Edge & Hosting: Cloudflare and Amazon Web Services. Application: Google Fonts, Vimeo and YouTube. Data & Observability: Google Analytics. Company Ops: Google Workspace. Last checked October 3, 2026.

What cloud does Hospital Rio Grande run on?

Hospital Rio Grande uses Amazon Web Services for hosting. We found Amazon Web Services through custom domain.

What email provider does Hospital Rio Grande use?

Hospital Rio Grande uses Google Workspace for email and documents. We found Google Workspace through email records.

What analytics tools does Hospital Rio Grande use?

Hospital Rio Grande uses Google Analytics for analytics. We found Google Analytics through website code.

Does Hospital Rio Grande use Cloudflare?

Yes. We found Cloudflare at Hospital Rio Grande through DNS records and website code. Cloudflare is used by 147,753 companies we track.

How does runsonwhat know what Hospital Rio Grande uses?

We read public traces only: Hospital Rio Grande'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.