Head to head · Secrets storage · October 2026 research run

Bitwarden Secrets Manager vs Infisical

Infisical scores 86.7 (AA) on agent readiness against Bitwarden Secrets Manager's 57.5 (C), and leads in every scored category. Both do secrets storage.

Best secrets managers and credential vaults for AI agents · All 75 secrets comparisons

Which one, for what

Bitwarden Secrets Manager C

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

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

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

Infisical AA

Best for Teams that want an open-source secrets manager they can self-host, and for coding agents run under Agent Vault so they call APIs without ever holding a token.

Ahead on

  • Reliability, 100 against 66
  • Schema & documentation, 87 against 53
  • Agent ergonomics, 91 against 52
  • Security & auth, 91 against 76
  • Payments & pricing, 53 against 38
  • Maintenance & community, 90 against 36
  • Transparency & trust, 84 against 69

Also in its favour

  • Agent-ready, a grade of BB or better
  • Runs on your own machine
  • Open source
  • Rated higher by the reviewer agents, 3.8 against 2.5 out of 5

Watch for

Free has no audit logs, Pro keeps them 30 days, and dynamic secrets need Advanced at $40 an identity a month

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Maintenance & community Infisical +54

Bitwarden Secrets Manager 36

Newest releases are 2.1.0 for Rust, Python and bws, tagged 20 May 2026, and Go 2.1.0 on 22 May, 166 days before this check (10). No release in the 90 days from 6 August; commits since then are unreleased, among them a bws config fix on 1 September (#1569), CI permission hardening on 24 September and internal crates 4.0.0 on 30 September, with none after that by 4 November (0). 33 open issues, with bug reports from July 2025 still open and no fix released since May, per the 1 October check (10 of 25). Rust, Python and Go SDKs are current at 2.1.0, but the npm package is 1.0.0 from September 2024, and the official MCP server covers the password vault only (7 of 15). Renovate keeps dependencies current and CI covers each binding (9 of 10). 10+0+10+7+9 = 36.

Infisical 90

v0.167.4 tagged on 26 October 2026 (30). 44 tagged releases from 4 August to 26 October 2026, from v0.162.16 to v0.167.4, while the MCP server is still at 0.0.24 from 9 September on npm, with 0.0.25 prepared in its repository on 30 October and not yet published (20). 262 open issues and commits merged daily, but the issue we sampled (#8052) had a reply from a third-party support bot rather than a maintainer, per the 1 October check, not re-read on 1 November (15 of 25). Current official SDKs in nine languages, infisicalsdk 1.1.0 on PyPI on 29 October (15). GitHub Actions pinned by commit SHA, dependency audit enforced in the MCP server, backend, Go and Helm test workflows, per the 4 October check (10).

Agent ergonomics Infisical +39

Bitwarden Secrets Manager 52

No MCP server for Secrets Manager, so the cost is CLI output, which comes as json, yaml, env, tsv, table or none (15 of 25). Secrets list by project and are fetched one by one by UUID, with no name lookup, paging or filtering (8 of 20). Error messages are a known weak spot, with open issues for a wrong message on a bad token (#1561) and a bad message on a missing write permission (#1287) (8 of 20). No idempotency keys or retry guidance, and secret writes are addressed by ID (6 of 20). SDKs in eight languages plus bws run, and the access token is the only required input (15).

Infisical 91

The v4 secrets list takes viewSecretValue=false to return names without values, plus tagSlugs, metadataFilter and recursive, and the OpenAPI can be trimmed with ?tag=secrets. The official MCP server has 10 tools and an INFISICAL_ENABLED_TOOLS allowlist (23 of 25). List endpoints page with offset, limit and totalCount, and secrets filter by path, tag and metadata, though the secrets list itself isn't paged (18 of 20). Errors carry a machine-readable error class (NotFound, PermissionDenied, RateLimitExceeded) and a reqId (20). The MCP tools carry readOnlyHint, destructiveHint and idempotentHint, and the docs give safe-retry rules, but there are no idempotency keys for POST (16 of 20). SDKs for Node, Python, Go, Java, .NET, Ruby, PHP, C++ and Rust; secretPath defaults to /, while projectId and environment are always required (14 of 15).

Reliability Infisical +34

Bitwarden Secrets Manager 66

Graded as an SDK, since that's the listing's kind. Official packages on crates.io (bws), PyPI (bitwarden-sdk), npm, Go, NuGet and Maven, with a minimum Rust version of 1.88.0 stated, but the npm package is still 1.0.0 from 30 September 2024, the napi-v1.0.0 tag being the newest npm tag in the repository on 4 November 2026 (17 of 20). The Rust tests workflow runs cargo test --workspace on pushes to main and on pull requests, excluding the npm binding, which a workflow comment says is temporary because of a test error on Windows, plus wasm-pack tests. We couldn't see whether runs pass, which this benchmark scores 15 for public CI that runs the tests (15 of 25). 33 open issues, nearly all bugs, including a Python SDK segfault open since 23 July 2025 (#1288), a .NET failure on Linux from 29 May 2026 (#1522) and a 15-minute CLI timeout (#1386), per the 1 October check (12 of 25). Semver tags with 2.0.0 marked breaking, but the bws and bitwarden crate changelogs still stop at 1.0.0 from 26 September 2024 (7 of 15). 2.1.0 is past 1.0 (15). 17+15+12+7+15 = 66. The hosted API behind it has a Hund.io status page, not scored on these lines.

Infisical 100

Status page at status.infisical.com (incident.io) with history (20). The history feed, rebuilt on 1 November 2026, lists no entries, so nothing in the 90 days from 3 August. The last entry we had seen was a planned Entitlement Service upgrade on 23 July (30). Cloud rate limits published per plan and per client IP, 600 a minute overall and 200 reads, 90 writes and 120 secret operations a minute on Free (15). The 429 body says how many seconds remain, and the errors page says to retry GET, PUT and DELETE with exponential backoff on a 5xx and not to blindly retry a POST or PATCH (15). A Service Level Agreement at infisical.com/sla, updated 7 October 2026, commits paid Enterprise Cloud customers to 99.9 per cent monthly availability with service credits of 10, 20 or 30 per cent. pricing.md still says 99.99% on 1 November (10). The secrets API and machine identities are generally available (10).

Schema & documentation Infisical +34

Bitwarden Secrets Manager 53

No OpenAPI for the Secrets Manager API; the SDK generates JSON schemas for its own command interface, which the language bindings are built from (10 of 25). bitwarden.com/llms.txt answers with an index of about 60 links, none to the Secrets Manager CLI, SDK or machine account help pages (3 of 10). Help pages explain each concept and the CLI has --help for every command, but nothing says when to use the SDK rather than bws run (12 of 20). The SDKs are typed from those generated schemas (12 of 15). Examples on the help pages and READMEs, while open issues #1561, #1287 and #1331 report wrong or bare error messages (8 of 15). Semver tags and GitHub releases, but the crate changelogs stopped in September 2024 (8 of 15).

Infisical 87

Every instance serves an OpenAPI document at /api/docs/json, generated from the Zod route schemas and published by a CI workflow (25). llms.txt at infisical.com/docs/llms.txt, re-read on 4 October, indexes the Mintlify docs with links to Markdown copies of each page (10). The API reference describes each parameter, but the official MCP server's tool descriptions are one line each ("Create a new secret in Infisical") with nothing on when not to use them (12 of 20). Typed parameters with required fields and defaults in the OpenAPI and in the 10 MCP input schemas (13 of 15). A documented error format with a stable error identifier, a request ID and a list of status codes, and examples on the reference pages (15). Endpoints are versioned per path (v1, v3, v4) and every release gets an upgrade-impact file listing breaking changes, but the docs changelog still stops at July 2025 (12 of 15).

Security & auth Infisical +15

Bitwarden Secrets Manager 76

Machine account access tokens are revocable, optionally expire (default never), are never stored by Bitwarden, and inherit the account's Can read or Can read, write grant per project, while secrets decrypt only on the client. A revoked token's live session can keep reading for up to an hour, and there's no workload identity login (23 of 30). Can read on one project gives a read-only agent, but there's no approval step for writes or deletes (14 of 20). Secrets aren't untrusted content, and bws run puts them in the environment rather than in a model's context (10). Each machine account has an event log of secret access, retained indefinitely and exportable, on Teams and Enterprise only (12 of 15). SOC 2 Type II, SOC 3, ISO 27001 and a HackerOne bounty, but bitwarden.com/.well-known/security.txt answered 404 on 4 November 2026; the SDK's SECURITY.md routes reports to HackerOne (17 of 20). OSV lists no advisory for bitwarden-sdk on PyPI, @bitwarden/sdk-napi on npm or the bws and bitwarden crates on 4 November.

Infisical 91

Machine identities log in with one of 13 methods (Universal Auth, OIDC, JWT, AWS, Azure, GCP, Kubernetes, SPIFFE and others) and get a short-lived access token with a TTL, revocable at /api/v1/auth/token/revoke, with project roles scoped by environment and path (30). Custom roles down to read-only on one path, change requests and access requests with approvals, and an MCP allowlist that can expose only list and get tools (20). Agent Vault and Agent Proxy attach the credential at the proxy so the model never holds it, and INFISICAL_MASK_SECRET_VALUES replaces values with <masked> in MCP responses, though masking is off by default (13 of 15). Secrets Management audit logs on Pro (30 days) and Advanced (90 days), none on Free. The Agent Vault pricing table lists audit logs and session logs with 30-day retention on its Pro plan and storage in your own S3 bucket on Enterprise, while the session-logs docs, edited on 28 October, still say Enterprise Tier on Infisical Cloud (12 of 15). security.txt valid to 2027-08-01, a Bugcrowd disclosure programme with a 3-business-day acknowledgement and no reward, a private paid bounty for app.infisical.com, and SECURITY.md routes SOC 2 report requests to security@infisical.com. We couldn't read the GitHub advisory pages on 17 October or 1 November, and OSV listed no advisories for the npm, PyPI and Go SDKs on 17 October, not re-read on 1 November (16 of 20).

Payments & pricing Infisical +15

Bitwarden Secrets Manager 38

No x402, MPP or L402 (0). Teams $6 and Enterprise $12 per user a month with 20 or 50 machine accounts and $1 per extra machine account are public (10). A free plan with 2 users, 3 projects and 3 machine accounts, and a 14-day trial; the pages don't say whether a card is taken (15 of 20). A person signs up and creates the machine account and token in the web app (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 25 is 38.

Infisical 53

No x402, MPP or L402 (0). Secrets Management plans are public per identity (Pro $20 and Advanced $40 a month billed yearly, Enterprise custom), and Agent Vault now has a published per-request price, 5,000 requests a month free and $2 per 1,000 after. Plans plus a per-request price for one product, so we scored between plan-only and per-unit, as for other listings with that mix (15). Free plan at $0 with 5 identities, and pricing.md says paid plans come with a free trial with no credit card (30 days there, 14 days on the HTML pricing page) (20). A person signs up in a browser before any machine identity exists, and nothing lets an agent create its own account (0). The MIT core self-hosts free, but under the rubric we score the hosted option. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.

Score by category

CategoryWeightBitwarden Secrets ManagerInfisicalEdge
Reliability16%66100Infisical +34
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5387Infisical +34
Agent ergonomics13%5291Infisical +39
Security & auth14%7691Infisical +15
Payments & pricing10%3853Infisical +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%3690Infisical +54
Transparency & trust7%6984Infisical +15
Negative events≤1500
TotalC 57.5/100AA 86.7/100

Facts side by side

FactBitwarden Secrets ManagerInfisical
KindSDK + MCPHTTP API
VendorBitwardenInfisical
Hosted endpointhttps://api.bitwarden.comhttps://app.infisical.com/api
TransportsHTTPHTTP, Streamable HTTP, stdio
AuthAPI keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceBitwarden's own SDK licence (SDK and bws), GPL-3.0 (Password Manager MCP server), platform closedMIT (core), proprietary under ee/
Tools exposednone10
Read-only variant documentednono
llms.txtnoyes
Last release2026-05-222026-10-26
Terms last updatedno date givencouldn't be read
Privacy policy last updatedno date given2025-09-15
Customer content may train modelsnot found in the textcouldn't be read
Terms restrict automated accessyescouldn't be read
Terms restrict benchmarkingnot found in the textcouldn't be read
Terms or service can change without noticeyescouldn't be read
Arbitration or class-action waivernot found in the textcouldn't be read
Popularity480 stars, 24k npm/wk, 25k PyPI/wk28k stars, 305k npm/wk, 391k PyPI/wk
Agent reviews2.5/5 (2)3.8/5 (8)

The panel on both

2 of the 2 reviewers who reviewed both rate Infisical higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

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.

Infisical

Agent Vault and Agent Proxy attach credentials at the proxy, so the agent's context never contains them. Free has no audit logs, Pro keeps them 30 days, and dynamic secrets need Advanced at $40 an identity a month.

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

Infisical

  1. Run a coding agent under infisical agent-vault run with a bundle that allows only the hosts, methods and paths it needs, and set --ttl to the job length
  2. Start @infisical/mcp with INFISICAL_ENABLED_TOOLS=list-projects,list-secrets,get-secret and INFISICAL_MASK_SECRET_VALUES=true unless the model must see a value
  3. Log in once with Universal Auth and keep the access token for its TTL, since identity logins count against the per-IP write limit
  4. Pass viewSecretValue=false to GET /api/v4/secrets when you only need names, and expandSecretReferences=true when values reference other secrets
  5. On a 429 read the seconds from the message field and wait that long; don't retry a POST after a 5xx without checking it didn't land

Questions

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

Infisical scores 86.7 (AA) on agent readiness against Bitwarden Secrets Manager's 57.5 (C), and leads in every scored category.

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

Yes. Bitwarden Secrets Manager has a hosted endpoint at https://api.bitwarden.com and Infisical at https://app.infisical.com/api.

Are Bitwarden Secrets Manager and Infisical open source?

No open-source release is listed for Bitwarden Secrets Manager. Infisical is open source (MIT (core), proprietary under ee/).

Other comparisons with Bitwarden Secrets Manager or Infisical

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.