Local Planning Software for Domestic Makers
For domestic implant makers, planning software is often the last imported layer. A vendor-neutral planner licensed locally closes that gap on your own catalog.
Key takeaways
In markets that push local production, a domestic implant maker can localize almost its entire value chain, casting, machining, sterile packaging, distribution, while the preoperative planning software stays imported. Planning is frequently the last foreign layer: the metal is domestic, but the digital workflow that decides component size and alignment still belongs to a foreign robot or a foreign brand's ecosystem. A vendor-neutral, implant-agnostic, CT-based AI planner that is licensed locally closes that gap. It lets a domestic maker offer modern digital planning on its own catalog without building a machine-learning team or a capital robot. The commercial shape is a white-label licence: the software builder provides the CT-to-plan engine (segmentation, CPAK phenotyping, alignment options, sizing support), the maker presents it under its own brand and keeps its implant relationship, and IP is defined by contract. Salnus builds exactly this software for manufacturers to license. It is currently Research Use Only (RUO) and not a cleared device, so engagements begin as pilots and co-development, not as a purchase of a cleared product, with no claim of clearance, outcome, or superiority.
Why planning is the last imported layer
Localization programs in orthopedics tend to move from the outside in. The parts easiest to bring home are physical and industrial: alloy supply, forging and machining, coating, packaging, sterilization, warehousing, and the field sales force. A domestic implant maker can reach a high local-content percentage on the hardware alone. What resists localization is the software layer that sits above the metal, specifically the preoperative planning that turns a patient's imaging into a component size and an alignment target.
That planning layer usually arrives from abroad in one of two forms. Either it is bundled inside an imported robotic system, in which case buying the plan means buying the whole capital platform, or it lives inside a foreign brand's ecosystem and quietly steers toward that brand's implants. In both cases the domestic maker has localized the product but not the workflow around it. The plan, the part the surgeon actually interacts with before the case, is still foreign. For a national program measuring local content, that is a visible and awkward gap.
What a locally licensed vendor-neutral planner changes
A vendor-neutral, implant-agnostic planner is built so the anatomy work is independent of the implant. The software segments the CT, characterizes the knee with CPAK phenotyping, presents alignment options, and supports component sizing, and only at the end does it fit the selected implant library. Because the neutrality lives in the engine rather than in a brand, the same underlying planner can be applied to a domestic maker's own catalog.
Licensed locally, this becomes the missing piece of the value chain. The maker can offer surgeons a modern CT-based planning experience that runs on its own components, without the plan pointing anywhere else. The distinction between a neutral engine and a locked ecosystem is the whole point, and it is worth seeing how vendor-neutral and vendor-locked planning differ in practice. A locally licensed neutral planner keeps the surgeon relationship with the domestic maker while giving that maker a digital front door it did not have to build from scratch.
How the CT-to-plan workflow reaches the maker's catalog
The engine underneath is the same regardless of whose implant sits at the end of it. A CT-based 3D preoperative workflow starts from the patient's scan, builds a three-dimensional model of the bone, and produces a plan the surgeon can review before theater. The value points for a domestic maker sit along that path:
- Sizing support. A plan that estimates component size before the case can reduce tray uncertainty and support more predictable inventory conversations around the maker's own components.
- Alignment context. Neutral presentation of alignment options and phenotype lets the surgeon plan on the anatomy first, with the domestic maker's implant fitted to that plan rather than the reverse.
- A domestic digital front door. A maker without a robot or an in-house planner still wants to be present where surgeons plan. A locally licensed neutral planner gives it that presence on its own catalog.
- Localization credibility. In a program that rewards local content, closing the software layer is a concrete step, not a marketing line, because the last imported piece of the workflow becomes locally licensed.
None of this is a clinical-outcomes claim. The software is RUO and not cleared, so the honest framing is workflow support and evidence-building, not proven surgical superiority.
The commercial model and where IP sits
The way this reaches a domestic maker is a white-label licence, with the maker as the customer, rather than a per-seat surgeon subscription. The software builder supplies the CT-to-plan engine; the maker presents it under its own brand, integrated with its own catalog. Payment follows the ordinary shape of enterprise software supply: a development fee, an annual licence, and services, sized to scope. We do not quote numbers here, and any localization program will have its own procurement constraints that sit outside this software discussion.
One structure to avoid, and it matters more in Turkey than in most markets: a neutral third-party planner given to surgeons at no charge and funded by the implant maker. Turkish medical device promotion rules work from a closed list of what may be provided to healthcare professionals, and a physician at a public or university hospital may be treated as a public official, which moves the question into the Penal Code rather than administrative law. A white-label product sold to the maker as a customer does not raise that question in the same way, because it is the maker's own product planning its own implants. This is a structural observation and not legal advice; it belongs with counsel before anything is offered.
Two of these shapes matter most for a domestic maker. A white-label license lets an implant company present the planning experience under its own brand while the neutral engine stays underneath, which is a natural fit when the goal is a domestic-branded workflow. Co-development suits a maker that wants a particular catalog integration or sizing behavior tailored to its components. In every case IP is contract-defined: a maker can co-fund surrounding work and still not own the core planning engine, and that clarity keeps the platform neutral for the next maker that licenses it.
For a product or business-development leader, the underlying choice is build, buy a robot, or license neutral software. Building in-house pulls a device company into a machine-learning discipline it may not want to own, and the trade-offs of building versus buying an OEM planning capability are worth weighing before committing. Licensing a locally deployed vendor-neutral planner is the lightest path to closing the last imported layer with a credible digital offering.
Bottom line
For a domestic implant maker, planning software is often the one part of the value chain that stays imported after everything physical has been localized. A vendor-neutral, implant-agnostic, CT-based planner, licensed locally as a white-label product, closes that gap and puts a modern digital planning workflow on the maker's own catalog, with IP defined by contract so the platform stays neutral for everyone who licenses it. Salnus is Research Use Only, so any engagement begins as a pilot and co-development relationship, not a turnkey purchase of a cleared product. If you are localizing production and want to close the software layer too, see how Salnus works with manufacturers to scope a pilot.
Reviewed by the Salnus biomedical engineering team.