FAQ
Does kovra send anything to the cloud?
Section titled “Does kovra send anything to the cloud?”No. kovra is a local tool — the vault lives on your machine and nothing is transmitted as a side effect of normal use. The only network calls happen when you use a cloud reference (kovra resolves it under your own provider identity). There is no telemetry and no phone-home.
Does it work offline?
Section titled “Does it work offline?”Yes. Everything except cloud references (which, by definition, call your cloud provider) works with no network at all.
What actually leaves my machine?
Section titled “What actually leaves my machine?”By default, nothing. A secret value only moves when a cloud reference resolves against your provider. Even then, the plaintext is never written to disk, argv, or an agent’s context.
Is .env.refs safe to commit?
Section titled “Is .env.refs safe to commit?”Yes — that’s the point. It holds addresses, not values. A leaked .env.refs
exposes where secrets live, never the secrets. Add a
git hook as a backstop against committing real values by
accident.
Can an AI agent read my secrets?
Section titled “Can an AI agent read my secrets?”It can use them, not see the sensitive ones. An agent over MCP runs under a
scope and never receives the plaintext of a high,
prod, or inject-only secret. The only thing it can read back is an ordinary
secret you explicitly marked revealable.
Where are my secrets stored?
Section titled “Where are my secrets stored?”In an encrypted vault under ~/.vaults (or KOVRA_VAULT_DIR). Every entry is
sealed; see Configuration and
Cryptography.
Is it free? What’s the license?
Section titled “Is it free? What’s the license?”The core is free to use (download the installer from kovra.sh); the enterprise tier is a paid subscription. kovra is proprietary, closed-source software — security is verified through independent audits and source review under NDA rather than public source. See License.
Is kovra a server or a daemon?
Section titled “Is kovra a server or a daemon?”A local CLI, with a small background service on macOS — and nothing listens on the network. On macOS kovra runs kovrad, a per-user service that starts at login and runs the credential gate; it listens only on a socket in your vault folder, readable by your user alone, and makes no network connection. The Dashboard is on-demand and loopback only — it isn’t exposed to the network and shuts down when idle.
Do I need the MCP server?
Section titled “Do I need the MCP server?”Only to use kovra from an AI agent. The CLI and vault work on their own; kovra mcp,
built into the kovra command, is the bridge for Claude Code and other MCP clients.
What if I lose my machine or my Keychain?
Section titled “What if I lose my machine or my Keychain?”Restore from a key backup — see Backup & recovery. Make that backup before you need it.
Which platforms are supported?
Section titled “Which platforms are supported?”kovra 0.12.1 ships for macOS. Windows returns when its approvals go through Windows Hello with no file-based path an agent could use to approve its own request; Linux is on the roadmap. See Platform support.