Give every object one verifiable identity.
io2p gives any real-world object — a part, a product, a document, a device, a building — one tamper-proof digital identity. Data that’s scattered across systems, vendors and lifecycles finally collects in one place.
/00 — the problem
The physical world’s data is scattered and trapped.
A single object’s information lives across dozens of systems, vendors and file formats — each with its own IDs and silos. The same thing is re-entered and re-modelled over and over, and when it changes hands or reaches end-of-life, its history and its value disappear.
There’s no shared, neutral layer that says: this is the object, here’s its verified history, get it from the source.
today
one identity
/01 — what io2p gives you
Four primitives, one neutral foundation.
A protocol that proves provenance and integrity — and gets out of the way of every tool you already use.
One global identity for any object
Every object gets a unique identifier and a complete, verifiable history — instantly findable and traceable across tools, organizations and time.
Tamper-proof by design
Every change is recorded as permanent, verifiable history. Nothing can be silently rewritten — you always know who said what.
Federated, not centralized
No central database. Data stays at its source, with its owner. Discovery is shared across the network — you fetch from the source.
Truly open & permissionless
Open-source under MIT. No vendor lock-in, no usage fees, no gatekeeper. Networks set their own policy on top of a neutral protocol.
/02 — how it works
Three primitives. Any domain.
io2p is a vendor-neutral identity layer plus a federated discovery network. It stays model-agnostic — the same foundation serves any domain.
Object
Any single thing — with its own properties, values and files. A part, a document, a sensor, a material sample.
Composition
Objects assembled into larger objects, at any level of detail. Same primitive, recursive.
Process
Any input → output transformation, recorded as verifiable history with cryptographic signatures.
compose, don’t replace
Bridges IFC, Brick, BACnet and more — the standards you already use stay, io2p is the neutral glue between them.
/03 — what it unlocks
The compound effects of one shared identity layer.
Once every object is addressable and verifiable, a stack of capabilities collapses into primitives instead of products.
Model anything
Capture, link and reuse data from the smallest part to an entire portfolio — at any level of detail.
Works with your tools
Bridges IFC, Brick, BACnet and more — neutral glue, no costly re-platforming.
Ready for AI
Resolvable identifiers and verifiable metadata: trustworthy inputs for analytics, twins and agents.
Provenance built in
A complete history makes provenance, reuse and lifecycle reporting automatic.
Circular economy
Track material flows across owners and decades — turn buildings into verifiable resource banks.
Compliance, automated
ESG, embodied carbon, digital product passports — derived, not authored.
/04 — principles
Three lines we never cross.
Every object has one verifiable identity
Each object receives a unique identifier and a tamper-proof history, ensuring authenticity and consistency everywhere. io2p proves provenance and integrity — who said it, and that it's unaltered.
Open participation for everyone
Anyone can join a network by running a node. Reading is permissionless, and participation is open to any organization or developer. No central gatekeeper.
Interoperable and vendor-neutral
Data flows between different systems through open standards — preventing lock-in and keeping data sovereign at its source.
/05 — implementations
Built on io2p.
Networks building on the protocol — starting with the built environment, with more domains to follow.
IoM — Internet of Materials.
The flagship implementation, applied to the built environment: material identity, provenance and reuse, embodied-carbon and ESG reporting, and interoperability across BIM, ERP and IoT — turning the materials hidden in our buildings into a verifiable, circular asset.
Your domain next: build your models, run your network, on an open protocol.
/06 — who it’s for
Built for everyone who touches an object’s data.
One neutral layer, many vantage points — from the developer minting an identifier to the city tracking it for decades.
Developers & integrators
Build on an open standard with stable identifiers and verifiable data — no lock-in.
Platform & tool vendors
A neutral identity and interoperability layer between the systems you already ship.
Organizations & institutions
Sovereignty over your own data, with no central gatekeeper to depend on.
Circular economy & ESG
Track objects across their whole life — provenance, reuse and reporting, by default.
New-domain builders
Bring the protocol to your field: define your own models, run your own network.
Bring io2p to your domain.
Build your own models, run your network, contribute to the protocol — or just say hello and tell us what you’re working on.
/08 — questions