Built · tested · owned IP · no operator yet
The platform for people who want to be the platform.
A multi-tenant, network-agnostic telehealth platform with hard tenant isolation, an LLM reliability layer, and the legal starter set already drafted. Licence it to run your own telehealth, or acquire it to become the provider.
Licence or acquire + deployment · you own the IP
What it is
Network-agnostic telehealth infrastructure.
Multi-tenant by design: each clinic or brand is an isolated tenant on shared infrastructure, so the marginal cost of the next tenant trends toward zero. Bring your own clinical network — the platform plugs into it.
- Multi-tenant SaaS — PostgreSQL row-level security — a query that forgets its WHERE returns nothing, not another clinic’s patients
- LLM reliability layer — eval harness and retrieval-quality gates in front of anything a patient reads
- Network-agnostic — the clinical and prescribing integration sits behind a typed boundary and can be swapped
- Patient intake, scheduling, records — plus secure messaging, across four subdomains
- No long-lived database passwords — per-service IAM and RDS IAM auth throughout
- 37 migrations — schema is versioned and reproducible, not hand-applied
Where compliance actually stands
A head start on the paperwork. Not a substitute for your attorney.
Building multi-tenant telehealth infrastructure is a year, a team and six figures. That part is done, tested, and yours. The platform is built HIPAA-ready: row-level tenant isolation, per-service IAM, no long-lived database credentials, and an architecture designed for a business associate relationship.
It also ships with five drafted legal documents — platform services agreement, business associate agreement, privacy policy, terms, and billing terms — so your counsel starts from a draft rather than a blank page.
Said plainly, because it matters: those documents are starter drafts for a healthcare attorney to finalise. They are not compliant as-written, and no software is “HIPAA-compliant” by itself — compliance is a property of your whole programme, not of a codebase. Do not accept PHI on this or any platform until your attorney has finalised the BAA. Anyone selling you “compliant on day one” is selling you a risk they will not be carrying.
Who it’s for
Three shapes of operator
Telehealth operators
Infrastructure now, with tenant isolation and the reliability layer already built and tested.
Clinic and wellness brands
Run your own branded telehealth rather than a generic vendor’s, on infrastructure you control.
Companies that want to be the platform
Acquire the infrastructure and white-label it to many clinics under your own brand.
Two ways in
Licence it, or acquire it.
Licence — run your own telehealth
For a clinic or brand
You want your own branded telehealth, owned for good.
- ✓A perpetual, tenant-isolated deployment that is yours
- ✓I deploy it, brand it, and wire your clinical or prescribing network
- ✓The reliability layer, and the BAA drafts to take to your counsel
- ✓Bug fixes and updates included; new build-out scoped separately
- ✓Your patients, your data, your brand — always
Acquire — be the provider
For a company
You want to own the platform and offer it to others.
- ✓The codebase and IP outright, source in hand
- ✓I deploy it, build it out, and transition it to your team
- ✓White-label it to your clinics under your brand
- ✓The legal draft set comes with it
- ✓Optional ongoing engineering support, scoped
01
Scope
Your model, your clinical network, single clinic versus be-the-platform, and which states.
02
Deploy & tailor
I stand it up on your infrastructure, wire your integrations and apply your brand.
03
Handover
You own it, documented — with me on call for fixes and extensions.
Be the anchor
First operator advantage.
The platform is built and tested and has no operator yet. I would rather say that than imply a customer I do not have — and it is the offer, not an apology: the first operator gets founding terms and a direct line to the engineer shaping it, on a finished foundation rather than a roadmap.
Why me
I architected the platform, its reliability layer and its legal starter set — the whole stack. I am a forward-deployed engineer: I embed, deploy on your infrastructure, and stay reachable when something breaks at an hour that matters.
Let’s talk
Tell me what you’re building.
Twenty minutes: your model, your clinical network, and whether licensing or acquiring this beats building it. If building it yourself is the right answer, I will say so.
Start the conversationBuilt and owned by me. It has no live client and has never carried patient data — a proven-architecture asset, not a live-user claim. More on how I work — jaklabs.io/engineering.