OEM & White-Label

Ship 3D Software Under Your Own Brand

MeshInspector is a production-ready 3D repair, inspection and preparation application, built by the team behind the MeshLib geometry engine. License it under your own brand, build your product on top of it, or have our engineers develop exactly what your hardware needs.

Book a discovery call See how it ships

MeshInspector Mesh Healer repairing an industrial part on a laptop screen

100+

developers specializing in 3D data processing

30+

CAD/CAM software custom development projects

30+

named inventors on patents and patent publications

25+

years of market presence

Building this in-house costs two years you don't have

Mesh repair that survives real scan data. Booleans that don't fail on the hundredth operation. A viewer that opens a two-hundred-million-triangle model without falling over. Every hardware company that has tried to build this in-house discovers the same thing: the demo takes a month, production-grade takes years, and it never stops needing maintenance.

MeshInspector is that layer, already built and already shipping. You decide how much of it becomes yours.

Three ways to work with us

White-label

White-label MeshInspector — your brand, our application

Deploy MeshInspector as your own product: your name, your logo, your colors, your feature set. Available as a cross-platform desktop application for Windows, macOS and Linux, and as a browser-based Web Suite you can embed directly into your own platform.

Branded UI, installer and licensing
A feature set scoped to your workflow — nothing your users don't need
Defaults preconfigured for your device
Desktop, browser, or both
Updates that follow our release line

Best for: hardware makers who need software to ship with the machine, and platforms that want 3D tools without hiring a 3D team.

Build on the platform

Build your product on MeshInspector — our platform, your product

MeshInspector is built on the MeshLib viewer stack, and the same plugin architecture we use to build our own tools is open to you. Add your algorithms, your interface and your workflow, and keep them as your own module.

Plugin API with support from the core developers
Your algorithms running inside our application
Menu and UI structure shaped around your process
Automation and scripting through the Python bindings
On-premise, cloud or hybrid deployment

Best for: companies with a proprietary algorithm or process who don't want to build the application around it.

Custom development

Custom development — we build what's missing

The engineers who wrote the engine build your feature: inside MeshInspector, inside MeshLib, or standalone. From a single module to a complete application.

Fixed-scope quote before work starts
Milestone delivery with reporting at your cadence
QA on your real production data, not synthetic samples
Documentation, training and handover
Optional long-term maintenance

Best for: a defined gap — a slicing strategy, a segmentation pipeline, a scan-to-CAD step, a format bridge.

Book a discovery call Not sure which fits? Send us your workflow

What your users get on day one

Repair and healing

Automatic hole filling, self-intersection and degenerate-geometry cleanup, watertight repair of real, dirty scan data.

Inspection and measurement

Deviation analysis against a reference, measurements, tolerance checks.

Editing and preparation

Booleans, offsets, remeshing, decimation, subdivision, noise reduction.

Point clouds and scans

Point-cloud import, triangulation, registration and alignment, segmentation.

Automation

Scripting and integration through C++, C, C# and Python bindings.

Interoperability

A broad set of mesh, point-cloud and CAD exchange formats; the exact list is fixed per build.

Built around your machine

For each vertical: the workflow end to end, what MeshInspector covers out of the box — and what we typically build for your machine.

3D scanner manufacturers

Your customer scans a part, and everything after the capture becomes your software problem: noise, holes, misaligned passes, and a mesh that has to be watertight before anyone can measure anything. MeshInspector covers the whole post-capture chain — noise reduction, registration, hole filling, watertight repair, deviation measurement against a reference — under your brand.

Typically customized: a direct point-cloud handoff from your capture SDK with no file round-trip, cleanup defaults tuned to your scanner, an inspection report in your format.

capture → clean → align → repair → measure → export

3D printer manufacturers

A model that fails to print becomes a support ticket for you, not for the designer who made it. MeshInspector repairs and prepares the mesh before it ever reaches your slicer, and ships as the front end of your print workflow with your branding on it.

Typically customized: your slicing or nesting strategy as a module, your material and machine profiles, one-click send to your printer.

import → repair → orient → hollow or thicken → arrange → hand off to your slicer

CT scanner and medical imaging vendors

Turning a reconstructed volume into a clean, printable, plannable surface is the step your clinical users struggle with most. MeshInspector covers surface extraction, cleanup, repair and export; segmentation and volume handling are where most CT projects need work built specifically for them.

Typically customized: your segmentation output as a native input, anatomy-specific presets, integration on the DICOM side.

volume → segmentation → surface extraction → cleanup → export for planning or printing

CNC machine and CAM vendors

MeshInspector gives you the model-preparation and verification half of this: feature detection, tolerance checking, and geometry clean enough to machine from. Toolpath generation and G-code simulation are built for you on top of the geometry layer — offsets, booleans, distance fields and swept volumes are already there, and our team has delivered CAM projects on them.

Typically customized: toolpath simulation and G-code preview as a module, stock and fixture collision checks, tolerance verification reports.

model → feature check → toolpath simulation → G-code preview → verification

Why OEMs choose this over building it

A geometry engine that already ships. MeshInspector runs on MeshLib — the same engine inside commercial scanning, dental, metrology and construction products today.
Robustness where it actually hurts. Repair and booleans that survive real, dirty production data — and we publish our benchmarks rather than asserting the result. Decimation benchmark, 11 libraries →
Your IP stays yours. What you add ships as your module, under terms agreed before work starts.
The people who built the engine build your feature. Not a services layer resold on top of someone else's kernel.
One codebase, every target. Windows, macOS and Linux on the desktop; the same engine in the browser through WebAssembly.
Brand and territory in writing. Naming, branding and where you may sell are fixed in the agreement, not left to interpretation.

How it ships

Desktop

A branded cross-platform build for Windows, macOS and Linux, with your installer and your licensing.

Browser

The Web Suite: MeshInspector's tools running in the browser and embedded into your platform. Branding covers tool arrangement, colors and logos. Import and export from AWS and Azure storage is supported. Performance scales with the user's browser and machine.

Under the hood

A C++ core with C, C# and Python bindings for automation and integration.

A commercial model shaped around your product

Hardware bundles, embedded modules, volume-based terms — every OEM ships differently, and we keep the commercial side flexible rather than forcing a fixed scheme. Tell us how your product reaches its users, and we'll shape the model around it together.

Discuss your model

How we work

Discovery call
your device, your workflow, your users.
Scope and fixed quote
what ships in v1, what comes later, what it costs.
Agreement
IP, branding and territory in writing.
Build
with your team or autonomously, with milestone reports at your cadence.
QA on your data
real production files, not synthetic samples.
Delivery
installer, documentation, training, handover.
Maintenance
optional, following our release line.

FAQs

Whose brand does it carry?

Yours. Your name, logo, colors and installer; our name does not appear in the product unless you want it to.

Can we ship it with our hardware?

Yes — that is the standard white-label case. Distribution scope is agreed with you before work starts.

Who owns what we add?

You own your modules and your algorithms. We keep the core. Both are written into the agreement before work starts.

Can we start with the browser version and add desktop later?

Yes. Both run on the same engine, so the second target is an extension, not a rewrite.

What happens when you release an update?

Your build follows our release line; how and when you take updates is agreed with you rather than pushed.

Can we evaluate before committing?

Talk to us about an evaluation build scoped to your workflow.

Let's scope it

Tell us what your machine does and who uses it. We'll come back with what MeshInspector covers today, what needs building, and what it takes.

Book a discovery call Send us your workflow

Cookie	Duration	Description
meshinspector_cookie_consent	1 year	Stores your choices and a random consent ID used only to prove your consent.
__cf_bm	30 minutes	Set by Cloudflare on HubSpot and LinkedIn domains to tell people from bots, for example when the HubSpot forms on our contact and reseller pages load.
_GRECAPTCHA	Up to 6 months	Strictly necessary for the security of our contact form: Google reCAPTCHA sets it on google.com for its risk analysis, which protects the form against spam and abuse.
rc::a, rc::d-* (local storage)	Until cleared	Strictly necessary for the security of our contact form: Google reCAPTCHA stores them on google.com, in its frame inside the form, to tell people from bots.
rc::c (session storage)	Session	Strictly necessary for the security of our contact form: Google reCAPTCHA stores it on google.com for the current visit, to tell people from bots.

Cookie	Duration	Description
_ga	2 years	Google Analytics: distinguishes visitors.
_ga_SCHM0KJKPH	2 years	Google Analytics: keeps the session state.
_clck	1 year	Microsoft Clarity: keeps the Clarity user ID and preferences.
_clsk	1 day	Microsoft Clarity: connects several page views into one session.
_cltk (session storage)	Session	Microsoft Clarity: identifies the browser tab.
__hstc	6 months	HubSpot: main analytics cookie with visitor and session data.
hubspotutk	6 months	HubSpot: visitor identity; links a contact-form message or a reseller application to your earlier visits.
__hssc	30 minutes	HubSpot: counts page views in the current session.
__hssrc	Session	HubSpot: detects a new browser session.

Cookie	Duration	Description
_fbp	90 days	Meta (Meta Platforms Ireland Ltd. for the EEA): stores a unique ID to deliver and measure Facebook/Instagram ads, for the Meta pixels 1466808574144374 and 1230677305725443 (the second one through HubSpot ads).
_fbc	90 days	Meta: stores the ad click when you arrive from a Facebook or Instagram ad.
lastExternalReferrer, lastExternalReferrerTime, multiFbc (local storage)	Until cleared	Meta: the last other website that linked to ours and, after an ad click, its click IDs.
_gcl_au	90 days	Google Ads: links ad clicks to visits (conversion linker).
_gcl_aw, _gcl_dc, _gcl_gb	90 days	Google Ads conversion linker: stores the ad click (gclid, dclid, gbraid) when you arrive from a Google ad.
_gcl_ls (local storage)	90 days	Google Ads: conversion linker data in local storage.
li_fat_id	30 days	LinkedIn: stores the ad click when you arrive from a LinkedIn ad.
bcookie	1 year	LinkedIn: identifies the browser for the LinkedIn Insight tag.
li_gc	6 months	LinkedIn: stores your consent to non-essential LinkedIn cookies.
lidc	1 day	LinkedIn: selects the data center.
UserMatchHistory, AnalyticsSyncHistory, li_sugr, bscookie	30 days to 1 year	LinkedIn: set on linkedin.com by the Insight Tag, for example when you are signed in to LinkedIn; ad ID syncing and browser identification.
MUID, MR, SM, ANONCHK, SRM_B	Session to 13 months	Microsoft: set on clarity.ms and bing.com when Microsoft Clarity loads with this consent; identify the browser across Microsoft sites.
IDE	13 months in the EEA, Switzerland and the UK; 24 months elsewhere	Google: ad delivery and retargeting on doubleclick.net, when Google signals is active.