Trust model
How to evaluate VaultPilot safely.
VaultPilot should be tested before it is trusted. This page explains the current trust model, what the software does, and what it does not replace.
Source availability
VaultPilot is currently closed source commercial software. That is a trust consideration, especially for backup tooling, so evaluation should start with a trial, restore verification, and review of operational evidence before production reliance.
Local-first operation
VaultPilot is designed for self-hosted Linux systems. Backup archives remain on storage controlled by the operator. License activation and download access use the VaultPilot licensing service.
Restore evidence over promises
The recommended workflow is to create a small backup, run restore verification, inspect dashboard history, and confirm failure reporting before enabling scheduled protection.
AI is optional
AI integration is optional and operator-facing. The core backup, checksum, encryption, retention, and restore-verification workflow does not depend on AI being correct.
Operator responsibility
VaultPilot does not replace database-native dumps, off-site backups, immutable storage, disaster recovery testing, or independent review of restored data.
Recommended first test
Request a trial key, install VaultPilot on a VM or non-production Linux host, create a small test backup, run restore verification, and inspect the evidence before using it for important data.