I'm still building Shush. Expect things to change.
Built for the AI-agent era · no .env on disk

Your .env file
is a liability.

Cursor, Claude Code and Copilot read every file in your project — they don't respect .gitignore, and your keys end up in chain-of-thought logs on infra you don't control. Shush fetches secrets at runtime and injects them straight into the process. Memory only. Never written to disk.

Self-hosted Open source Every read audited
~/payments-api
$ shush run --env dev -- npm run dev
✓ authenticated · maya@acme.dev
✓ fetched 14 secrets · payments-api/dev
injected as env vars → child process
✗ 0 secrets written to disk
↳ 14 reads logged to audit trail
▸ ready on http://localhost:3000
memory only no .env agent-safe
THE PROBLEM

Secrets on disk were always risky. Agents made it worse.

Agents read every file

Cursor, Claude Code and Copilot index your whole working tree to build context. Your .env is just another file to them — .gitignore doesn't apply.

Secrets leak into logs

Once read, keys flow into chain-of-thought traces, prompt caches and model logs running on infrastructure you don't own or control.

.env sprawl

Dev .envs, test .envs, a copy on every laptop, pasted into chat for the new hire. Each one is a credential you can never fully revoke.

.env ON DISK · LIABILITY
DATABASE_URL=postgres://u:p@db.prod…
STRIPE_SECRET_KEY=sk_live_4eC39Huak2…
JWT_SIGNING_KEY=b7d3f0a1c9e84f12…
OPENAI_API_KEY=sk-proj-9Xa2kQ…
Readable by every AI agent in your editor
Committed by accident, forever in git history
Pasted into Slack to onboard a teammate
Stale and un-revocable across laptops
shush run IN MEMORY · AUDITED
$ shush run --env dev -- npm run dev
✓ 14 secrets injected into the process
env vars live in memory only
↳ every read written to the audit log
Injected at process start, in memory only
Nothing on disk for an agent to read
Granted per project, env and person
Revoke once — every copy dies with it
HOW IT WORKS

Don't store secrets on disk. Fetch them at runtime.

1

Store in Shush

Secrets live encrypted (AES-256-GCM) per project and environment, versioned with full history — never in a file.

2

Run with shush

shush run fetches the secrets your process is allowed to see and injects them as environment variables at launch.

3

Gone when it exits

They live in memory for the life of the process and vanish when it stops. Every fetch is authorised and audited.

DEV ONBOARDING

A new dev ships on day one. No .env handoff.

No more hunting for the right keys, copying a teammate's .env, or pasting secrets into Slack. They log in, they're granted access to the project, and Shush does the rest.

Hunt down the right .env file
Paste secrets into Slack / DMs
Re-share keys after every rotation
Maintain a stale setup doc
day-one.sh
$ shush login
✓ welcome, dev@acme.dev
$ shush run --env dev -- pnpm dev
→ access: payments-api · dev (Viewer)
▸ running. zero setup, zero .env.
A REAL SECRET MANAGER UNDERNEATH

Runtime injection, backed by everything you'd expect.

Projects & environments

Secrets isolated per project across dev, staging and prod. Promote between environments without copy-paste.

Encrypted & versioned

AES-256-GCM at rest, every change versioned with author and timestamp, and one-click rollback.

Groups & RBAC

Grant groups or people access scoped per environment. Owner, Admin, Editor, Viewer — enforced on every call.

Every access audited

Read, write and delete events with actor, source, IP and result. Filter, drill in, export for compliance.

CLI, SDK & gRPC

shush run for any runtime, native SDKs, and scoped service tokens for CI and machine identities.

Self-hosted

Runs entirely on your infrastructure — Clerk-backed auth, your Postgres, your keys. Secrets never leave your network.

In memory
never written to disk
Audited
every single read
Self-hosted
on your own infra
Open source
Apache-2.0 licensed

Get your secrets off disk.

Open source and self-hosted. Clone it, run it on your own infra, and stop shipping .env files around.