GOVERNATLAS / PRODUCT DOSSIER

SimpleRisk

SimpleRisk describes risk lifecycle tracking, policy and exception management, control testing and cross-framework mapping. It distinguishes its open-source Core from paid Extras and hosted/on-premises configurations; individual features need edition-specific review.

01 / CONTEXT & SCOPE

Understand the proposition.
Define the boundary.

The decision to make

Choose the minimum operating workflow before selecting Extras. A risk register is valuable when a mitigation owner can explain why a score changed and a reviewer can challenge closure. Keep the scoring method and evidence relationship explicit rather than accepting a heatmap as a complete decision record.

What this record does not establish

The homepage’s deployment-time, savings and broad framework statements are not independently measured. Free Core does not automatically include every listed paid capability. Verify the selected Extras, migration behavior, hosting responsibilities and ongoing support.

1 current source · 1 published assertion
Source coverage is a research boundary, not a quality score.

02 / YOUR EVALUATION

Turn interest into a useful trial.

Open the evaluation playbook ↗
A

A test worth running

In a proposed trial, import a small synthetic register with one duplicate and one missing owner. Link a mitigation to a control test, expire an exception and inspect the resulting report. Change a risk assumption and confirm that previous scores and rationale remain distinguishable after export.

GovernAtlas editorial proposal. We have not performed this test.

B

Evidence to bring back

  1. An imported risk/mitigation/test chain with historical scoring rationale.
  2. An edition/Extras matrix and a demonstrated exception-expiry and export path.

03 / DOCUMENTED EVIDENCE

Read the claim. Inspect the basis.

Each statement retains its classification and preserved source. A vendor assertion is not an independent test result.

01
vendor asserted

SimpleRisk describes risk lifecycle tracking, policy and exception management, control testing and cross-framework mapping. It distinguishes its open-source Core from paid Extras and hosted/on-premises configurations; individual features need edition-specific review.

Source, dates & preserved provenanceSimpleRisk — official current product scope ↗

Authority: vendor owned
Observed 2026-10-15 · Reviewed 2026-10-15 · current until 2026-11-14

Artifact SHA-256: 6253c29512bebe5911f5370b10b3c1a83417f478dcdc60ce8c008a1a3b1d8589

The hash identifies the preserved capture. The live source may have changed.

Source register

SimpleRisk — official current product scope ↗vendor owned · captured 2026-10-15
Brand asset provenance

Organization identity asset from its official website; inclusion does not imply endorsement.

Official website ↗ · Original asset ↗

04 / BEFORE YOU COMMIT

Better questions.
A clearer decision.

Resolve these with the provider and your own evaluation team.

01

An imported risk/mitigation/test chain with historical scoring rationale. Can this be demonstrated for the proposed configuration?

02

An edition/Extras matrix and a demonstrated exception-expiry and export path. Who owns and reviews this evidence?

03

Which version, modules, services and commercial entitlements are included?

Regulatory applicability requires a separate, current determination. Inclusion is not certification.

KEEP THE RECORD USEFUL

A dossier should stand up to scrutiny.

Have a source that changes this picture? Submit it for editorial review.

Raise an evidence issue ↗