White-label telehealth hides three different models: a hosted portal skinned with your logo (fastest start, vendor owns your conversion), a marketplace attachment under revenue-share (you are effectively an affiliate), and API infrastructure (you own the product and patient relationship; the vendor operates the clinical back office). Portals validate demand; the API model is what brands at meaningful volume end up wanting.
What people mean by "white-label telehealth"
A brand wants to offer medical care — weight management, hormones, dermatology — without becoming a medical group. Some vendor supplies the clinicians, the prescriptions, and the compliance, and the brand supplies the customers. That arrangement gets called white-label telehealth, but the term hides three structurally different models, and they age very differently.
Model 1: the white-label portal
The vendor hosts a patient experience — intake pages, visit flows, a patient dashboard — skinned with your logo and colors. You point customers at it, usually on a subdomain. It is the fastest possible start and the least engineering, which is exactly its ceiling: your "product" is a theme on someone else's product. You control colors, not conversion. Funnel experiments, bundled offers, retention features — all wait on the vendor's roadmap. And because the patient relationship lives in their system, moving away later means a real migration.
Model 2: the marketplace attachment
You send customers to an existing telehealth service under a revenue-share, sometimes with co-branding. It is the model behind most "powered by" partnerships. Cheap to try, but you are effectively an affiliate: thin margins, no patient relationship, and churn belongs to nobody. Reasonable for testing demand; rarely a business.
Model 3: API infrastructure
You build and own the patient experience — your app, your checkout, your funnel — and call an API for the clinical events: intake submission, clinician visit, prescription, labs, fulfillment. The vendor operates the medical group, pharmacy routing, and 50-state compliance behind the interface. This is the model that treats care like payments companies treat Stripe: infrastructure underneath, brand equity on top.
The trade-off is honest: you need engineers. If you cannot build a front-end at all, a portal is the realistic start. But every brand we have seen at meaningful volume eventually wants what the API model gives: control of conversion, ownership of the patient relationship, and the ability to change vendors without patients noticing.
The three models, side by side
| Portal | Marketplace | API infrastructure | |
|---|---|---|---|
| You own | Logo and colors | The referral | Product, funnel, patient relationship |
| Vendor owns | Experience, conversion, roadmap | Everything | Clinical back office behind the API |
| Engineering needed | None | None | A front-end team |
| Time to launch | Days–weeks | Days | Weeks |
| Ceiling | Vendor’s template | Affiliate margins | Yours |
| Switching cost later | Real migration | Low | Vendor swap behind your app |
How to choose
- You have no engineering team and need to validate demand this quarter: portal, with an exit plan in the contract.
- You have a funnel you have already paid to optimize: API infrastructure — do not hand your conversion rate to a vendor's template.
- You are testing whether your audience buys care at all: marketplace attachment, briefly.
Questions that expose the difference
- Who renders the checkout page — us or you? (Who owns conversion?)
- Can we export every patient record via API, today, without asking?
- If we redesign our onboarding flow next month, does anyone at your company need to be involved?
- Whose name is on the BAA, the pharmacy relationships, and the clinician contracts?
Lithos is the third model: one API for intake, visits, eRx, benefits, labs, and pharmacy, with the clinical back office — clinician network, compliance, audit — operated behind it. Your patients only ever see you.
Frequently asked questions
What does white-label telehealth cost?
It varies by model: portals typically charge platform plus per-visit fees, marketplaces take revenue share, and API infrastructure prices platform plus per-visit economics that scale with volume. Compare against the fully loaded cost of building clinical operations yourself.
Which model launches fastest?
The hosted portal — little to no engineering. The trade is ceiling: your funnel, retention features, and patient relationship live on the vendor’s roadmap.
Can we start on a portal and move to the API later?
Yes, and many brands do — but it is a real migration, so negotiate data-export rights and an exit plan into the portal contract on day one.
Who actually employs the doctors behind a white-label brand?
A physician-owned medical group operated by (or affiliated with) the vendor — the structure corporate-practice-of-medicine rules require. Ask whose name is on the clinician contracts, the BAA, and the pharmacy relationships.
Get the Journal by email
Our best guides on building compliant telehealth programs — a couple a week, unsubscribe any time.
Do DTC telehealth brands need an EHR? EHR vs. clinical infrastructure
What an EHR is actually for, what a DTC program actually runs, and the four questions that decide which system of record you need.
Read the guide
The telehealth tech stack in 2026: what you build vs. what you rent
Eight layers, a build/rent verdict for each, and where the engineering time actually goes.
Read the guide
The best white-label telehealth platforms in 2026: an honest comparison
Nine vendors sorted by model and fit — done-for-you operators, enterprise networks, developer platforms, and API infrastructure — with our bias disclosed.
Read the guideFrom first call to first patient, in weeks.
A 15-minute intro call, sandbox credentials the same day, go-live in 3–4 weeks — new launches and existing patient bases alike.