Private BioChain provides a dedicated BioChain environment for an organisation, programme or consortium. It's intended for evidence chains involving multiple systems, teams or organisations where provenance needs to survive beyond the boundary of any one application. Your existing operational systems remain in place — The BioChain becomes the shared provenance and integrity layer between them.
Your organisation's own systems and your partners' systems each continue operating exactly as they do today. A Private BioChain deployment sits alongside both, recording the provenance relationships between them without requiring either side to migrate data or change how their systems work day to day.
Shared provenance
Operational data remains within the systems authorised to hold it. The BioChain records the identifiers, integrity references, attestations and provenance relationships required by the deployment — not the underlying laboratory results, commercial terms or sensitive datasets themselves. Each participant keeps its own systems, its own access controls and its own data-protection obligations exactly as they are today.
That is the default rather than the only arrangement. Where an organisation or consortium would rather The BioChain held some of that data — because no suitable system exists for it, or because a shared programme needs neutral ground that no single participant owns — hosted storage is available within the deployment, with backup and recovery options alongside it. Moving data is an option, not a requirement.
A dedicated chain can serve one organisation, a programme, or an approved consortium of several independent organisations. Participants can retain their own systems and their own data responsibilities while contributing to a shared provenance history — the same deployment model works whether it's a single company connecting its own internal systems, or a group of laboratories, partners and suppliers who have agreed to make their evidence chain jointly verifiable.
There is no published price list, because no two Private BioChain deployments are the same. A single organisation connecting two of its own systems and a consortium connecting twenty independent organisations across several jurisdictions are different pieces of work, and one figure would misrepresent both.
What a deployment involves depends on how many organisations are being connected, which systems they already run, how much evidence moves between them, whether data stays in existing systems or is hosted, and what the resulting provenance has to prove. More than one commercial model is available, so the arrangement can follow how an organisation or consortium actually wants to fund the work rather than being forced into a single shape.
The practical starting point is a conversation about the evidence chain itself. Once the organisations, systems and provenance questions are clear, the scope and the commercial model follow from them.
Tell us about the organisations, systems and evidence involved — we'll help you work out what a dedicated deployment would need to look like.
Client deployments are confidential by design. See The Ancient BioChain for the same architecture running in the open.