Introduction

Turn your entire .env into one deployable key. Use the CLI for secret management and build-time injection. Use the SDK for runtime loading.

Why KeyDrop

Traditional deployment requires copying every secret to every platform:

Traditional deploymentenv
DATABASE_URL=...
JWT_SECRET=...
OPENAI_API_KEY=...
STRIPE_SECRET_KEY=...
NEXTAUTH_SECRET=...

With KeyDrop:

keydrop push
↓
KEYDROP_KEY=proj_xxxxxxxxx
↓

Deploy

One key. One project. Deploy anywhere.

At a Glance

CLI

Manage secrets, push .env files, and inject secrets at build time with keydrop run.

SDK

Load secrets at runtime with init(). Secrets end up in process.env automatically.

One Key

Deploy with only KEYDROP_KEY on Vercel, Railway, Docker, AWS, and more.

How It Works