NeoLife Inc.'s tech stack
What does NeoLife Inc. use?
NeoLife Inc. (neolife.health) uses at least 14 tools we can see from public records, including Amazon Web Services for hosting, Google Workspace for email and documents, web-vitals for monitoring and Cloudflare for content delivery. Last checked .
“AI-native intake, compliance, and cross-pharmacy routing for modern healthcare — telehealth and brick-and-mortar clinics, and the pharmacies that fill for them.”
- Industry
- Telemedicine
- Based in
- Sheridan, United States
- Founded
- 2025
- Company page
- Tools found
- 14
- Categories
- 9
- Layers
- 5 of 5
- Last checked
- Oct 2026
NeoLife Inc.'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
CDN & Edge
Application
2 tools, what the product is built with
Frontend
Data & Observability
1 tool, what they measure and store
Monitoring
Go-to-market
1 tool, how they find and keep customers
Marketing
Company Ops
8 tools, what the team runs on day to day
Email Delivery
Workspace
NeoLife Inc. tech stack FAQ
What tools does NeoLife Inc. use?
We've found 14 tools at NeoLife Inc. (neolife.health). Edge & Hosting: Cloudflare and Amazon Web Services. Application: Next.js. Data & Observability: web-vitals. Company Ops: Google Workspace, Let's Encrypt and Sectigo. Last checked October 4, 2026.
What cloud does NeoLife Inc. run on?
NeoLife Inc. uses Amazon Web Services for hosting. We found Amazon Web Services through custom domain.
What email provider does NeoLife Inc. use?
NeoLife Inc. uses Google Workspace and Proton Mail for email and documents. We found Google Workspace through email records.
Does NeoLife Inc. use Cloudflare?
Yes. We found Cloudflare at NeoLife Inc. through DNS records and website code. Cloudflare is used by 147,753 companies we track.
How does runsonwhat know what NeoLife Inc. uses?
We read public traces only: NeoLife Inc.'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.