State store

Hostwright uses local SQLite schema v24 for desired and observed state, operations, reservations, identity, ownership, events, and recovery records. It does not use a hosted database or synchronize state to a service.

Database path

State-backed commands use the secure per-user Application Support database by default. An explicit --state-db <path> overrides HOSTWRIGHT_STATE_DB, which overrides the default. Hostwright validates the selected path, ownership, and file permissions before opening the database.

hostwright paths --output json
hostwright doctor --output json
hostwright state integrity --output json

See the core local paths and migration guide for precedence, permissions, and recovery details.

Migrations and recovery

Schema migrations are checksummed and move forward only. Newer, corrupt, foreign, or ambiguous databases fail closed. Lifecycle intent is persisted before provider effects; interrupted operations retain exact checkpoints and ownership evidence for recovery.

Backups

Hostwright implements online state backup, verification, catalog inspection, and confirmation-bound restore. State repair is limited to documented reconstructible projections. These commands preserve the authoritative ledger and refuse to invent ownership or discard ambiguous records. See the core state backup and recovery reference.

Concurrency and secrets

Hostwright fences its own writers and validates state before use. This is not a same-user sandbox: stop external processes that write the SQLite file before restore or repair. Resolved secret values are not persisted in state or diagnostics.