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

Contact & Enterprise

Enterprise — custom terms, deployment, and procurement. General — billing and product questions. We reply from Yusuf@yusuf-choudhury.com.

Enterprise

Custom terms, procurement, and deployment questions.

· Custom terms & invoicing
· Security questionnaire & deployment
· SSO (SAML) — roadmap honest

Trust pack: Procurement · Security overview · SOC 2 status · SSO · MSA · Design partners

Business plan · £124/mo

Enterprise enquiry

Company, team size, and message — protected with Turnstile when configured.

Customers vs partners

We keep this explicit so procurement and BD conversations stay honest.

Enterprise customers

Companies that buy Latchkey for their teams: platform / security engineering, AI tooling leads, regulated shops with MCP or agent rollouts. Global 5000 fits here when they need approve gates, audit, SSO, and MSAs — start with design partners, not cold logo hunting.

Partners (ecosystem)

Model vendors, IDE platforms, cloud marketplaces, and security resellers who integrate or co-sell — e.g. MCP hosts, agent frameworks, SIEM vendors. Anthropic, Meta, OpenAI, etc. are usually partners or distribution, not your first paid seat deal; your buyers are their customers' security teams.

Use the Enterprise form above for procurement; general contact below for everything else.

General contact

Solo–Business billing, licence help, or product questions — not procurement.