Dental

Aligner planning in a day, on the hardware you already own.

Planning is where clear-aligner turnaround goes, and it is where the compute bill goes too. We rebuilt the pipeline so a manufacturable plan comes back in a day, on ordinary servers.

1day
Scan to manufacturable plan.
3–4weeks
The industry norm it replaces.
CPU
Planning runs on general-purpose server hardware.

Where the three to four weeks actually goes

Almost none of it is computation. It is queueing. A case waits for a technician. The technician produces a setup. The clinician reviews it and sends it back. It waits again. Each round trip is a day of work and about a week of calendar.

Which is the reason we put the clinician inside the pipeline rather than at the end of it. Compressing the planning step on its own would just move the queue.

Why the compute claim is a commercial claim

If your planning cost tracks accelerator pricing, it is not a cost you control. For a laboratory running thousands of cases a month, the gap between a pipeline that requires an accelerator fleet and one that runs on general-purpose servers is a structural margin difference rather than an infrastructure preference.

It also makes on-premise realistic, which matters to laboratories that would rather not send patient scans anywhere.

A finished appliance, printed from a plan produced by this pipeline.

Aligner manufacturers and dental service organisations.

Throughput, clinician acceptance rates and integration detail are shared under agreement.