What should be running, what is actually running, and the delta.
Release records say what was approved. Nobody can prove what is deployed where right now. ReARM closes the loop between plan and actual.
Instances and environments registered
Every instance and environment is a first-class object in ReARM, not a spreadsheet row.
↳ Deployment ModelPlan vs actual, continuously reconciled
Approved and expected state vs observed state, resolved side by side and kept current.
↳ ReconciliationDrift surfaced immediately
The moment actual diverges from plan, it is visible. No quarterly audits to find out.
↳ Drift DetectionFeature-set targeting
Point an instance at a feature set; ReARM reconciles what should land there. Your CI/CD queries ReARM for the latest release that passed all required approval gates and promotes only that version. No approved status in ReARM, no deployment.
↳ Feature SetsEvidence, extended to runtime
The same evidence trail that covers releases now covers what actually runs.
↳ Audit EvidenceReARM CD closes the loop
ReARM CD, the open-source deployment controller, pulls each instance's expected state from ReARM, applies it, and reports back what actually landed. The reconcile loop that keeps plan and actual honest.
↳ ReARM CD