VIN / VPS

Public edge node: TLS termination, auth, tunnel endpoint, warm standby control plane.

Class

tier-0 Fleet-fatal: loss stops the estate or risks data. Everything else waits.

RTO (declared)

15m

RTO (achievable)

15m

RPO

—

State

rebuildable

Redundancy

single node

Failover

none

Failure domain

fd-vps

Health check: jarvisos-agent heartbeat every 90s — proves the VPS is running and reachable. Self-reported: nothing outside the service confirms it.
Blind spot: The console runs on VIN. It cannot observe VIN's own death — the last thing a dying node does is stop disagreeing with itself.

Without it: Everything published is offline. Home-rack services keep running on the LAN and are reachable from the home network, not from outside.

• ✕ Open gap: Health is self-reported: a wedged process that still answers looks healthy. vin
  VIN / VPS reports its own health (jarvisos-agent heartbeat every 90s); nothing outside it confirms.
• § Accepted risk: The class requires redundancy and there is none. vin
  VIN / VPS is single-node but tier-0 requires a redundancy model.
  Accepted by homelab-operator, review 2027-02-15: VIN is the only public-ingress node in the estate. A second edge means a second VPS bill and DNS-level failover; the fleet's cost policy is zero new recurring spend. A 15 minute rebuild from the crown-jewels backup is the accepted answer.

Full classification and SLOs →

Depends on: none