Is Open Dental Cloud-Based? The Honest Answer

No. Open Dental is an on-premise application. It is Windows software that runs against a database on a server, and the vendor does not operate a cloud service you can subscribe to.

That is the short answer, and it is worth being blunt about because the longer answer — “but you can host it in the cloud” — is true, widely repeated, and regularly misunderstood in a way that costs practices money.

What Open Dental actually is

Open Dental installs on Windows workstations and connects to a MySQL database. In a conventional setup, that database lives on a server in a cupboard in your practice, and the workstations talk to it over the local network.

This architecture is why Open Dental can be as cheap as it is. Its published fee schedule is $199 per month per location for the first 12 months, then $149, covering up to three providers, with $20 per month for each provider beyond that. There is no hosting cost in that figure because the vendor is not hosting anything. You are.

That is a genuinely good deal — it is the cheapest credible way to run a multi-dentist practice — but the number is only comparable to a cloud product’s price once you add what the cloud product includes and this one does not.

The three ways to reach it remotely

People ask “is Open Dental cloud-based” because they want a specific outcome: access from home, from a second location, or from a laptop, without a server in the building. There are three routes, and they are not equivalent.

1. Self-hosting on a cloud server

Put the Open Dental database on a virtual machine at a cloud provider, and connect workstations to it over the internet.

What it costs: the VM itself, plus a Windows licence, plus backup storage. Cheaper in raw compute than buying a server outright.

What it costs that people forget: you now administer a Windows server that holds protected health information. Patching, backups, monitoring, access control and the BAA with your infrastructure provider are all yours. If nobody in the practice does this, you are paying an IT contractor to, and that line item is usually larger than the software.

When it makes sense: multi-location groups with real IT support, who want central data and are already managing infrastructure.

2. Third-party Open Dental hosting

A specialist company runs Open Dental for you and you connect to it, usually over remote desktop. Several vendors serve this market specifically.

What it costs: typically quoted per user or per practice per month, on top of Open Dental’s own fee. Because it is not part of Open Dental’s published pricing, you have to ask — and this is where the transparency advantage of choosing Open Dental partly evaporates, since you are back to requesting quotes.

What you get: somebody else patches and backs up the server, and you should have a BAA with them.

What you do not get: a browser-based product. You are using remote desktop, which means a session that can drop, printing that needs configuring, and a scanner or sensor integration story that needs checking carefully. Imaging in particular is the thing to test before committing — local hardware talking to a remote application is the most common source of pain in this setup.

When it makes sense: single and small-group practices that want Open Dental’s pricing and feature set without owning a server, and who have verified their imaging hardware works over the connection.

3. Remote desktop into your existing office server

Keep the server in the practice and reach it remotely.

What it costs: little, in cash. It is often the default because it appears free.

What it costs that people forget: your practice’s internet connection and that one server are now a single point of failure for remote access, and exposing remote desktop to the internet is a well-known attack vector. If you do this, it must be behind a VPN, with multi-factor authentication and current patching. Ransomware groups actively scan for exposed RDP, and dental practices are a targeted sector.

When it makes sense: occasional after-hours access for a practice that is otherwise happy on-premise.

Why the distinction matters commercially

“Cloud-hosted” and “cloud-native” get used interchangeably in sales conversations, and they describe genuinely different products.

	Cloud-native	Open Dental, hosted
How you use it	Browser, no local install	Remote desktop session, or local install talking to a remote database
Who patches the server	The vendor	You, or your host
Who owns backups	The vendor	You, or your host
Who holds the HIPAA responsibility for the server	The vendor, under a BAA	You, or your host, under a BAA
What happens on a bad connection	Slow page loads	Session drops
Imaging hardware	Vendor-supported integration	Needs testing over the connection
What is in the headline price	Hosting, backups, updates	Software support only

Neither column is better. The cloud column trades control for convenience; the Open Dental column trades convenience for control and a lower software bill. The mistake is comparing a $149 per month on-premise licence against an $829 per month cloud platform as if they were the same purchase.

The honest cost comparison

For a single-location practice with three dentists wanting remote access, using Open Dental’s own published add-on rates:

Line	Cost
Open Dental support (after year 1)	$149/month
eClipboard (digital forms)	$45/month
eConfirmations	$25/month
Integrated texting (base)	$5/month
Web Sched (online booking)	$75/month
Software subtotal	$299/month
Hosting (self-managed or third-party)	quote required
IT support	quote required

The $149 headline is real. The bill for a practice that wants forms, reminders, texting, online booking and remote access is not $149. Our full pricing breakdown runs this alongside the equivalent for Practice-Web, which reaches $472 per month on the same basis.

Against that, tab32 publishes $125 per month for a start-up practice’s first year — genuinely cloud, hosting included — and CareStack publishes $829 per month with essentially everything native. Comparing like with like changes the shortlist.

So should you still choose Open Dental?

Often, yes. It remains our pick for cost control, and the reasons are real:

Per-location pricing. A three-dentist practice pays the same base rate as a solo one. Almost nothing else in this market prices that way.
A genuinely open API and direct database access. Third-party tools integrate without asking the vendor’s permission. This is rare and valuable.
Published pricing, including every add-on — one of only five vendors out of fourteen that publish anything at all.
A large independent developer ecosystem, because the source is available.

Choose it if you have IT support, or are willing to buy it, and want maximum control at the lowest predictable software cost.

Choose something cloud-native if you want nobody in the practice to think about a server again — and price that convenience honestly, because it is worth something.

Why this question gets asked so often

“Is Open Dental cloud-based” is one of the most-searched questions about the product, and the reason is that the answer keeps appearing to be yes.

Hosting companies market it as cloud. Several businesses exist specifically to host Open Dental, and their marketing reasonably describes the outcome — access from anywhere, no server in your practice. A practice owner reading that page comes away believing Open Dental is a cloud product, because from where they are standing the difference is invisible until something breaks.

Peers describe it as cloud. A dentist who reaches Open Dental from home genuinely experiences it as cloud software. They are not being inaccurate about their experience; they are describing an outcome, not an architecture.

Comparison sites list it in cloud categories. Directory sites frequently tag it as cloud-capable, which is true in the sense that it can be hosted, and misleading in the sense that matters for budgeting and responsibility.

The distinction only becomes concrete at three moments: when you get the hosting invoice, when you ask who patches the server, and when something goes wrong at 8am on a Monday. Those are the moments worth thinking about in advance, which is what the rest of this guide is for.

The HIPAA question nobody asks early enough

This is the part that gets skipped in the excitement of a cheaper licence, and it is the part with real consequences.

Wherever your Open Dental database lives, someone is responsible for protecting the protected health information on it. With a cloud-native product, that is the vendor, under a Business Associate Agreement, and their security team does the work. With Open Dental, the responsibility follows the server.

Server in your practice — the responsibility is entirely yours. Patching, antivirus, disk encryption, access control, physical security of the cupboard it sits in, and backups you have actually tested restoring.
Self-hosted on a cloud VM — still yours. Your infrastructure provider gives you a BAA covering their layer, but the operating system, the database and the application are your responsibility, not theirs.
Third-party Open Dental host — shared, and the split must be written down. You need a BAA with that host, and you need to know specifically who patches what.

The honest summary: Open Dental’s lower software cost partly reflects work that has been moved to you. That is a legitimate trade — plenty of practices would rather own it — but it is not free, and pricing it at zero is how the “$149 versus $829” comparison goes wrong.

A practical red flag: if a hosting provider cannot tell you, in one sentence, who is responsible for operating-system patching, do not sign with them.

Remote desktop, specifically

Because option three is the one practices drift into by accident, it deserves its own warning.

Exposing Remote Desktop Protocol directly to the internet is one of the most reliably exploited configurations in small business IT. Ransomware operators scan for it continuously, and healthcare is a targeted sector because the data is sensitive and the downtime pressure makes payment more likely.

If you use remote desktop to reach Open Dental, the minimum is:

Never expose RDP directly. It sits behind a VPN, always.
Multi-factor authentication on that VPN.
Current patching on the server and the VPN appliance.
Account lockout and strong passwords — credential-stuffing against RDP is automated and constant.
Offline or immutable backups, because ransomware that reaches the server will look for the backups too.

None of that is exotic, and all of it costs either money or somebody’s attention. Factor it into the comparison honestly.

What “cheap” actually buys you

It is worth being fair to Open Dental here, because the trade-offs run both ways and the product genuinely earns its reputation.

Per-location pricing is unusually good value at scale. Most competitors charge per provider or per user, so costs rise as you hire. Open Dental charges per location for up to three providers and $20 per month per provider beyond that. A six-dentist practice pays $149 + $60 = $209 per month in software. There is nothing else in this market at that number for that many clinicians.

The open API is a real strategic asset. Direct database access and a documented API mean third-party tools integrate without asking permission, and an independent developer ecosystem exists as a result. If you ever want to build a custom report, connect an unusual piece of hardware, or wire the practice into something the vendor never anticipated, you can. On most competitors, you can ask.

Published add-on pricing is rarer than it sounds. Open Dental publishes not just the base fee but every eService rate. Only five of the fourteen vendors we track publish anything at all, and fewer publish add-ons.

You are not locked in by opacity. You can compute your own bill, in advance, without a sales call. That is worth something on its own.

Deciding, in three questions

Does someone own your IT? If yes — a contractor, an in-house person, a genuinely capable practice manager — the on-premise economics are strongly in your favour. If the honest answer is “nobody, we call someone when it breaks”, the cheaper licence is buying you a liability.
How many providers? At one or two, the price gap between Open Dental and a cloud all-in-one narrows considerably once you add the eServices. At five or six, per-location pricing pulls decisively ahead.
What happens to the practice if the server dies on a Monday? If you do not have a confident answer, that is the real cost of on-premise, and it is worth either fixing or buying your way out of.

What to ask before you commit

If you are leaning towards Open Dental with hosting:

Get the hosting quote in writing, separately from the software price, and confirm what happens to it at renewal.
Test your imaging hardware over the connection before signing. Sensors and scanners are the most common failure point.
Confirm the BAA. Whoever holds that server needs a Business Associate Agreement with you.
Ask what the backup and restore process is, and how long a restore takes. Ask when it was last tested.
Ask who patches Windows, and on what schedule.

If any of those answers is vague, that vagueness is the hidden cost of the cheap licence.

Next: what dental software actually costs, or which vendors publish their prices at all.

Frequently asked

Is Open Dental cloud-based?

No. Open Dental is Windows software that runs against a database on a server. You can reach it remotely by self-hosting on a cloud server, using a third-party Open Dental hosting provider, or running remote desktop — but the vendor does not operate a cloud service, and all three options are hosting you arrange and pay for on top of the licence.

Can Open Dental be hosted in the cloud?

Yes, and many practices do it. You can put the server on a cloud VM you manage, or pay a specialist Open Dental hosting company to run it. Either way you are hosting an on-premise application remotely, which is a different thing from a cloud-native product — you still own patching, backups and the HIPAA responsibility for that server.

How much does it cost to host Open Dental in the cloud?

Third-party Open Dental hosting is typically quoted per user or per practice per month, on top of Open Dental's own $149 to $199 per location. Self-hosting on a cloud VM costs less in raw compute but adds your own or a contractor's time for patching, backups and monitoring. Get a written quote — hosting is not part of Open Dental's published fee schedule.

What is the difference between cloud-hosted and cloud-native?

Cloud-native software is built to run in a browser and is operated by the vendor, who is responsible for uptime, patching and backups. Cloud-hosted means conventional software running on somebody else's server, usually reached by remote desktop. The user experience, the failure modes and who carries the responsibility are all different.

Software prices referenced in this guide were read from vendor sites on 2026-08-01 and are linked to their sources. Always confirm current pricing with the vendor.