runsonwhat

FutureClinic's tech stack

What does FutureClinic use?

FutureClinic (futureclinic.com) uses at least 9 tools we can see from public records, including Vercel for hosting, Google Workspace for email and documents, Intercom for customer support and Customer.io for marketing. Last checked .

“Personal doctors through chat”

Industry
Healthcare
Size
1–10 employees
Based in
New York City, United States
LinkedIn
Company page
Tools found
9
Categories
8
Layers
4 of 5
Last checked
Oct 2026

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

Go-to-market

3 tools, how they find and keep customers

Company Ops

2 tools, what the team runs on day to day

Email Delivery

FutureClinic tech stack FAQ

What tools does FutureClinic use?

We've found 9 tools at FutureClinic (futureclinic.com). Edge & Hosting: Cloudflare and Vercel. Application: WorkOS. Go-to-market: Intercom and Customer.io. Company Ops: Google Workspace and Resend. Last checked October 2, 2026.

What cloud does FutureClinic run on?

FutureClinic uses Vercel for hosting. We found Vercel through custom domain.

What email provider does FutureClinic use?

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

What does FutureClinic use for customer support?

FutureClinic uses Intercom for customer support. We found Intercom through email records.

What marketing software does FutureClinic use?

FutureClinic uses Customer.io for marketing. We found Customer.io through custom domain.

Does FutureClinic use Cloudflare?

Yes. We found Cloudflare at FutureClinic through DNS records and website code. Cloudflare is used by 147,753 companies we track.

How does runsonwhat know what FutureClinic uses?

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