runsonwhat

Microhealth's tech stack

What does Microhealth use?

Microhealth (microhealth.com) uses at least 10 tools we can see from public records, including Google Workspace for email and documents, Google Analytics for analytics, Contentful for its website and UptimeRobot for monitoring. Last checked .

“Rare Disease-Focused Care Delivery and Evidence Generation Platform”

Industry
Consumer Health and Wellness
Size
11–50 employees
Based in
Claymont, United States
Tools found
10
Categories
9
Layers
4 of 5
Last checked
Oct 2026

Microhealth'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.

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

Company Ops

2 tools, what the team runs on day to day

Security & Compliance

Microhealth tech stack FAQ

What tools does Microhealth use?

We've found 10 tools at Microhealth (microhealth.com). Application: GSAP and Next.js. Data & Observability: Google Analytics, Google Tag Manager and UptimeRobot. Go-to-market: Google Ads and Contentful. Company Ops: Google Workspace and Vanta. Last checked October 2, 2026.

What email provider does Microhealth use?

Microhealth uses Google Workspace for email and documents. We found Google Workspace through email records.

What analytics tools does Microhealth use?

Microhealth uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.

What CMS does Microhealth use?

Microhealth uses Contentful for its website. We found Contentful through website code.

Does Microhealth use Google Workspace?

Yes. We found Google Workspace at Microhealth through email records. Google Workspace is used by 126,364 companies we track.

How does runsonwhat know what Microhealth uses?

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