Telehealth backend as a service is the model where a brand keeps its name, storefront, marketing and customer relationship, and leases everything that makes treatment legal and operational: licensed providers in every state, the professional-entity structure, medical intake, the clinical record, e-prescribing, pharmacy fulfillment, labs, the patient portal, subscription billing rails and the compliance program. The brand ships a front door. The backend runs the medicine.
For a founder, the practical answer is this: in 2026 a health brand should lease the backend unless it already employs clinicians, holds its own pharmacy relationships and has a compliance team on payroll. The reasons are time and risk. Building the stack means forming professional entities in corporate-practice states, credentialing clinicians, signing business associate agreements with every vendor that touches protected health information, certifying for electronic prescribing of controlled substances and earning LegitScript certification before a single ad can run. A backend vendor has already done that work and amortizes it across many brands. MyOrbitHealth is one such backend: a hosted platform and a REST API, 2,400+ board-certified providers in all 50 states, OrbitRx e-prescribing into a LegitScript-certified pharmacy network, and a fee model with no revenue share and 0% medication markup. This guide explains the layers, the three ways to connect, who owns what, and how to evaluate any vendor, including us. It is general information, not legal advice.
Key takeaways
- A telehealth backend as a service supplies the ten operational layers a health brand cannot legally or practically run itself on day one: provider network, licensing and credentialing, intake, clinical record, e-prescribing, pharmacy, labs, patient portal and app, payments and subscriptions, and compliance under an MSO structure.
- Brands connect to a backend one of three ways: a hosted, white-labeled storefront and portal; a REST API with signed webhooks into their own product; or an embeddable SDK that drops the clinical flow into a page they already own.
- The ownership questions that matter at exit are patient records, customer data, the merchant account and the pharmacy relationship; a brand should be merchant of record and should be able to export its data at any time.
- Building the stack in-house is a multi-quarter project that front-loads legal, credentialing and certification cost before revenue; leasing converts that to a flat platform fee plus variable clinical and pharmacy cost.
- Evaluate a backend on what it publishes: the fee model, the credentialing standard, the pharmacy terms, the API contract and the exit terms, not on the demo.
Who this is for
- Founders of DTC health brands in GLP-1, TRT, hormone, hair, skin, sexual health or peptides deciding whether to build or lease the clinical stack.
- Product and engineering leaders at consumer apps, fitness platforms or supplement brands who need prescribing inside a product they already run.
- Operators at med spas and clinics adding a virtual program without replacing their EHR.
- Not for: health systems or payers procuring enterprise staffing and revenue-cycle services, which is a different market.
What is a telehealth backend as a service?
A telehealth backend is the set of regulated and operational services that sit between a patient clicking "start" and a medication arriving at their door. Backend as a service means a vendor runs those services under its own licenses, contracts and certifications, and exposes them to a brand through a hosted interface, an API, or both.
Three rules shape the whole category. First, the clinician must hold a license in the state where the patient is physically located at the time of care. Second, in many states, non-physicians cannot own the entity that employs physicians, which is why backends operate through a management services organization (MSO) and an affiliated professional corporation; our telehealth compliance and MSO model guide covers the structure. Third, anyone who creates, receives, maintains or transmits protected health information on behalf of a covered entity needs a business associate agreement under 45 CFR 164.504(e). A backend vendor signs that BAA with the brand as a matter of course.
What layers does a brand lease instead of build?
Here is what a backend runs, layer by layer, and what each one would cost a brand to replicate.
| Layer | What it has to do | Why brands lease it |
|---|---|---|
| Provider network | Licensed MD/DO/NP/PA capacity in every launch state, with specialty coverage and fast response | Fifty-state coverage by hiring takes quarters; a network has it on day one |
| Licensing and credentialing | Primary-source verification of licenses, education, board status and sanctions; monthly OIG/SAM exclusion screening; re-credentialing | Credentialing is a standing program, not a one-time task; a missed exclusion is a compliance event |
| MSO and professional entity | Friendly-PC structure in corporate-practice states, management agreement, fee arrangements that survive scrutiny | Entity formation and counsel in multiple states is slow and expensive before revenue exists |
| Medical intake | Adaptive questionnaire, severity scoring, red-flag escalation, identity verification, state-specific consent | Clinical logic needs clinician sign-off and continuous maintenance as protocols change |
| Clinical record and console | Encounter documentation, prescriptions, provider roles, audit trail, reporting | A HIPAA-grade system of record with role-based access and audit logs is a product in itself |
| E-prescribing | Surescripts routing, EPCS with two-factor identity proofing for controlled substances such as testosterone | Surescripts connectivity and EPCS certification are gated; brands cannot obtain them directly |
| Pharmacy | 503A compounding and retail dispensing, LegitScript-certified partners, cold chain to 50 states | Pharmacy contracting, licensing checks and shipping logistics are a dedicated operations function |
| Labs | Provider-ordered tests via walk-in, at-home kit or mobile phlebotomy, with results into the chart | Lab orders must be signed by a licensed provider and results need clinical review |
| Patient portal and app | Branded portal, messaging, refills, native iOS/Android app | A white-label app and portal are a substantial product build with ongoing maintenance if built from scratch |
| Payments and subscriptions | Checkout, recurring billing, refunds tied to clinical outcomes (no Rx, no charge) | Subscription logic has to be aware of clinical state, which generic billing tools are not |
| Compliance program | HIPAA policies, BAAs, a SOC 2 program, breach response, LegitScript certification, advertising review | Certifications gate advertising and partnerships; the program needs ongoing ownership |
On MyOrbitHealth these layers map to named products: the Provider Network (2,400+ providers, 38+ specialties, 50 states, average response under six minutes during business hours), Orbit Intake, OrbitOS (the clinical console with full HIPAA audit trail and operational reporting), OrbitRx (EPCS-ready e-prescribing to a LegitScript-certified pharmacy network, 0% medication markup), Orbit Labs (Quest or Labcorp walk-in, Tasso at-home kit, or mobile phlebotomy), and the branded storefront, portal and native app included in the platform. Managed LegitScript certification is part of onboarding: MyOrbitHealth prepares, files and manages the application through approval, typically days once filed, with LegitScript making the decision.
How does a brand connect to a telehealth backend?
Every backend worth considering offers more than one integration path, because brands arrive with different amounts of product. The three patterns below are the ones that matter. Pick by how much front end you already own and how much you want to own.
| Path | The brand builds | The backend runs | Fits when |
|---|---|---|---|
| Hosted (white-label storefront, portal, app) | Brand assets, marketing site, ad accounts, content | Storefront, intake, provider review, Rx, pharmacy, labs, portal, app, billing | You have a brand and an audience but no product team; you want to be live in days |
| API and webhooks | Your own storefront, app or CRM; the UX for intake handoff and status | Patient, appointment and prescription lifecycle behind documented endpoints; signed webhook events back to you | You have engineers and an existing product; you want the clinical flow inside your experience |
| SDK embed | A page or screen that mounts the clinical flow component | Everything the component does: intake, scheduling, status, messaging, under the vendor's BAA | You want a native-feeling embed without building the clinical UI yourself |
Hosted is the fastest. The brand points a domain, supplies its logo, colors and copy, picks programs and states, and the backend serves the storefront, checkout, intake, portal and app under that brand. MyOrbitHealth brands typically go live in days on this path; 50+ digital clinics run on it today. Launch is gated by LegitScript certification, which a managed application typically clears in days once filed, with LegitScript making the decision.
API is for brands with their own product. MyOrbitHealth's product API lives at https://api.myorbithealth.com/v1 with bearer-token auth, environment-scoped test and live keys, path versioning, X-RateLimit-* headers at 600 requests per minute per key with burst to 1,200, and documented endpoints for patients, appointments, prescriptions and webhook registration. Signed webhooks deliver events such as appointment.completed and prescription.dispensed. A sandbox is provisioned within a day after a short partner review. The telehealth API overview and /api-docs carry the contract.
An illustrative example of creating a patient record from your own storefront (field names are examples; use the documented schema):
curl -X POST https://api.myorbithealth.com/v1/patients \
-H "Authorization: Bearer $MYORBIT_TEST_KEY" \
-H "Content-Type: application/json" \
-d '{"email":"patient@example.com","state":"TX","program":"glp1-weight-loss"}'
Errors come back in one shape, { "error": { "code", "message", "details" } }, across every endpoint.
SDK is the middle path. MyOrbitHealth ships a React SDK that mounts the clinical flow inside a page the brand controls; the brand owns the surrounding experience and the component owns the regulated part. Our developers page covers the product API and the separate, free AI-agent layer (an MCP server with 21 tools, 19 read and 2 consent-gated action tools), which is not the production clinical API.
Who owns what on a telehealth backend?
Ownership is where backend vendors differ most, and the demo never shows it. Get each line in writing.
| Asset | Should belong to | What to check in the contract |
|---|---|---|
| Brand, domain, marketing assets | The brand | No vendor license over your marks; your domain, your ad accounts |
| Patient relationship and customer list | The brand | Export at any time in a usable format; no restriction on contacting your own customers |
| Clinical records | The professional entity, with the brand holding rights to the operational data it needs | Records portability on exit; audit trail preserved; the vendor does not hold your patients hostage |
| Merchant of record | The brand | Payments settle to your merchant account; the vendor does not take revenue share from the top line |
| Pharmacy relationship and medication pricing | Passed through transparently | Medication markup stated in writing; 0% is the standard to hold vendors to |
| Provider relationships | The backend's professional entity | Bring-your-own-providers supported if you later employ clinicians; same console, same audit trail |
| Compliance artifacts (BAA, SOC 2 report, LegitScript) | Shared | BAA in every contract; SOC 2 Type II report available on request; LegitScript certification held for your brand |
| Exit terms | The brand | No termination fee; month-to-month after onboarding; data export on exit |
MyOrbitHealth's model on each line: the brand owns its patients, records and data with export at any time, is merchant of record, pays 0% medication markup, pays no revenue share, has no exit or termination fee, and runs month-to-month after onboarding. The platform fee is flat and scoped at onboarding to verticals, states and volume; there is no published price list, and the startup cost calculator gives directional ranges.
Each step, who does it
Here is the launch path on a leased backend, and who does each step.
| Step | MyOrbitHealth runs | You run |
|---|---|---|
| Entity and compliance structure | MSO and affiliated professional-entity structure, BAA, HIPAA policies, SOC 2 Type II | Your operating company, business insurance, state registrations for your own entity |
| Program and protocol selection | Clinical protocols per vertical, state eligibility rules, intake logic | Choosing which programs and states to launch; pricing your offer |
| Brand setup | White-label storefront, portal and app configuration; custom domain | Logo, colors, copy, product photography, terms and privacy pages |
| LegitScript certification | Preparing, filing and managing the application through approval | Supplying business documents and signing where required; keeping marketing claims compliant |
| Provider coverage | 2,400+ credentialed providers across 50 states, load balancing, collaborating physicians for NPs/PAs where required | Nothing, unless you bring your own clinicians, who are onboarded into the same console |
| Intake and identity | Orbit Intake with severity scoring and red-flag escalation; identity verification | Deciding where intake sits in your funnel; driving traffic to it |
| Provider review and prescribing | Encounter, charting, OrbitRx e-prescribing via Surescripts, EPCS where needed | Nothing clinical; you do not direct treatment decisions |
| Pharmacy fulfillment | Routing to a LegitScript-certified 503A or retail pharmacy, cold-chain shipping to all 50 states | Customer-facing shipping expectations and support macros |
| Labs | Provider-ordered labs by walk-in, at-home kit or mobile phlebotomy; results into the chart | Choosing whether labs are part of your program; patient communication |
| Payments and subscriptions | Checkout and recurring billing rails inside the storefront; refill cadence tied to clinical state | Merchant account, pricing, refund policy, chargeback handling |
| Marketing and growth | Nothing; the platform does not run your acquisition | Ads, content, creators, email, retention |
| Reporting and operations | OrbitOS operational and revenue/retention reporting, uptime and queue health, audit trail | Reading the numbers and deciding what to change |
Should you build or lease a telehealth backend?
The honest comparison is between leasing a backend and running a multi-vendor build: an EHR with e-prescribing, hired or staffed clinicians, a credentialing vendor, a pharmacy, a lab partner, a billing stack, a compliance consultant and MSO counsel. Each is a contract, a BAA and an integration.
| Dimension | Build it yourself | Lease a backend |
|---|---|---|
| Time to first patient | Months to quarters: entities, credentialing, EPCS, pharmacy contracts, LegitScript, product build | Days on a hosted path; weeks on an API build, driven by your own front end |
| Upfront cost shape | Legal, credentialing, certification and engineering spend before revenue | Onboarding fee plus flat platform fee; clinical and pharmacy cost variable with volume |
| Fifty-state coverage | Hire or contract clinicians state by state; IMLC helps eligible physicians but does not remove per-state licenses | Aggregate coverage from a credentialed network on day one |
| Compliance ownership | Yours end to end: policies, audits, BAAs with every vendor, breach response | Shared; the backend carries the clinical, pharmacy and infrastructure controls, you carry your own operating company |
| Product control | Total; you own every screen | High on API and SDK paths; configuration-level on hosted |
| Vendor count | Six to ten | One, plus your own payment processor and marketing stack |
| Scaling a new vertical or state | New protocols, new licenses, possibly new pharmacy | Enable it in configuration if the network and pharmacy already cover it |
| Exit risk | None from a vendor; all operational risk is yours | Depends on contract: insist on data export, no termination fee, merchant of record |
| Fits | Existing practices with clinicians and an EHR; companies at very high, predictable volume | Launching brands, product teams adding care, med spas and clinics adding virtual programs |
The crossover point is later than most founders think. Owning clinicians makes sense once volume in specific states is high and predictable; our provider network vs hiring guide walks the break-even. Even then, the usual outcome is a hybrid, with the brand's own clinicians inside the backend's console alongside network providers, which is why bring-your-own-providers support matters.
What does a telehealth backend cost in 2026?
Backends price three ways, and the shape matters more than any single number. Our white-label telehealth platform cost guide goes deeper; the summary:
Setup plus monthly platform fee plus per-consult. Published and predictable. Cuvo Health is the clearest example: as of October 2026, per their site, Launch is $9,800 setup plus $997 per month, Grow is $15,000 setup plus $2,500 per month, all plans carry $25 per completed consult, 0% medication markup, no revenue share and month-to-month terms, with API and webhooks on Grow and above and a branded mobile app as a $4,999 per year add-on. See MyOrbitHealth vs Cuvo.
Monthly tier plus a percentage of sales. Fuse Health publishes Growth at $699 per month and Partner at $3,000 per month plus a 2% merchant fee on sales, onboarding fee not published, API on the top plan only, as of October 2026 per their site. Telegra publishes Plus at $3,000 per month plus $5,000 onboarding and Pro at $6,000 per month plus $10,000 onboarding, consult fees billed separately. CareValidate does not publish platform fees and charges 3.7% payment processing.
Quoted, enterprise. OpenLoop, Wheel and Beluga Health do not publish pricing as of October 2026; Wheel prices deal by deal with a go-live target under 90 days. These fit health plans, health systems and funded digital health companies more than a launching brand.
MyOrbitHealth publishes its model rather than a number: a flat platform fee scoped at onboarding to verticals, states and volume, 0% medication markup with pharmacy cost passed through, no revenue share, the brand as merchant of record, no exit fee, month-to-month after onboarding. Lab pricing is quoted per program. The brand sees the total before signing.
How should you evaluate a telehealth backend vendor?
Use the vendor's public material and the contract, in that order. Ten questions; a missing answer is a disqualifier.
- What is the fee model, in writing? Setup, monthly, per consult or per patient month, medication markup, revenue share.
- Who is merchant of record? If the vendor's account takes the payment and remits to you, your exit is harder.
- What is the credentialing standard, and how often is exclusion screening run? NCQA-standard primary-source verification with monthly OIG and SAM screening is the bar. Ask for the written policy.
- How many providers, in which states and specialties, and what is the measured response time? A number and a method.
- Which pharmacies, at what markup, and who holds the relationship? 0% markup, LegitScript-certified partners, and the ability to see the pharmacy cost.
- Is the API documented publicly, versioned, with a sandbox? Auth, rate limits, error shape, webhook signing and events should be readable before you sign.
- What certifications does the vendor hold, and will you see the reports? HIPAA with a BAA in every contract, SOC 2 Type II, EPCS with identity proofing, LegitScript for the pharmacy network.
- Can you bring your own clinicians later? If not, the vendor caps your clinical strategy.
- What happens on exit? Data export, patient continuity, termination fee, notice period.
- Who runs LegitScript certification for your brand, and who holds it? Managed filing is a major time saver; confirm the certification is for your brand.
Our guide to choosing a white-label telehealth partner expands each question into a due-diligence script.
Which backends serve which brands?
MyOrbitHealth fits brands that want both a hosted path and a documented API, a large multi-specialty network and a fee model without revenue share or medication markup. Cuvo Health fits founders who want fully published tier pricing and six verticals on every plan. Fuse Health fits peptide-first brands comfortable with a percentage of sales. Telegra fits brands that prefer a higher fixed fee with consults billed separately. OpenLoop, Wheel and Beluga Health fit enterprise buyers who expect a proposal rather than a rate card. Each has a compare page: vs OpenLoop, vs Wheel, vs Beluga Health, vs Fuse Health, vs Telegra. If your front end is a Shopify store, our companion post on adding prescription treatments to Shopify covers the storefront specifics, and the best telehealth provider networks ranking compares the clinician layer on its own.
Frequently asked questions
What is telehealth backend as a service?
Telehealth backend as a service is a model where a vendor runs the regulated layers of a virtual care business, including licensed providers, the professional-entity structure, intake, the clinical record, e-prescribing, pharmacy, labs, the patient portal and compliance, and exposes them to a brand through a hosted white-label platform, an API, or an SDK. The brand keeps its name, customers and marketing. The backend carries the licenses, certifications and clinical operations.
Can a telehealth backend work with my own app or website?
Yes, if the vendor publishes an API. MyOrbitHealth exposes a REST API at api.myorbithealth.com/v1 with bearer-token auth, documented endpoints for patients, appointments, prescriptions and webhook registration, signed webhooks and a React SDK, with a sandbox provisioned within a day. Brands without a product team use the hosted storefront, portal and native app instead.
Does a telehealth backend include providers licensed in all 50 states?
The good ones do, and you should verify it rather than accept the claim. MyOrbitHealth's Provider Network has 2,400+ board-certified MD, DO, NP and PA providers across 38+ specialties in all 50 states, credentialed to NCQA-standard primary-source verification with monthly OIG and SAM screening. Ask any vendor for provider counts by state and specialty for your launch map.
Who owns the patients and revenue on a telehealth backend?
It depends on the contract, so read it. On MyOrbitHealth the brand owns its patients, records and data with export at any time, is merchant of record so payments settle to its own account, pays no revenue share, and can leave month-to-month with no termination fee. Vendors that take payment into their own merchant account and remit to the brand should be treated as a different, less favorable model.
How much does a telehealth backend cost?
Published models range from setup plus monthly plus per-consult pricing, such as Cuvo Health at $9,800 setup plus $997 per month and $25 per completed consult on its Launch tier as of October 2026 per their site, to monthly tiers with a percentage of sales, to enterprise quotes. MyOrbitHealth charges a flat platform fee scoped at onboarding with 0% medication markup and no revenue share, and does not publish a price list; its startup cost calculator gives directional ranges.
Should a brand build its own telehealth backend?
Rarely at launch. Building means forming professional entities, credentialing clinicians, obtaining Surescripts and EPCS connectivity, contracting pharmacies and labs, signing BAAs with every vendor and earning LegitScript certification before advertising, all before revenue. Leasing makes sense until a brand has high, predictable volume in specific states, and even then most brands keep the backend and bring their own clinicians into it.
Sources
- 45 CFR 164.504(e), business associate contracts (eCFR)
- 21 CFR Part 1311, requirements for electronic orders and prescriptions, including EPCS (eCFR)
- NCQA Credentialing Standards and Guidelines
- HHS Office of Inspector General, List of Excluded Individuals/Entities
- Cuvo Health pricing page
- MyOrbitHealth developers page
- MyOrbitHealth telehealth API
Lease the backend, keep the brand
MyOrbitHealth runs the medical, regulatory and pharmacy layer for 50+ digital clinics: 2,400+ providers in all 50 states, OrbitRx e-prescribing into a LegitScript-certified pharmacy network at 0% markup, Orbit Labs, a branded storefront, portal and native app, and a documented REST API with signed webhooks and a React SDK. No revenue share, no exit fee, and you are merchant of record. Book a demo to map your brand onto the stack, or read the telehealth API overview first.
