2 comments

[ 0.28 ms ] story [ 16.8 ms ] thread

  Every developer knows the pain: your .env file has 15 API keys, it's not in git (for good reason),
  and when you get a new laptop or a teammate joins, you spend hours hunting through dashboards to
  recreate them. Some keys were shown once and are gone forever.

  Shipkey fixes this by using the password manager you already have (1Password or Bitwarden) as your
  API key backend. It works in 3 steps:

  1. shipkey scan – auto-detects every API key your project needs by scanning .env files, GitHub
  Actions workflows, wrangler.toml, and package.json dependencies
  2. shipkey setup – opens a browser wizard with direct links to each provider's dashboard and
  permission guidance inferred from your code
  3. shipkey pull – restores all keys on any new machine in seconds

  It also syncs keys to GitHub Actions secrets and Cloudflare Workers with shipkey sync, so you manage
  everything from one place.

  No central server, no new SaaS subscription, no network dependency. Just a local CLI that talks to op
   or bw on your machine. Supports 40+ providers out of the box (Stripe, OpenAI, Supabase, AWS,
  Cloudflare, etc.).

  Built with TypeScript/Bun. Open source.
This seems cool and all but a simple password manager or something like vault solves this as well.