Does Latchkey send my keys to the cloud?

No. Secrets are encrypted on your device with libsodium secretbox. The website handles accounts, billing, and licence delivery — never vault plaintext.

How is encryption implemented?

Vault entries use libsodium secretbox (XSalsa20-Poly1305). The master key prefers the OS keychain via keytar, with an Argon2id passphrase wrap as fallback.

Can an AI agent read every key?

Only names listed in that project’s .latchkey.toml can be requested. Each request still needs your approve or deny in the app or CLI.

Is there a free tier?

No. Paid plans start at Solo. There is a £2.99 one-off leak scan (one per email and device).

What is the leak scan?

An offline heuristic pass over a repo or pasted text that looks for exposed key shapes, then gives step-by-step rotation guidance. It does not upload your files.

How do MCP tools get a secret?

The Latchkey MCP server exposes a get-secret tool. Your agent requests a name; you approve or deny; the value is returned only on approve and an audit line is written.

What does the audit log contain?

Metadata only: timestamp, action, secret name, agent or process label, and decision. Secret values are never written to the audit log.

What is .latchkey.toml?

A per-project allowlist of environment variable names Latchkey may inject. Commit the file; keep values out of git.

Which platforms does the CLI support?

macOS, Windows, and Linux with Node.js 20+. Keychain backends are Keychain, Credential Manager, and Secret Service respectively.

How do licences work?

After checkout, Latchkey issues an Ed25519-signed licence token. Activate it with latchkey login. The CLI verifies the signature offline with a bundled public key.

What do you never see?

We never receive vault plaintext, master keys, or passphrase material. Servers may store account email, plan entitlements, device metadata, and audit metadata you choose to sync — not secret values.

Who do I contact for Enterprise or support?

Email Yusuf@yusuf-choudhury.com. Business plan includes priority email support within one business day.

← Latchkey

Agent sandbox

Phase: design — complementary to the approve gate. Stops many MCP/token issues; sandbox adds isolation for what still runs after you approve.

Layers

Approve gate (shipped) · Live
Human deny/approve before secret injection — latchkey run & MCP.
Tool allowlists (shipped) · Live
.latchkey.toml secret names + MCP approve env.
Isolated tool runtime · Planned
Optional sandbox for MCP/tool child processes — no broad filesystem/network by default.
Policy export · Planned
Enterprise: SIEM-friendly audit export, org templates (E2/E3).

CLI preview (M22-cli)

latchkey run --sandbox -- node your-agent.js
# Warns + sets LATCHKEY_SANDBOX_REQUESTED=1 — isolation NOT enforced yet.

# Planned (not active yet)
# latchkey run --sandbox -- agent-tool ...
# LATCHKEY_SANDBOX=1

Until this ships, use approve/deny + Latch Check waitlist for pre-flight scans.

Dashboard shows sandbox status · Threat model