Show IH: Built a local-first credential manager for Mac — API keys, seed phrases, secrets
Hey IH! Launched CypherKeep today on the App Store and Product Hunt.
The problem: I had API keys in .env files, seed phrases in Notes, secrets in Slack. One breach away from losing everything.
Existing managers either sync to the cloud (attack surface) or are too generic — they don't understand what an API key is.
What I built:
- AES-256-GCM encryption, Argon2id key derivation, SQLCipher — zero plaintext ever touches disk
- Live API key testing — paste a key, auto-detects provider, shows green/yellow/red status
- BIP39/SLIP39 seed phrase validation
- Touch ID + clipboard auto-clear
Built solo with SwiftUI + AI assistance. First app on the App Store.
Happy to answer questions about the technical decisions, security architecture, or the vibe coding process.
Product Hunt: https://www.producthunt.com/products/cypherkeep-credential-manager-for-mac
App Store: https://apps.apple.com/us/app/cypherkeep/id6763648343?mt=12
This is a strong build because the wedge is not just “password manager for developers.” It is specifically local-first credential control for API keys, seed phrases, and secrets, which is a much sharper trust position than a generic vault.
The live API key testing is probably the most interesting differentiator. That moves it from passive storage into active credential hygiene, which is a stronger long-term category if you keep building around dev/security workflows.
One naming thought: CypherKeep is clear, but it also sounds close to the broader password-manager/security-vault space. If this expands into a serious local-first secrets/security layer for builders, Davoq.com would carry a harder infrastructure/security feel and give you more room than a “keep” style name.