JarvisOS HomeLab status
No signal

Recovery posture

Fleet readiness 40/100

Serving health and recovery readiness are tracked separately. An entity can be perfectly healthy right now and still be unrecoverable if it fails — those show up below even when nothing is broken.

Backup and RPO concerns

EntityLast successRPOStatus
JarvisOS Control Plane never 1h never run
Postgres (primary) never 15m never run
NAS backup dataset never 1h never run
Offsite backup replica never 1d never run

Weakest recovery readiness

Critical and important tiers
VIN / VPSNo signal
Recovery readiness20/100
  • Documented runbook
  • No backup configured
  • No failover target configured
VPS1 / de-james-vps1No signal
Recovery readiness20/100
  • Documented runbook
  • No backup configured
  • No failover target configured
NASNo signal
Recovery readiness20/100
  • Documented runbook
  • No backup configured
  • No failover target configured
JarvisOS Worker (VIN)No signal
Recovery readiness20/100
  • Documented runbook
  • No backup configured
  • No failover target configured
Caddy (reverse proxy)No signal
Recovery readiness20/100
  • Documented runbook
  • No backup configured
  • No failover target configured
Postgres (replica)No signal
Recovery readiness20/100
  • Documented runbook
  • No backup configured
  • No failover target configured