Skip to content
SmileInspector

For aligner brands, labs and dental CAD companies

Custom Development

Your product, built on the engine behind SmileInspector

Extend SmileInspector, build a new appliance workflow on our core, or rebuild what you already run. We have been building custom geometry processing and dental 3D software for 20+ years, long before SmileInspector existed. The same team, the same MeshLib core and the same algorithms are available for your project.

Discuss your projectSee MeshLib SDK

Three starting points

Which one are you?

  1. Your protocol, our engine

    Extend SmileInspector

    Extend the platform you already know. Custom algorithms, new modules, movement logic or staging rules written to your protocol, added to a planning engine that is already deployed, maintained and FDA 510(k) cleared for its own intended use. The shortest of the three paths to production, and you inherit every future release.

  2. Any appliance, your workflow

    Create a new product on our core

    The same geometry engine that plans aligners handles veneers, retainers, night guards, splints, bite raisers, expanders and restorative work. Segmentation, tooth-level control, margin detection, booleans, offsets and shell generation are already there. We build the planning and design workflow around your appliance and your production method. You get a purpose-built product without funding years of geometry R&D.

  3. Same business, maintained code

    Modernize your legacy software

    Legacy in-house software that still runs the business but cannot be extended, cannot be hired for, or cannot keep up with case volume. We take over the codebase, replace the geometry layer and port it to a maintained cross-platform stack. Your data and formats migrate while the old system keeps running.

What we build

Start here when configuration is not enough. Many requirements are covered by account configuration, white labeling on request, or, for clients running a high volume of cases, our API. Custom Development is for what is left.

Not sure which side of the line you are on? Tell us the requirement. When it is a configuration change, we say so.

  • Algorithms

    Movement logic, staging rules, margin detection or attachment strategies specific to your clinical protocol.

  • Proprietary formats and pipelines

    Integration with scanners, mills, printers and production systems that speak their own language.

  • New modules

    Functionality SmileInspector does not have and your workflow needs.

  • Standalone applications

    Desktop, web or embedded 3D tools built on MeshLib for appliances and tasks outside aligner planning.

  • Migration at scale

    Moving legacy case archives and proprietary formats into a working digital pipeline.

Beyond aligners

SmileInspector solves aligner planning. The engine underneath solves geometry.

Whatever you are building, the hard parts are the same: segmentation, booleans on imperfect scan data, thickness and offset control, margin detection, shell generation, output a machine can make. Each of these already ships in our own products. The clinical logic on top is what we build with you.

The same applies outside dentistry: scanning, metrology, additive manufacturing, medical devices.

The foundation

Code you can still maintain in ten years. Four reasons.

  • MeshLib SDK

    Our own 3D geometry core: meshes, point clouds, voxels, distance maps. C++ with C, C#, Python and JavaScript bindings. Runs on Windows, macOS, Linux and WebAssembly, with CUDA acceleration. Source available on GitHub.

    meshlib.io

  • Dental domain depth

    Segmentation, articulation, final position, staging, attachments, IPR, margin detection, shell generation. We did not learn these on your project.

  • 20+years
    30+projects
    100+developers

    20+ years of dental and orthodontic software for leading US dental companies, 30+ custom CAD/CAM projects delivered, and 100+ developers specializing in 3D data processing.

  • Products in production

    The same team ships and maintains MeshInspector, MeshLib and SmileInspector, and SmileInspector is FDA 510(k) cleared. Your project is built by the people who maintain those products.

How we work

From requirement to production

  1. 01

    Scoping call

    You describe the workflow, the appliance and the production method. We tell you which of the three paths fits.

  2. 02

    Technical proposal with timeline and fixed estimate

    Approach, architecture, timeline and fixed estimate, plus the ownership, IP and regulatory scope for your product, before any commitment.

  3. 03

    Development in increments

    Working builds on a regular cadence, so you see progress and steer it before handover.

  4. 04

    Deployment and handover

    Integrated into your environment, documented, with a support arrangement you choose.

Questions about Custom Development

Is this a configuration change or custom development?

Tell us the requirement. When it is a configuration change, we say so, and nothing is billed for the answer. Enterprise

Ownership, IP and exclusivity are agreed per project, before development starts. Where your competitive advantage depends on it, exclusivity is part of the agreement, and it is written into the technical proposal before any commitment.

Custom work built on SmileInspector is added to a planning engine that is deployed and maintained by the same team, and you inherit every future release. Release compatibility for your module is part of the scoping call and the proposal.

The team that ships and maintains MeshInspector, MeshLib and SmileInspector: 100+ developers specializing in 3D data processing, with 30+ custom CAD/CAM projects delivered. The scoping call tells you which part of that team your project needs.

Yes. Integration with scanners, mills, printers and production systems that speak their own language is one of the five kinds of work we build. Bring the format and the equipment to the scoping call.

No. The same geometry engine handles veneers, retainers, night guards, splints, bite raisers, expanders and restorative work, and the same core is used outside dentistry in scanning, metrology, additive manufacturing and medical devices. See MeshLib SDK

No. SmileInspector's FDA clearance covers its own intended use. Clearance and registration for a custom product are scoped per project and agreed before work starts.

A scoping call costs you an hour. After it you receive a technical proposal with approach, architecture, timeline and a fixed estimate, before any commitment. Discuss your project

Tell us what you're building

A scoping call costs you an hour. We tell you which of the three paths fits, and we tell you straight when configuration or our API already covers it.

Discuss your project