How to Set Up a Private AI Assistant for Your Medical or Dental Practice
James Ballard · August 8, 2026
If you run a medical or dental practice, you've probably felt the pull of AI tools—drafting patient communications, summarizing notes, answering routine questions—while also feeling a knot in your stomach about where all that information actually goes.
That knot is reasonable. When you paste patient details into a random chatbot, you often have no idea which servers store it, who can read it, or how it might be reused. For a practice that handles sensitive health information, "I'm not sure" isn't an acceptable answer.
This guide walks through a different approach: running a private AI assistant on a server you own, set up without any technical skills. We'll be honest about what this does and doesn't do—because when patient records are involved, honesty matters more than hype.
Why a shared, public AI tool is the wrong fit for a practice
Most consumer AI tools are multi-tenant. Your conversations live on infrastructure controlled entirely by the vendor, mixed in with millions of other users. You accept whatever their data policy says today, and whatever it becomes tomorrow.
For a practice, three problems stand out:
- You don't own the environment. You can't point to a specific server and say "our data lives here."
- You have limited control over retention. What's kept, for how long, and by whom is the vendor's decision.
- Convenience encourages oversharing. When the tool is right there, staff paste in things they shouldn't.
The alternative is a private assistant—one that runs on a server your practice controls, so you decide what it touches and where it lives.
What "private and owned" actually means
Here's the model LaunchMy.ai uses, described plainly so you know exactly what you're getting.
You end up with your own AI assistant running on a cloud server that your practice owns—specifically a server (a "Droplet") in your own DigitalOcean account. You also connect your own Anthropic account for the AI itself. That means:
- The server is yours. It's in your cloud account, under your billing, under your control.
- The AI usage is yours. It runs through your own Anthropic account, not a shared pool.
- We are the launcher, not the operator. LaunchMy.ai helps you set the assistant up through a simple web portal called the Launchpad. We don't hold the keys to your machine, and we don't run your assistant for you day to day.
An important note on privacy honesty: "you own the server" is not the same as "no one on earth can ever access anything." Your cloud provider operates the physical infrastructure, and your AI provider processes the requests you send it—that's how any hosted AI works. What you gain is a dedicated, single-practice environment you control, instead of a shared consumer tool. That's a meaningful difference, and we'd rather state it accurately than oversell it.
But I'm not technical—isn't running a server hard?
Normally, yes. Setting up a server usually means Linux commands, cryptic configuration, and constant maintenance. That's exactly why most practice owners never self-host, even when they want to.
LaunchMy.ai is built to remove that entirely. There's no Linux, no terminal, no server jargon to learn. You use a guided web portal, click through setup, and your assistant gets launched for you.
Ongoing upkeep is handled by Dex, the built-in AI sysadmin. Dex watches over your server—monitoring it, performing maintenance, and handling repairs—so you're never expected to open a technical tool. Think of Dex as the quiet IT person who keeps the lights on without needing an office.
Step-by-step: getting your practice's private assistant running
Here's what the process looks like in practice.
1. Create your cloud account
You'll set up a DigitalOcean account if you don't have a device to run the assistant on. This is where your server will live, in your name and under your billing. Budget roughly $12/month for the server itself—paid directly to DigitalOcean, not to us.
2. Connect your AI account
You'll connect your own Anthropic account, which powers the assistant's intelligence. You pay Anthropic directly for what you use. Usage-based billing means light use costs little; heavy use costs more. Being transparent: this is a separate cost from your LaunchMy.ai subscription.
3. Launch through the Launchpad
Using our web portal, you'll walk through a guided setup that deploys your assistant onto your server. No commands, no configuration files. This is the part that would normally require a developer—and it's the part we handle for you.
4. Let Dex keep it healthy
Once launched, Dex takes over the routine care of the server so you can focus on your patients instead of your infrastructure.
5. Add assistants for your team (optional)
If your front desk, billing, and clinical staff each want their own assistant, you can add more—up to six total—so people aren't sharing one login.
Setting sensible internal rules (this part is on you)
A private environment reduces exposure, but good habits still matter. A few practical policies for any practice:
- Minimize what you enter. Ask whether you need a real patient name or record number to get useful help. Often you don't.
- Decide what the assistant is for. Drafting general patient-education text or cleaning up internal notes is different from processing full records. Set clear boundaries with staff.
- Consult your compliance advisor. LaunchMy.ai is a deployment tool, not a compliance program. If you handle protected health information, review your obligations (including any required agreements with your service providers) with someone qualified in healthcare compliance. We can't make a compliance determination for you.
We'd be doing you a disservice to imply that installing any tool automatically makes a practice compliant. It doesn't. What a private, owned environment gives you is a stronger foundation and far more control than a public chatbot—paired with your own sound policies.
What it costs
Here's the straightforward breakdown for LaunchMy.ai:
- Starter plan: $9.99/month for your first assistant. Launch offer: $5.99/month for your first 6 months (40% off), then it renews at $9.99/month.
- Additional assistants: $6.99/month each, up to 5 more (6 total). Launch offer: $4.19/month each for the first 6 months.
- Annual option: $99.90/year Starter (pay 10 months, get 12), with a launch first year of $79.90.
- Expert Help: one-time setup support if you'd like a hand, at $49 / $99 / $199.
Plus the two costs that go directly to your own providers: your server (~$12/month to DigitalOcean if you need a cloud server) and your AI usage (to Anthropic, based on how much you use).
The bottom line
A public chatbot asks you to trust a shared system you can't see. A private assistant on infrastructure you own flips that: your server, your AI account, your rules—set up without touching a terminal, and kept running by Dex.
For a medical or dental practice, that shift in control is the whole point. Pair it with sensible internal policies and guidance from your compliance advisor, and you get the usefulness of modern AI without handing your practice's sensitive information to a black box.
The service is provided "as is," and we're deliberately careful not to promise outcomes we can't control. What we can offer is a genuinely private, genuinely owned setup—done the easy way.