Self-hosted hazard log

One golden thread.

Every hazard. Every control. Every piece of evidence.

One open, auditable, self-hosted place for the argument that each hazard is controlled. For fusion, nuclear and defence programmes, on-prem or air-gapped.

Under active development. The register on this page is illustrative data.

FWP-01Feed water pumping projectIllustrative

Hazard register

Showing 3 of 10 open hazards. Illustrative. Colour never stands alone.

Open hazards10
Intolerable residual1
Open actions4
Last baselineBL-03
RefHazardResidual riskStatus
HL-0042 Coolant line breach during bake Intolerable
In review
HL-0038 Shield block misaligned after maintenance Undesirable
Overdue
HL-0031 Monitor drift beyond calibration window Tolerable
Controlled

Overview

Hazard records live in spreadsheets, shared drives and email threads. The golden thread is lost. Sentinel Log holds every hazard in one living register and links hazard, cause, consequence, control, evidence and residual risk end to end. An audit trail stays with the record.

How it works

Linked end to end. Traceability is a first-class view, not an export afterthought. A living register, with baselines and a risk matrix you configure.

Hazard
Cause
Consequence
Control
Evidence
Residual risk
Hazard
HL-0042 Coolant line breach during bake
Cause
Weld defect on the bake-loop joint, found at the last outage.
Consequence
Loss of coolant to the bake circuit. Personnel and plant both exposed.
Control
CTL-011 Replace the joint before the next bake. Owner: mechanical.
Evidence
EV-088 Weld procedure and hold point, not yet verified.
Residual
Intolerable

One illustrative record. The argument is the links, not the score alone.

Inside Sentinel Log

Views of the living hazard record. These are screen grabs of the product. Select a grab to enlarge it.

Home

Signed in. Open hazards, actions due, and where to start.

Why Sentinel

Built for high-hazard programmes. You configure the product as data rather than forking the code.

  • Your infrastructureOn-prem or air-gapped. Docker or Podman Compose, with PostgreSQL, on Rocky, RHEL-compatible Linux or Ubuntu.
  • A defensible recordAn audit trail and immutable baselines stay with the hazard.
  • No lock-inOpen formats and stable IDs. Full export to xlsx, CSV and JSON. You own the data.
  • A 20-year support horizonDesigned to keep running, and to keep exporting, for the life of the programme.
  • Open by designApache-2.0. Releases ship a CycloneDX SBOM. Python, Django and PostgreSQL.
  • Checked each releaseDesigned for OWASP ASVS Level 2 and WCAG 2.2 AA.

Standards

Sentinel Log is specified to hold the hazard-log record these standards expect a tool to keep. Holding that record is not a certified safety case. The accountable person still accepts the risk.

  • MIL-STD-882EThe register keeps hazard status, controls, verification and the acceptance record through the life of the system.
  • Def Stan 00-056The log shows the control status of hazards, the evidence for them, and the risk estimate, and it can be updated as the design changes.
  • ASEMS SMP11The hazard log separates controls in place from controls still planned, and a closed entry keeps its justification.
  • HAZOP and FMEA/FMECAWhen a project uses those analysis types, the worksheet fields are part of the record: guide word and deviation for HAZOP, failure mode, effect and detection for FMEA/FMECA.

Coming next

Not in the first release. Off by default. None of these set a risk score, a ranking, or a review outcome.

AI drafting

A draft is written beside the record. A person approves it before it is saved. Adapters follow your allowlist.

Agent interface

An agent can read the register through an interface you switch on. A token names the agent, the projects it may reach, and when it expires.

Chat over your records

Ask what is in the register. Answers come from your own hazard data, not from a separate knowledge base.

Quality checks

The assistant can flag a gap in the record. A person decides what to do with the flag.

FAQ

Who owns the data?

You do. The product runs under your control. Full export with stable IDs keeps the records portable.

Where does it run?

On your infrastructure: Docker or Podman Compose with PostgreSQL, on Rocky, RHEL-compatible Linux or Ubuntu.

Can it work offline?

Yes. Designed for offline, air-gapped installation on isolated networks.

How do we get data in and out?

Import hazards, controls, evidence and actions from Excel or CSV. Export the full dataset to xlsx, CSV and JSON. Re-import your own JSON into an empty instance.

Can we tailor risk matrices and workflows?

Yes. Risk criteria, status labels and reference lists are data, admin-managed after handover. You configure the product rather than fork it.

What happens if we stop working with you?

You keep the software under Apache-2.0, your data in open formats, and the install you already operate. No lock-in.

About JG Systems Consulting

JG Systems Consulting Ltd is a systems engineering consultancy. We are engineers who build the tools we use: grounded in model-based systems engineering and systems architecture, open by default, and designed to run on your own infrastructure.

Software tools for engineering and safety teams. SysML v1 and v2. Sectors: aerospace, defence, space and launchers, and C4I. We work to ISO/IEC/IEEE 15288, 42010 and 29148, the INCOSE SE Handbook, and ARP4754A.

MBSESystems architectureSysMLAerospace and defenceSpace and launchers

Registered in England and Wales. Company no. 11910666. Established 2019. Based in Leeds.

JG Systems Consulting Ltd is Cyber Essentials certified.

Get in touch

If this is the register you need, email me. I will walk you through it on a call, on illustrative data. Then we can decide if you want it on your network.

It runs on your network. You keep the data. Export stays open.

support@jgsystemsconsulting.com

Look at the demo

JG Systems Consulting Ltd. Company no. 11910666. Leeds, United Kingdom.