Curve Dental Software in 2026: What Still Runs in Your Office
"How was the process? How was the training?" That is what a dentist moving from Dentrix to Curve asked other owners on a public forum in September 2025. Nobody in the thread asked what happens to the sensor computers, the Macs at the front desk, the internet line or the old server once the database is gone, and those are the questions the demo never reaches.
This guide reads Curve's own requirements, imaging-compatibility, data and conversion pages (all checked on 6 November 2026) from the IT side: what Curve needs from your computers and internet, which sensors capture natively and which need a bridge, what happens when the internet or the vendor is down, who backs up what, what a conversion asks of your IT, and what your IT provider still owns after you sign.
Curve Dental is browser-based practice management: the database, application and backups live in Curve's Amazon Web Services hosting, and your team works in Chrome on a PC or Mac. What stays in your office is everything that touches a device or a wire: imaging computers and drivers, the network and internet line, operating-system updates and any 3D imaging software.
- Curve hosts the database, application and its backups in AWS; imaging computers, drivers, bridges, 3D volumes, the network, the internet line and the browser cache stay in your office.
- Curve asks for current Chrome, 8 GB (16 GB recommended) and 10 Mbps down / 5 up for one to ten users on a wired line; satellite and wireless are not recommended as the primary.
- Curve's supported list includes Windows 10, macOS 12 Monterey and macOS 13 Ventura, which Microsoft has retired and Apple's security-releases page has not updated since 2024 and 2025; run Windows 11 and a current macOS regardless.
- Imaging has three paths: native capture for listed sensors (two on Mac), TWAIN on Windows only for unlisted sensors, and a bridge for pans, 3D and existing imaging suites.
- Curve Capture does not run on RDP or Citrix and Schick drivers need an x86 processor, so every operatory with a sensor needs a real Windows or Mac computer.
- Curve's data policy says it cannot secure data in your browser cache, so disk encryption, screen locks and individual sign-ins are your IT provider's job.
In this guide
- Is Curve Dental really cloud-only, and what does that mean for your office?
- What does Curve Dental need from your computers and internet?
- How does imaging work with Curve: Curve Capture, sensors, bridges and 3D?
- What happens to Curve when the internet drops, or Curve itself is down?
- Who backs up what with Curve Dental?
- What does moving to Curve involve, and what does the conversion plan leave to your IT?
- What does Curve Dental cost, and which IT costs actually go away?
- Does Curve fit a multi-location group or a Mac office?
- The IT side: what your IT provider owns after you sign with Curve
- What to verify before you sign with Curve
- What to ask your IT provider about Curve Dental
- How Legend Networking can help
- Frequently asked questions
- The bottom line
Is Curve Dental really cloud-only, and what does that mean for your office?
Yes, for the practice software itself. Curve's FAQ says you need "a web browser and an Internet connection" and no server or backup system, because Curve hosts the database in an Amazon Web Services data center. Cloud-only describes where the patient database lives; it does not describe the sensors, cameras, printers, phones and computers that still fill the operatories.
Curve's pricing page frames the subscription as removing "server hardware and 3rd-party IT fees," and for the server that is true: there is no practice database to host, patch or restore. The table below separates what moves to Curve from what stays yours. It is the first thing to settle, because every other question on this page follows from it.
| Component | Where it lives with Curve | Who owns it day to day |
|---|---|---|
| Patient database, schedule, ledger, charts | Curve's hosting (AWS); your practice has its own database | Curve |
| Application updates | Pushed by Curve; "continuous automated updates" | Curve |
| Database backups and snapshots | Curve ("back up your data throughout the day," copies in a separate location) | Curve |
| X-ray capture (Curve Capture or a bridge) | A Windows or Mac computer in each operatory, with the sensor driver | You and your IT provider |
| 3D scans (CBCT) | Captured through a bridge into the scanner's own software; the volumes stay where that software stores them | You and your IT provider |
| Chrome, Windows and macOS updates | Every workstation | You and your IT provider |
| Internet line, router, firewall, Wi-Fi, cabling | Your office | You and your IT provider |
| Browser cache on each computer | Each workstation; Curve says it "cannot provide security for any data stored in the Client's cache" | You and your IT provider |
| Documents outside Curve (scans, letters, exports, payroll, email) | Your computers, Microsoft 365 or a file share | You and your IT provider |
| Printers, label printers, scanners, signature pads, card terminals | Your office | You and your IT provider |
| Phones, cameras, door access, music | Your office | You and your IT provider |
Vendor statements from curvedental.com pages read on 6 November 2026; the ownership column is the usual split in a practice, not a Curve contract term.
If you are still choosing between hosted systems, start with our guide to cloud-based dental practice management software compared, which puts Curve beside Dentrix Ascend, Open Dental Cloud, Denticon and four others. This page goes deeper on Curve alone.
What does Curve Dental need from your computers and internet?
Curve asks for a current Chrome browser on Windows 10 or 11 or a recent macOS, 8 GB of memory (16 GB recommended), a 19-inch monitor at 1920x1080, and a wired connection of at least 10 Mbps down and 5 Mbps up for one to ten users. Satellite and wireless service "are not recommended." Imaging computers carry extra rules.
Those are the vendor's published minimums. The IT reading of each line is what decides whether the office feels fast or slow after the move.
| Requirement | What Curve publishes | What it means for your IT |
|---|---|---|
| Browser | "Google Chrome: Always use the latest version, which is the only browser fully supported for Curve." | Chrome updates itself on a schedule you do not control; a workstation that blocks updates, or an old Chrome pinned by a policy, is a support call waiting to happen |
| Operating system (Curve) | Windows 11, Windows 10; macOS 14, 13, 12, 11 | Supported by Curve is not the same as patched by Microsoft or Apple (next table) |
| Operating system (Curve Capture) | Windows 11, Windows 10; macOS 14, 13, 12 | The capture app on an imaging PC has a shorter macOS list than the browser app |
| Terminal servers | Curve Capture "is not supported on terminal servers (including RDP or Citrix) because it requires direct, local access to imaging devices" | Offices that run operatories from a terminal server need a real PC wherever a sensor is plugged in |
| Processor | "Schick/IOSS imaging drivers require an Intel or AMD (x86/x64) processor"; ARM Surface Pro devices "may have issues installing drivers" | Check the chip before buying tablets for the operatories |
| Memory | "8GB or higher of RAM (16GB or higher recommended)" | Buy 16 GB; Chrome with several tabs and a capture app will use it |
| Display | 19 inches or better; 1920x1080 recommended, 1280x1024 minimum; monitors "calibrated periodically" for clinical review | Operatory monitors need a color and brightness check in the acceptance test, not only a cable |
| Internet | "10 Mbps download and 5 Mbps upload" for "the average practice (1-10 users)"; more if you share a building's bandwidth or move large files; "Satellite and wireless service are not recommended" | Size for uploads of x-rays and intraoral photos, phones and card terminals together, and plan a second line (next section) |
| Mobile | Curve Go on the latest two iOS versions and latest three Android versions | Phones that stop getting OS updates fall off the list |
Source: curvedental.com/system-requirements, read 6 November 2026. Curve's FAQ page still shows an older figure of 5 Mbps down and 1 Mbps up; use the requirements page.
Supported by Curve is not the same as patched by the OS maker
Curve's list includes operating systems whose makers no longer ship security updates. A Curve login works fine on them; the risk is the machine underneath, which holds the browser cache, the sensor drivers and your staff's email.
| Operating system | On Curve's supported list? | Security updates from the maker (checked 6 November 2026) |
|---|---|---|
| Windows 11 | Yes (Curve and Curve Capture) | Current |
| Windows 10 | Yes (Curve and Curve Capture) | Microsoft: "Windows 10 will reach end of support on October 14, 2025." Organizations can buy Extended Security Updates at "$61 USD per device for Year One," doubling each year, for at most three years |
| macOS 14 Sonoma | Yes (Curve and Curve Capture) | Current (Apple lists Sonoma 14.8.9 on 6 August 2026) |
| macOS 13 Ventura | Yes (Curve and Curve Capture) | Apple's security-releases page lists no Ventura update after 13.7.8 on 20 August 2025 |
| macOS 12 Monterey | Yes (Curve and Curve Capture) | No Monterey entry after 12.7.6 on 29 July 2024 |
| macOS 11 Big Sur | Yes (Curve only) | Apple's page lists one Big Sur entry, 11.7.11 dated 2 February 2026 with "no published CVE entries," and nothing else since 2023 |
Sources: Microsoft Lifecycle and Extended Security Updates pages; Apple security releases (page dated 30 October 2026). Lifecycle dates are written as US calendar dates.
The practical rule: a Curve office should run Windows 11 and a macOS that Apple still updates, whatever the vendor list allows. If your front-desk Macs are on Monterey because "Curve still supports it," that is a replacement conversation, not a Curve problem. Our batch guide on the full technology stack a dental office runs shows where each of these machines sits.
How does imaging work with Curve: Curve Capture, sensors, bridges and 3D?
Curve has three imaging paths. Native capture, through its Curve Capture app, covers the sensors, pans, phosphor plates and cameras on its published list. Devices not on that list use TWAIN drivers, on Windows only. Everything else, including 3D, goes through a bridge to the imaging software you already own, and the images are referenced or uploaded into Curve.
Curve says its list is not complete ("We do not have every brand listed"), so the first job is to match every device in the building to one of the three paths before the contract is signed. The table uses Curve's compatibility page as read on 6 November 2026; the device names are the vendor's.
| Your device situation | Path with Curve | Best for | What your IT provider checks |
|---|---|---|---|
| Sensor on Curve's Windows list: DEXIS/Kavo Titanium or Platinum, Gendex GXS-700, Schick 33, Elite or WiFi, Carestream RVG 5100, 5200, 6100 or 6200, Planmeca ProSensor USB, Vatech EzSensor or EzSensor P, XDR, EVA, Jazz Imaging Solo, QuickRay | Native capture in Curve Capture on a Windows PC | Offices that want one program and no second imaging suite | Driver version per operatory; USB port and cable; Windows 11; no RDP |
| Sensor on Curve's Mac list: Planmeca ProSensor USB or Video Dental Concepts QuickRay (E2V) | Native capture in Curve Capture on macOS 12 to 14 | Mac-only offices with these two sensors | macOS version Apple still patches; the exact QuickRay model |
| Sensor Curve lists under "Currently in Use by Curve Customers but Not Yet Certified by Curve Labs" (Sopix 2, Apteryx Tuxedo, DentiMax Dream, Progeny ClearVision, Schick AE, Owandy and others) | TWAIN driver into Curve, Windows only | Offices keeping an older or less common sensor | TWAIN driver installs and survives Windows updates; "Twain drivers are not compatible with MAC OS" |
| Pan on Curve's list: CS 8100, CS 9300, Planmeca ProMax 2D S2 or S3, ProOne, Sirona Orthophos XG 3, XG 5, XG 3DReady, XG SL Ready | Native capture | Offices whose pan is on the list | The pan's acquisition PC meets the Capture requirements; Planmeca pans carry a vendor footnote ("Planmeca Panoramic devices do not have a direct integration") and are not supported for Mac, so get the capture path for your exact model in writing |
| Phosphor plates (ScanX Classic, Ortho, I/O, Duo, Swift listed) or an intraoral camera on the list | Native capture | Offices on plates or with listed cameras | Scanner driver and USB 3 ports |
| Any device you want to keep in its own software: DEXIS, Romexis, Sidexis, Dimaxis, CDR-DICOM, Patterson Imaging, Vixwin, Visix, XrayVision, Tigerview, DTX Studio, CaptureLink, CADI, RadioVision | Bridge from Curve to that software; 2D images can be uploaded into Curve | Offices with a mature imaging suite or several device brands | Bridge PC stays a managed Windows machine; "The only imaging software bridge supported on Mac computers is RadioVision" |
| CBCT or any 3D | Bridge only: "Offices are able to capture 3D images using a bridge today" | Every office with a 3D unit | Where the volumes are stored, how they are backed up, and which PC can open them when the internet is down |
What the three paths mean in the operatory
Native capture still needs a real computer. Curve Capture runs on the operatory PC, talks to the sensor through the manufacturer's driver, and uploads the image. That PC needs the right Windows build, a driver that matches the sensor, and a USB path that does not drop when the chair moves. A sensor that stopped working after a patch is the same problem on Curve as on any server system; see our guide to a sensor that stopped working after a Windows update.
TWAIN is a Windows-only fallback. It works, and many offices live on it, but the driver is the manufacturer's, not Curve's, and it is the first thing to re-test after an update. Keep the installer and the version number in your IT provider's documentation.
Bridges keep a second imaging program alive. If your pan, cephalometric unit or 3D scanner lives in Romexis, Sidexis or DEXIS, that program stays installed on a Windows PC in your office, with its own database, its own backups and its own update cycle. Curve's FAQ confirms you can "upload 2D images to reference inside of Curve"; the originals and every 3D volume stay in the bridged software. For how bridges behave day to day, our guide to imaging integration troubleshooting covers the failure patterns.
The quiet consequence is that a 3D office on Curve is a hybrid office: no practice database on site, but a local imaging store that needs a managed computer and a backup. Our guide to what still needs a server with cloud dental software works through when that store should be a workstation, a small server or a NAS. Reviewers notice the seam: one owner wrote in August 2025 that "the x-ray viewing setup isn't my favorite" and asked for tooth-by-tooth views; another in June 2025 said "Curving Imaging and GRO still feel limited in terms of functionality." Decide on the demo whether Curve's viewer is enough for your clinicians or whether the bridge stays.
Ask on the demo: "Capture on our exact sensor, on our exact Mac or PC, and open one of our CBCT volumes from Curve."
What happens to Curve when the internet drops, or Curve itself is down?
With Curve, no internet means no schedule, chart or ledger until the connection returns; nothing runs locally except what the browser has cached. A vendor-side outage has the same effect with a working line. The plan is a second connection that fails over automatically, phones that do not depend on the office line, and a printed day sheet.
Curve publishes a status page at curvedental.com/status listing Curve Hero, Curve GRO, payment processing, Curve Imaging and Business Analytics, with an average-uptime figure. Reviewers describe both sides: one wrote in August 2025 that "the system has had almost no downtime"; another in October 2025 that "there are times when outages happen and some updates take a while to roll out during business hours." Both can be true of the same product, and neither is your office's internet line, which is the more common cause of a blank screen.
The large-scale example is the Amazon Web Services disruption of 19 and 20 October 2025. AWS says the event in its Northern Virginia (us-east-1) region began late on 19 October and ended on the afternoon of 20 October, Pacific time, and that during the first phase customers "were unable to establish new connections" to the affected service. On a dentists' forum that morning an owner reported "We use Vyne for claims and it is also currently down," with the practice software out as well. Curve's FAQ says its data is stored in an AWS data center; whether a given vendor was affected depends on which region and services it uses, and that is a question to ask Curve in writing, not something to assume either way.
The failover plan a browser-based office needs
- Two internet paths, one of them not on the same cable. A fiber or cable primary and a cellular (LTE or 5G) or fixed-wireless secondary, on a firewall that fails over by itself. Curve says satellite and wireless service "are not recommended" as the primary; a wireless secondary that carries the office for an afternoon is a different purpose.
- Size the secondary for Curve, not for email. Ten users at 10 down and 5 up is the vendor's floor; x-ray uploads during a hygiene column need more, and the secondary should be tested under load, not just pinged.
- Phones that live elsewhere. A phone system that routes through the office router goes down with the internet; make sure calls fail over to mobiles.
- A printed or exported day sheet before the first patient. Curve's data policy says you can "download it at any time, right through our application"; a morning export of the day's schedule costs nothing and saves the day when it is needed.
- A written triage order. Is it the vendor (status page), the internet (your firewall and the ISP), or one computer (Chrome, a cached session, a sign-in)? Our guide to what to do when the office internet is down has the first-hour steps.
- Imaging that still captures. Native capture through Curve Capture needs the connection; a bridged imaging suite on a local PC can keep taking x-rays and sync later. Know which path each operatory is on before the outage.
The same plan covers the opposite risk: an internet line that is fine while Curve is unavailable. Nothing on your side fixes that, but a day sheet, mobile phones and a known status page turn an outage into an inconvenience rather than a closed office.
Who backs up what with Curve Dental?
Curve backs up the practice database. Its data-management page says data is backed up "throughout the day," stored "in a separate location" and tested regularly, with the database replicated across availability zones and archived in snapshots. You still back up everything Curve does not hold: bridged imaging stores, 3D volumes, scanned documents, email and the files on each computer.
That split is where cloud offices get caught. The vendor's backup is real, and it covers the part that used to live on your server, but the pricing page's "Continuous Backup, Intrusion Detection, & Disaster Recovery" describes Curve's platform, not your building.
| Data | Who backs it up | How to prove it |
|---|---|---|
| Patient database, ledger, charts, images stored natively in Curve | Curve ("regularly back up your data throughout the day") | Ask Curve, in writing, for the retention period and how a point-in-time restore is requested |
| Your own copy of practice data | You, if you choose: Curve's data policy says you can "download it at any time, right through our application," exported in a format "compatible with common business software such as Microsoft Excel" | Schedule a periodic export and store it encrypted off the workstations |
| Bridged imaging software and its database (Romexis, Sidexis, DEXIS, XrayVision and others) | You and your IT provider | A tested restore of that PC or server, including the 3D volumes |
| CBCT volumes | You and your IT provider | Size them; they decide the backup target and the restore time |
| Scanned documents, consent forms, letters and exports kept outside Curve | You and your IT provider | A file-share or Microsoft 365 backup with versioning |
| Email and Microsoft 365 | You and your IT provider | Microsoft retention plus a third-party backup where the practice wants it |
| Workstation images (drivers, Capture, TWAIN installers) | You and your IT provider | A documented rebuild path per operatory |
Our guide to dental data backup covers the local side in detail, including how to test a restore rather than trust a green tick.
The browser cache is yours too
Curve's data policy is unusually direct about one thing: Chrome caches data locally to improve performance and allow some access when offline, "a small amount of it may, in some circumstances, contain protected health information," and "the Hosted Programs cannot provide security for any data stored in the Client's cache." The policy tells clients to make sure appropriate security measures are in place on the computers used to access Curve.
For your IT provider, that is a short list: full-disk encryption switched on and verified on every PC and Mac, a screen lock that engages in minutes, individual sign-ins rather than a shared "Front Desk" account, and a secure wipe before any computer leaves the building. A stolen laptop with an unencrypted Chrome profile is still a data problem, cloud or not.
What does moving to Curve involve, and what does the conversion plan leave to your IT?
Curve runs the conversion in three published stages: a set-up with a test conversion from a copy of your data, a data review in a Hero database, and a final assembly that "typically takes just three business days," with imaging and document conversions starting after go-live. The IT work runs beside it: workstations, drivers, internet and the old server.
Curve's conversion page lists its counts "as of July 2026": 2,434 Dentrix conversions, 2,348 Eaglesoft, 916 SoftDent, 474 Open Dental, 472 PracticeWorks, 466 Easy Dental, 244 MacPractice and 194 Dentrix Ascend, from "OVER 90 practice management software products" in total. Training is online: an eight-session Boot Camp, optional sessions including a 90-minute recorded imaging video on capturing "from your device or hard drive," and three Go Live sessions. None of that touches a computer in your office, which is why the IT track below exists.
| Week | Curve's track (vendor page) | Your IT track (what nobody else owns) |
|---|---|---|
| Before signing | Demo; quote | Device inventory against Curve's compatibility list; macOS and Windows versions; internet speed test at the front desk; CBCT storage location |
| Set-up | Copy of data and A/R report; preliminary test conversion; project manager intro | Order Windows 11 or current macOS replacements; install Chrome and Curve Capture on one operatory PC and capture with the real sensor; confirm TWAIN or bridge path per operatory |
| Data review | Hero database with the test conversion; issue review | Check converted images open; test the bridge from Curve to your imaging suite; set up the second internet path and firewall failover |
| Final assembly | "The final data conversion typically takes just three business days!"; Final Assembly Conference | Freeze changes on the old system; take and verify a full backup of the old server and imaging stores; print day sheets for go-live week |
| Go live | Three Go Live sessions | Staff sign-ins (one per person), screen locks and disk encryption verified; printers, label printers and signature pads tested from Chrome |
| After go live | Imaging and document conversions "start right after you Go Live" | Run the old system read-only until every historical image is confirmed in Curve or the bridge; then decommission the server (wipe, license records, retention copy) |
Two IT points are easy to miss. First, Curve's own page puts the imaging conversion after go-live, so your office runs two image sources for a period; staff need to know where last year's bitewings are during that window. Second, the old server does not become scrap on go-live day. It holds the only full copy of the pre-conversion database and images until the conversion is accepted, and its retention copy is yours to keep, encrypted, for as long as your records policy says. Our dental software migration checklist covers the acceptance tests in detail, and our batch guide on Windows Server 2016 end of support explains why that retired server should not stay switched on and connected.
One owner's question from the forum in September 2025 is still the right one: "How was the process? How was the training?" Add a third: "Who checked the operatory computers before day one?"
What does Curve Dental cost, and which IT costs actually go away?
Curve publishes no list price. Its pricing page offers a personalized quote, startup pricing on implementation and license fees, and frames the subscription as including unlimited eClaims, ERA and eligibility, native imaging "direct to the cloud," and platform backup and disaster recovery. What goes away is the server; what stays is every device, line and license in the office.
| Cost line | With Curve | Still yours |
|---|---|---|
| Practice database server, its Windows Server license, UPS and replacement cycle | Gone | — |
| Server backup and disaster recovery for the database | Curve's platform | Backup of imaging stores, documents and workstations |
| Clearinghouse fees for claims, ERA and eligibility | Curve's page says these are included ("Unlimited eClaims, ERA, and Eligibility") | Attachment and payer rules still need testing |
| Imaging software subscription | Native imaging included for listed devices | Bridged imaging suites and their support contracts for pans, 3D and unlisted sensors |
| Workstations | — | A Windows 11 or current-macOS computer per operatory and desk, with 16 GB |
| Internet | — | A business primary line sized above the 10/5 Mbps floor, plus a failover line |
| Network | — | Firewall, switches, Wi-Fi, cabling |
| Operating-system currency | — | Windows 10 machines need replacement or Extended Security Updates at Microsoft's published "$61 USD per device for Year One" |
| Microsoft 365, email, phones, printers, card terminals | — | Unchanged |
| IT support for all of the above | — | The managed-IT line continues; its scope changes from server care to endpoint, imaging, network and vendor-coordination work |
Curve statements from curvedental.com/pricing, read 6 November 2026; Microsoft price from its Extended Security Updates page. Curve quotes per practice; get every fee, including implementation, conversion, imaging and payment processing, in the written quote.
Reviewers raise one line the pricing page does not spell out: in June 2025 a user wrote that "mobile access requires a separate GRO subscription even though the software is already cloud-based." Ask which modules are in the quoted price and which are add-ons. For the wider picture of what a practice spends on software each year, our batch guide on what dental software really costs per year sets Curve beside the server systems.
Does Curve fit a multi-location group or a Mac office?
Curve's FAQ describes group and DSO use with centralized administration and location-based permissions, which removes the per-site server and the VPN between offices. Each location still needs its own internet line, failover, imaging computers and drivers. Mac offices run Curve in Chrome on a supported macOS, but native Mac capture covers two sensors, TWAIN does not run on Mac, and only one imaging bridge does.
Groups. Curve's FAQ lists "centralized administrative operations, role-based security, custom reporting & analytics, function- and location-based permissions" for groups and DSOs. The IT standard that makes that work is the same at every site: the same Windows build, the same Chrome policy, the same sensor driver versions, the same firewall model with failover, and one place that documents which operatory is on which imaging path. For the operating model, see our page on DSO IT support.
Mac offices. Curve runs in Chrome, so a Mac office can use the practice software without a Windows machine at the desk; its compatibility page is explicit about the imaging limits: native capture on macOS is listed for the Planmeca ProSensor USB and the Video Dental Concepts QuickRay (E2V) only; "Twain drivers are not compatible with MAC OS"; "The only imaging software bridge supported on Mac computers is RadioVision." A Mac office with DEXIS or Schick sensors therefore ends up with a Windows PC in each operatory for capture, or a change of sensor. Our guide to dental imaging software and what it needs from your network covers the sensor-driver layer across platforms.
Startups. Curve's startup page promises "no server to buy" and startup pricing on implementation and license fees. The build-out still needs cabling to every operatory, a firewall with two internet paths, operatory PCs that meet the Capture rules and a sensor on the list. If you are opening a practice, our guide to dental startup IT puts those items on the construction timeline.
The IT side: what your IT provider owns after you sign with Curve
After the move, your IT provider's job changes shape rather than disappearing. The server tasks go; endpoint, imaging, network and continuity work grows, because every operatory PC is now the whole system from the staff's point of view, and the internet line is production infrastructure. Here is the list, in the order it usually bites.
- Workstations and operating systems. Windows 11 and a current macOS everywhere, patched on a schedule; Chrome managed so it updates but does not surprise a hygienist mid-capture; full-disk encryption and screen locks because of the cache clause; one sign-in per person.
- Imaging computers. Curve Capture or TWAIN installers and versions documented per operatory; the no-RDP rule respected; x86 processors; USB paths tested after every Windows feature update; the bridge PC for pans and 3D treated as a small server with its own backup.
- Internet and network. A primary line sized above Curve's 10/5 floor with room for uploads, phones and card terminals; a cellular or fixed-wireless secondary with automatic failover; wired operatories ("wireless service are not recommended"); a firewall that logs; see our guide to dental office network setup.
- Backups you still own. Imaging stores, 3D volumes, documents, email and workstation images, with a tested restore; a periodic export of your Curve data kept encrypted.
- Continuity. The printed or exported day sheet, phone failover, a triage order and a named person who checks the status page.
- Vendor coordination. When a sensor stops capturing, three parties can own it: the sensor maker's driver, Curve Capture, or the PC. Your IT provider should be the one who reproduces the fault and calls the right desk with the evidence; confirm in your agreement whether that time is included.
- Monitoring. Patch status, disk encryption state, failover tests and backup results need watching, because nothing in the office tells you a secondary line has been dead for a month until the primary fails.
This is the work behind our dental practice management software support: the Windows and Mac workstations, sensor drivers, bridges, network and backups that a browser-based system still depends on. Where a practice wants one provider for all of it, managed IT services for dental practices is the usual shape of the agreement.
What to verify before you sign with Curve
Curve's pages are clear about requirements; the contract and the demo are where you make them binding. Put each of these in writing before the quote becomes a signature.
- Every device, by name, against Curve's compatibility list. Sensors, pans, phosphor plates, cameras and 3D, each marked native, TWAIN or bridge, with Curve's confirmation for anything not on the page.
- A live capture on your own hardware. Your sensor, your PC or Mac, your Chrome, during the demo, with the resulting image opened in Curve.
- Which macOS and Windows versions Curve will support in 12 months. The current list includes versions their makers no longer patch; ask how much notice Curve gives before dropping one.
- Internet requirements for your user count. The published floor is for one to ten users; ask for the figure for your actual headcount and image volume.
- What the quoted price includes. Implementation, conversion, imaging, eClaims and eligibility, mobile access, payment processing, and each add-on module.
- Conversion scope and timing. What converts (ledgers, notes, treatment plans, documents, images), when imaging conversion completes, and how exceptions are logged.
- Your data on exit. The export formats, who runs them, the cost, and how long after cancellation you can still sign in.
- Backup retention and restore. How long Curve keeps point-in-time copies and how a restore of a single patient record or the whole database is requested.
- Outage communication. The status page address, how incidents are announced, and support hours in your time zone.
- The business associate agreement. Signed before any data is uploaded for the test conversion.
What to ask your IT provider about Curve Dental
Before the contract
- Which of our sensors, pans and 3D units are native, TWAIN or bridge with Curve, and what does each path need in the operatory?
- Which workstations are on Windows 10, Monterey or older, and what is the replacement plan before go-live?
- What is our measured upload speed at the front desk during a hygiene column, and what secondary line will carry Curve when the primary fails?
During the conversion
- Who freezes and backs up the old server and imaging stores before final assembly, and who verifies the restore?
- Which computers will still have the old system or a bridged imaging suite after go-live, and for how long?
- Is full-disk encryption on and verified on every PC and Mac that will open Curve?
After go-live
- How are Chrome, Windows and macOS updates scheduled so a sensor PC is never updated mid-column?
- Where are our CBCT volumes and bridged images backed up, and when was the last test restore?
- When Curve or the internet is down, what is the triage order and who owns each step?
How Legend Networking can help
Legend Networking is a Dallas-based dental IT company that has served over 3,500 practices since 2004, with 22+ years in dental IT and 24/7 monitoring. Legend supports the IT environment for the practice software Dentrix, Eaglesoft, Open Dental and Archy, and for the imaging systems DEXIS, Vatech, Carestream, Planmeca/Romexis and Dolphin Imaging; DEXIS, Vatech, Carestream and Planmeca appear on Curve's compatibility page as sensors, pans or bridges. Onsite dispatch is by appointment across served dental markets; support is remote-first nationwide, with dental IT support in your city listed by location.
The author, Ian Lynch, has 22 years in dental IT and oversees the NOC, onsite dispatch and client technology roadmaps. Legend holds a 4.8 rating from 173 Google reviews. For the kind of groundwork a browser-based office still needs, see a recent practice build covering workstations, network, imaging systems, backups and practice software.
Frequently asked questions
Is Curve Dental cloud-based or does it need a server?
Curve Dental is browser-based: the practice database and application run in Curve's Amazon Web Services hosting, and staff sign in through Chrome on a PC or Mac. No practice server is needed for the database. Imaging computers, any bridged imaging software, 3D volumes, the network and the internet line stay in the office and remain the practice's responsibility.
What internet speed does Curve Dental need?
Curve's system-requirements page recommends at least 10 Mbps download and 5 Mbps upload for an average practice of one to ten users, more if the building shares bandwidth or the office moves large files, and says satellite and wireless service are not recommended. Plan a business-grade primary line with room for x-ray uploads and phones, plus a second connection that fails over automatically.
Does Curve Dental work on a Mac?
Yes for the practice software, which runs in Chrome on macOS 11 to 14 by Curve's list, with Curve Capture on macOS 12 to 14. Imaging is the limit: Curve lists native Mac capture for the Planmeca ProSensor USB and Video Dental Concepts QuickRay only, says TWAIN drivers are not compatible with macOS, and supports one imaging bridge, RadioVision, on Mac.
Which X-ray sensors work with Curve Dental?
Curve's compatibility page lists native Windows capture for DEXIS/Kavo Titanium and Platinum, Gendex GXS-700, Schick 33, Elite and WiFi, Carestream RVG 5100 to 6200, Planmeca ProSensor USB, Vatech EzSensor and EzSensor P, and several others. Sensors it marks as in use but not yet certified by its labs use TWAIN drivers on Windows. Curve says the list is not complete and to ask about any sensor not shown.
Can Curve Dental store CBCT or 3D scans?
Curve's imaging FAQ says offices capture 3D images through a bridge, and that 2D images can be uploaded into Curve for reference. The 3D volumes stay in the bridged software on a computer in your office, so a Curve practice with a CBCT unit still needs a managed local machine for that data, with its own backup and a plan for opening scans when the internet is down.
What happens in a Curve office when the internet fails?
Curve runs in the browser, so when the office internet fails no computer can open the schedule, charts or ledger until the connection returns, apart from whatever Chrome has cached. The practical answer is a second internet path with automatic failover, phones that do not depend on the office line, a printed or exported day sheet each morning, and a written triage order for staff.
Does Curve back up my data, and do I still need a backup?
Curve states that it backs up practice data throughout the day, stores copies in a separate location and replicates the database across availability zones. That covers the hosted database. You still need backups of bridged imaging software, 3D volumes, scanned documents, email and workstation configurations, plus, if you want your own copy, a scheduled export of your Curve data, which its data policy says you can download at any time.
How long does a Curve data conversion take?
Curve's conversion page describes three stages: an initial set-up with a test conversion from a copy of your data, a data review in a Hero database, and a final assembly that typically takes three business days. Imaging and document conversions start after go-live. Allow extra weeks on your side for workstation replacements, sensor tests, the second internet line and the old server's retention copy.
How much does Curve Dental cost per month?
Curve publishes no list price; its pricing page offers a personalized quote and special implementation and license pricing for startups. The page describes eClaims, ERA, eligibility, native imaging and platform backup as included. Ask what the quote covers, including conversion, imaging, mobile access and payment processing, and budget separately for workstations, internet lines, network equipment and ongoing IT support, which remain yours.
Do I still need an IT company with Curve Dental?
Curve removes the practice server, not the rest of the office's technology. Someone still has to keep Windows and macOS patched, manage Chrome, maintain sensor drivers and imaging bridges, size and fail over the internet, back up imaging stores and documents, encrypt the computers that hold the browser cache, and work out whether a fault is the sensor, Curve Capture, the PC or the line.
The bottom line
Moving to Curve is a good moment to look at everything that stays: the operatory computers, the sensors and bridges, the internet line and the backups you still own. Ask for a Free Dental IT Assessment, a review of your computers, software, network security, backups and performance with written findings and prioritized recommendations, alongside our dental software migration checklist and our dental practice management software support page. If the move has you weighing IT providers as well, our guide on how to choose a dental IT company carries the scorecard to compare them on.

