Enterprise
Run every brand you own on one telehealth platform
Multi-brand control, granular access, a full audit trail, and the pharmacy and prescribing rails underneath — so you can launch a new brand without launching a new stack.
Scale
Already running at national scale
Your brands run on the same engine that has already carried millions of patients, over ten million orders and more than a billion dollars in payments.
7,781,906+
patients have flowed through Bask
12,081,906+
orders fulfilled in record time
$1,535,000,000+
processed through Bask Payments
Multi-brand
One account, every brand
Each brand gets its own domain, theme, catalog, intake flows and patient portal. You get one login, one team, and one place to move between them.
Switch brands without switching accounts
Your team signs in once and moves between every store you own from the account menu.
Separate where it matters, shared where it helps
Independent domains, branding, pricing and catalogs per brand; one team roster, one contract, one invoice behind them.
Launch the next brand from a template
Clone a working site, theme and intake flow instead of starting from an empty canvas.
Your brand, not ours
Custom domains and full branding removal across the storefront, the intake and the patient portal.
Each brand, its own patient journey
Separate intake flows and patient portals per brand, so patients only ever see the brand they signed up with.
One contract, one invoice
Every brand runs under the same agreement and bills to a single invoice, however many you launch.
Security & governance
Clear your security review the first time
Over 100 permissions enforced on the server, a record of every action, and the compliance and architecture behind them — written plainly enough to forward straight to your reviewer.
Every permission, checked on the server
Over 100 granular permissions enforced server-side, so what a seat can see in the dashboard is exactly what it can reach through the API.
A full record of who did what
Every change is logged with the actor, the action, the source IP and the result — ready to export when a reviewer asks.
The three every telehealth buyer asks about on the first call.
Business associate agreements and clinic service agreements are signed inside your dashboard, tracked per clinic, not chased over email.
Which store a request belongs to is derived on the server and never trusted from the client; every session-bound call asserts that the patient and the store match.
Publishable keys for the browser, secret keys for your server, admin keys that cannot touch patient data at all.
500 requests per minute per key, tighter limits on authentication endpoints to stop credential stuffing, and a correlation id that ties every event back to the request that caused it.
API versions run side by side, each with its own published specification, so an upgrade is a decision you make rather than one made for you.
Roles as a starting point
Owner, admin, customer service and pharmacist roles come preset, then every permission is adjustable per seat.
Sensitive surfaces, separately granted
Patient health data, order fees, analytics exports and payout figures are each their own permission, so a support seat never inherits finance access.
Four kinds of log, not one
Audit, user, activity and session logs, plus a dedicated log of every call made against your headless API keys.
Including us
Support actions taken on your account land in the same audit trail, with the actor, the change, the source IP and the result.
Operations
Operations at national scale
Prescribing, fulfillment, the vendor network and the financial picture are part of the platform, not integrations you go and buy.
Clinical and pharmacy
One pharmacy network fills in every state, with compounding for formulas only you sell. Asynchronous intake, clinical review and e-prescribing run in one flow, with synchronous visits when a state or a protocol requires one.
Finance and data
Order-level revenue, fees and margin, refreshed continuously rather than batched overnight — and BaskQL for direct query access when a report isn’t enough, gated by its own permission.
Hold your vendors to a number
SLA rules per vendor and per fulfillment stage, tracked on a dashboard instead of in a spreadsheet.
Operational depth
Replacement mapping, custom order statuses, refund controls and custom fields, configured by your team instead of filed as tickets.
Export on a schedule
Scheduled data exports into the warehouse you already run.
Payouts and invoicing
Payouts, invoices, usage and transaction fees are all visible in-product, each behind its own permission.
50 states
filled through one national pharmacy network
12,081,906+
orders fulfilled in record time
Build your way
Visual, headless, or driven by an agent
The same platform, reached three ways — and the same operations underneath all three, so they can’t drift apart.
Build sites, themes, intake flows and catalog visually — no engineering ticket required.
120+ REST endpoints and two dozen webhook events behind your own front end.
Connect an agent to your account and let it drive the same operations your team does.
Pages, theme and intake already wired together, with domain, launch plan and publish in one place.
Run an experiment on any question or step in a flow.
A correlation id on every event and a dedicated log of every call made against your keys.
Claude, Cursor, VS Code or any MCP client, connected with an API key from your Bask admin.
Tell us what you’re running today
Most enterprise conversations start with an existing stack and a migration date. Send us both and we’ll come back with what moving looks like.
Trusted by 500+ telehealth companies building, launching, and scaling patient care on Bask.