Technology
Technology and data
Native code, local data
Technical choices that serve speed, control and traceability.
Rust, native desktop.
One compiled application. No browser engine in the middle.
GPU viewport.
3D rendering through wgpu on Vulkan, for smooth handling of dense meshes.
Open project file (.dcprj).
A ZIP container with checksums, versioned and documented.
Privacy by design.
Patient data is pseudonymised: no names in project files.
Offline-first.
Work on local projects. An account (auth.dentalcraft.app) is planned for licences and support only.
Bilingual UI.
English and Italian.
Details will be published as the project format stabilises.
Regulatory
Regulatory stance
Honest about where we are
In development. Not a medical device. Not for clinical use.
DentalCraft is not a medical device and is not certified. It must not be used for clinical purposes.
The project is being built with a regulatory mindset: requirements, risk management and traceability are carried over from the earlier work. The intention is to pursue the appropriate medical-device conformity path when the software is ready for it. That is an intention, not a status.
FAQ
Questions, answered plainly
Is DentalCraft available?
Not yet. It is in early development. The application shell, project format and 3D viewport exist. Scan import and the clinical algorithms are being ported and validated.
Is it certified? Is it a medical device?
No. DentalCraft is not a medical device and holds no certification. It is not for clinical use. We are building with a regulatory mindset and intend to pursue the appropriate conformity path in the future.
Which platforms will it run on?
Linux and Windows first. macOS later.
How much will it cost?
Pricing has not been decided.
What happens to patient data?
The design is offline-first: projects stay on your machine. Project files are pseudonymised and carry no patient names. An account is planned only for licences and support.
Can I try it?
Not yet. Early access is planned for later. Come back to this site for news.
What can it do first?
The first module is Aligners, for clear aligner planning. The intended workflow is described above; it is being ported and validated, and nothing in it is available yet.
Which file formats does it use?
Scans in STL, OBJ and PLY are intended as inputs. Projects use a single open .dcprj file. Per-stage export is intended as STL.
Contact
Privacy
Privacy note
No cookies, no tracking, no forms
This website sets no cookies, runs no analytics or tracking scripts, loads nothing from third parties and has no forms. We do not collect personal data through it. Your language choice is kept only in your own browser, so that the site can open in your language next time.
Like any web server, the one hosting this site may keep standard access logs (IP address, time, page requested) for security and troubleshooting. If you write to hello@dentalcraft.app, we use your message only to reply.