Zero-knowledge vault for API keys

Secure your API keys before one leaks

A leaked key keeps working, and keeps billing you. Yours stay encrypted on your device and go straight into your .env, VS Code, or secret store — never through the clipboard.

Free to install, works offline, no account needed to start.

Built for Modern Developers

Everything you need to manage API keys securely and efficiently.

Generate .env Files Instantly

Choose from 60+ services and download formatted .env files ready for any environment—Vite, Next.js, Docker, Kubernetes, and more.

AES-256-GCM Encryption

AES-256-GCM with 600K-iteration PBKDF2 key derivation. Your master password never leaves your device — we can't decrypt your data even if we wanted to.

Organize by Project

Group keys by project and environment. Switch between projects effortlessly with custom templates for each application.

Sync Across Devices

Access your encrypted keys from any computer. Everything syncs securely across all your devices automatically.

Control Access

Authorize specific websites to use your keys. Revoke access anytime with granular permission controls.

Zero-Knowledge Sharing

Share API keys with your team through end-to-end encrypted vaults. Nobody—not even us—can see your shared secrets.

Why this exists

Six ordinary ways a working key ends up somewhere it should not be. Each one has its own page, including what we do not fix.

01

Your keys are sitting in plaintext on disk

A .env file is a text file. Everything on your machine that reads text files can read it.

Read the detail
02

The clipboard is the most-used secrets manager in the world

Every key gets copied at least once. The copy is what escapes, not the original.

Read the detail
03

Rotation gets deferred because nobody knows where the key went

Everyone agrees keys should be rotated. Almost nobody does it on a schedule, and the reason is logistical, not lazy.

Read the detail
04

Sharing a key is a one-way operation

You can revoke access to a document. You cannot revoke a string someone has already read.

Read the detail
05

A key committed once is committed forever

Deleting the line in a follow-up commit changes nothing. Git kept the first one.

Read the detail
06

Fetching a key costs more than the twenty seconds it takes

The interruption is not the tab switch. It is losing the thing you were holding in your head.

Read the detail
Read all six in detail →

Why Developers Trust Us

Every secret is encrypted before it leaves your device. Our servers store only ciphertext.

AES-256
GCM authenticated encryption with unique IV per operation
600K
PBKDF2 iterations for master password derivation
E2E
Encrypted sharing via ECDH P-256 key exchange
Zero
Plaintext keys on our servers — ever

Simple, Transparent Pricing

Start for free, upgrade as you scale.

Starter

$0/month

Perfect for hobbyists & side projects.

  • 1 Project
  • 30 Keys per Project
  • Local Storage
  • .Env Generation
Most Popular

Pro

$9/month

For serious developers and freelancers.

  • 10 Projects
  • 50 Keys per Project
  • Unlimited .env Generations
  • Cloud Sync (Multi-device)

Team

$29/month

Collaborate securely with your team.

  • Everything in Pro
  • Unlimited Projects & Keys
  • E2E Encrypted Shared Vaults
  • Role-Based Access Control

See it in action

Normally, you'd paste your OpenAI key here. With APIKeyConnect, simply authorize the domain and your keys are securely injected.

  • No hardcoded keys in your code
  • No copy-pasting from text files
  • Revoke access instantly
  • Works with 50+ services
🤖 OpenAI Integration DemoDisconnected