MDfit's tech stack
What does MDfit use?
MDfit (mdfit.com) uses at least 11 tools we can see from public records, including Vercel for hosting, Microsoft 365 for email and documents, Vercel Analytics for analytics and Amazon SES for email delivery. Last checked .
“Enterprise healthcare technology for provider directory management, patient scheduling, and Voice AI automation.”
- Industry
- Healthcare
- Size
- 11–50 employees
- Based in
- Pittsburgh, United States
- Founded
- 2013
- Company page
- Tools found
- 11
- Categories
- 10
- Layers
- 4 of 5
- Last checked
- Oct 2026
MDfit'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
Hosting & Cloud
Application
3 tools, what the product is built with
Data & Observability
2 tools, what they measure and store
Analytics
Company Ops
4 tools, what the team runs on day to day
Email Delivery
Workspace
Dev Tools
Security & Compliance
MDfit tech stack FAQ
What tools does MDfit use?
We've found 11 tools at MDfit (mdfit.com). Edge & Hosting: Amazon Route 53 and Vercel. Application: Vimeo and Next.js. Data & Observability: Vercel Analytics and Fathom. Company Ops: Microsoft 365, Atlassian and Amazon SES. Last checked October 6, 2026.
What cloud does MDfit run on?
MDfit uses Vercel for hosting. We found Vercel through DNS records, custom domain and website code.
What email provider does MDfit use?
MDfit uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records and email records.
What analytics tools does MDfit use?
MDfit uses Vercel Analytics and Fathom for analytics. We found Vercel Analytics through website code.
Does MDfit use Microsoft 365?
Yes. We found Microsoft 365 at MDfit through DNS verification records and email records. Microsoft 365 is used by 685,421 companies we track.
How does runsonwhat know what MDfit uses?
We read public traces only: MDfit'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.