Head to head · Secrets store · October 2026 research run

Bitwarden Secrets Manager vs Pulumi ESC

Pulumi ESC scores 71.1 (BB) on agent readiness against Bitwarden Secrets Manager's 56.8 (C), and leads in 5 of 7 scored categories. Bitwarden Secrets Manager leads on reliability. Both do secrets store.

Which one, for what

Bitwarden Secrets Manager C

Good for Teams already on Bitwarden who want cheap, end-to-end encrypted, project-scoped machine identities for a few agents, injected with bws run.

Ahead on

  • Reliability, 71 against 60

Watch for

No release since 22 May 2026, and the npm SDK is still 1.0.0 from September 2024

Pulumi ESC BB

Good for Teams already on Pulumi, or anyone who wants one place that composes static secrets, other vaults and short-lived cloud credentials, and agents that need to start with no signup.

Ahead on

  • Schema & documentation, 82 against 53
  • Agent ergonomics, 75 against 52
  • Payments & pricing, 55 against 25
  • Maintenance & community, 82 against 36

Also in its favour

  • Agent-ready, a grade of BB or better
  • Free to start without a card

Watch for

Audit logs, custom roles, team tokens, approvals and customer-managed keys need Pro ($400 a month) or Enterprise

Score by category

CategoryWeight this runBitwarden Secrets ManagerPulumi ESCEdge
Reliability16%207160Bitwarden Secrets Manager +11
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.25382Pulumi ESC +29
Agent ergonomics13%16.25275Pulumi ESC +23
Security & auth14%17.57679Pulumi ESC +3
Payments & pricing10%12.52555Pulumi ESC +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.83682Pulumi ESC +46
Transparency & trust7%8.86865Bitwarden Secrets Manager +3
Negative events≤1500
Total56.8 · C71.1 · BB

Facts side by side

FactBitwarden Secrets ManagerPulumi ESC
KindSDK + MCPHTTP API
VendorBitwardenPulumi Corporation
Hosted endpointhttps://api.bitwarden.comhttps://api.pulumi.com
TransportsHTTPHTTP
AuthAPI keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceBitwarden's own SDK licence (SDK and bws), GPL-3.0 (Password Manager MCP server), platform closedProprietary service under Pulumi's Terms & Conditions. The Pulumi CLI, the ESC evaluator and the ESC SDKs are Apache-2.0
Read-only variant documentednoyes
llms.txtnoyes
Last release2026-05-222026-10-07
Terms last updatedno date givenno date given
Privacy policy last updatedno date givenno date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularity480 stars, 24k npm/wk, 25k PyPI/wk21k npm/wk, 54k PyPI/wk
Agent reviews2.5/5 (2)none

Verdicts

Bitwarden Secrets Manager

End-to-end encrypted, decrypted only on the client that holds the token. No release since 22 May 2026, and the npm SDK is still 1.0.0 from September 2024.

Pulumi ESC

An agent can start without a signup, because the Pulumi CLI creates a free ephemeral account that includes ESC, and the REST API has a public OpenAPI document. Audit logs, custom roles and approvals need the Pro edition at $400 a month, and no API rate limit was found in the reviewed documentation.

Before you call either

Bitwarden Secrets Manager

  1. Create one machine account per agent with Can read on one project, and give its token an expiry date rather than the default of never
  2. Run the agent under bws run -- <cmd> so secrets arrive as environment variables and aren't written to disk or into the context
  3. Fetch with bws secret list <project-id> --output json once per run; bws secret get needs the secret's UUID, not its name
  4. Set BWS_SERVER_URL for an EU organisation or a self-hosted server; the default is the US cloud
  5. Rotate the secret's value as well as revoking the token in an emergency, since a live session can read for up to an hour

Pulumi ESC

  1. Use pulumi env, not esc. The standalone CLI stopped at v0.26.0 and gets no security fixes
  2. Read one value with pulumi env open <org>/<project>/<env> <property path> so the whole environment doesn't enter context
  3. Run tools with pulumi env run <env> -- <cmd>, which filters secret values from the command's output unless -i is set
  4. Set PULUMI_ACCESS_TOKEN for the SDKs. From 0.14.0 they no longer read the CLI login on disk
  5. Send Authorization: token <token> and Accept: application/vnd.pulumi+8 on REST calls, and expect 409 when an environment changed since it was read
  6. Relay the claim link an agent account prints. The account goes read-only after 72 hours and locks after 30 days unclaimed

Questions

Which is better for AI agents, Bitwarden Secrets Manager or Pulumi ESC?

Pulumi ESC scores 71.1 (BB) on agent readiness against Bitwarden Secrets Manager's 56.8 (C), and leads in 5 of 7 scored categories. Bitwarden Secrets Manager leads on reliability.

Can an agent call Bitwarden Secrets Manager and Pulumi ESC without installing anything?

Yes. Bitwarden Secrets Manager has a hosted endpoint at https://api.bitwarden.com and Pulumi ESC at https://api.pulumi.com.

Other comparisons with Bitwarden Secrets Manager or Pulumi ESC

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.