$ every product image on this site is an unretouched screenshot of the running platform — demo tenant, fictional people, captured live
⚖️ Platform · Reconcile

Expected vs actual.
Per grant, with a reason.

The engine at the heart of the platform: every run compares what access should exist against what actually exists in your systems — and explains every difference.

Drift, explained

Every difference carries its explanation.

"Expected via policy X" — "not expected, flagged for review" — "expected but missing". Reconciliation runs continuously and each grant's verdict is recorded as evidence, not just counted.

  • Per-grant reasons on every run — auditors get answers, not exports
  • Drift classified by kind: unapproved, missing, attribute drift, orphans
  • Per-connector drift policy: auto-fix, review, or keep
app.rapidvalue.eu/reconciliation
reconciliation — every difference explained
reconciliation — every difference explained

The control room

Writes you can watch, gate, and trust.

Provisioning runs in batches you can approve manually until you release the gate. Failures never disappear into a void — they land in a triage queue, grouped by cause, and retry is gated on an actual config change.

  • Batch approval per system (training wheels)
  • Failed-jobs queue grouped by failure cause, with a fix-config deep-link
  • Safety thresholds stop a runaway policy at the limit — not at your AD
…/provisioning
provisioning operations — batches, gated writes, triage
provisioning operations — batches, gated writes, triage

Related

See reconciliation running on your own data.

A 30-minute kickoff connects your HR feed and one system — working POC the same day.