ISOHub

CAP (Continuous Assurance Protocol) · your AI chat is the workbench, ISOHub is the evidence

Continuous assurance platform for medical safety work.

Do the work in the AI chat you already use. Figures come from a versioned deterministic engine rather than a model's arithmetic, every act is hash-chained to the person, client and model behind it, and every artefact carries a provenance dossier you can hand an assessor.

Start free Try the live demo

Deterministic engine · hash-chained provenance · signature evidence · SSO · row-level isolation on every table

Show me the conformance posture for the cobot cellWhich ISO 10218 clauses are still uncovered?Diff v13 and v14 of the EPS snapshotList every requirement derived from HAZ-CC-003Who signed the last release, and when?What breaks if I change the torque limit?Build the provenance dossier for the safety conceptRun SISTEMA on the guard-door functionShow me the conformance posture for the cobot cellWhich ISO 10218 clauses are still uncovered?Diff v13 and v14 of the EPS snapshotList every requirement derived from HAZ-CC-003Who signed the last release, and when?What breaks if I change the torque limit?Build the provenance dossier for the safety conceptRun SISTEMA on the guard-door function

Natively connected to the clients your engineers already use

ClaudeChatGPTCursorGeminiCopilotWindsurf

Everything the record needs, on one platform

Not a document store with a chatbot bolted on. The objects, the graph and the audit trail are the product; documents are just one rendering of them.

Assessor-ready provenance

Every artefact answers the three questions an assessor asks: who or what produced it, what supports its correctness, where its trace originates. One call returns the dossier — acts, models, hashes, signatures, refusals, and the gaps stated plainly.

Deterministic, not generated

PL, PFH, SPFM, PMHF, cut sets and CCF come from a versioned engine with an input hash and a result hash — never from a model's arithmetic. Missing an input is refused, not assumed.

Assurance as code

Requirements, hazards, analyses and claims are schema-backed objects with stable identity — not paragraphs in a document. Render any view you need from one source.

Architecture as code

A machine-readable graph links functions, components, interfaces and failure modes, so impact and traceability are queries rather than workshops.

An immutable record

Every change is a signed commit with a hash chain, a derivation record and the client, model and route it came through. Rollback is a move, never an edit.

Agentic · CAP over MCP

One endpoint. Eight tools. Answers that draw themselves.

Paste the CAP endpoint into Claude, ChatGPT or Cursor and your project becomes something an agent can read, check, diff and — with a signature — change. Tool output carries render blocks, so posture comes back as a chart and requirements as a table.

Open the live demo

ISOHub · CAP over MCPread-only demo project8 tools connected

Connected over CAP (Continuous Assurance Protocol). Ask about a project's posture, requirements or snapshot record.

Stop writing the evidence. Start holding the record.

Agents propose, your qualified engineers ratify, and the chain proves who did which — down to the client and model that drafted it.

Start free See it answer