An engineer reviewing a bowtie risk diagram in the Bowtie Risk Engine editor on a desktop monitor.
About us

Australian-built risk software for the people who carry the consequences.

Bowtie Risk Engine is designed and built in Australia for the engineers, safety professionals, and consultants who own critical risk — and answer for it when it matters.

IEC 31010· CCPS Process Safety· ICAO Doc 9859· ISO 14971· RCM / Asset Integrity

Our mission

To make critical risk legible — to give the engineers who own a hazard a single, honest model where the diagram everyone can read and the evidence an auditor demands are the same living artefact, kept in lock-step revision after revision.

A bowtie communicates risk at a glance. The register behind it — every control with its criticality and the conditions that can defeat it — is what survives scrutiny. Our mission is to make sure those two things never drift apart, so the picture you present and the proof you defend are always the same.

Proudly Australian

Bowtie Risk Engine is designed and built in Australia by a small team here. We price in Australian dollars, we support customers in Australian business hours, and the product is shaped by the high-consequence industries this country runs on — resources and process plant, aviation, healthcare, and critical infrastructure.

Being built in Australia also means we build for the world. The method follows international practice — IEC 31010, CCPS, ICAO Doc 9859, ISO 14971 — so the outputs speak the language reviewers expect wherever your work is read.

Bowtie diagram for loss of containment of flammable hydrocarbon, showing threats and preventive controls on the left, the risk in the centre, and consequences with recovery controls on the right.
One model — the picture and the proof, drawn the way engineers think

The problem we set out to solve

Bowtie analysis is one of the clearest ways to communicate risk: a single diagram captures the hazard, what could cause it, what could follow, and the controls in between. Auditors read it. Operators read it. Boards read it. But too often the diagram lives in one tool and the control register lives in a spreadsheet in another — re-keyed, and out of date by the next revision.

What we're building

A focused application where the diagram and the register are one model. Draw the bowtie; the register follows. Change a control; the export updates. Risks, threats, preventive and recovery controls, degradation factors, and consequences are first-class — modelled the way practitioners are taught, exported the way reviewers expect.

Who it's for

How we're licensed

Bowtie Risk Engine is commercial, licensed software on an annual subscription, for one practitioner or a whole site. That model lets us support the tool properly and keep investing in it. See pricing for the details, or request a demo to see it on your own scenarios first.

Where this is going

The roadmap is shaped by what licensed users ask for: deeper register analytics, shared libraries of control types, team workspaces, and integrations with adjacent risk tooling. If there's something your workflow needs, tell us — that's how this gets better.

Founder

The person behind it

Evren Gokkaya

Founder

Bowtie Risk Engine was built with the ongoing input of two process safety and risk management engineers, whose feedback shaped the editor from its earliest versions. I am an engineer by background rather than a risk practitioner, which is exactly why their input mattered. Much of how the tool works today comes directly from what they needed in practice, building a product that holds up in the pace of a live workshop and the scrutiny of an audit.

See it on your own risks.