NOOSChain for supply chain

Each shipment gets a single history
everybody can verify.

NOOSChain is a permissioned blockchain for supply networks. It records custody, condition, and compliance events as a shared, cryptographically verifiable history. Every participant checks the record independently. No central gatekeeper.

Get Started Read the documentation
Built for real-world collaboration Open interfaces — public SDK & HTTP API
The problem

Multi-tier supply chains fail on trust, not on data.

Your ERP knows what happened inside your four walls. It knows nothing about your tier-2 suppliers. It cannot tell you when the cold chain broke, or whether the certificate your logistics partner sent is the one the regulator will accept. Each party keeps its own version of events. The version that wins belongs to whoever is biggest — not whoever is right.

Reconciliation disputes

Disputes between OEM, suppliers and logistics providers that no one can settle with evidence.

Paperwork, not proof

Serialization and traceability obligations (pharma, food origin, luxury authenticity) met with paperwork instead of proof.

Blocked data sharing

Data-residency and confidentiality rules that block the data sharing your network actually needs.

Pilots that die

Blockchain pilots that die between the PoC and production.

Why NOOSChain

A blockchain built for collaboration between known organisations.

NOOSChain turns distributed trust, control and accountability into a practical system for supply networks — without removing the boundaries organisations need.

01

Shared truth without central control

Every participant gets one verifiable history. No single party owns it. That kills the classic project-killer: the "who hosts the system of record" deadlock between OEM, suppliers and logistics providers. And the history is tamper-evident by construction: validator admission, suspension and voting power are on-chain governance transactions — membership is governed, not staked — and every node verifies the recomputed block hash and state root before persisting anything.

02

Governance built into the system

Membership, permissions and state changes are explicit, signed and auditable from the start. Onboarding a supplier becomes a governed act, not an email thread.

03

Sensitive data stays controlled

Verifiable chain state is separated from encrypted payloads. The network proves an event happened; only authorised parties read the content behind it. Suppliers share proof without exposing commercially sensitive detail.

04

Shared rules run on-chain

Deterministic smart contracts give every validator the same authorised logic on the same ordered state. Cold-chain excursion thresholds, quality gates, retention rules — encoded once, executed identically everywhere.

05

Computation runs where data lives

Authorised analytics and AI workloads travel to the data's home node. Run cross-network analytics without shipping another party's data across borders.

Capabilities

What it gives a supply chain network.

Decide who can act, what data can travel, and how every node responds — without forcing every piece of data into every location.

01 / Protect

Per-record and per-bucket encryption

Suppliers join the network without exposing pricing or process data to competitors on the same chain.

Solves
  • Over-sharing across consortia
  • Unclear access boundaries
  • Sensitive data in shared infrastructure
02 / Place

Policy-driven replication

Replication rules decide which nodes receive or retain payloads. Data can travel to approved participants, stay with its source, or be selectively available while its proof stays shared. Your Mexican plant's data stays where the law says it must.

Solves
  • Data-residency constraints
  • Unnecessary copies and exposure
  • Different retention obligations
03 / Execute

Deterministic smart contracts

Compliance logic the auditor can replay.

Solves
  • Rules interpreted differently by each party
  • Manual multi-party workflows
  • Opaque automation
04 / Compute

Data-local workloads

Authorised scripts and container images travel to eligible nodes and run against protected bucket data inside the environment where that data is allowed to live.

Solves
  • AI without exporting source data
  • Cross-organisation analytics
  • Unverifiable processing results
The outcome

Participants agree on what happened, reveal only what each party may see, store data only where it is allowed to live, and bring approved computation to the data itself.

Use cases on the chain

Four industries.
One shared history.

Every use case below runs on the same governed record — provenance at each custody change, and proof without exposure.

01

Pharmaceutical serialization & traceability

Record every custody transfer and compliance event from API to pharmacy. Manufacturer, wholesaler, logistics provider and regulator each operate a node that validates transactions. The audit trail is the chain, not a PDF bundle. And where other traceability vendors stop at the ledger, NOOSChain adds data locality: residency rules decide where each payload may live, and compute-to-data brings approved analytics to the plant's data instead of forcing an export. The certificate the regulator accepts, without the data leaving the jurisdiction it must stay in.

02

Food origin & condition

Producers verify origin. Logistics records condition events. On-chain rules flag a cold-chain excursion the moment it happens — not at the delivery dispute.

03

Luxury & high-value goods authenticity

Provenance is recorded at each custody change. Brand, customs and buyer verify it independently, with no single party holding the master record.

04

Multi-tier supplier compliance

Certificates, audit results and quality events are recorded once and shared precisely. The OEM sees what it is entitled to see. Tier-2 competitors on the same network see nothing they shouldn't.

Compute-to-data

The computation moves.
The protected data stays.

For analytics and AI on network data, package the workload as a signed script or container image. NOOSChain authorises it, routes it to eligible nodes, and records the results on-chain.

01

Register

Publish a signed workload with an immutable script or container-image digest.

02

Authorise

Approve its identity, buckets, purpose, runtime limits and output policy.

03

Route

Select nodes that hold the required data and are permitted to execute it.

04

Run locally

Query protected buckets inside the node's controlled execution environment.

05

Record

Commit execution status, results, artifacts and provenance to the blockchain.

Authorising a workload does not authorise its creator to read the underlying data. Access is scoped to the signed workload, selected buckets, eligible nodes and its execution policy. Use it for demand forecasting across supplier data, quality validation, and compliance workflows with a verifiable execution trail. Commercially sensitive source records never leave their authorised environment.

Read the guide
Next step

Let's get started.

NOOSChain is our product. We designed it, we run it in production, and we know exactly where it fits. Whatever you're moving — shipments, clinical data, AI pipelines — bring us the problem and we'll design the network around it.

Book a meeting
  1. 1

    Evaluate locally

    Start NOOSChain with Docker and inspect the node using the CLI and Web UI.

    npm run docker:up
  2. 2

    See it live

    The Web UI is public — real chain height, live blocks, a data explorer. See the chain move before you talk to anyone.

    Open the Web UI
  3. 3

    Design your network

    Define organisations, validators, access rules and the deployment model — with us, when the collaboration model is clear.

    Book a meeting
Why us, for this problem

Built in production, not pilot theatre.

Noosware builds NOOSChain as proprietary infrastructure used across its own EU Horizon projects — including MARS, digital twins and AI for SME supply chains. The product is scoped through discovery, validated early, and designed for production deployment, not pilot theatre. It supports use cases from enterprise to EU-driven initiatives that require more than experimentation.

Ready to start?

Put one verifiable history
under your supply chain.

Book a meeting