ProductUri
The ProductUri identifies the software product rather than the running instance: every copy of the same product carries the same ProductUri, assigned by its vendor. It appears in the ApplicationDescription exchanged during discovery and in the BuildInfo structure under the Server object, alongside ProductName, ManufacturerName, SoftwareVersion and BuildNumber.
Product versus instance
ApplicationUri answers which installation this is; ProductUri answers what software it is. Only ApplicationUri is checked against the certificate, so ProductUri is free-form vendor metadata - it is never a security control and never unique per device. Vendors normally use an http URI under their own domain, and change it only when the product itself is different, not on version bumps.
Where you read it and why you would
Browse Server, then ServerStatus, then BuildInfo, and read ProductUri, ProductName, ManufacturerName, SoftwareVersion, BuildNumber and BuildDate. That structure is the single best fleet-inventory read in OPC UA: one call per server tells you what software each device is running, which is what you need before a firmware campaign, a CVE assessment or a compatibility check across a plant.
Example
BuildInfo, read from the Server object
Server / ServerStatus / BuildInfo
ProductUri http://vendor.example/UAServer
ManufacturerName Vendor AG
ProductName Vendor UA Server
SoftwareVersion 3.2.1
BuildNumber 4471
BuildDate 2026-03-11T09:14:02Z
ProductUri is identical on every device running this software.
ApplicationUri (urn:plc01:Vendor:UAServer) is not.Defined in: Part 4 - Services for the ApplicationDescription; Part 5 - Information Model for BuildInfo under the Server object.
Last verified 7 September 2026 against OPC UA 1.05.07. OPC UA Connect is an educational resource and is not affiliated with the OPC Foundation.