The modules

License what you need. Grow when you're ready.

Each UniSentinel module is a complete product on its own — with built-in fallbacks where a counterpart is missing, and automatic data promotion the day you add it.

The ecosystem effect

Standalone first, stronger together

Cross-module integration is engineered, not implied. Every dependency is a named integration point with a defined fallback and a promotion path.

  • Buy one module: local fallbacks (simple lists, checklists) keep the full workflow usable.
  • Add a counterpart later: a guided wizard promotes your fallback data into the new module — with a dry-run preview.
  • Nothing re-typed, nothing lost: promoted records keep their history and links.
  • Events flow between licensed modules automatically — a completed task rolls up treatment progress; a submitted assessment updates compliance status.
Integration points
Risk ← scope entitiesCatalogLinked
Risk ← treatment tasksTasksLinked
Compliance ← self-assessmentsAssessmentsLinked
Audit ← risk-based planningRiskFallback
Hub ← cross-module widgetsAllLive

Adoption path

A typical rollout

  1. 01

    Start

    Pick the module with the most pain — most teams start with Risk Management or Compliance.

  2. 02

    Anchor

    Add Service Catalog so risks, audits and requirements scope against one real inventory.

  3. 03

    Execute

    Add Tasks & Activities so every finding, gap and treatment becomes tracked work.

  4. 04

    Oversee

    Add Management Hub when leadership wants the whole program on one executive dashboard.

Get started

See UniSentinel running on your terms

Book a 30-minute walkthrough. We'll map your program to the modules you need — cloud, on-prem Linux or Windows Server.

Every module works standalone. License only what you need — grow when you're ready.