D4W vs EXACT: how your dental software decides what you can actually build

When a dental practice asks us to build something custom — a branded patient portal, smarter online booking, a treatment-plan tool — the first question we ask isn’t about the feature. It’s “what practice management system are you on?” Because with dental software in Australia, the platform you already run decides more about what’s possible than the idea itself.

Two of the most common systems in the market sit at opposite ends of that spectrum: D4W (Dental4Windows) by Centaur Software, and EXACT by Software of Excellence, now part of Henry Schein One. Both are capable, widely-used systems. But how you build around them could hardly be more different — and knowing that before you scope a project saves a lot of money and disappointment.

D4W: on-premises, which changes everything

D4W has long Australian heritage and is broadly adopted in mid-market practices. It typically runs on-premises — the database lives on a server in your practice, not in the cloud. That’s not a criticism; plenty of practices prefer it. But it shapes every integration decision that follows.

When the system of record sits inside your building, a custom integration can’t just call a cloud API from anywhere. The build has to account for:

• How data leaves the practice safely. A patient portal on the internet needs to read appointment and account data that lives on your local server. That connection has to be engineered deliberately — secure, controlled, and with explicit Australian data-residency handling — not assumed.
• What the system actually exposes. On-premises dental systems generally offer more limited integration surfaces than cloud-native ones. The realistic patterns are portal extensions, online booking, and recall automation built within what’s available — not unlimited two-way access to everything.
• Keeping the practice’s copy authoritative. The clinical record stays the source of truth on your server. Anything patient-facing is a carefully-synced layer on top, never a competing second copy.

None of that makes D4W a poor choice — it makes the engineering the thing that matters. Done properly, D4W practices absolutely can have branded portals, treatment-specific booking, payment-plan tooling and automated recalls. It just has to be built by someone who respects where the data lives.

EXACT: a managed API marketplace, a different set of rules

EXACT sits in the larger-practice and dental-group segment, and as part of Henry Schein One it comes with something D4W doesn’t: a managed API Exchange — a large, documented catalogue of endpoints and approved integration partners.

That changes the build in the other direction:

• The integration surface is broader and better documented, which means richer patient-facing and reporting layers are on the table.
• But it’s a governed marketplace. Access, approval and the terms of what you can build sit inside Henry Schein One’s programme. The upside is stability and clear rules; the trade-off is that you build within that framework rather than around a system you fully control.
• It suits scale. For a multi-location group, EXACT’s group-operations features plus a custom brand-and-reporting layer on top is genuinely powerful — the kind of platform that keeps each practice’s identity while giving the group consolidated visibility.

Why this matters before you spend a dollar

The mistake we see practices almost make is scoping a feature — “we want online booking that knows a crown needs a longer slot than a checkup” — without checking whether their PMS makes it a two-week job or a two-month one. The feature is identical; the platform determines the cost.

A quick way to think about it:

• On D4W, prioritise the patient-facing layer and automation that reads cleanly from the local record. Expect the value to come from a well-built portal, booking and recalls — with the engineering effort in the secure data flow.
• On EXACT, you can be more ambitious with two-way integration and reporting, especially across a group — provided the plan fits inside the Henry Schein One API Exchange’s rules.

Either way, the patient experience you can deliver is excellent. The route there is just different, and the smart move is to know which route you’re on before you brief anyone.

We build the bespoke layer for Australian dental practices across all the major systems — including the cloud-native option, Praktika, where the API access is more open again. If you’re weighing a custom project, the honest first conversation is about your platform, not the feature list — and we’re happy to have it before you commit to anything.