Sakra world hospital's tech stack
What does Sakra world hospital use?
Sakra world hospital (sakraworldhospital.com) uses at least 10 tools we can see from public records, including Google Cloud for hosting, Google Analytics for analytics and reCAPTCHA for security. Last checked .
- Industry
- Healthcare
- Size
- 1,001–5,000 employees
- Based in
- Panathur, India
- Founded
- 2013
- Company page
- Tools found
- 10
- Categories
- 6
- Layers
- 5 of 5
- Last checked
- Oct 2026
Sakra world hospital'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
3 tools, what they measure and store
Go-to-market
3 tools, how they find and keep customers
Marketing
Ads & Pixels
Company Ops
1 tool, what the team runs on day to day
Security & Compliance
Sakra world hospital tech stack FAQ
What tools does Sakra world hospital use?
We've found 10 tools at Sakra world hospital (sakraworldhospital.com). Edge & Hosting: Google Cloud. Application: YouTube and GTranslate. Data & Observability: Google Analytics, Google Tag Manager and Hotjar. Go-to-market: Meta Pixel and Google Ads. Company Ops: reCAPTCHA. Last checked October 3, 2026.
What cloud does Sakra world hospital run on?
Sakra world hospital uses Google Cloud for hosting. We found Google Cloud through DNS records.
What analytics tools does Sakra world hospital use?
Sakra world hospital uses Google Analytics, Google Tag Manager and Hotjar for analytics. We found Google Analytics through website code.
Does Sakra world hospital use Google Analytics?
Yes. We found Google Analytics at Sakra world hospital through website code. Google Analytics is used by 89,943 companies we track.
How does runsonwhat know what Sakra world hospital uses?
We read public traces only: Sakra world hospital'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.