Ourbits builds open technologies for representing, connecting, and verifying the lifecycle of physical products and assets.
We are working toward an interoperable infrastructure where a product can carry trusted context across its lifecycle:
Purchase → Ownership → Maintenance → Claims → Resale → Refurbishment → Recycling
The goal is simple: product information should not disappear every time ownership, service, or lifecycle state changes.
Ourbits focuses on the infrastructure layer behind circular product ecosystems.
Open data models for representing physical assets, their identifiers, ownership, lifecycle events, evidence, and claims.
Structures and APIs for maintaining a continuous record of what happens to an asset throughout its useful life.
Mappings and integrations with established standards and protocols, including the UNTP ecosystem, rather than creating another isolated standard.
Mechanisms for establishing provenance, evidence, data integrity, and verifiable lifecycle events.
Technology that enables trusted handoffs between consumers, brands, service providers, resellers, refurbishers, recyclers, and other participants.
We believe circular economy infrastructure should be built around continuity and interoperability, not isolated applications.
A receipt should be useful beyond the purchase.
A warranty record should be useful during a claim.
A service history should improve resale confidence.
A product identity should survive ownership transfer.
A verified recycling event should become usable evidence.
Ourbits connects these pieces through shared models and infrastructure.
The Ourbits Asset Model is our foundation for representing physical assets and their lifecycle.
It is designed around concepts such as:
Asset
├── Identity
├── Ownership
├── Product information
├── Lifecycle events
├── Evidence
├── Claims
├── Service history
├── Condition
├── Provenance
└── Verification
The model is intended to be extensible and interoperable with existing standards rather than replacing them.
Ourbits is designed to work with existing standards and emerging digital product infrastructure.
We are particularly interested in the UNTP ecosystem and related standards for digital product passports, credentials, identifiers, and interoperable supply-chain information.
Our goal is not to create another competing passport standard.
Instead, we are building infrastructure that can:
- Represent richer asset and lifecycle information.
- Map Ourbits data to relevant standards.
- Consume and produce interoperable credentials and passport information.
- Extend consumer and lifecycle workflows around standardized product data.
The Ourbits organization contains focused repositories rather than one monolithic codebase.
| Project | Purpose |
|---|---|
| Asset Model | Open model for physical assets and lifecycle information |
| Asset Core | Core libraries and primitives for asset lifecycle infrastructure |
| Interchange | Data exchange and interoperability components |
| Passport | Digital product and asset passport infrastructure |
| Verification | Provenance, evidence, and verification components |
| Integrations | Connectors for standards and external systems |
Repository names and scopes may evolve as the architecture develops.
Ourbits infrastructure is designed to support products with different users and use cases.
Consumer ownership and post-purchase intelligence.
It organizes receipts, product information, warranties, maintenance records, and related evidence into a persistent product record.
AI-powered warranty and support workflows that can operate on structured product and ownership information.
The system is designed around claims as structured events rather than treating email as the underlying system.
A future trusted second-life commerce layer using product history, ownership evidence, condition, warranty information, and lifecycle signals.
Tools for brands and operators to work with product identity, claims, lifecycle information, buy-back workflows, compliance preparation, and circularity programs.
The long-term architecture separates infrastructure from applications:
Standards & Protocols
│
▼
┌─────────────────────┐
│ Ourbits Platform │
│ │
│ Asset Model │
│ Identity │
│ Lifecycle Data │
│ Evidence │
│ Verification │
│ Interoperability │
└──────────┬──────────┘
│
┌──────────────┼──────────────┐
▼ ▼ ▼
HoldMyBill Brand Systems Resale
│ │ │
└──────────────┼──────────────┘
▼
Circular Product Lifecycle
The applications remain focused on their users while sharing common infrastructure underneath.
Circular product ecosystems involve many independent organizations.
Manufacturers, retailers, consumers, service providers, resellers, refurbishers, recyclers, auditors, and regulators all need different systems to communicate with each other.
Closed infrastructure creates another silo.
Open models, APIs, reference implementations, and interoperability tooling can help create a common technical foundation without requiring every participant to adopt the same application.
Our current engineering focus is on:
- Asset data modeling
- Lifecycle event modeling
- Evidence and provenance
- Passport infrastructure
- UNTP interoperability
- Verification and trust
- Developer tooling and APIs
The infrastructure is being designed to support consumer applications today while remaining capable of supporting brand, compliance, resale, refurbishment, and recycling workflows later.
We welcome contributions around:
- Data models
- Standards mappings
- Interoperability
- APIs
- Rust libraries
- Verification
- Developer tooling
- Reference implementations
- Documentation
If you are working on digital product passports, asset identity, circular economy infrastructure, product lifecycle data, or related interoperability standards, we would like to hear from you.
Website: https://ourbits.io
GitHub: https://github.com/ourbits
Documentation: Coming soon
Individual repositories define their own licenses. Check the repository documentation before using or distributing a component.