Licensing & acquisition

License the position,
or acquire it.

Four issued United States patents covering autonomous vehicle surface treatment, vehicle lighting, service-centre orchestration and dermatological imaging — together with the control software that implements them, and the inventor.

Structures

Four ways to take a position. Which fits depends on whether you want permission to practise or the asset itself.

Structure 01

Evaluation licence

A time-boxed licence to run the control software against your own process and decide whether it does what you need. Source access to the modules under evaluation, and the patent-claim acceptance harness so your engineers can run the checks themselves rather than take ours.

Time-boxed · Your hardware or simulation · Engineer-to-engineer

Structure 02

Field-of-use licence

A licence limited to a defined application — a vehicle surface treatment, a lighting operation, a service-centre deployment. The field is drawn around what you actually do, which keeps the grant narrow enough to price and broad enough to be worth having.

Defined field · Territory by agreement · Renewable

Structure 03

Exclusive licence

Exclusivity within a field of use, a territory, or both. This is the structure for a party that intends to build a business on the position rather than protect an existing one.

Exclusive in field · Milestones by agreement · Longest term

Structure 04

Acquisition

Outright assignment of the patents. A buyer acquires the asset itself rather than permission to practise it, and diligence is correspondingly deeper: chain of title, encumbrances and the full family position are established from USPTO and counsel records before anything closes.

Full assignment · Deeper diligence · Software and marks discussed separately

No price is published, and none is set. Terms depend on the field, the territory and the structure, and are discussed directly.

What comes with it

Inventor involvement

The inventor is available to the licensee — remotely as standard, and on site anywhere in the United States where it is useful. Technology this specific transfers faster in a room than in a document.

The software, not just the paper

A licence can include the control platform: the modules, the test suite and the acceptance harness. What is implemented and what is not is documented honestly, per claim element.

Engineering handover

Architecture walkthroughs, the claim-to-code mapping, and the hardware-in-the-loop path — the stage a licensee or development partner would enter at.

The portfolio

PatentSubjectGrantedClaims
US 12,643,243 B1 Vehicle surface treatment 2026-06-02 10
US 12,649,240 B1 Vehicle lighting 2026-06-09 15
US 12,511,598 B1 Vehicle service centers 2025-12-30 20
US 12,507,946 B1 Dermatological imaging 2025-12-30 17
Every patent has its own page with the claim structure and the implementation status of each mapped claim element. See the detail →

Why United States rights

What is on offer is a United States position — four issued US patents with roughly nineteen years of term remaining and no maintenance fee yet due.

For an operator

The jurisdiction you operate in

A party running robotic vehicle surface treatment, lighting service or a fleet-orchestrated service centre in the United States needs United States rights. That is the whole of the question for anyone whose vehicles, bays and customers are here.

For an acquirer

A question closed rather than carried

Acquiring the portfolio settles whether a US operation reads on these claims, instead of leaving it open while a programme scales. The claims, their structure and the software written against them are published in full on this site so that question can be examined before any conversation about terms.

Territory is a term of the deal, not an assumption. Whether a licence or an assignment is limited by field, by territory or by neither is settled in the agreement.

What you would be evaluating

Stated plainly, because it is the first thing a serious counterparty establishes anyway.

The software is simulation and control code, not deployed hardware. It is labelled that way throughout this site. Hardware-in-the-loop is the stage a licensee or development partner would enter at, and the implementation status of every claim element is published rather than summarised.