Skip to content
avancerPI
Nutanix-focused by design · DR readiness & governance command centre

Recerta

Know you are ready before recovery becomes urgent.

DR readiness, evidence and governance — purpose-built for Nutanix. Recerta turns NCM Self-Service blueprint and runbook activity, together with Nutanix Leap recovery operations, into deterministic readiness, audit-grade evidence and controlled execution.

Three questions

The three answers nobody can produce during an incident.

Did DR happen?
Failover, failback, validation and sanity-test history reconstructed from actual runs, tasks, scripts and timings.
Are we ready?
Blueprint and application readiness assessed with deterministic rules, test recency and recovery-point currency.
Can we run safely?
Pre-flight checks, approval gates and separation of duties applied before any authorized DR action proceeds.
Operating flow

Discover to evidence, in one environment.

01

Discover

Find the blueprints, runbooks and recovery plans already in use across the Nutanix estate.

02

Capture

Record what actually ran — tasks, scripts, timings and outcomes — from real executions.

03

Assess

Coded rules evaluate historical outcomes, test recency and recovery-point age.

04

Explain

Plain-language answers to plain-language questions, grounded only in captured evidence.

05

Govern

Pre-flight checks, approval gates and separation of duties before any DR action proceeds.

06

Evidence

Consequential events linked by cryptographic hashes, plus a numbered operational ledger.

What Recerta delivers

Six things a DR programme can be held to.

Unified DR posture

Applications and blueprints classified ready, at risk or not ready — with the evidence behind each verdict.

Evidence-based readiness

Coded rules evaluate historical outcomes, test recency and recovery-point age.

DR run reconstruction

Captured NCM Self-Service and Leap activity becomes a readable sequence of recovery operations.

Grounded DR inquiry

Plain-language questions answered only from captured evidence.

Governed DR actions

Permitted actions routed through request, pre-flight, approval and controlled execution.

Tamper-evident audit chain

Consequential events linked by cryptographic hashes, plus a numbered operational ledger.

How trust is built

AI explains. Code computes.
Humans approve.

AI classifies questions and explains evidence. Deterministic code calculates readiness, timing and verdicts. Authorized people approve controlled DR actions. AI does not invent RTO or RPO results, decide readiness verdicts, or trigger failover. Offline-first: a locally hosted model keeps sensitive evidence inside your environment.

  • AI classifies and explains
  • Deterministic scoring engine
  • No LLM in the scoring path
  • Named approver on every action
  • Locally hosted model, offline-first
  • Evidence never leaves your estate
Live readiness

One score per domain, computed — not asserted.

Blueprint posture · 13 blueprints
Computed by rules, not asserted
4
Ready
2
At risk
7
Not ready
Evidence coverage100%
Recovery-point age · DC and DR1 hour
What the rules evaluate
  • Run outcome and historical success rate
  • Recency of the last successful DR test
  • Recovery-point age and RPO currency
  • Blueprint and application configuration
  • Whether enough evidence exists to support the conclusion at all

Figures are from an authenticated read-only review of avancerPI’s reviewed environment, not a customer deployment.

Every finding, every approval

An evidence chain built for the auditor who shows up unannounced.

Each consequential event is linked to the hash before it. Editing or deleting history breaks downstream verification — which is the only way a record proves anything.

Evidence chainSHA-256, append-only · chain verified
  1. #0041 · Requester · Operations

    DR action requested — sanity, payments-dr

    9f3a1c…82be
  2. #0042 · Recerta · deterministic

    Pre-flight passed — 5 checks, target site healthy

    e04d77…1a90
  3. #0043 · Approver · DR Governance

    Approval granted — requester could not self-approve

    c1289b…f34c
  4. #0044 · Recerta engine

    Executed and evidence captured — request closed

    5b6ea2…c701

Each row hashes its own content plus the hash before it. Editing or deleting history breaks every verification downstream — which is what makes the record worth anything. Sequence numbers and hashes shown here are illustrative.

The workspaces

Eleven places to look, one body of evidence underneath.

Recerta separates evidence from interpretation. The source facts are captured Nutanix events, tasks, scripts, output, timings and recovery points — deterministic code computes the posture, and the AI may summarize it but cannot change the numbers.

  • DR Posture

    The daily dashboard — ready / at-risk / not-ready roll-up, blueprint and run totals, site recovery points and recent runs.

  • DR Console

    Grounded natural-language inquiry. Questions about failovers, flows, Leap plans and readiness, answered from evidence and coded reports.

  • Blueprints

    Task and script evidence — browse tasks, explanations, the real scripts and the output they actually produced.

  • Applications

    System-of-record drill-down: application → run → task → executed script and stdout.

  • Runbooks

    The DR sequence reconstructed from captured evidence, as a phase and flow view with step-level explanation.

  • Recovery Plans

    Nutanix Leap visibility — plans by site, plus recent validate, migrate and test-failover jobs.

  • DR Actions

    Governed execution: raise, pre-flight, approve, execute or simulate, and capture the evidence.

  • Readiness

    Deterministic blueprint posture — verdict, instances, runs, success rate and last-success age.

  • Compliance

    The evidence pack — ISO 22301 and SOC 2-aligned reporting, coverage, RPO currency and the blueprint table.

  • Audit Chain

    Tamper-evident provenance — SHA-256-linked events and whole-chain verification.

  • Ops Ledger

    A numbered, filterable operational record of every action Recerta performed.

Before anything runs

Five pre-flight checks, and a requester who cannot approve themselves.

Non-disruptive checks require one sign-off; production cutover is designed for two distinct approvers. Hard failures block; soft issues warn.

  • The blueprint is not on the do-not-touch list
  • The target site is healthy and reachable
  • The recovery point is fresh enough
  • A recent passing sanity test exists, where policy requires it
  • No conflicting DR action is already in flight
Where execution actually is

What has shipped, what is in trial, and what is planned.

Recerta governs and evidences DR today. Live execution against a production estate is staged deliberately, and we would rather say so here than in the third meeting.

  • E1 · Request pipelineLiveRequest through simulated execution and evidence capture, with no mutation of the estate.
  • E2 · Live sanityIn trialA real, allowlisted NCM Self-Service sanity launch against a single test blueprint.
  • E3 · Failover and failbackPlannedProduction cutover with dual control, break-glass and abort.
By design

What Recerta is not.

  • Not an AI that invents RTO, RPO or verdictsDeterministic code computes readiness, timing and pass/fail. The model classifies questions and narrates results that were already calculated.
  • Not a replacement for NCM Self-Service or LeapIt organizes, explains, governs and evidences their DR operations. The automation you already run stays where it is.
  • Not an unrestricted write pathLive execution is master-switched, allowlisted and approval-gated — and evidence collection itself is read-only.
  • Not a general multi-platform DR orchestratorThe product is Nutanix-focused by design. If your DR does not run on Nutanix, Recerta is not the right fit yet.
Built around your Nutanix DR automation

Recerta connects what you already run.

It does not replace NCM Self-Service or Nutanix Leap. It connects their evidence, computes readiness from it, governs the approvals around it, and proves traceability afterwards.

  • NCM Self-Service blueprintsApplication-level DR automation, tasks, scripts and results.
  • NCM Self-Service runbooksRepeatable recovery, validation and operational workflows.
  • Nutanix LeapRecovery-plan activity, failover orchestration, protected-site context.
  • RecertaConnects evidence, computes readiness, governs approvals, proves traceability.avancerPI
Who it's for

Built for the people who have to prove readiness, not just claim it.

Infrastructure & DR leads

A current view of readiness across every protection domain and application.

Risk & compliance teams

Evidence-grade attestations that hold up to regulatory review.

Internal & external auditors

A tamper-evident chain of findings, remediations and approvals.

CIOs & CISOs

A single defensible readiness position instead of a quarterly slide.

Nutanix platform & NCM teams

Readiness that stays connected to the blueprints and runbooks that execute it.

Business continuity owners

Proof that failover and failback actually happened — not just that they were scheduled.

Built for Nutanix estates
Nutanix AHVNCM Self-ServiceNutanix LeapPrism CentralServiceNowSlack

Current product scope: Recerta is designed for Nutanix-based disaster recovery and is not positioned as a general multi-platform DR orchestration solution. Its strongest fit is an environment where NCM Self-Service blueprints and runbooks are already used — or will be adopted — for DR automation, with Nutanix Leap for recovery planning.

Turn disaster recovery into continuous readiness.

Bring us one business service and we'll show you exactly how Recerta captures, assesses and evidences its recovery.