runsonwhat

MediSearch's tech stack

What does MediSearch use?

MediSearch (medisearch.io) uses at least 13 tools we can see from public records, including Vercel for hosting, Microsoft 365 for email and documents, Amplitude for analytics and Sentry for monitoring. Last checked .

“Search engine for trustworthy medical information.”

Industry
Consumer Health and Wellness
Size
1–10 employees
Based in
London, United Kingdom
Tools found
13
Categories
8
Layers
4 of 5
Last checked
Oct 2026

MediSearch'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

2 tools, what the product is built with

Data & Observability

4 tools, what they measure and store

Company Ops

5 tools, what the team runs on day to day

MediSearch tech stack FAQ

What tools does MediSearch use?

We've found 13 tools at MediSearch (medisearch.io). Edge & Hosting: Vercel and Google Cloud. Application: OpenAI and Next.js. Data & Observability: Sentry, Atlassian Statuspage and web-vitals. Company Ops: Microsoft 365, Google Workspace and SendGrid. Last checked October 2, 2026.

What cloud does MediSearch run on?

MediSearch uses Vercel and Google Cloud for hosting. We found Vercel through custom domain and website code.

What email provider does MediSearch use?

MediSearch uses Microsoft 365 and Google Workspace for email and documents. We found Microsoft 365 through DNS verification records.

What analytics tools does MediSearch use?

MediSearch uses Amplitude for analytics. We found Amplitude through website code.

Does MediSearch use Microsoft 365?

Yes. We found Microsoft 365 at MediSearch through DNS verification records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what MediSearch uses?

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