Industrial DPPs Without an Internet Resolver: QDat.io On-Premise, Privacy by Design

Industrial DPPs That Work Offline: Product Passports for Corporate Assets Without a Resolver

The European DPP regulation was written with batteries, textiles, and consumer electronics in mind — products that move through retail channels and end in households, where a phone tap and an online resolver are reasonable assumptions. Industrial assets break those assumptions.

A wind turbine in the North Sea. A submarine valve manifold on a 30-year overhaul cycle. A switchgear cabinet in a mining substation 400 km from the nearest cell tower. A motor on a steel mill that nobody plans to retire before 2065. None of these can depend on a brand-operated online resolver to deliver their DPP — not when the network is gone, not when the brand has been acquired three times, not when the asset outlives any single vendor's commercial interest in keeping a redirect alive.

For corporate assets, the DPP has to survive offline, without an Internet resolver, and for decades — and every read, write, and audit query must stay within the operator's perimeter. The resolver still exists; it just runs on-premise, on infrastructure the operator owns.

What the EU mandate doesn't say out loud

The ESPR text is centered on a consumer-grade interaction model: the article is in the consumer's hand, the consumer scans, a server somewhere answers. Industrial buyers — utilities, refineries, mines, fleets, defense, infrastructure — live in a different operational reality.

A DPP that returns "host unreachable" at the moment the regulator, the inspector, or the maintenance team needs it is no DPP at all. For industrial assets, the data has to be on the tag, the chip has to be the source of truth, and the operator's local infrastructure has to make sense of it without Internet.

NFC NDPP — the URL (and the data) live on the tag

The NFC Forum Digital Product Passport (NDPP) standard was designed for exactly this constraint. The relevant DPP content — URL, structured record, signed claims, dismantling instructions, compliance certificates, repair history — lives in the tag's NDEF memory and adjacent on-chip storage.

Operationally, this matters because:

For corporate assets, this is the defining property: the DPP is portable with the asset, not tethered to a third-party network resource that may be gone before the asset is.

Spatiotemporal resolution — operator-owned, network-optional

The companion mechanism is spatiotemporal resolution, reframed for the industrial context. The same architecture that lets a retail kiosk render a DPP for an anonymous shopper works for an offline maintenance crew on a refinery — and arguably works better there, because the operator already controls every reader on site.

In the industrial pattern:

1. A site-local RAIN or NFC reader sees the tag at a known location at a known time, captures EPC, sensor payload, and any NDPP record present.

2. The read is published to a site-local instance of the [Spatiotemporal Intelligence Automation Plane](/blog/spatiotemporal-intelligence-automation-plane). This may run on an edge box, a vehicle, a maintenance laptop, or a regional data center — but it does not require the public Internet.

3. DPP context is resolved from local state plus on-tag content. The technician's tablet, the supervisor's dashboard, the auditor's checklist all render from infrastructure-side state — not from a request to a brand-operated resolver.

4. Sync happens opportunistically. When the site has a network window — a satellite pass, a return to base, a scheduled upload — events flow upstream to the global plane. Until then, every read, every event, every signed record is locally valid and locally authoritative.

The network is not in the critical path.

QDat.io as the on-premise resolver — local round-trip, operator-owned privacy

The DPP architecture has always assumed *some* resolver — a server that takes the URL on the tag and returns the structured content the URL points to. The conventional assumption is that the resolver lives on the public Internet, run by the brand, the regulator, or a marketplace operator. It does not have to.

QDat.io can run as the resolver — on-premise.

The practical implication: for a corporate fleet operator running 50 vessels, 200 substations, or 10,000 racks, there is no day-one Internet dependency to engineer around — and no day-one telemetry leak to a brand resolver. Each site has its own QDat.io resolver, each chip's URL routes to its site's resolver, and the global picture is reconciled when bandwidth permits.

Why corporate assets need both

NFC NDPP gives the operator a chip that is independent of any one vendor's online infrastructure. Spatiotemporal resolution gives the operator a way to assemble those chip-resident facts into a coherent operational record without renting a brand's resolver. Combined:

The asset's identity, history, and compliance state travel with the asset itself, in physical custody of the operator who owns it.

Concrete scenarios

Where QDat.io fits

QDat.io plays two roles at once for industrial DPPs:

The RAIN side (CoolTag, multimodal RAIN+NFC tags) provides bulk readability across pallets, racks, yards, and portals. The NFC side hosts the NDPP record — signed at commissioning, lockable, readable by any handheld. The plane consolidates reads locally first, then syncs upstream — so the operator never depends on the public Internet to maintain operational truth.

When a regulator, auditor, or maintenance technician reads a chip on the asset, the URL routes to the local QDat.io instance — not to a brand resolver, not to a regulator's portal, not to a third-party aggregator that may have changed hands twice since the asset was commissioned. Because the resolver lives inside the operator's perimeter, every consultation is also a privacy event the operator owns: no third party sees who read what, when, or where.

Getting started

The lightest industrial DPP pilot starts at one asset class and one site:

In every case the asset's DPP is present, valid, and operator-controlled — without depending on a network that may not be there.

Book a demo to see how an offline-first industrial DPP looks in practice.