Technical evaluation
Evaluate a zero-knowledge secrets manager on your Windows Server
Request a demo, then test VaultPilot against your deployment model before production. Run representative vault tasks, verify recovery and update trust, and write down every gap that needs another product or a control your team owns.
Tell us what the demo should cover
Your request reaches support@vaultpilot.io as one email, and we reply to your work email. The website keeps no copy. Leave out passwords, vault exports, databases, backups, private keys, access tokens, and unredacted screenshots.
01 · FIT
Check that the deployment and product boundary match your problem
VaultPilot ships as a Windows Server MSI with browser access over HTTPS. It is a self-hosted password and secrets manager. Out of scope: Linux or macOS server packages, Docker, PAM session brokering, SIEM, SSO, and vulnerability scanning.
- A browser with Web Crypto
- HTTPS and backups run by your team
- API clients and the optional DC Agent as the integration surface
02 · TRUST AND USE
Follow a secret through create, use, share, audit, and lock
Confirm which payloads are encrypted in the browser, which metadata stays on the server, how roles change vault access, and where plaintext can appear during an authorized workflow. Use synthetic records only.
- Server session separate from the master-password workflow
- Extension pairing, share revocation, and the audit entries they leave
03 · OPERATIONS
Test backup and updates before you rely on them
Create the recovery package that fits your scenario and restore it in a test. Verify the release source, the Ed25519-signed manifest, the file's SHA-256 hash, and its size. For v3.0.3, plan for the unsigned MSI instead of assuming signer metadata.
- Quick Recovery compared with the full Backup Tool
- Service health, login, and audit state after an update