Replace your .env file
with one token.
Encrypted vault, automatic rotation, and a smart proxy for every API your app talks to.
One credential in, every provider out.
Works with every API, LLM, and OAuth service you use.
34 provider templates built in. Anything else works via "Custom."
The reality of
secrets management.
Putting API keys directly into your source code is a ticking time bomb. When you hardcode secrets into your frontend, mobile app, or public repository, hackers can easily decompile and extract them.
The result? Massive API abuse and thousands of dollars in stolen usage running up your bill before you even notice.
You already know this is a problem.
You just havenβt had a solution thatβs easier than the problem.
const OPENAI_KEY = "sk-proj-xyz9...";
// TODO: Replace with secure backend call later
fetch('https://api.openai.com', { ... })
Engineered for absolute control.
Centralize your workflow, rotate keys with zero downtime, and completely decouple credentials from your codebase.
Store everything in one place
A single source of truth for all environments. No more syncing files over Slack or hunting through DMs.
Apps never see raw keys
Your application processes request temporary access tokens on the fly. Raw API keys stay safely encrypted.
Full visibility
Know exactly which environment, user, or service accessed each key, right down to the millisecond.
Stop managing secrets the wrong way.
See the immediate impact of adopting a centralized proxy architecture.
1. Slack DMs
2. Notes App
π API Keys
sk-proj-a1b2...
sk_live_8xyz...
3. .env File
# DO NOT COMMIT
OPENAI_API_KEY=sk_...
AWS_SECRET=AKIA...
STRIPE_KEY=sk_liv...
4. Git History
+ OPENAI_API_KEY=sk-proj...
- // No keys were here
5. The Scatter Problem
The Broken Architecture
Raw credentials are tied directly to your source code, creating multiple points of vulnerability and zero visibility.
1. Team Sharing
2. Documentation
π‘οΈ Vault Credentials
3. Local Config
APILOCKER_REFRESH_TOKEN=rtk_β’β’β’β’β’β’β’β’
# that's it. every provider is reachable.
4. Version Control
β Clean history. Nothing sensitive to commit.
5. One Source of Truth
Technical Flow
The raw key was never exposed to your application β it existed only in memory for the duration of the call.
Zero friction.
Three steps. Five minutes. Done.
Install the CLI
npm install -g apilocker
Authenticate securely
apilocker register
Run your app
apilocker run -- node index.js
Your vault. Everywhere you work.
Manage your credentials natively through beautifully engineered interfaces.
CLI
Native terminal commands for seamless local development, quick script injections, and CI/CD pipelines.
Web Portal
A beautiful, centralized browser interface to manage team members, review audit logs, and rotate keys manually.
MCP Server
Natively expose your vault securely to your local AI agents using the Model Context Protocol standard.
IDE Integration
Native extensions for Google Antigravity, Cursor, Windsurf, & VS Code. Inject keys without leaving the editor.
Your vault, inside
Browse credentials, reveal secrets, rotate keys, create tokens, and monitor vault health β all without leaving your editor.

Works in your IDE today
Native extensions for VS Code, Cursor, Windsurf, and Antigravity.
Install in seconds
Search "API Locker" in your extensions marketplace and authenticate with one click.
Everything in the sidebar
Manage environments, view secret status, and copy values with zero context switching.
Your existing vault, instantly
Already using the CLI or dashboard? Your credentials appear automatically. Same vault, new surface β zero reconfiguration.
Engineered
for peace of mind.
Free. Seriously.
API Locker is completely free while in beta. Enjoy uncompromising security with unlimited usage.
- Basic Encryption
- Limited Integrations
- Strict Quotas
- AES-256 Native
- Unlimited Integrations
- Unlimited Keys
- Unlimited Usage
- Complex Setup
- Enterprise Tax
- Needs DevOps Team
Your keys deserve better than a .env file.
npm install -g apilocker && apilocker register