Parency Ivf Hospital's tech stack
What does Parency Ivf Hospital use?
Parency Ivf Hospital (parencyivf.com) uses at least 9 tools we can see from public records, including Zoho for sales, Google Tag Manager for analytics, WordPress for its website and Trustindex for marketing. Last checked .
- Industry
- Healthcare
- Size
- 51–200 employees
- Based in
- Jayanagar East, India
- Company page
- Tools found
- 9
- Categories
- 7
- Layers
- 4 of 5
- Last checked
- Oct 2026
Parency Ivf 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
DNS
Application
3 tools, what the product is built with
Frontend
Media & UI
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
4 tools, how they find and keep customers
Parency Ivf Hospital tech stack FAQ
What tools does Parency Ivf Hospital use?
We've found 9 tools at Parency Ivf Hospital (parencyivf.com). Edge & Hosting: GoDaddy. Application: jQuery, Google Fonts and Vimeo. Data & Observability: Google Tag Manager. Go-to-market: WordPress, Zoho and Trustindex. Last checked October 6, 2026.
What CRM does Parency Ivf Hospital use?
Parency Ivf Hospital uses Zoho for sales and CRM. We found Zoho through email records.
What analytics tools does Parency Ivf Hospital use?
Parency Ivf Hospital uses Google Tag Manager for analytics. We found Google Tag Manager through website code.
What CMS does Parency Ivf Hospital use?
Parency Ivf Hospital uses WordPress for its website. We found WordPress through website code.
What marketing software does Parency Ivf Hospital use?
Parency Ivf Hospital uses Trustindex for marketing. We found Trustindex through website code.
Does Parency Ivf Hospital use jQuery?
Yes. We found jQuery at Parency Ivf Hospital through website code. jQuery is used by 395,629 companies we track.
How does runsonwhat know what Parency Ivf Hospital uses?
We read public traces only: Parency Ivf 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.