runsonwhat

Pharos's tech stack

What does Pharos use?

Pharos (pharos.health) uses at least 22 tools we can see from public records, including Vercel for hosting, Microsoft 365 for email and documents, PostHog for analytics and Stytch for sign-in. Last checked .

“Helping hospitals identify and prevent avoidable harm using AI”

Industry
Healthcare IT
Size
1–10 employees
Based in
San Francisco, United States
LinkedIn
Company page
Tools found
22
Categories
12
Layers
5 of 5
Last checked
Oct 2026

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

3 tools, where the bytes are served from

Application

6 tools, what the product is built with

Data & Observability

4 tools, what they measure and store

Go-to-market

1 tool, how they find and keep customers

Company Ops

8 tools, what the team runs on day to day

Pharos tech stack FAQ

What tools does Pharos use?

We've found 22 tools at Pharos (pharos.health). Edge & Hosting: Vercel, Google Cloud and Fastly. Application: Google Fonts, Anthropic and OpenAI. Data & Observability: Sentry, web-vitals and PostHog. Company Ops: Microsoft 365, Google Workspace and Let's Encrypt. Last checked October 2, 2026.

What cloud does Pharos run on?

Pharos uses Vercel and Google Cloud for hosting. We found Vercel through custom domain.

What email provider does Pharos use?

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

What analytics tools does Pharos use?

Pharos uses PostHog for analytics. We found PostHog through website code.

Does Pharos use Microsoft 365?

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

How does runsonwhat know what Pharos uses?

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