White-Label AI Knee Planning for Makers
White label AI knee planning software OEM guide: how an implant maker offers CT-based digital knee planning under its own brand, IP and field-of-use defined.
Key takeaways
If you are an implant maker weighing white-label AI knee planning software as an OEM offering, the core idea is simple: you can put modern, CT-based digital knee planning in front of your surgeons under your own brand, integrated with your own implant library, without building a robot or a full planning platform yourself. Salnus provides the licensable planning layer: vendor-neutral, implant-agnostic, CT-to-plan software that handles segmentation, CPAK phenotyping, alignment options, and sizing support, while you keep the implant relationship and the surgeon channel. The commercial model is manufacturer-pays / OEM co-development, so the software is offered to surgeons as part of your ecosystem rather than sold to them directly. What stays negotiated in the contract is the part that matters most to a maker: IP ownership, field-of-use exclusivity, branding, and integration scope. One honest caveat frames everything below: Salnus is Research Use Only (RUO) today, not a cleared device, so an engagement starts as a pilot and co-development path, not an off-the-shelf cleared product.
Why a maker would white-label planning instead of building it
Building a planning platform in-house is a multi-year commitment: imaging pipelines, segmentation, an alignment engine, sizing logic, a surgeon-facing interface, plus the validation and quality system that a clinical tool eventually needs. Most implant companies would rather invest that capital in implants, instrumentation, and their commercial channel. A robot is an even larger bet, and it locks planning to hardware you then have to manufacture, service, and place.
White-labeling a vendor-neutral planner lets you skip that build and still offer surgeons a digital planning experience that carries your brand and works with your catalog. The planning software stays independent of any single implant system by design, which is exactly what makes it integrable with yours. For the underlying rationale on why implant independence is the durable position, see our note on implant-agnostic surgical planning. If you want to understand where this sits relative to robots and cleared measurement tools, our overview of which companies offer AI knee planning maps the landscape.
What white-label / OEM integration actually looks like
A white-label engagement has a few concrete layers, and it helps to separate what Salnus provides from what stays yours.
- The planning layer (Salnus provides). CT-based segmentation of the knee anatomy, CPAK phenotyping, a choice of alignment philosophies, and sizing support that produces a structured plan. This is the licensable software layer. For how CT drives a 3D plan, see how CT-based 3D planning works.
- The implant library (you provide). Your components, sizes, and constraints are integrated so the plan speaks in your catalog rather than a generic one. The surgeon plans toward your implants, not someone else's.
- The brand and channel (you own). Surgeon-facing naming, look, and the relationship stay under your name. The planning experience reads as part of your ecosystem.
- The commercial model (manufacturer-pays). Rather than charging surgeons per plan, the maker funds access as part of its implant offering. We describe drivers and structure here, not amounts, because per-plan pricing and volumes are deal-specific and should not be quoted as fixed figures.
The important framing: Salnus does not compete for the implant relationship. We build the planning software for manufacturers to license and brand. The maker keeps the customer.
What stays contract-defined: IP and field-of-use
For a medtech decision-maker, the interesting negotiation is not the interface, it is the paper. Several things are deliberately left to the contract rather than assumed:
- IP ownership. The core planning software and any derived model assets remain owned by Salnus unless the agreement says otherwise. Custom integration work, your implant data, and your brand assets remain yours. A co-development agreement defines who owns what, cleanly, before work starts.
- Field-of-use exclusivity. A maker often wants assurance that a competitor is not offered the same integrated experience in the same segment or region. That is a field-of-use question, and it is negotiable: it can be time-boxed, procedure-scoped, or territory-scoped. This is a lever, not a giveaway.
- Re-training and data governance. Where imaging data lives, who may use it, and whether anything may be used to improve models are all contract terms, not defaults. For an RUO tool this matters even more, because research data handling has its own obligations.
- Regulatory path and responsibility. Because Salnus is RUO today, the agreement should state who drives clearance for the intended market, who holds the resulting regulatory asset, and how a pilot converts into a cleared offering.
Making these contract-defined is a feature, not a hedge. It lets a serious maker get the exclusivity and IP clarity it needs while keeping the arrangement honest about what exists today.
Honest caveats a maker should price in
A white-label planner is attractive, but a credible partner should name the limits.
- RUO, not cleared. Salnus is Research Use Only. It is not a cleared device and makes no claim of clinical superiority, outcomes, or regulatory clearance. A branded clinical offering requires a clearance path that the agreement plans for explicitly.
- Pilot first. The realistic entry point is a co-development pilot with your catalog and a small surgeon group, not an instant nationwide rollout of a finished product.
- Integration is real work. Mapping your implant library, agreeing on the alignment options you want surfaced, and fitting the plan into your channel take engineering and clinical alignment time.
If your team is comparing this against buying or building a robot, our comparison of robotic versus software-only TKA planning lays out the trade-offs, and our 2026 comparison of orthopedic 3D planning software places the software options side by side.
Bottom line
An implant maker does not need to build a robot or a planning platform to offer modern AI-based digital knee planning. It can license a vendor-neutral, implant-agnostic planning layer, integrate its own implant library, and put the result in front of surgeons under its own brand, with a manufacturer-pays model and with IP and field-of-use kept contract-defined. Salnus is that licensable layer for the knee, Research Use Only today, and built specifically to be co-developed and white-labeled by manufacturers. If you are evaluating how to offer digital planning under your own name, see what a manufacturer engagement with Salnus looks like and start a conversation about a pilot.
Reviewed by the Salnus biomedical engineering team.