Skip to content
keyshroud logo

keyshroud

Keeps API keys in a self-hosted Vaultwarden, injects them into agent shell commands, and masks secret values in tool output.

Actively maintained

At a glanceswept Oct 20, 2026

1k installs/mo

Established

For
developers using AI coding agents like Claude Code, Codex, or Cursor who need API keys hidden from the model
Activity
Actively maintainedrelease 3 days ago · site updated 8 days ago
Runs as
CLISelf-hosted
Used for
  • run agent commands without exposing API keys to the model
  • scrub secret values from tool output before the model reads it
  • scan a repository for leaked secrets before committing
Worth knowingcomputed from what we read · each with its source
  • Publishes llms.txt, a file written for AI assistantskeyshroud.dev ↗
  • Launched on Product Hunt on Oct 20, 2026Product Hunt ↗
Alternatives in Developer toolsby use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

Compare keyshroud with

Pick up to two.

All 10 alternatives to keyshroud →

All Developer tools tools →

Not it? Say what you need

beta

Three tools from the Atlas for the job you describe, each with what fits and what does not.

From people who use itnot part of the reading

No notes yet. What do you use keyshroud for?

Sign in to leave a note
Questions this page answers
  • What is keyshroud?

    Keeps API keys in a self-hosted Vaultwarden, injects them into agent shell commands, and masks secret values in tool output. It is listed in the Atlas under Developer tools.

  • Who is keyshroud for?

    developers using AI coding agents like Claude Code, Codex, or Cursor who need API keys hidden from the model

  • Do people use keyshroud?

    Established: 1k installs/mo (npm).

  • Is keyshroud still maintained?

    Actively maintained: release 3 days ago · site updated 8 days ago.

  • What are alternatives to keyshroud?

    In Developer tools, by use: Cursor, Postman, Ollama, Warp, AI Operator by BLACKBOX AI, Zed Docs Agent.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.

How we read every tool → · By INITE Atlas Desk