Guide
Where to store API keys on a Mac
Put API keys in an encrypted vault next to the project’s logins — not in plaintext files you might commit. Bevel Keys is built for that Mac workflow.
Logins and secrets in one vault
Developers often juggle site passwords, API keys, and snippets from .env files. Spreading those across Keychain, Notes, and Slack DMs is how secrets leak. Bevel Keys organizes accounts by category (for example one category per project) with notepad space for keys and env details.
The vault stays encrypted on your Mac. Export discipline still matters: never commit real secrets to git; use the vault as the store of record.
FAQs
Quick answers
Where should you store API keys on a Mac?+
Keep them in an encrypted vault or secrets manager — not in plain text notes or committed env files. Bevel Keys lets you store API keys and env-related notes in category notepads next to project logins.
Is Bevel Keys a password manager for developers?+
It is aimed at side-project builders and early startups who want logins plus project secrets (API keys, env content, notes) in one local Mac vault.