Why VaultPilot
A team password manager that stays on your own Windows Server
Use VaultPilot when your vault cannot move to a vendor-hosted service. Check three things before you decide: where the data lives, what the product covers, and which work stays with your team.
Service, data, certificates, and backups stay in your environment
VaultPilot installs on Windows Server and serves authorized browsers over HTTPS. Vault values are encrypted in the browser before they are saved; the server keeps encrypted records, wrapped keys, salts, and operational metadata in local SQLite.
- Installed from one MSI package
- No application runtime hosted by VaultPilot
- Your team owns the HTTPS certificate and the backups
One console for records, sharing, audit, recovery, and integrations
The core is a vault for passwords, credentials, API keys, secure notes, certificates, and file-backed secrets. A paired Chromium extension, Discovery, selected-record sharing, audit history, recovery tools, API clients, and an optional directory agent build on that core. It does not replace a PAM tool, a SIEM, or a vulnerability scanner.
See the product features
What the product does and what stays with your team
VaultPilot enforces sign-in, roles, browser encryption, and update checks. Your team keeps the server patched, owns the HTTPS certificate and the off-server backups, and protects master passwords, authenticator devices, and agent tokens.
- Guides for installation, recovery, updates, and daily use
- Release notes and verification steps for each tagged release
Fit, installation, and where the data lives
Here are short answers to the three questions that decide whether VaultPilot fits your environment, and the system requirements page lists every host, port, and browser detail.
- Which environment does VaultPilot fit? A 64-bit Windows Server 2019 or later host that your team runs, with users connecting from a browser over HTTPS on port 1734 by default.
- What does installation need? Local Administrator rights, .NET Framework 4.x, and at least 2 CPU cores, 8 GB RAM, and 250 GB disk; one MSI installs the service, its own Node.js 22 runtime, and local SQLite, and adds the firewall rule.
- Where does the data live? On your own server, in a local SQLite database under C:\ProgramData\VaultPilot; the browser encrypts vault values before they reach it, and the plaintext master password is not sent.
See VaultPilot in your own environment
Tell us what the evaluation should cover, or open the live demo with sample data first.