Upcoming visit
Tue · 10:30
Bientera (bee-en-TAIR-uh)
We build the door. Your own branded telehealth platform.
We run and maintain the platform, so you can run your business.
Working software with a fictional-data demo. Not approved for real patient data.
The problem
For cash-pay telehealth startups, clinics, and physician-owned practices, Bientera (bee-en-TAIR-uh) is white-label software that gives each client its own branded patient portal and mobile app. It is designed to route that client’s patients across up to five provider networks and the pharmacies the client chooses. To change a provider network or pharmacy, the client changes its routing settings, not its app. Its brand, its portal, and its patient relationships stay in place. We do not supply clinicians or pharmacies, and the software does not give medical advice.
Each client gets its own patient portal and mobile app under its own name, colors, and web address, and lists the app in its own Apple and Google developer accounts. Behind that front end, Bientera is designed to route patients across up to five provider networks and the pharmacies you choose, following rules you set, such as state licensure and language. If you change a partner, you change the routing, not the app your patients use.
How it works
Patients see your portal and your app. Partner choices live in settings, where you can change them.
From the admin console, set the name, logo, colors, font, domain, and English copy, and publish. The same document updates the portal, the console, and the mobile theme. You do not get a separate code fork, and you do not need a developer to change the look.
The platform is designed to connect your portal to up to five provider networks and the pharmacies you choose. You decide which partners are in the mix. We do not supply clinicians or pharmacies.
Routing is designed to follow rules you set, including state licensure, language, weights, capacity caps, and failover. To change a partner, you change the routing. Your brand, your portal, and your patient relationships stay in place.
Product
Items marked “Designed to” are targets or are not connected for live use. Items marked “In the product” are in the current software. The demo uses fictional data only.
In the product
A clinic admin edits a brand document: name, colors, logo, mark, favicon, font from a short list, corner roundness, shadow, light or dark mode, button style, and selected English and Spanish phrases. The screen shows the DNS steps for a custom domain. It does not change DNS for you.
In the product
Each clinic is built with its own database schema, its own database role, and forced row-level security. The application must work inside one clinic at a time. A request that tries to read another clinic’s data is denied. A separate encryption key, file store, and database per clinic are on the roadmap.
In the product
Intake forms and questionnaires are in the product. A clinic publishes the consent language it chooses. Bientera does not provide legal or clinical advice.
In the product
Scheduling is in the product and can be turned on or off for each clinic. Turning a module off hides it from the menu.
Add-on
Video visits are an add-on, off by default, and only a platform operator can turn them on. The visit screen is built. Live video is designed to use a meeting service and is not approved for real patient visits. Recording stays off.
In the product
Health logs and treatment logs are in the product. The software shows patient-entered logs. It gives no dosing recommendations and no risk scores.
In the product
Messaging between a clinic and a patient is in the product. Web traffic is served over HTTPS by the host. This is not a claim of a security certification.
In the product
A resource library is in the product and can be published in English and Spanish. It is not clinical decision support. Platform content has not been clinically validated.
Designed to
Designed to route each clinic’s patients across up to five provider networks and the pharmacies that clinic chooses, using weights, state licensure, language, capacity caps, and failover. Decisions are written to that clinic’s audit log as opaque identifiers and reasons, not names. The demo uses practice networks for illustration. Live partner credentials are not connected.
In the product
Clinic staff and operators use an authenticator app when the clinic requires it, which is the default. Each person receives one-time recovery codes. Repeated wrong codes lock the account. Patients are not asked for this staff factor.
In the product
A monthly active patient is a distinct patient with an authenticated portal action in a UTC calendar month. That is the usage count behind plan limits.
In the product
A clinic admin can download a patient export in FHIR R4 and CSV, and a portability package. Restoring another clinic’s bundle into yours is blocked. A restore does not replay payments, video sessions, or outbound messages.
Routing
Each clinic sets its own routing. The engine is designed to weigh the networks you connect, filter by state licensure and language, respect capacity caps, and fail over when a path is unavailable.
An audit log for that clinic records opaque identifiers and reasons, not names. Chart-read events store a short fixed summary, not the chart text. The current demo uses built-in practice networks. A live network would connect through a referral interface, and those credentials are not connected.
The same path, listed for small screens.
White label
Patients see the clinic’s name, colors, and address. Bientera stays in the background. The layout is shared, so every clinic runs on one product.
Try the example brands below. They show how the same screens take on another name, palette, and domain. They are illustrations, not clients, and not a promise about a timeline.
Patient portal
Welcome back
Tue · 10:30
2 in the inbox
Upcoming visit
Tue · 10:30
Example brands, for illustration only. They are not clients.
Security and privacy
Bientera is built with clinic-by-clinic isolation, hashed passwords, sealed staff authenticator secrets, audit logs, strict browser security headers, and automated checks on every proposed change. Web traffic is served over HTTPS by the host.
We do not claim that Bientera is covered by HIPAA compliance, SOC 2, FDA clearance, signed business associate agreements, or any security certification. Those require organizational policies, vendor agreements, and reviews that have not been completed. The software is not approved for real patient data.
Passwords and staff recovery codes are stored as scrypt hashes. Staff authenticator secrets are sealed with AES-256-GCM.
Database connections use TLS when that is set in the connection settings. Chart fields are not encrypted column by column. Demo files are stored locally, not in a per-clinic encrypted bucket. A per-clinic encryption key is on the roadmap and is not deployed.
Time-to-recover figures have not been measured on the hosted database.
Pricing
Approved November 15, 2026 (v1.0). These are software subscription fees for the platform. They are not a quote, not a charge for clinical services, and not approval to use Bientera with real patient data.
$750 per month
$4,500 one-time setup
Best for Cash-pay startups and small practices starting on one brand
$1,500 per month
$7,500 one-time setup
Best for Growing clinics and networks that need more seats, more partners, and a written service target
$3,500 per month
$15,000 one-time setup
Best for Multi-brand operators
$0.75 per monthly active patient above the included amount. A monthly active patient is a distinct patient with an authenticated portal action in that UTC calendar month. This is a usage metric, not a share of clinical revenue and not a per-referral fee.
$200 per month
A platform operator turns video visits on for that clinic. The visit screen (waiting room, mute, camera, and leave) is in English and Spanish. Fair-use cap of 500 fifteen-minute visits per month. Recording stays off. Live meetings are not the default and are not approved for real patient visits.
$2,500 one-time + $150 per month
Per brand. A branded build from the shared codebase, and help getting the first internal test track ready. The clinic publishes from its own Apple and Google accounts. Store fees are the clinic’s. No store listing has been submitted.
$250 per month
One additional network slot above the 2 included on Launch or the 5 included on Growth. A partner that needs a new custom adapter is a separate service. Live partner credentials are not connected.
$2,500 one-time
A guided import or export, with the scope confirmed before work starts. Self-serve export is already included on every plan. Assisted migration is a professional service, not a self-serve switch.
Live video, e-prescribing, pharmacy submission, and live card payments are not on for real care in the current demo. Sending this form does not create an order.
FAQ
Bientera is white-label software that Valtorres Capital Group, LLC licenses to clinics and telehealth practices under the clinic’s own name and look. Patients see your brand on the website and on a mobile app built for your practice.
The platform is designed to route patients across up to five provider networks and the pharmacies you choose. If you later change a network or pharmacy partner, your brand and your patient relationships stay in place.
The platform includes a patient portal, a clinic admin console, a care-team workspace, a routing engine, and one mobile codebase that is branded per clinic.
It is built for cash-pay telehealth startups, clinics, and physician-owned practices that want a branded portal and app, and that may work with more than one provider or pharmacy partner.
It is not offered today as a system for real patient care. The public demo uses fictional patients only.
Yes. A clinic admin edits a brand document in the console — name, colors, fonts, logos, plans, and copy — and publishes it. That update applies to the portal, the console, and the mobile theme. You do not get a separate code fork, and you do not need a developer to change the look. The page layout stays the same, so every clinic runs on one shared product.
In the branding screen you can set the clinic name, colors, logo, mark, and favicon; a font from a short list; corner roundness, shadow, light or dark mode, and button style; care plans and the amounts patients see; English and Spanish wording for selected phrases; your own domain name (the screen shows the DNS steps and does not change DNS for you); and which modules are on.
Eight visual presets ship with the product. The editor warns you if a color pair may be hard to read, and you can still publish.
Yes. The patient portal, the clinic console, and the mobile app share one English and Spanish catalog. A clinic can replace individual phrases with its own wording in either language. The resource library and intake questionnaires can also be published in English and Spanish. A patient’s language is used when the routing engine looks for a matching clinician.
This marketing website is English only for now.
Most care modules can be turned on or off per clinic. When a module is off, it is hidden from the menu, and a direct link tells the visitor that the feature is turned off for that clinic.
Modules include intake forms and questionnaires, scheduling, messaging, a bilingual resource library, health logs, treatment logs, prescription status, payments (off until you turn it on), and video visits (an add-on that only a platform operator can turn on; it is off by default). Home, the patient list, branding, and staff profiles stay available.
Each clinic gets its own database schema, its own database role, and row-level security that is forced on. The application can only act as a restricted role, and it must work inside one clinic at a time. A request that tries to read another clinic’s data is denied, and that denial can be recorded in the caller’s own audit log. Automated tests create a second clinic and check that the API, connectors, routing, and logs stay isolated.
A completely separate database per clinic, and a separate encryption key and file store per clinic, are on the roadmap. They are not how the current demo is hosted.
The software includes clinic-by-clinic isolation, hashed passwords, sealed staff two-factor secrets, audit logs, strict browser security headers, and automated checks that run on every proposed change. Web traffic is served over HTTPS by the host.
We do not claim HIPAA compliance, SOC 2, signed business associate agreements, or approval for real patient data. Those require organizational policies, vendor agreements, and reviews that have not been completed.
Yes, for clinic staff and operators. When a clinic requires it — and that setting is on by default — clinicians, medical directors, clinic admins, and operators enter a code from an authenticator app after their password. Each person also receives one-time recovery codes. Repeated wrong codes lock the account, an admin can reset someone, and attempts are logged.
Patients are not asked for this staff factor. They can optionally use the biometric unlock already on their phone. That is a device lock, not staff two-factor sign-in.
A backup job runs on every proposed software change: it copies a temporary database, encrypts the copy, restores it, and checks that the data and the clinic boundaries came back correctly.
A nightly encrypted backup of the hosted database is built and is on the roadmap. It has not been run yet, because the hosted backup keys have not been added. Time-to-recover figures have not been measured on the hosted database.
Video visits are a planned add-on. They are off by default, and only a platform operator can turn them on for a clinic. The visit screen is built: a waiting room, device check, mute, camera, and leave, in English and Spanish. Recording is off. On a phone, visits currently open inside the app’s built-in browser view. A fully native video module is on the roadmap.
Live video is designed to depend on a connected meeting service. The demo uses a stand-in unless that service is configured. It is not the default, and it is not approved for real patient visits.
There is one mobile app codebase. Each clinic gets its own branded iOS and Android build, using the same look as the website. Patients can sign in, complete intake, book, message, join a visit, keep health logs, and view prescription status.
Each clinic publishes the app from its own Apple and Google developer accounts. No store listing has been submitted yet, so there is not yet a downloadable app in the App Store or on Google Play.
Patients can optionally turn on the phone’s biometric unlock. Sessions on the phone end after 15 minutes of idle time.
Launch is $750 per month plus a $4,500 setup fee, and includes 500 active patients and 5 staff. Growth is $1,500 per month plus a $7,500 setup fee, and includes 2,000 active patients and 15 staff. Scale is $3,500 per month plus a $15,000 setup fee, and includes 5,000 active patients and unlimited staff. Extra active patients above a plan’s included amount are $0.75 each per month.
Video visits, a native app, assisted migration, and extra networks are paid add-ons. A custom connector is a separate paid service. English and Spanish, a custom domain, and self-serve data export are included. These software fees were approved on November 15, 2026 (v1.0). They are not a quote for clinical services, and they are not approval to use Bientera with real patient data.
The platform has slots for provider networks, pharmacies, e-prescribing, video, email, push notifications, and payments. In the current demo those slots use test or mock providers.
Provider routing uses built-in practice networks for demonstration. A live network is designed to connect through a standard referral interface. An e-prescribing adapter is present and is not connected. It will not call a live service until it is configured. Pharmacy submission to a real dispenser is not connected.
Payments can open a test checkout only. The app does not collect a card number, and a live payments key is refused. Email and file storage use local stand-ins in the demo. Production email and cloud file storage are on the roadmap.
Push notifications are designed to send a short template and an opaque id, not chart text. The push service is not connected. Controlled-substance prescribing is off.
No. Authenticated pages, branded pages, the demo, and the mobile app do not load advertising pixels or third-party analytics. This marketing site does not either. Fonts are hosted with the site.
Yes. A clinic admin can download a patient export (FHIR R4 and CSV) and a portability package for a planned move. Restoring another clinic’s bundle into yours is blocked. Some operational records — for example, payment and video-session rows — are archived and are not replayed on restore, so a restore cannot accidentally charge a card, send a message, or reopen a visit.
No. We do not claim HIPAA compliance, SOC 2, signed business associate agreements, completed clinical, legal, or security reviews, or approval for real patient data. Some technical safeguards that those programs usually look for are already in the software. The security section on this page describes them.
The organizational work — policies, training, vendor agreements, a formal risk analysis, and outside review — is still ahead. Please do not use the demo or the current hosted environment for real patient data.
The company
Bientera (bee-en-TAIR-uh) joins the Spanish words bien and entera. It reads as “whole and well.” That names the product, not a health result.
Bientera is a product of Valtorres Capital Group, LLC, in Virginia Beach, Virginia. The company is the contracting party, the licensor, and the invoicing entity. Bientera is a product name, not a separate legal entity.
Patients see the client’s brand. Bientera appears in business materials, the admin console, and legal notices. The company does not supply clinicians or pharmacies, and the software does not give medical advice.
Next step
Tell us about your organization. There is no online checkout. A person from Valtorres Capital Group, LLC will follow up about a demo. Please keep health information out of this form.