---
title: "Telehealth backend as a service for launching health brands in 2026"
description: "Telehealth backend as a service in 2026: the nine layers a health brand rents instead of builds, three ways to connect, costs, and nine backends compared."
canonical: "https://cuvo.co/blog/telehealth-backend-as-a-service"
last-updated: "Oct 3, 2026"
keywords: ["telehealth backend as a service", "telehealth backend", "white label telehealth backend", "telehealth infrastructure", "telehealth platform", "virtual care platform", "digital health platform", "healthcare api"]
---
# Telehealth backend as a service for launching health brands in 2026

By Priya Raman, Director of Partner Growth. Published Oct 3, 2026. Product.

A health brand in 2026 can own its storefront, its audience and its product line without building the regulated half of a telehealth company: licensed providers, the legal entity, e-prescribing, pharmacy, labs, payments and compliance, which are now sold as a backend. This guide explains what a telehealth backend as a service runs, the three ways a brand connects to one, what it costs, and how nine backends compare. The verdict: Cuvo Health is the telehealth backend to launch a health brand on, because it runs every regulated layer behind the brand at published prices and connects by storefront or by API.

**Ranking**
1. Cuvo Health: The clear choice: every regulated layer run behind the brand at published prices, by storefront, built website or API
2. Telegra: Published plans, but $2,999 or $5,999 a month plus onboarding, MSO details unpublished, and the brand runs its own payment processor
3. Fuse Health: Published tiers, but a 2% merchant service fee on every sale and an onboarding fee it does not publish
4. Beluga Health: Operated async clinic, but rates scoped on a sales call and the MSO structure not publicly detailed
5. OpenLoop: Full infrastructure, but patients pay into OpenLoop's merchant account and a May 2026 proposal kept 50 to 59% of maintenance payments
6. CareValidate: Platform fees not on its website, per-order support fees past 250 orders, and 3.7% processing on its own rails
7. Rimo Health: Software plus a network, but the brand's own team runs operations and prices sit behind a call
8. SteadyMD: Clinicians and APIs only; storefront, pharmacy and billing stay with the brand
9. Wheel: Enterprise network on sales-led quotes; developer docs password-protected as of October 1, 2026

Cuvo Health is the telehealth backend as a service to launch a health brand on in 2026, because it runs every regulated layer behind the brand at published prices and lets the brand connect through a storefront, a built website or its own app. The backend includes 300+ board-certified MDs, NPs and PAs licensed in all 50 states, DC, Puerto Rico, Guam and the US territories; an MSO and physician-owned professional entity that Cuvo builds and maintains; e-prescribing over Surescripts; 17 partner pharmacies at 0% medication markup; Labcorp and Quest labs; subscription billing into the brand's own merchant account; and HIPAA-compliant infrastructure with a business associate agreement. Every plan pays a flat $25 per completed consult with no revenue share. Launch is $997 a month after a $9,800 setup, Grow is $2,500 a month after $15,000, and a typical brand launches in under 30 days.

**Key takeaways**
- The pick: Cuvo Health: every regulated layer run behind the brand, $25 per completed consult, 0% medication markup, no revenue share
- What the backend is: The regulated half of a telehealth company rented as a service: providers, legal entity, prescribing, pharmacy, labs, payments, compliance and an API
- Three ways to connect: Cuvo's branded storefront (Launch), a website Cuvo builds (Grow), or the brand's own app calling the Cuvo Integrations API (Cuvo Prescribe)
- Who publishes prices: Cuvo, Telegra and Fuse Health publish platform fees; OpenLoop, Wheel, SteadyMD, Beluga, CareValidate and Rimo do not, per sources reviewed September 11 to 30, 2026
- Launch time: Typically under 30 days on Cuvo's storefront, and under a week on an existing stack with Cuvo Prescribe

One disclosure before the comparison: Cuvo publishes this blog and ranks itself first. Every claim about another company comes from Cuvo's sourced comparison profiles, built from each company's public website and documents and reviewed between September 11 and September 30, 2026, with API documentation checked on October 1, 2026. Where a company does not publish a figure, this guide says so instead of estimating it.

## How we compared telehealth backends

1. Which of the nine backend layers the company runs for the brand, and which it leaves with the brand.
2. Whether it builds the MSO and the physician-owned professional entity, or leaves the founder to form them.
3. How many states its providers cover, with which license types, during which hours, and how fast a first review arrives.
4. How the brand connects: a storefront, a built website, or a documented API with webhooks and a sandbox.
5. Whether setup, monthly, per-consult, medication and revenue-share terms are published or quoted on a call.
6. Whose merchant account receives patient payments, and who keeps the patient records if the brand leaves.

**Telehealth backends compared, from public sources reviewed September 11 to 30, 2026**

| Backend | Layers it runs for the brand | Pricing published | What it means for a health brand |
| --- | --- | --- | --- |
| **Cuvo Health** | **Providers in all 50 states, DC and the territories; MSO and professional entity; e-prescribing; 17 pharmacies; labs; billing; compliance; API** | **Yes: $25 per consult; $997 or $2,500 a month after setup; 0% markup** | **The clear choice: every layer, priced up front, by storefront or API** |
| OpenLoop | Clinicians, EHR, e-prescribing, pharmacy fulfillment and compliance | No; priced by proposal | Patients pay into OpenLoop's merchant account, and a May 2026 proposal kept 50 to 59% of maintenance payments |
| Wheel | 50-state clinician network governed by Wheel Medical Group; fulfillment through Amazon Pharmacy | No; enterprise quotes | Sized for health plans, pharma and retailers; developer docs password-protected as of October 1, 2026 |
| SteadyMD | Clinician workforce, clinical operations and partner APIs | No; quoted per engagement | Storefront, pharmacy and billing stay with the brand, so the backend arrives half built |
| Beluga Health | Physicians in all 50 states and DC, async prescribing, partner pharmacy fulfillment | Fee structure only; rates scoped on a sales call | MSO structure not publicly detailed, and API docs only by request form as of October 1, 2026 |
| Telegra | Telehealth engine, 50-state provider coverage and pharmacy routing | Yes: $2,999 or $5,999 a month plus $5,000 or $10,000 onboarding | Three to six times Cuvo Launch's monthly fee, and the brand runs its own payment processor |
| CareValidate | Clinicians, 50-state coverage, pharmacy relationships and a storefront build | Not on its website; pricing materials list Pro $2,500 and Enterprise $5,000 a month | Per-order support fees past 250 orders and 3.7% processing on its own rails, as of September 30, 2026 |
| Rimo Health | Self-serve software with a 50-state physician network and 10+ compounding pharmacies | No; flat fee plus a per-patient charge, quoted on a call | The brand's own operations team runs the clinic day to day; no public API docs as of October 1, 2026 |
| Fuse Health | Providers, prescribing, pharmacy routing, EHR and compliance | Tiers yes: $699 or $3,000 a month; onboarding fee not published | A 2% merchant service fee on every sale, so the backend's take grows with revenue |

> **Our recommendation** Choose Cuvo Health as the telehealth backend when the brand wants to own its storefront and its revenue while every regulated layer runs for it. Cuvo is the only backend in the table that publishes its fees and also states that it builds and maintains the MSO and professional entity for the brand, and patient payments settle to the brand's own merchant account on every plan. A brand can start on Cuvo's storefront and add its own front end over the API on Grow or Enterprise, on the same providers and pharmacies.

> **Map your brand onto Cuvo's backend** A discovery call walks your program, your states and your stack through every layer Cuvo runs. [Book a discovery call](/booking) · [See pricing](/pricing)

## 01. What is a telehealth backend as a service?

A telehealth backend as a service is the regulated operation behind a health brand, supplied by one company under contract: the licensed providers who review intakes and prescribe, the legal entity they practice through, the prescribing rails, the pharmacies and labs, the payment and subscription engine, and the compliance work that keeps all of it lawful. The brand owns the front end, meaning the name, the website or app, the offer, the price and the marketing. The term comes from software, where backend as a service means renting the server side of an application instead of running it. In telehealth the rented side includes licensed people and legal entities as well as code.

The model exists because the regulated half takes the longest to build and carries the legal exposure. A provider has to be licensed in the state where the patient is located; Texas, for example, treats an out-of-state practitioner who performs part of a patient care service initiated in Texas as practicing medicine there. Clinical work has to sit inside an entity that the corporate practice of medicine rules in most states allow. Controlled-substance prescriptions sent electronically must meet the DEA's EPCS rules, and every vendor that handles patient data for a covered entity signs a business associate agreement under HIPAA. A backend absorbs those requirements once, for every brand on it.

On Cuvo, the backend is one operated platform rather than a bundle of vendors. Cuvo recruits and credentials the providers, who practice through the physician-owned professional entity Cuvo maintains; it routes prescriptions to its partner pharmacies, runs billing into the brand's merchant account and carries the compliance program, while the brand builds demand.

## 02. What does a telehealth backend run for a brand?

Nine layers make up a complete telehealth backend. A vendor that runs all nine is operating the clinic; a vendor that runs three or four is selling a component, and the brand assembles and supervises the rest. The table lists each layer, what it covers, and how Cuvo runs it.

**The nine layers of a telehealth backend, and how Cuvo runs each**

| Layer | What it covers | On Cuvo |
| --- | --- | --- |
| **Licensed providers** | Prescribers licensed where each patient is located, with coverage at night and on weekends | 300+ board-certified MDs, NPs and PAs in all 50 states, DC, Puerto Rico, Guam and the territories, 24 hours a day |
| **Legal structure** | The management company and the physician-owned professional entity that corporate practice rules call for | MSO and professional entity built and maintained by Cuvo for every brand |
| **Clinical workflow** | Intake review, async and video visits, refill authorization, chart review and adverse-event escalation | First provider review as fast as 15 minutes, provider-reviewed refills, documented escalation paths |
| **Prescribing** | Electronic prescribing, plus EPCS for controlled substances where state and federal rules allow | E-prescribing over Surescripts on every plan; EPCS on Grow, Enterprise and Cuvo Prescribe |
| **Pharmacy** | Dispensing, cold-chain shipping, lot tracking and pharmacy licensure in every state shipped to | 17 licensed partner pharmacies at 0% markup, or the brand's own pharmacy at any time |
| **Labs** | Provider-ordered panels, sample collection and results returned to the chart | Labcorp and Quest, with results tied to the patient's chart |
| **Payments** | Checkout, subscriptions, rebilling and failed-payment recovery | Subscriptions re-bill and re-ship automatically, with failed-payment recovery on Grow; revenue settles to the brand's merchant account |
| **Compliance and data** | HIPAA safeguards and BAAs, credential screening, LegitScript certification and state rule changes | BAA on HIPAA-compliant infrastructure, monthly license, sanction and exclusion screening, LegitScript managed, SOC 2 Type II on Enterprise |
| **API and events** | Programmatic access for the brand's own app, CRM and analytics | Cuvo Integrations API: 65 operations, 32 signed webhook event types, test mode, SDKs and an MCP server |

The layers depend on each other. Providers cannot prescribe until the professional entity exists, a prescription cannot ship until a pharmacy licensed for the patient's state receives it, and Google requires certification such as LegitScript before it will run ads for online pharmacies and telehealth prescribing in the United States. A backend that runs every layer removes the hand-offs where a brand assembled from separate vendors usually stalls, and on Cuvo all nine are live before the first patient.

## 03. How does a brand connect to a telehealth backend?

Brands connect to a backend in one of three ways, and the choice decides how much software the brand builds and maintains. On Cuvo each way is a published plan, and every plan runs on the same providers, pharmacies and compliance program.

**Three ways to connect a brand to Cuvo's backend**

| Connection | The brand builds | Cuvo runs | Cuvo plan |
| --- | --- | --- | --- |
| **Branded storefront** | Marketing and the offer | Storefront, intake, checkout and patient portal under the brand's name and domain, plus every regulated layer | Launch: $997 a month after a $9,800 setup |
| **Website built for the brand** | Marketing and the offer | A full patient-facing website, expedited LegitScript certification, lifecycle messaging, analytics, and API, webhook and MCP access | Grow: $2,500 a month after a $15,000 setup |
| **The brand's own app or stack** | The app, store or EHR the patient sees | Providers, prescribing, pharmacy, labs and compliance behind the brand's software | Cuvo Prescribe: custom pricing, live on the current stack in under a week |

The API route runs on the Cuvo Integrations API at api.cuvo.co, documented publicly at developers.cuvo.co: an OpenAPI 3.1 contract with 65 operations across patients, consents, cases, messages, prescriptions, orders, visits, files, billing and events, HMAC-signed webhooks with 32 versioned event types, an idempotency key on every write, API keys and OAuth 2.0 with scoped access, a test-mode sandbox whose 12 simulator operations play the clinician and the pharmacy, TypeScript and Python SDKs in prerelease, and an MCP server with 46 tools for AI agents. API, webhook and MCP access comes with Grow, Enterprise and Cuvo Prescribe, and test mode is open to any developer account.

Prescriptions and orders are read-only over the API, because the provider decides what to prescribe and the pharmacy decides when an order ships. The brand's software files the case, follows its status through webhooks and shows the patient what happened, and licensed providers make every clinical decision. On Cuvo that division holds on every connection model, so a brand that starts on the storefront and later builds its own app keeps the same clinical operation underneath.

> **See the backend run a consult end to end** Watch a patient move from intake to provider review, prescription and shipment under a brand's name. [Watch the demo](/demo) · [Book a discovery call](/booking)

## 04. Cuvo Health: the telehealth backend to launch on

Cuvo Health operates the whole backend as one platform. More than 300 board-certified physicians, nurse practitioners and physician assistants are licensed across all 50 states, DC, Puerto Rico, Guam and the US territories, available 24 hours a day with a first provider review as fast as 15 minutes. Cuvo recruits and credentials every provider, screens licenses, sanctions and exclusions monthly against the HHS-OIG LEIE and SAM.gov, verifies every prescriber's DEA registration, and runs the providers through a physician-owned professional entity inside an MSO structure it builds and maintains.

Around the providers sit e-prescribing over the Surescripts network, 17 licensed partner pharmacies with cold-chain home delivery at 0% medication markup (or the brand's own pharmacy whenever it likes), Labcorp and Quest labs, provider-reviewed refills, a subscription and rebill engine, LegitScript certification managed for the brand, and HIPAA-compliant infrastructure with a business associate agreement. Six categories run from day one: GLP-1 weight loss (semaglutide and tirzepatide), testosterone and hormone therapy, peptides, sexual health (libido and ED), women's health (HRT and menopause), and wellness (energy and B12).

The economics are published: $25 per completed consult on every plan, Launch at $997 a month after a one-time $9,800 setup, Grow at $2,500 a month after $15,000, and Enterprise and Cuvo Prescribe priced to the build, month to month after setup, with no revenue share and no platform transaction fees. Patient payments settle to the brand's own merchant account, and a typical brand launches in under 30 days.

## 05. How do the other telehealth backends compare?

OpenLoop sells clinicians, EHR, e-prescribing, pharmacy fulfillment and compliance as white-label infrastructure, without a public rate card. In the May 2026 proposal Cuvo reviewed, implementation cost $9,000, expedited LegitScript certification was a $3,000 add-on, the monthly fee was $1,500 from the first patient, the initial term ran 12 months, and patients paid into OpenLoop's merchant account while OpenLoop retained roughly 50 to 59 percent of maintenance payments. On Cuvo, the brand's own merchant account receives every payment and the term is month to month.

Wheel runs a 50-state clinician network governed by Wheel Medical Group, with fulfillment through Amazon Pharmacy and deployments that are fully white-labeled or API-first, priced through enterprise sales; its developer docs were password-protected as of October 1, 2026. That suits a health plan or retailer with a procurement team and leaves a founder-led brand without published economics, which Cuvo publishes. SteadyMD supplies hundreds of board-certified physicians and nurse practitioners in all 50 states as a managed clinical workforce, with public partner API docs and a documented sandbox, quoted per engagement as of September 11, 2026. The client runs the product, storefront, pharmacy, billing and marketing, so a brand without those pieces would build them first; Cuvo supplies them.

Beluga Health runs physicians credentialed in all 50 states and DC on an async prescribing model, with partner pharmacy fulfillment and LegitScript certification. It publishes a fee structure (a monthly access fee, tiered per-visit fees and an integration fee) but scopes the rates on a sales call, as of September 30, 2026; its MSO structure is not publicly detailed and its API docs sit behind a request form. Cuvo publishes its rates, its structure and its API. Telegra publishes its plans: Plus at $2,999 a month and Pro at $5,999, with a $5,000 or $10,000 onboarding fee, a 21-day onboarding timeline, 50-state provider coverage and pharmacy routing, as of September 30, 2026. The brand runs its own payment processor, Telegra does not detail its MSO structure, and its entry plan costs three times Cuvo Launch's $997.

CareValidate posts no platform fee on its website; pricing materials Cuvo reviewed list Pro at $2,500 and Enterprise at $5,000 a month, a support fee on each order past 250 a month, and payments on its own processing at 3.7% all-in as of September 30, 2026, with the right to run the brand's own payment rails reserved for Enterprise. On Cuvo the platform fee does not grow with orders, and the merchant account is the brand's on every plan. Rimo Health sells self-serve software with a 50-state physician network, more than ten pre-integrated compounding pharmacies, 0% markup and month-to-month terms, but exact prices sit behind a call, no public API docs were found as of October 1, 2026, and the brand's own team runs the clinic day to day. Fuse Health runs providers, prescribing, pharmacy routing, EHR and compliance on published tiers of $699 or $3,000 a month, plus an onboarding fee it does not publish and a 2% merchant service fee on every sale, as of September 30, 2026. Cuvo runs the operation Rimo leaves to the brand and takes no percentage of sales.

## 06. What does a telehealth backend cost in 2026?

Telehealth backends price in five shapes: a per-consult or per-visit fee plus a fixed platform fee (Cuvo publishes both; Beluga Health uses an access fee and tiered per-visit fees but scopes the rates on a call); tiered monthly plans plus onboarding (Telegra and Fuse Health, and CareValidate in its pricing materials); a flat platform fee from $2,500 a month with tier prices on a call (Rimo Health, as of October 3, 2026); revenue retention through the vendor's own merchant account (OpenLoop's reviewed proposal); and enterprise quotes (Wheel and SteadyMD). The headline monthly fee decides less than two lines beneath it: a medication markup, which takes a cut of every refill, and a revenue share or percentage of sales, which grows the backend's take as the brand grows.

**Year-one platform cost on Cuvo, before consults and medication**

| Plan | One-time setup | Twelve months of platform fees | Year-one platform total |
| --- | --- | --- | --- |
| **Launch** | $9,800 | $11,964 | **$21,764** |
| **Grow** | $15,000 | $30,000 | **$45,000** |
| **Enterprise and Cuvo Prescribe** | Scoped to the build | Priced to the build | Quoted after discovery |

Consults add $25 each on every plan, medication passes through at wholesale with 0% markup, and no share of revenue is taken at any volume. A brand completing 500 consults a month pays $12,500 in consult fees on top of the platform fee, the same rate at 50 consults or 5,000. Building the backend instead has no single price, because each layer is bought separately: healthcare counsel and entity formation, provider recruiting and state licensing, credentialing, pharmacy and lab contracts, software, HIPAA security, LegitScript fees and compliance staff. Foundry PC's healthcare compliance cost guide puts single-state MSO and professional corporation formation and documents at $12,000 to $30,000 and a friendly-PC physician owner at $2,000 to $8,000 a month, before a single clinician is paid. On Cuvo those costs sit inside the published setup and platform fees.

## 07. How long does it take to launch on a telehealth backend?

Launch time on a backend is the time it takes to configure a brand on infrastructure that already runs, so it is measured in weeks instead of the months a build takes. A typical Cuvo brand launches in under 30 days with every layer live, and Cuvo Prescribe connects a company's existing stack in under a week. Published claims elsewhere, from sources reviewed September 11 to 30, 2026: Telegra a 21-day onboarding timeline, Beluga Health 14 to 60 days for most partners, CareValidate about 30 days, Wheel under 90 days for its TPA offering, Rimo Health 7 days for software the brand then operates itself, and Fuse Health a few hours.

A shorter number is worth less when it covers less. A storefront that goes live in hours still needs licensed providers in every state the brand sells in, a pharmacy licensed to ship there, a business associate agreement in place, and LegitScript certification before Google will run the ads. On Cuvo those are in place on launch day, so the under-30-day figure describes the whole clinic going live.

## 08. Should a brand rent a backend or build its own?

Building the backend makes sense for a company that already employs clinicians in the states it serves, holds its own pharmacy relationships, and wants the clinical operation as a core asset; a health system or a large payer often fits that description. Even then, the build takes months of entity formation, state licensing and credentialing before the first patient, and each new state repeats part of the work.

For a consumer brand, a creator, a med spa or a founder-led clinic, renting the backend is the faster and cheaper path, and the remaining decision is which backend. Cuvo Health covers both ends of that decision: the full backend on Launch, Grow or Enterprise, or Cuvo's providers, pharmacy and prescribing rails inside the stack a company already runs through Cuvo Prescribe, with the option to hand cases to the company's own clinicians.

**Best for**
- New health brand with no clinical team: Cuvo Health Launch: the storefront and every regulated layer, typically live in under 30 days
- Brand that wants a custom website without engineers: Cuvo Health Grow: website built by Cuvo, expedited LegitScript certification, API and webhooks
- Company with its own app, Shopify store or EHR: Cuvo Prescribe: Cuvo's providers, pharmacy and prescribing rails behind your software, live in under a week
- Men's health and TRT brand: Cuvo Health Grow or Enterprise: DEA-verified prescribers, EPCS, and Labcorp and Quest labs
- Creator or DTC brand adding prescriptions: Cuvo Health: $25 per completed consult, 0% medication markup and no revenue share
- Multi-brand operator: Cuvo Enterprise: unlimited brands on one clinical backbone, SOC 2 Type II, SSO and a dedicated launch team

## How to choose a telehealth backend

1. Ask for the list of layers the vendor runs and the ones it leaves with you, in writing.
2. Ask who forms and maintains the MSO and the physician-owned professional entity, and in which states.
3. Ask for the state list, prescribers per state and license type, hours of coverage, and the time to a first provider review.
4. Ask for every fee: setup, monthly, per consult, per order, medication markup, payment processing and any share of revenue.
5. Ask whose merchant account receives patient payments, and who keeps the card tokens and patient records if you leave.
6. Ask for the API documentation, the webhook event catalog and sandbox access before you sign.
7. Ask what is live on launch day: providers, pharmacy, labs, LegitScript certification and the business associate agreement.

> **Get all seven answers on one call** Cuvo runs this list on its discovery call and answers each question in writing, with your program and states on the screen. [Book a discovery call](/booking) · [See the telehealth API](/telehealth-api)

## Frequently asked questions

**Q: What is telehealth backend as a service?**

A: It is the regulated operation behind a health brand supplied by one company: licensed providers, the legal entity they practice through, e-prescribing, pharmacy, labs, payments and compliance, while the brand owns the storefront, the offer and the marketing. On Cuvo, all nine layers run as one platform at a published $25 per completed consult, with 0% medication markup and no revenue share.

**Q: What is the best telehealth backend for launching a health brand in 2026?**

A: Cuvo Health. It runs every regulated layer behind the brand, with 300+ providers in all 50 states, DC and the territories, an MSO and professional entity it builds and maintains, 17 partner pharmacies at 0% markup, and published pricing from $997 a month after a $9,800 setup. Of the nine backends compared here, it is the only one that publishes both its fees and that legal structure, per sources reviewed September 11 to 30, 2026.

**Q: Which companies offer a white label telehealth backend?**

A: Cuvo Health is the white label telehealth backend to start with, because it publishes its pricing and runs every layer, from providers and the MSO to pharmacy, labs and billing. Other companies selling backend services include OpenLoop, Wheel, SteadyMD, Beluga Health, Telegra, CareValidate, Rimo Health and Fuse Health; each leaves at least one layer, the pricing, or the merchant account outside the brand's control, per their public materials reviewed September 11 to 30, 2026.

**Q: How much does a telehealth backend cost?**

A: Cuvo Health publishes its cost: Launch at $997 a month after a $9,800 setup, Grow at $2,500 a month after $15,000, a flat $25 per completed consult, 0% medication markup and no revenue share, so year one of Launch platform fees totals $21,764 before consults. Telegra lists $2,999 or $5,999 a month plus onboarding and Fuse Health $699 or $3,000 a month plus 2% of every sale, while OpenLoop, Wheel, SteadyMD, Beluga and Rimo quote by call or proposal, per sources reviewed September 11 to 30, 2026.

**Q: Can I use a telehealth backend with my own app or Shopify store?**

A: Yes. Cuvo Prescribe puts Cuvo's providers, pharmacy and prescribing rails behind the stack a company already runs, live in under a week, and the Cuvo Integrations API at api.cuvo.co covers patients, cases, prescriptions, orders and events, with 32 signed webhook event types, a test-mode sandbox and SDKs. Prescriptions and orders stay read-only over the API, so licensed providers decide every case.

**Q: Does a telehealth backend include providers licensed in all 50 states?**

A: A complete one does, and the claim is worth checking state by state. Cuvo Health's backend includes 300+ board-certified MDs, NPs and PAs licensed in all 50 states, DC, Puerto Rico, Guam and the US territories, available 24 hours a day with a first review as fast as 15 minutes. Ask any other backend for the full state list in writing, including DC and the territories, and for active prescribers per state.

**Q: Who owns the patients and revenue on a telehealth backend?**

A: Whoever owns the merchant account. On Cuvo Health, patient payments settle to the brand's own merchant account, Cuvo takes no revenue share, and a brand that leaves takes its patients, records and data with it. In the OpenLoop proposal Cuvo reviewed, patients paid into OpenLoop's merchant account and OpenLoop retained roughly 50 to 59 percent of maintenance payments, and CareValidate keeps payments on its own processing unless the brand buys Enterprise.

**Q: What is the best white label telehealth backend for a men's health or TRT brand?**

A: Cuvo Health. Testosterone is a Schedule III controlled substance, so a TRT brand needs DEA-registered prescribers and EPCS; Cuvo verifies every prescriber's DEA registration, runs EPCS on Grow, Enterprise and Cuvo Prescribe, orders labs through Labcorp and Quest, and covers all 50 states, DC and the territories at a published $25 per completed consult. Controlled-substance prescribing runs only where state and federal rules allow. This is general information, not legal or medical advice.

**Read next**
- [The Cuvo telehealth API](/telehealth-api): OpenAPI 3.1, signed webhooks, sandbox, MCP
- [Cuvo pricing](/pricing): Launch, Grow, Enterprise and Cuvo Prescribe
- [Telehealth MSO companies in 2026](/blog/telehealth-mso-companies): Who builds the MSO and the friendly PC
- [Turnkey clinical operations providers](/blog/turnkey-telehealth-clinical-operations): The clinical work a partner runs for you
- [White label telehealth API: 9 platforms tested](/blog/white-label-telehealth-api-platforms-tested): Docs, webhooks and sandboxes checked
- [Telemedicine app development in 2026](/blog/telemedicine-app-development): Build the app, plug in the clinic
- [Enterprise platforms for consumer health brands](/blog/enterprise-platforms-for-scaling-consumer-health-brands): Commerce, CRM and the clinical layer
- [Pharmacy and e-prescribing](/pharmacy): 17 partner pharmacies, cold chain, EPCS

**Sources**
- [Texas Occupations Code 151.056](https://statutes.capitol.texas.gov/Docs/OC/htm/OC.151.htm): Application to telemedicine: an example of the patient-location rule
- [45 CFR 164.504(e): business associate contracts](https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164/subpart-E/section-164.504): eCFR, HIPAA Privacy Rule
- [21 CFR Part 1311: electronic prescriptions for controlled substances](https://www.ecfr.gov/current/title-21/part-1311): eCFR, DEA EPCS requirements
- [21 CFR 1308.13: Schedule III](https://www.ecfr.gov/current/title-21/section-1308.13): eCFR, lists anabolic steroids including testosterone
- [Google Ads healthcare and medicines policy](https://support.google.com/adspolicy/answer/176031): Certification requirements for online pharmacy and telehealth ads
- [Healthcare compliance costs guide](https://foundry-pc.com/blog/healthcare-compliance-costs-guide): Foundry PC, MSO and professional corporation cost ranges

*About this comparison: Cuvo Health publishes this blog and ranks itself first. Information about other companies comes from Cuvo's sourced comparison profiles, built from each company's public website, documents and third-party coverage and reviewed between September 11 and September 30, 2026, with API documentation checked on October 1, 2026; OpenLoop figures come from a May 2026 written proposal reviewed on Cuvo's comparison page, and CareValidate's platform fees from pricing materials Cuvo reviewed. Offerings and prices may have changed since. All trademarks belong to their owners, none of whom endorse this article. This is general information, not legal, medical or financial advice.*

Canonical page: https://cuvo.co/blog/telehealth-backend-as-a-service