UBIQS

Count every chip: IP licensing you can verify

A chip IP vendor, a design house or a software licensor gets paid on a number the licensee reports. It almost never sees the real count.

Share LinkedIn X Email

Most technology licensing still runs on an honor system. A licensor sends an invoice based on a spreadsheet, prepared months later by the party that pays more if the number is higher.

Where the count leaks

When licensors do check, they almost always find a gap. In a 2013 report, royalty compliance firm Invotex found that 89% of the licensees it audited had underreported and underpaid, and Stout cites average underpayments of 10% to 25%. Most of it is not fraud: misread terms, missed sales, deductions nobody approved. The result for the licensor is the same.

In silicon and AI, the leaks are larger and harder to see:

  • Overbuilt chips. A fab or assembler can build more units than ordered and sell the extras. Researchers have studied this overbuilding risk for years; the licensor of the IP inside never learns those chips exist.
  • Silent reuse. A licensed block goes into a second product line the agreement never covered.
  • Gray market units. Parts leak out of authorized channels and are counted nowhere.
  • Per-machine software. Software licensed per machine runs on more machines than the license allows, and nobody outside the operator can count them.

Why audits do not close the gap

An audit checks the licensee's own records, so it can only find what those records contain. It is late, often years after the fact. It is expensive, so many licensors never use the audit right they negotiated. It is adversarial, and can sour a relationship worth more than the shortfall. And it is blind to what was never recorded: an overbuilt chip appears in no ledger.

Let the silicon do the counting

If every licensed unit carries an identity that cannot be copied, the count stops being a report and becomes a fact. At UBIQS that identity is silicon-intrinsic with no stored secret: silicon-proven, patented, and backed and validated by the U.S. Army. A unit that was never enrolled has no way to fake an enrollment.

  1. Enroll at the source. Every unit built with the licensed IP is enrolled at the fab or assembler, with its identity, origin and lot, so each unit is counted exactly once.
  2. Prove before it runs. At activation and in the field, the unit proves it matches its enrollment. An overbuilt unit, a cloned part or a deployment beyond the license cannot, so it is refused or flagged.
  3. Count live. Licensed, enrolled and activated units sit side by side, as they happen, not in a spreadsheet months later.
  4. Extend to machines. Where software is licensed per machine, each machine in our distributed AI inference network proves its identity, so seat counts come from the hardware rather than the operator's word.

Good for both sides

Verified counting helps the honest licensee as much as the licensor. The licensor is paid on every unit actually built and activated, sees overbuilt and cloned units flagged, and can offer usage-based terms with confidence. The licensee pays for what it uses with no surprise back-billing, sees the same numbers so invoices are never in dispute, skips months of audit document requests, and gets its own product protected from counterfeits.

Licensing ran on trust because there was nothing better. Now the silicon can keep the count.

Sources

Keep reading

Related

Licensing chip IP, designs or per-machine software?

We're talking with licensors and licensees who want a live, verified count instead of a spreadsheet and an audit.