Know where every API key lives. Without giving us a single one.

KeyAtlas will read your Cloudflare, Vercel, GitHub and Supabase consoles read-only, map every key to every app that uses it, and warn you before one expires or goes stale. Values will never leave your machine.

Preview · in development Sample data, made-up apps
Preview of the KeyAtlas app by key map with made-up apps. Each row is a key; each cell shows the platform and the last four characters of the key bound in that app.
Key tidepool-webledgerly-apinorthwind-shopharbor-cmsquill-adminorbit-jobsfernhouse
CF_API_TOKENexpires in 6 days
not used
not used
not used
not used
GH ActionsActions…0b3e
GH ActionsActions…0b3e
not used
OPENAI_API_KEY142 days old
Workers…a91f
Vercel…a91f
Vercel…a91f
Workers…a91f
GH ActionsActions…a91f
Workers…a91f
Vercel…a91f
RESEND_API_KEYunused 60d
Workers…19dd
not used
not used
Workers…19dd
not used
Workers…55a0
not used
STRIPE_SECRET_KEYhealthy
not used
Vercel…7c02
Vercel…7c02
not used
not used
not used
Vercel…e4b8
SUPABASE_SERVICE_ROLEhealthy
Workers…c7aa
not used
not used
not used
Vercel…c7aa
not used
not used
Scroll for more apps
We never see your keys.

Only names, salted hashes, last 4 characters and dates.

Your OpenAI key is in 7 apps. Do you know which?

The problem

Keys live in six consoles and nobody rotates them. 64% of secrets leaked in 2022 still worked in 2026.

GitGuardian, State of Secrets Sprawl 2026

Scattered
Wrangler secrets, Vercel env, GitHub Actions, Supabase, and .env files you're scared to delete.
Rotation is a scavenger hunt
Rotating one key means finding every app that uses it.
Expiries ambush you
A Cloudflare token or GitHub PAT dies and a deploy breaks at 2am.

How it works

  1. 1

    Connect read-only.

    Give KeyAtlas read-only tokens for Cloudflare, Vercel, GitHub and Supabase. It will list secret names and where they're bound. It won't be able to change your apps.

  2. 2

    Fingerprint locally.

    npx keyatlas scan will read your .env or vault on your machine and send only a salted hash and the last 4 characters, so the map can tell two apps share one key without seeing it.

  3. 3

    Get the map and the alerts.

    Expiring, older than 90 days, unused, duplicated across apps. Rotate with keyatlas rotate openai: it will run wrangler secret put and vercel env add locally for every place the key lives.

TerminalPlanned command
# planned command
$ npx keyatlas scan
Found 23 secrets in 7 apps · 1 expiring · 4 older than 90 days
$ keyatlas rotate openai
Updated 7 locations

We never see your keys.

Nothing labelled "value" ever crosses the boundary. Here is what does.

Trust boundary plan, wide YOUR MACHINE KEYATLAS PROVIDER APIs, READ-ONLY .env / vaultvalues hash computed heresalted sha256+ last 4 characters value stops here BOUNDARY names · salted hashes last 4 · dates map + alertsnames, dates read-only tokennames, bindingsno values/writes Cloudflare · Vercel GitHub · Supabase secret names and where bound. Never values. read-only token: names and bindings only A Trust boundary plan, stacked YOUR MACHINE .env / vaultvalues valuestops here hash computed heresalted sha256+ last 4 characters BOUNDARY names · salted hashes last 4 · dates KEYATLAS map + alertsnames, dates read-only tokennames and bindingsno values, no writes A read-only token: names and bindings only PROVIDER APIs, READ-ONLY Cloudflare · Vercel GitHub · Supabase secret names and where bound.Never values.
AWhat the server receives
{
  "name": "OPENAI_API_KEY",
  "app": "ledgerly-api",
  "platform": "vercel",
  "fingerprint": "sha256:9f1c…e07b",
  "last4": "a91f",
  "checked_at": "2026-11-18T09:12:00Z"
}
Sample payload. No field holds a key value.
  • Keep your vault. KeyAtlas will work alongside Infisical, 1Password, Doppler or plain .env.
  • Read-only tokens. We won't be able to change your apps.
  • The CLI will be open source (MIT), so you can check exactly what it sends.
  • Delete your account and the data will be gone.
What we never receive
  • key values
  • .env files
  • write access

For agencies

Running client apps? One workspace per client, a handover report when someone leaves, and a Slack alert before a client's key dies.

1Workspace per client
2Handover report
3Slack alert

Planned pricing

PLANNED

Agency

$49/mo

  • Client workspaces
  • Handover reports
  • Slack alerts
Join the waitlist

Planned pricing. Waitlist members get founding pricing.

Get early access.

Two minutes. Tell us how you work so we build the right thing.

Step 1 / 3
Step 1 of 3: email and role

We use your email only for KeyAtlas updates.

You are

FAQ

Do you store my API keys?

No. Values stay on your machine. We store names, salted hashes, the last 4 characters and dates.

How is this different from Doppler, Infisical or 1Password?

Those store keys. KeyAtlas will map where keys are used and when they need attention, and work alongside them.

Isn't this just a CLI?

The CLI will fingerprint keys locally. The map, the console connectors, reminders and client workspaces are what KeyAtlas will add on top.

Which providers?

At launch: Cloudflare, Vercel, GitHub and Supabase. Tell us what else you need in the form.

Is the CLI open source?

It will be, under MIT.

When does it ship?

Waitlist members get early access first. We're not promising a date.