RiskForge Studio

FTA and FMEA — deterministic and standard-compliant.

From your architecture and failure model: fault tree (IEC 61025), FMEA, prioritized cut-sets, common-cause and report. Three ways to the model — editor, chat or from source code.

Deterministic engines — they compute, they don’t guess.

The problem

FTA and FMEA by hand are slow and error-prone.

Safety analyses live in spreadsheets and drawing tools today — hand-maintained, hard to keep current, barely reproducible.

  • 01 Every architecture change breaks the fault tree — maintenance eats weeks.
  • 02 Cut-sets, common-cause and prioritization are curated by hand and go stale.
  • 03 Reviews stumble over inconsistent tables instead of real safety questions.
The core

Three ways to the model, one deterministic analysis.

How you reach the model is your choice. What comes out the other end is always the same: a fault tree per IEC 61025 and an FMEA — computed, not guessed.

How you reach the model is your choice. What comes out the other end is always the same: a fault tree per IEC 61025 and an FMEA — computed, not guessed. Editor Write in the Studio Chat Generate from prose Source code Pilot + The code path delivers more → FtaDSL / FmeaDSL mcsa + fta-render Fault tree IEC 61025 · SVG/PDF FMEA Table + report
all lead into FtaDSL / FmeaDSL → FTA + FMEA
Editor Live

Write in the Studio

Author the model directly on the Studio canvas as FtaDSL/FmeaDSL — structured, versionable, instantly checkable.

Chat Live

Generate from prose

rfChat produces the DSLs from your description. You state the case in words, the model takes structured shape.

Source code Pilot

Recover from code

rfRecover reconstructs the model from your source code. In pilot today — the entry point for existing codebases.

The target is the core: a fault tree (mcsa + fta-render) and an FMEA. The three ways are just how you get there.

What you get

Honestly staged: what ships today — and what’s coming.

Delivered — the FTA/FMEA core

Live

Real and live today.

  • Fault tree per IEC 61025 Symbology strictly per IEC 61025, as SVG and PDF — cleanly typeset, audit-ready.
  • Prioritized cut-set list Minimal cut-sets, ordered by relevance.
  • Common-cause list Common causes flagged systematically.
  • FMEA table Derived from the same model, consistent with the fault tree.
  • Final report A consolidated report for review and sign-off.
Differentiation

Why deterministic.

The analysis engines compute, they don’t guess. No black-box LLM decides your safety claim.

They compute, they don’t guess

Cut-sets, common-cause and prioritization are calculated — traceable back to the source.

Empty slot = finding

If something is missing from the model, it is reported as a gap — completeness instead of silent omission.

Reproducible, auditable

Same model, same result. Repeatable any time, defensible in every review.

Standards

Built for the standards context.

RiskForge Studio produces artifacts that have their place in the relevant functional-safety standards.

  • ISO 26262 Road vehicles
  • IEC 61508 Functional safety
  • IEC 62304 Medical software
  • IEC 61025 Fault tree analysis
Get started

FTA and FMEA, deterministic. Today.

Request Early Access or get in touch — we’ll show you the path from your model to a finished analysis.

0 / 250 words

Or directly: info@riskforge.studio