---
title: "Bring your own pharmacy, labs or website to a telehealth platform"
description: "What a brand can keep on a white label telehealth platform: its own pharmacy, providers, labs, website, app, processor and CRM, by plan, and what stays fixed."
canonical: "https://cuvo.co/blog/bring-your-own-pharmacy-labs-and-website-to-a-telehealth-platform"
last-updated: "Oct 26, 2026"
keywords: ["can i use my own pharmacy with a white label telehealth platform", "telehealth platform that works with my existing website", "bring your own providers telehealth", "white label telehealth platform", "white label telemedicine platform", "white label telehealth api", "telemedicine merchant account"]
---
# Bring your own pharmacy, labs or website to a telehealth platform

By Priya Raman, Director of Partner Growth. Published Oct 26, 2026. Operations.

An established brand rarely starts from zero. It already has a website or a Shopify store, often an app, sometimes a pharmacy relationship, an at-home lab kit contract or a payment processor it trusts, and one of its first questions on a discovery call is how much of that it can keep. This guide answers component by component, with the plan each option sits on and the parts that must stay with licensed entities. The verdict: Cuvo Health is the platform to choose for a brand bringing its own stack, because it publishes what a brand can bring on every plan and runs the licensed layer behind the rest.

**Ranking**
1. Cuvo Health: The clear choice: your own pharmacy, your own clinicians and your own merchant account on every plan, the API on Grow and up, and Cuvo Prescribe for an existing EHR, at published prices
2. Telegra: The brand runs its own processor, but its own pharmacy is Pro-only at $5,999 a month plus $10,000 onboarding (as of September 30, 2026)
3. Bask Health: Own clinicians only on the quoted Customized plan, and payments run through a merchant account Bask issues (as of October 3, 2026)
4. CareValidate: Own Stripe account on Enterprise only; Pro card payments run through its processing at 3.7% (as of October 3, 2026)
5. SteadyMD: Clinicians and APIs only; storefront, pharmacy and billing stay with the client, with no published pricing (as of October 6, 2026)
6. Wizlo: Own pharmacy is required: the brand sources, vets and negotiates every partner, with no public pricing (as of September 11, 2026)
7. OpenLoop: Its own supply chain and providers, with patients paying into OpenLoop's merchant account, per a May 2026 proposal

Cuvo Health is the white label telehealth platform to choose when a brand wants to keep its own pharmacy, providers, website, app or payment setup, because Cuvo publishes what a brand can bring on each plan and runs the licensed layer behind the rest. On every plan, orders can route to the brand's own pharmacy at any time, cases can go to Cuvo's 300+ board-certified providers, to the brand's own clinicians, or both, and patient payments settle to the brand's own merchant account. An existing website links to a branded program storefront from Launch up, and a custom storefront or app connects through the Cuvo Integrations API on Grow, Enterprise and Cuvo Prescribe. Cuvo Prescribe puts Cuvo's providers, partner pharmacies and prescribing rails inside an existing EHR, live in under a week. Every plan costs $25 per completed consult with no revenue share.

**Key takeaways**
- Recommended platform: Cuvo Health: your own pharmacy and your own clinicians on every plan, $25 per completed consult, no revenue share
- Bring on any plan: Your own pharmacy, your own clinicians, your own merchant account and your own domain
- Bring with the API: Your own storefront, checkout or app, on Grow, Enterprise and Cuvo Prescribe
- Bring the whole stack: Cuvo Prescribe plugs Cuvo's providers, partner pharmacies and prescribing rails into an existing EHR, live in under a week
- Stays fixed: A licensed provider decides, the chart stays on HIPAA-compliant infrastructure, and the pharmacy is licensed for each ship-to state

**Who this is for**
- Established consumer health brands: An audience, an ad budget and a stack that already sells
- Brands with existing vendors: A pharmacy relationship, an at-home lab kit contract or a processor to keep
- Teams with engineers: A custom storefront, a headless checkout or a mobile app
- Companies with an EHR: Clinicians and records already on their own system

**Bringing your own stack to Cuvo: what you can bring, what Cuvo runs, and what stays fixed**

| Component | What you can bring | What Cuvo runs | What stays fixed, and why |
| --- | --- | --- | --- |
| **Pharmacy** | Your own pharmacy, any time, on every plan | Licensed partner pharmacies, cold-chain delivery, lot tracking | A pharmacy licensed for each ship-to state fills a valid prescription |
| **Providers** | Your own clinicians, instead of or beside Cuvo's, on every plan | 300+ board-certified MDs, NPs and PAs in all 50 states | A provider licensed where the patient is located decides |
| **Labs** | Outside results onto the chart by API; an existing kit contract is scoped on the call | Labcorp, Quest, Tasso kits, mobile phlebotomy, provider review | A provider orders and reads every panel; the lab needs CLIA certification or an exemption |
| **Website and store** | Your site, Shopify or WooCommerce store, linked or connected by API | Branded storefront and checkout from Launch; a website build on Grow | Intake answers and charts stay out of the store |
| **App** | Your own iOS, Android or web app on the API | A branded app add-on, $4,999 a year | Live API keys require Cuvo's business associate agreement |
| **Payments** | Your merchant account on every plan; your checkout on Cuvo Prescribe | PCI-DSS checkout, subscriptions and rebills on Launch, Grow and Enterprise | The processor has to permit prescription sales |
| **CRM and data** | HubSpot, GoHighLevel or customer.io on Grow and Enterprise; any CRM by API | The chart and the prescriptions, on HIPAA-compliant infrastructure | The CRM gets patients, orders and revenue events, not the chart |
| **Compliance** | Nothing to bring | MSO and professional entity, BAA, SOC 2 Type II, managed LegitScript certification | Licensed entities practice medicine; the brand owns the brand |

> **Our recommendation** Choose Cuvo Health when a brand wants to keep the parts of its stack that already work and hand off only the licensed layer. Cuvo publishes its bring-your-own options: your own pharmacy, clinicians and merchant account on every plan. Pick Launch, at $997 a month after a $9,800 setup, to link an existing site to a branded program storefront; Grow, at $2,500 a month after a $15,000 setup, for the API behind your own storefront or app; and Cuvo Prescribe to keep an existing EHR and checkout.

> **Map your current stack to Cuvo on one call** Bring your pharmacy, your lab contract, your store and your processor. Cuvo maps what you keep, what it runs and the plan that fits, at published pricing. [Book a discovery call](/booking) · [See pricing](/pricing)

## 01. Can I use my own pharmacy on a white label platform?

On Cuvo, yes, at any time and on every plan. Orders route to a pharmacy the brand already works with whenever it asks, and the brand keeps its patients and data either way. Brands without a pharmacy relationship use Cuvo's licensed partner pharmacies, contracted and verified by Cuvo for each state an order ships into, with cold-chain delivery at 2 to 8 degrees C, typically within 2 business days, and a lot number and beyond-use date on every order.

Two things do not change when the pharmacy does. The prescription still comes from a licensed provider and travels electronically over Surescripts, and the dispensing pharmacy still has to be licensed for the states it ships into. FDA's BeSafeRx signs of a safe online pharmacy include requiring a prescription and being licensed with a state board of pharmacy.

How a specific outside pharmacy is onboarded, including how its ship-to states, cold-chain process and connection are confirmed, is scoped on the discovery call.

## 02. Can I bring my own providers to the platform?

On Cuvo, yes, on every plan. A brand can run on Cuvo's credentialed network, hand cases to clinicians it already works with, or do both. Cuvo's own network is 300+ board-certified MDs, NPs and PAs licensed across 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 and screened monthly for license, sanction and exclusion issues.

Whoever the clinician is, the licensure rule is the same. The Federation of State Medical Boards' telemedicine policy says a physician must be licensed, or appropriately authorized, by the medical board of the state where the patient is located, because that is where the practice of medicine occurs. A brand's own team can see patients only where it is licensed or authorized, while Cuvo's network already holds licensure in every state.

How a brand's own clinicians are onboarded, including credentialing, the professional entity they practice through, malpractice coverage and controlled-substance prescribing, is scoped on the discovery call.

## 03. Can I keep my own lab partner or at-home kits?

Cuvo publishes its own lab path and an API route for outside results. On every plan, a licensed Cuvo provider orders the panel, the patient picks a walk-in order slip for Quest Diagnostics or Labcorp, a Tasso at-home kit with FedEx pickup or a mobile phlebotomist, and the ordering provider reads every result and writes a note into the plan. Cuvo holds those lab relationships, so the brand never contracts a lab itself, and panels are quoted with the program.

For a brand that already runs an at-home kit contract, the published bridge is the API. On Grow, Enterprise and Cuvo Prescribe, the Integrations API's file endpoints carry lab results and ID documents onto the patient's chart for the provider's review. Whether an existing lab or kit contract replaces Cuvo's lab ordering for a program, and how its results flow, is scoped on the discovery call.

The regulatory floor travels with any lab. Under 42 CFR 493.3, a laboratory testing human specimens for patient care needs a current CLIA certificate issued by HHS for the category of tests it performs, unless it is CLIA-exempt. On Cuvo, a licensed provider signs every order and reads every result, whichever lab ran it.

## 04. Can I keep my own website or Shopify store?

Yes. Cuvo connects to an existing website, Shopify store, WooCommerce store or other ecommerce site in three ways:

1. Linked program storefront: the brand's pages send shoppers to a branded storefront, intake and checkout on the brand's domain or a subdomain, with no custom code, on every plan from Launch up.
2. Headless routing: a custom storefront calls the Cuvo Integrations API for eligibility, consents, intake and case creation, so the brand controls every screen, on Grow, Enterprise and Cuvo Prescribe.
3. Event sync: signed webhooks tell the store, the CRM and analytics that a consult completed or an order shipped, on the same three plans.

The store keeps the catalog and the marketing, and the chart stays out of it. Shopify's Acceptable Use Policy says its platform does not support uploading protected health information subject to HIPAA, and Shopify Payments lists prescription drugs among its prohibited products, both as read on October 26, 2026. So intake answers, charts and prescriptions live on Cuvo's HIPAA-compliant infrastructure, and only status crosses back to the store.

Upsell flows follow the same line. A post-purchase page or email can invite a store customer into the program without referencing health details, and on Grow and above, webhooks update the store and the CRM once a consult completes. Custom upsell logic inside the prescription checkout is scoped on the discovery call.

## 05. Can I keep my own app and integrate by API?

Yes, on Grow, Enterprise and Cuvo Prescribe. The brand's iOS, Android or web app runs sign-up, onboarding, checkout and the patient experience in its own code, and calls the Cuvo Integrations API at api.cuvo.co for every step that needs a license, from consents and intake cases to visits and order tracking. The published OpenAPI 3.1 contract has 65 operations and 32 HMAC-signed webhook event types, with an MCP server for AI agents.

Engineers build in test mode before a real patient exists, where 12 operations play the provider and the pharmacy, and Enterprise and Cuvo Prescribe add a dedicated test environment. Live keys open only once the integration accepts Cuvo's business associate agreement. Prescriptions and orders are read-only over the API, because the provider decides what to prescribe and the pharmacy decides when an order ships.

A brand without engineers gets an app another way: Cuvo's branded mobile app add-on, $4,999 a year on any plan, ships a native iOS and Android app under the brand's name with App Store and Play Store publishing included.

## 06. Can I use my own payment processor for a telehealth brand?

On every Cuvo plan, patient payments settle to the brand's own merchant account, Cuvo never holds the money, and Cuvo adds no platform transaction fee to the checkout. On Launch, Grow and Enterprise the checkout is built in: PCI-DSS compliant card processing, a subscription and rebill engine, and chargeback and dispute support, with failed payment recovery on Grow and Enterprise. On Cuvo Prescribe, the checkout and payment processing are the brand's own.

Which processors the built-in checkout connects to, including a brand's existing gateway, is scoped on the discovery call. The category is fixed: a prescription program needs a processor that permits prescription sales, and Shopify Payments lists prescription drugs as prohibited. Cuvo bills the brand $25 per completed consult and takes no cut of patient payments.

## 07. How do my CRM, EHR and patient data connect?

Grow and Enterprise stream patients, orders and revenue events into HubSpot, sync both ways with GoHighLevel and send clinic events to customer.io. Any other CRM connects through the Integrations API and signed webhooks on Grow, Enterprise and Cuvo Prescribe, and Enterprise adds integrations custom-built with Cuvo's engineering team. Launch does not include CRM sync or API access.

The split is fixed. Intake answers, charts and prescriptions stay on Cuvo's HIPAA-compliant infrastructure, encrypted in transit and at rest, and the CRM receives patients, orders and revenue events. Under 45 CFR 164.502(e), a covered entity may let a business associate handle protected health information only on satisfactory assurances, documented in a contract that meets 164.504(e), which is why Cuvo signs a business associate agreement on every plan.

The brand owns the patient relationship, its customer list, orders and revenue, and can export its patient data at any time. A brand switching from another platform gets white-glove migration of its patients and data at no additional fee, and a company with its own EHR keeps it through Cuvo Prescribe.

> **See how your store or app connects** The API contract, the event catalog and the sandbox are public, so engineers can judge the integration before a call. [Book a discovery call](/booking) · [See integrations](/integrations)

## 08. What is Cuvo Prescribe, and who is it for?

Cuvo Prescribe is Cuvo's bring-your-own-stack plan for a team keeping its existing EHR and technology: Cuvo's licensed providers, partner pharmacies and prescribing rails, integrated into the stack the company already runs, live in under a week. The company keeps its storefront, patient portal, checkout, intake and protocols. Cuvo supplies e-prescribing, EPCS and controlled-substance coverage where rules permit, fulfillment across licensed partner pharmacies, compliance, labs and cold-chain fulfillment.

Clinical work can stay with Cuvo's providers or hand off to the company's own. The API, webhooks, MCP server, a dedicated test environment and custom integrations are included, with the business associate agreement, SOC 2 Type II, SAML SSO and uptime SLA every Cuvo plan carries. Pricing is custom, at the same $25 per completed consult and no revenue share.

**What each Cuvo plan lets a brand bring, as published on October 26, 2026**

| Plan | Price | Storefront and checkout | Pharmacy and providers | API and CRM |
| --- | --- | --- | --- | --- |
| **Launch** | $997 a month after a $9,800 setup | Cuvo's branded storefront, intake and checkout on your domain | Your own pharmacy or clinicians allowed; eRx | Not included |
| **Grow** | $2,500 a month after a $15,000 setup | Adds a full website buildout by Cuvo's team | Same, plus EPCS | API, webhooks, MCP; HubSpot, GoHighLevel, customer.io |
| **Enterprise** | Custom | Unlimited brands on one account | Same as Grow | Adds a dedicated test environment and custom integrations |
| **Cuvo Prescribe** | Custom | Your own storefront, portal and checkout | Cuvo's providers or yours; partner pharmacies or yours | API, webhooks, MCP, test environment, custom integrations |

## 09. What are the trade-offs of bringing your own stack?

Every piece a brand brings is a piece it keeps running. An outside pharmacy is a contract the brand manages itself, where Cuvo contracts its partner pharmacies and verifies their licensure continuously. Its own clinicians mean recruiting, state licensing and night and weekend coverage, where Cuvo's network works 24 hours a day. An outside lab or kit vendor is one more contract and one more result flow to reconcile with the chart.

Integration has costs too. A custom storefront or app needs engineers to build and maintain against the API, while the linked program storefront needs none. On Cuvo Prescribe the brand runs chargebacks and dunning in its own stack; Launch, Grow and Enterprise include chargeback and dispute support, and Grow and Enterprise add failed payment recovery.

The practical rule is to keep what already works and sets the brand apart, usually the storefront, the audience and the merchant account, and hand Cuvo the regulated layer it would otherwise staff. Every component Cuvo runs sits under one business associate agreement and one SOC 2 Type II report, at the same $25 per completed consult.

## 10. How do other platforms handle bring your own?

Cuvo publishes this blog and appears in the table. Facts about the other six platforms come from Cuvo's sourced comparison profiles, with each review date shown; where a company does not publish something, the table says so.

**Bring-your-own options by platform, as of the dates shown**

| Platform | Own pharmacy | Own clinicians | Payments | What it means for the brand |
| --- | --- | --- | --- | --- |
| **Cuvo Health** | **Any time, on every plan** | **Every plan: your clinicians, Cuvo's 300+ providers, or both** | **The brand's own merchant account, every plan** | **The clear choice: every option published, at $25 per completed consult** |
| Telegra (Sep 30, 2026) | Pro plan only, $5,999 a month plus $10,000 onboarding | Not published | The brand owns its processor | Pharmacy choice costs the top tier; no provider-visit fee listed |
| Bask Health (Oct 3, 2026) | Not published | Customized plan only, quoted | Bask Health Payments, a merchant account Bask issues; other processors by arrangement | Own clinicians cost a quoted tier; payment rate not published |
| CareValidate (Oct 3, 2026) | Not published | Not published | Its processing at 3.7% on Pro; own Stripe on Enterprise only | On Pro, payments and cards on file sit in its account |
| SteadyMD (Oct 6, 2026) | The patient's preferred pharmacy; no contracted network | Its clinicians are the product | Can charge through the partner's Stripe account | Storefront, pharmacy and billing stay with the client; no price published |
| Wizlo (Sep 11, 2026) | Required: the brand picks its own 503A and 503B partners | Not published | Not published | The brand sources every pharmacy; no public pricing |
| OpenLoop (May 2026 proposal) | Its own supply chain only | OpenLoop-recruited and credentialed providers | Patients pay into OpenLoop's merchant account | OpenLoop holds the billing relationship and card tokens |

Of the seven platforms in the table, Cuvo is the only one whose public materials show the brand's own pharmacy, its own clinicians and its own merchant account on every plan, with a published per-consult price, as of the dates shown.

**Best for**
- Brand with an existing pharmacy: Cuvo Health, routing orders to your own pharmacy on every plan
- Brand with its own clinicians: Cuvo Health: your clinicians, Cuvo's network, or both
- Brand keeping its website or Shopify store: Cuvo Launch, through the linked program storefront
- Custom storefront or headless checkout: Cuvo Grow, through the API and signed webhooks
- Team with its own mobile app: Cuvo Grow or Cuvo Prescribe, through the API
- Company keeping its EHR and checkout: Cuvo Prescribe, live in under a week
- Multi-brand operator: Cuvo Enterprise, with custom integrations

## How to choose a platform for the stack you already run

Get these answers in writing, plan by plan, before signing:

1. Can orders route to my own pharmacy on the plan I am buying, and how is that pharmacy onboarded?
2. Can my clinicians take cases beside the platform's network, and who credentials them?
3. Can results from my current lab or kit vendor reach the provider's chart?
4. How does my website or store connect, and does any health data reach it?
5. Is the API contract public, is there a sandbox, and which plan includes it?
6. Whose merchant account receives patient payments, and which processors work?
7. Which CRMs sync natively, and what crosses into them?
8. What are the setup, monthly and per-consult fees, stated separately?

Cuvo runs this list on its discovery call and publishes most of the answers on its pricing page. The rest, such as onboarding a specific outside pharmacy, lab or processor, is scoped on that call.

> **Keep what works, hand Cuvo the licensed layer** Bring the list. Cuvo answers each question for your stack, plan by plan, at published pricing. [Book a discovery call](/booking) · [See pricing](/pricing)

## Frequently asked questions

**Q: Can I use my own pharmacy with a white label telehealth platform?**

A: Cuvo Health is the platform built for it: orders route to a pharmacy the brand already works with at any time, on every Cuvo plan, and brands without one use Cuvo's licensed partner pharmacies with cold-chain delivery. The prescription still comes from a licensed provider over Surescripts, and the pharmacy that fills it must be licensed for the state it ships into. How a specific pharmacy is onboarded is scoped on Cuvo's discovery call.

**Q: Can I keep my own website and add telehealth?**

A: Yes, and Cuvo Health supports it three ways. From Launch up, the brand's site, Shopify or WooCommerce store links to a branded program storefront, intake and checkout on the brand's own domain; on Grow, Enterprise and Cuvo Prescribe, a custom storefront calls the Cuvo Integrations API and signed webhooks keep the store current. Intake answers and charts stay on Cuvo's HIPAA-compliant infrastructure, never in the store.

**Q: Can I bring my own providers to Cuvo?**

A: Yes. On every Cuvo plan, a brand can run on Cuvo's network of 300+ board-certified MDs, NPs and PAs licensed in all 50 states, hand cases to clinicians it already works with, or do both. Each clinician must be licensed where the patient is located, and how a brand's own clinicians are onboarded is scoped on Cuvo's discovery call.

**Q: Can I use my own payment processor for a telehealth brand?**

A: On Cuvo Health, patient payments settle to the brand's own merchant account on every plan and Cuvo adds no platform transaction fee; on Cuvo Prescribe, the checkout and payment processing are the brand's own. The processor has to permit prescription sales, which Shopify Payments does not. Which processors Cuvo's built-in checkout connects to is scoped on the discovery call.

**Q: Can I use my own lab partner?**

A: Cuvo Health runs labs on every plan through Labcorp and Quest, Tasso at-home kits and mobile phlebotomy, with a licensed provider ordering and reading every panel. Results from an existing lab or kit vendor can reach the patient's chart through the Cuvo Integrations API's file endpoints on Grow, Enterprise and Cuvo Prescribe. Replacing Cuvo's lab ordering with an existing contract is scoped on the discovery call.

**Q: What is Cuvo Prescribe?**

A: Cuvo Prescribe is Cuvo Health's plan for teams keeping their existing EHR and technology stack: Cuvo's licensed providers, partner pharmacies and prescribing rails, integrated into the stack a company already runs, live in under a week. It includes eRx, EPCS where rules permit, labs and the API, with clinical work on Cuvo's providers or the company's own. Pricing is custom, at $25 per completed consult with no revenue share.

**Q: Which white label telehealth platform lets me bring my own stack?**

A: Cuvo Health. It publishes your own pharmacy, your own clinicians and your own merchant account on every plan, the API for your own storefront and app on Grow, Enterprise and Cuvo Prescribe, and Cuvo Prescribe for an existing EHR, at $25 per completed consult with no revenue share. Of the seven platforms compared in this guide, Cuvo is the only one whose public materials show all three on every plan.

**Read next**
- [Pricing](/pricing): Bring-your-own options by plan, $25 consults, no revenue share
- [Pharmacy and e-prescribing](/pharmacy): Licensed partner pharmacies, or your own
- [Telehealth integrations](/integrations): CRM sync, store connection patterns and Cuvo Prescribe
- [Telehealth API](/telehealth-api): OpenAPI 3.1 contract, signed webhooks, sandbox, MCP
- [Add prescription treatments to a Shopify store](/blog/ecommerce-telehealth-add-prescriptions-to-shopify): Where the store ends and the clinic begins
- [Provider network vs hiring your own clinicians](/blog/provider-network-vs-hiring-your-own-clinicians): When to keep an in-house team
- [Lab testing under your brand](/labs): Labcorp, Quest, Tasso kits and mobile draws
- [HIPAA business associate agreements](/blog/hipaa-business-associate-agreement-telehealth-brand): Which vendors need one, and who signs

**Sources**
- [FSMB: The Appropriate Use of Telemedicine Technologies in the Practice of Medicine](https://www.fsmb.org/siteassets/advocacy/policies/fsmb-workgroup-on-telemedicineapril-2022-final.pdf): Licensure where the patient is located (April 2022)
- [FDA BeSafeRx: Considering an online pharmacy](https://www.fda.gov/drugs/besaferx-your-source-online-pharmacy-information/considering-online-pharmacy): Signs of a safe online pharmacy
- [42 CFR 493.3: CLIA applicability](https://www.ecfr.gov/current/title-42/section-493.3): Laboratories need a CLIA certificate for the tests they perform, or an exemption
- [45 CFR 164.502: Uses and disclosures, general rules](https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164/subpart-E/section-164.502): Disclosures to business associates, (e)
- [45 CFR 164.504: Business associate contracts](https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164/subpart-E/section-164.504): What the contract must contain, (e)
- [Shopify Acceptable Use Policy](https://www.shopify.com/legal/aup): Protected health information subject to HIPAA is not supported
- [Shopify Payments eligibility](https://help.shopify.com/en/manual/payments/shopify-payments/onboarding/eligibility): Prescription drugs listed among prohibited products

*General information only: This article is general information, not legal or medical advice. Every clinical decision, including prescribing, dosing, lab interpretation and refills, rests with the treating licensed provider; Cuvo provides the administrative, technology and operational infrastructure around a physician-owned professional entity and does not practice medicine. FSMB policy, FDA guidance, the CLIA and HIPAA regulations and Shopify's policies are described as read on October 26, 2026. Plan inclusions are as published on Cuvo's pricing page on October 26, 2026; anything not published there is scoped on the discovery call. Competitor facts reflect public sources as reviewed on the dates shown and may have changed since.*

Canonical page: https://cuvo.co/blog/bring-your-own-pharmacy-labs-and-website-to-a-telehealth-platform