Shipped, live, and independently verifiable.
The three criteria in the Innovator Founder assessment — Innovation, Viability, Scalability — are backed by a production platform. Every claim below links to a live endpoint you can interrogate without ResilienceChain credentials.
The UK Cyber Security and Resilience Bill 2026 extends incident-notification and cross-sector resilience obligations to thousands of supervised entities — NHS trusts, critical national infrastructure operators, financial services firms. Every one of them must now prove, in writing and on time, that a cyber incident was detected, contained, reported to the right regulator, and coordinated across organisational boundaries: their MSP, their supply chain, their insurer, the regulator itself.
Today, nobody’s evidence chain survives the handoff. Incidents fire in the SIEM; evidence scatters across EDR, Slack screenshots, emails, and PDFs. Cross-tenant coordination happens by attachment. Regulators cannot independently verify that a reported timeline is the real timeline.
ResilienceChain is the cross-boundary cyber custody chain that closes this gap.
- 1Third-party time-anchored hash chain
The chain does not just prove 'these events have not been rewritten since they were written' — it proves 'these events existed by wall-clock time T'. Any auditor with the TSA public certificate can verify offline in 30 seconds.
- 2Open Evidence Schema with a conformance badge programme
Every payload ResilienceChain produces is defined in a published JSON Schema under CC-BY-4.0. Partners self-certify with a public CLI and earn the rc-conformant badge. An RFC 8615 discovery manifest lets any crawler find the specs.
- 3Federated threat-intelligence correlation with k-anonymity
Opted-in tenants contribute IoC observations to an aggregation that surfaces matches only when ≥3 tenants have independently seen the same indicator. Tenant identities never cross the API boundary.
- 4Cross-tenant AI triage, personalised per customer
Claude Sonnet 4.6 produces structured triage plans gated by Claude Haiku 4.5. Each tenant's prompt is augmented with their 3 most similar past resolutions (RAG over a private knowledge corpus). Triage quality compounds with platform usage — switching to a competitor resets the curve.
- Live production platform — self-serve signup, 5 AI agents, hash chain, TSA anchors, 4 regulator templates
- 18 weeks of solo delivery, forked from CustodyFlow (prior medical-equipment custody chain shipped to UK NHS trusts 2024–25)
- UK-hosted on GCP europe-west2 with Cloud SQL Enterprise — UK data residency baked in for regulated buyers
- 46 database migrations live, 7 published schemas, 4 regulator-pack templates, demo tenant receives synthetic Sentinel alerts every 5 minutes
- Infosecurity Europe 2026 Cyber Startup Award application in flight; NCSC For Startups alumni reopen tracked for 2027
- Public CLI at
npx @resiliencechain/conform— any partner can self-certify against the open spec
Every new opted-in tenant raises cross-tenant IoC match density; every closed incident personalises that tenant’s AI triage; every partner that earns the rc-conformant badge raises the cost of switching to a non-conformant competitor. The platform becomes more defensible with every customer.
Endorsement under the Innovator Founder criteria
Innovation, Viability, Scalability — each is supported by shipped, independently verifiable product alignment with UK regulatory priorities. Every claim in this document links to a live endpoint. Every schema, spec, and protocol is openly licensed and machine-readable.
Endorsing body pack: market sizing, three-year P&L, competitive landscape, team plan, evidence index. System architecture: cryptographic integrity layer, AI pipeline, forward roadmap (BYOK + multi-party ZK).