What you bought, what is on the rack.

The problem we were given

Finance had purchase orders. Operations had serials on the rack. Licensing had smart accounts, virtual accounts, leftover keys, and term licences that start when the box ships, even if the account assignment is still wrong. Air-gapped plants cannot phone home on every check. The three pictures never matched.

What our engineers built

Document intake plus a reconcile engine on Foundation, next to the customer licence manager, including the on-prem replica where the network is pulled.

Purchase orders, invoices, packing lists and agreement PDFs are read with citation back to the page. The engine matches order line to serial to account to entitled versus consumed. Exception queues for holding-account leftovers, term licences ticking before assignment, and over-consumption.

Immutable audit: who asked, which document, which match, which exception. No licence file or serial dump leaves the room.

What it is not

It does not replace the vendor licence portal. It does not open a vendor support case by itself. A human still files the mismatch.

Why the cloud answer fails here

Serials, contract vehicles and air-gapped estates do not belong in a public prompt. Some networks must not talk to a vendor cloud except on a schedule. A copilot in another region cannot sit next to the on-prem licence replica.

Controls in this workflow

These controls run on Private AI Foundation. Every ask goes through the same path.

• Work stays inside the customer perimeter. Inference does not require a network path out.
• You hold the encryption keys in every tier that touches your data.
• Every ask goes through the Model Gateway. There is no side door to a public model.
• Policy and DLP evaluate the request before weights run.
• RBAC names who may invoke which model class on which data class.
• Each step writes confidence and a citation back to the source. Originals are preserved.
• Consequential actions wait for a named approver. Nothing silent-posts to your core systems.
• Immutable audit is written on the same install: who, what, which model, which policy, outcome.
• Apache 2.0 and MIT weights only. Licence text and an SBOM ship on disk per release.

The paid proof of value

Thirty to forty-five days. Fixed fee. In the customer environment. One virtual account or one country estate. Success criteria and conversion price agreed in writing before starting.

Success is unmatched serials below an agreed threshold, ageing on holding-account lines made visible, and zero licence data egress. If it misses the threshold, the customer keeps the report and owes nothing further.