A SAFE PLACE FOR YOUR SECRETS

Your secrets.
In safe hands.

API keys. Credentials. The things that keep your app running. Store them securely, control who gets access, and get back to building.

Built for developers. Designed for peace of mind.
+ ONE HOME FOR EVERY SECRETINTERACTIVE PREVIEW +
console.wardkey.appDEMO WORKSPACE
storefront / production

Secrets 5

A little order. A lot of peace of mind.

SECRET NAMEVISIBILITYVERSION
All example secrets encrypted AES-256-GCM
Encrypted at rest. Available when you need them.YOUR SECRETS. YOUR RULES.

One source of truth.

Keep credentials organized by project and environment. No more hunting through scattered files.

The right level of access.

Give people and services access to what they need, with policies and per-secret visibility.

Already in your workflow.

Reach for the console, CLI, or API. Your secrets go where your code goes.

01 / PROTECTION WITH INTENTION

A secret should only
open the right doors.

Some values are everyday configuration. Others should never appear in a browser. Set the boundary for each secret.

For your services. Not your screen.

Keep production credentials out of the browser entirely. Only authorized service tokens can read the value, even when a person can manage the secret.

03 / 03 VISIBILITY TIERS
++
database/url
This secret stays sealed.
SERVICE-TOKEN ACCESS ONLY
ACCESS IS A DECISION. MAKE IT DELIBERATE.
AES-256-GCM encryption AWS KMS-backed keys Versioned secrets
02 / LESS FRICTION. MORE SHIPPING.

Your terminal.
Now with a vault.

Bring secrets straight into your application's environment. One command, your existing workflow, and fewer credentials sitting in local files.

Explore the CLI
~/storefront
# Your secrets. Your process. One command.
$wardkey exec -- npm run dev
Inject secrets into your app’s environment without a local .env file.
YOUR WORKFLOW, INTACTInstall the CLI ↗
FROM LOCAL DEVELOPMENT TO DEPLOYMENT
CLIREST APITypeScript SDKGo SDK
A LITTLE MORE CLARITY

Good questions.
Straight answers.

Read the documentation
What can I store in Wardkey?

API keys, database credentials, tokens, and application configuration. Organize secrets by project and environment, then access them through the console, CLI, or API.

How are my secrets encrypted?

Wardkey uses AES-256-GCM envelope encryption. Each secret version has a fresh data encryption key, wrapped by an organization key that is protected by AWS KMS. Access policies are checked before a value is decrypted.

Can I use Wardkey in my deployment pipeline?

Yes. Use a scoped service token with the Wardkey CLI to inject secrets into a process as environment variables. Service tokens can also read sealed secrets when their access policy permits it.

Is this a personal password manager?

Wardkey is built for application secrets and engineering teams. It gives your services, scripts, and deployments a shared source for credentials, rather than managing personal browser logins.

KEEP YOUR SECRETS. KEEP BUILDING.

A little less exposed.
A lot more in control.

Make room for your secrets