Deployment overview

Deploy a self-hosted password manager on Windows Server

One MSI installs the service and the browser application on your own server. Your team publishes it over HTTPS at the server’s IP address or DNS name and owns its certificates, backups, and updates.

Illustration: installing the server in a rack and finishing setup from a browser

Plan the server, the address, and the browsers

You need a supported Windows Server, administrator rights for the MSI, and a planned DNS name or IP address. Users need a browser with Web Crypto.

Read the HTTPS certificate guide
Illustration: planning the server, its address, and the browsers on a blueprint

Install, then publish over HTTPS

Run the MSI as Administrator. After installation, the server uses a managed self-signed certificate for HTTPS until you configure a trusted PFX or P12 certificate.

Read the install and first-run guide

Quick Recovery and the full backup do different jobs

Quick Recovery is a browser-encrypted package of profile data and accessible records without files. The Backup Tool captures the whole server. Neither replaces the other.

Read the backup and recovery guide

Verify every update before you install it

A single update path checks the version, the Ed25519 manifest signature, the file hash, the file size, and the allowed download host. The v3.0.3 MSI is unsigned, so trust comes from the manifest signature and the file hash.

Read the update steps
Illustration: an update package passes a three-step checkpoint before it reaches the server

Optional: the directory agent near the domain controller

The DC Agent is a Windows service on a host close to the domain controller, installed from an Administrator PowerShell session. It sends OU, group, and user metadata. The AD bind password is typed at its local prompt and stays on that host.

Read the directory agent guide

See VaultPilot in your own environment

Tell us what the evaluation should cover, or open the live demo with sample data first.

Why VaultPilot · Solutions