White-Label Patient Portal vs Custom Build: How to Decide

A white-label patient portal gets you to market under your brand fast. A custom build gives you the roadmap and the data model. How to compare the two on full cost, what stays your responsibility either way, and what to ask a vendor before you sign.

In short

  • Buy a white-label patient portal when your workflows match the product and speed matters more than control; build when the portal is your product, when you serve several organizations under their own brands, or when you need features and integrations a vendor will not add.
  • Either way, the obligations stay with you: a business associate agreement with the required terms, HIPAA right of access, information blocking rules for actors, and, for recipients of federal funding, WCAG 2.1 AA accessibility for web and mobile content provided through contracts or licenses.
  • Compare the full cost over the life of the portal, including integration, customization, per-patient fees and the cost of leaving, and get a written answer on data export before you sign.

A white-label patient portal is a vendor's product that you license and put your own brand on. A custom portal is software built for you that you own. Buy white-label when your workflows match what the product already does and getting live quickly matters more than control. Build when the portal is your product, when you launch it for several organizations under their own brands, or when you need features and integrations the vendor will not put on its roadmap. Whichever you choose, the compliance obligations stay with you, even when the vendor runs the software.

Founders, operations leaders and product owners at digital health companies, provider groups and payers usually face this choice with a portal on the plan and a budget to defend. The trade-offs, the rules that apply to both options and the questions to put to a vendor in writing are the same for all of them.

What are the options?

  • The EHR's own portal. Most providers already have one. It is tied to one EHR and changes on the EHR vendor's schedule.
  • A white-label portal. A vendor's product with your logo, colors and domain. You configure it, but the vendor owns the code and the roadmap.
  • A custom portal. Built for your workflows, on your infrastructure or a cloud account you control, with the code and data model yours.
  • A custom white-label platform. A custom build designed from the start to be rebranded, so you can launch it for several organizations. This is the option when the portal itself is what you sell.

Beyond features, the choice decides who controls the roadmap, who holds the data, and what it costs to change course in three years.

White-label patient portal and custom build compared
QuestionWhite-label portalCustom build
Who owns the codeThe vendorYou
Who sets the roadmapThe vendorYou
Best fitStandard workflows and a fast launchThe portal is your product, or several brands
Cost shapeUsually per-patient or per-provider feesMore up front, no per-patient license fee
Compliance obligationsStay with youStay with you

What stays your responsibility either way?

Buying a product does not move your legal obligations to the vendor. Four sets of rules apply whether you build or buy:

  • Business associate agreement. If the vendor handles PHI for a covered entity, HIPAA requires a contract that sets permitted uses and disclosures, requires appropriate safeguards, requires reporting of unauthorized uses and breaches, binds subcontractors to the same terms, supports patient access and amendment, and requires return or destruction of PHI at termination where feasible (45 CFR 164.504(e)).
  • Right of access. Patients can inspect and get a copy of their information. The covered entity must act within 30 days, with one extension of up to 30 more days, and provide it in the form and format requested if readily producible (45 CFR 164.524). A portal is one way to meet this duty, and the duty still applies to requests that arrive by other routes.
  • Information blocking. The 21st Century Cures Act rules apply to healthcare providers, developers of certified health IT and health information networks. A portal that makes sharing harder than it needs to be is a risk for the actor behind it.
  • Accessibility. Under 45 CFR 84.84, recipients of federal financial assistance must make web content and mobile apps they provide, directly or through contracts, licenses or other arrangements, conform to WCAG 2.1 Level A and AA. Recipients with 15 or more employees must comply from May 11, 2027, and smaller recipients from May 10, 2028.

The accessibility rule is the one buyers most often miss. The words contracts and licenses mean a licensed white-label portal is covered just like one you build. Ask the vendor for evidence of WCAG 2.1 AA conformance on both the web portal and the mobile apps, and test your own branded configuration, because your colors and content can break contrast and labels the vendor got right.

When does a white-label portal make sense?

  • Your workflows are standard: appointments, messages, forms, results, payments, and the vendor already does them well.
  • You need to launch quickly and can accept the vendor's design system with your branding on top.
  • The vendor already connects to the EHRs your organization uses, and you can confirm it with a live customer reference.
  • You do not have, and do not want, an in-house product and engineering team to run the portal.
  • The per-patient or per-provider pricing still works at the size you expect in three years.

When does a custom build make sense?

  • The portal is your product or a core part of it, so its roadmap is your company's roadmap.
  • You launch the same platform for several organizations, each under its own brand, with its own feature set.
  • Your care model needs things generic portals do not do well: care networks with families and helpers, remote monitoring, condition-specific programs, or provider and payer workflows such as claims and referrals.
  • Patients come to you from several EHRs and organizations, and you need one front door across them.
  • You want the data model and the patient relationship to live in your own systems.

Federal survey data shows why a single front door matters. In 2024, 59% of individuals had more than one online medical record or portal, up from 50% in 2022, and only 7% used an app to combine them. Patients collect portals from primary care offices, other providers, insurers, labs, pharmacies and hospitals. A white-label product tied to one vendor's integrations may simply become one more login.

What does a custom white-label platform look like?

We built one for a digital health company in Australia. It lets healthcare organizations launch branded apps for patients, carers and family networks, with each organization's logos and colors, and a super admin who sets the features of each copy. The platform has iOS and Android apps in React Native plus a web dashboard, and five user roles with different access: Captain, Admin, Helper, Inner-circle helper and the wider helper network.

The work started with discovery, because no specification existed, and the team tested 10 versions of the home page with users before settling on one. Six apps are live on that foundation, and the partnership has run since 2017. For buyers, this means white-labeling has to be designed in from the start: tenant settings, per-tenant feature switches and role models are hard to add later.

What should you ask a white-label vendor before you sign?

  • Will you sign our BAA, or show us yours, and does it cover every subcontractor that touches PHI?
  • At termination, how do we get all our data back, in what format, and within what time? What happens to the copies you hold?
  • Which EHRs do you connect to today, through which APIs, and can we speak to a customer on each one? Do you support SMART App Launch so the portal can open inside an EHR or let patients sign in with their EHR credentials?
  • Can you show WCAG 2.1 AA conformance for the web portal and the mobile apps, and how do you test branded configurations?
  • When did you last run a penetration test, and will you share the summary?
  • Are the mobile apps published under our developer account or yours?
  • What can we change ourselves, what needs a paid change request, and what will you never change?
  • How does pricing scale with patients, providers, locations and messages?

How do you compare the full costs?

License fees are the easy number. Put these next to them for both options, over the same period:

  • Integration with each EHR and system you use, including the work on the EHR side.
  • Configuration and customization, including change requests you will need in year two.
  • Per-patient or per-provider fees at the size you expect to reach.
  • Internal staff time to run the vendor relationship or the product team.
  • Hosting, monitoring and security testing for a custom build.
  • The cost of leaving: data migration, retraining patients and staff, and re-publishing apps.

A custom build puts more of the cost up front and carries no per-patient license fee. A white-label product usually works the other way round. The crossover point depends on your volume and on how much you will customize, which is why the year-two change requests matter so much in the comparison.

Is there a middle path?

Yes. Some teams license a white-label portal for launch and own the layer around it: identity, the integration layer to the EHRs, and a copy of the data in their own systems. If the product later stops fitting, they replace the front end without starting the integrations again. Others build a custom portal but buy the commodity parts, such as video, payments or messaging, as services. Both keep the most expensive work, integration and data, under your control.

Onix Systems has built software since 2000 and has more than 370 engineers. We sign a BAA before anyone on our team sees PHI, each clinician sees only their own patients, and we run a penetration test before launch. If you are deciding between a white-label portal and a custom build, talk to one of our engineers. Our free five-day technical audit ends with a written report comparing your options against your workflows and integrations.