Support
Get support for VaultPilot
Start with the guide for your task or the knowledge-base article for your symptom. Write to support@vaultpilot.io when the case needs details from your environment.
Describe the symptom, then continue by email
Your request reaches support@vaultpilot.io as one email, and the conversation continues by email. The website keeps no copy. Report a suspected vulnerability privately, not through this form.
Guides, screen help, and the knowledge base
The documentation covers installation, first run, HTTPS, server settings, backup, updates, sharing, the browser extension, Discovery, API clients, and the optional directory agent. In the product, the ? button in the top bar opens the guide for the screen you are on. The knowledge base starts from a symptom, such as a certificate warning, a pairing failure, or a stalled update, and separates safe checks from changes that need approval.
- Guides for audit posture, the license lifecycle, and the operator runbook
- Every guide in English and Turkish, written for v3.0.3
Email support@vaultpilot.io with redacted details
A good support request names the version, the affected area, the impact, the timeline, and the redacted error. Databases, backups, secret values, private keys, access tokens, and unredacted screenshots do not belong in a support request. Support cannot recover a master password, a private key, or other material your team was responsible for protecting. Report a suspected vulnerability separately, as a private security report.
- A checklist for redacting diagnostics
- Placeholders instead of real hostnames, user names, and vault names
See VaultPilot in your own environment
Tell us what the evaluation should cover, or open the live demo with sample data first.