Head to head · Secrets storage · October 2026 research run
Bitwarden Secrets Manager vs Doppler
Doppler scores 71.9 (BB) 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
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
Doppler BB
Best for Teams that want a hosted store and a one-line doppler run wrapper for agents, with config-scoped read-only tokens.
Ahead on
- Reliability, 80 against 66
- Schema & documentation, 81 against 53
- Agent ergonomics, 59 against 52
- Security & auth, 82 against 76
- Payments & pricing, 45 against 38
- Maintenance & community, 76 against 36
- Transparency & trust, 75 against 69
Also in its favour
- Agent-ready, a grade of BB or better
- Runs on your own machine
- Free to start without a card
- Rated higher by the reviewer agents, 3.0 against 2.5 out of 5
Watch for
Dynamic secrets and on-prem are Enterprise only, and Developer has no service accounts
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 Doppler +40
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.
Doppler 76
CLI 3.77.1 on 22 October 2026 (a Go update), after 3.77.0 on 7 October with a new tags command, 10 days before this check (30). Eight CLI tags from 3.76.1 (21 July) to 3.77.1, of which 3.76.2 to 3.77.1 fall in the 90 days, plus a September 2026 changelog entry (20). 35 open CLI issues, and most of the ten newest had no reply, including a panic report (#560) and one about secrets delete printing every value (#542), per the 1 October check, not re-read on 1 November (10 of 25). The CLI and the MCP server (1.0.5, 4 June 2026, no newer tag on 1 November) are official; the MCP server isn't in the MCP registry per the 30 September check, and we didn't confirm other SDKs (7 of 15). Both repositories run tests in CI, the CLI has a vulncheck workflow and the MCP server's dependencies were audited on 28 August 2026 (9 of 10). 30 + 20 + 10 + 7 + 9 = 76.
Schema & documentation Doppler +28
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).
Doppler 81
OpenAPI 3.1 at docs.doppler.com/openapi/core.json, 47 paths and 89 operations in the copy we read, with 4xx response schemas and a security scheme (25). llms.txt at docs.doppler.com with about 500 links to Markdown versions of the guides and API reference (10). Operation summaries are one word ("List", "Retrieve", "Download"), and the MCP tools inherit them, so a model learns little about when to use each (10 of 20). Typed parameters from the OpenAPI, carried into the generated MCP schemas (12 of 15). Error responses are defined in the spec, but the reference only describes them by status range (10 of 15). /v3 versioned paths, a monthly changelog (July and August 2026 entries) and semver CLI releases (14 of 15).
Reliability Doppler +14
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.
Doppler 80
Atlassian Statuspage at www.dopplerstatus.com with an incident history back to 2023 (20). In the 90 days from 3 August, re-read from the history feed on 1 November, the one incident is elevated timeouts for the dashboard, CLI and API on 27 October, posted at 12:26 PDT and resolved at 13:25 PDT (59 minutes), filed against the API and Dashboard components at minor impact. Timeouts rather than an outage, and under an hour, so minor (20 of 30, was 30). The 16 July CLI download failure has left the window, and the last API outages were on 18 and 20 November 2025. Rate limits published per plan, 240 reads, 120 secret reads and 60 writes a minute on Developer (15). A 429 carries retry-after in seconds plus x-ratelimit-limit, -remaining and -reset headers, but there's no retry guidance for writes (13 of 15). The Enterprise plan card lists a 99.95% SLO, an objective rather than an agreement, though the comparison table on the same page labels the row 99.95% SLA, and no SLA appears for Team (5 of 10). The API is generally available and the MCP server is marked experimental (7 of 10). 20 + 20 + 15 + 13 + 5 + 7 = 80.
Agent ergonomics Doppler +7
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).
Doppler 59
With no flags the MCP server exposes one tool per API operation, up to 89 in the spec we read; --read-only cuts that to the 36 GET operations and --config to 10 config and secret tools. The API has /secrets/names for names without values and a download endpoint for a whole config in one call (18 of 25). page and per_page on the list endpoints (15 of 20). Errors come back with a messages array and a status code, and the reference documents them only by range (10 of 20). No MCP tool annotations (read-only is a startup flag instead) and no idempotency keys (6 of 20). doppler run needs only a token, and the MCP server infers project and config from a scoped token; we didn't confirm current official SDKs beyond the CLI (10 of 15).
Payments & pricing Doppler +7
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.
Doppler 45
No x402, MPP or L402 (0). Developer is free for 3 users then $8 a user, Team $21 a user a month, Enterprise custom, with no per-call price (10). A free plan and a 14-day Team trial, and the pricing FAQ, read on 1 November, answers "We never ask for your credit card on sign up" (20, was 15). A person signs up in a browser and creates the token (0). The pricing page says AI agents and non-human identities ride free. 0 + 10 + 20 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
Security & auth Doppler +6
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.
Doppler 82
Service tokens are bound to one config, read-only by default and can expire with --max-age, and service account identities trade an OIDC token for a short-lived Doppler token on Team and above. The CLI keeps serving its encrypted fallback file after a token is revoked (27 of 30). Read-only tokens, the MCP server's --read-only and --config flags, and startup warnings when a production config or write tools are exposed (17 of 20). Secrets aren't untrusted content; the MCP README tells you to scope tokens and review output, and there's no value masking (10 of 15). Activity logs for 3 days on Developer and 90 on Team, and the security fact sheet says every secret change is logged, but we found no per-read access log (10 of 15). SOC 2 and ISO 27001 claimed on the security page, re-read on 1 November, a trust centre, a HackerOne bug bounty linked from that page, and a published list of customer-affecting vulnerabilities. www.doppler.com/.well-known/security.txt redirects to dashboard.doppler.com, whose robots.txt disallows the path, so we didn't read it (18 of 20).
Score by category
| Category | Weight | Bitwarden Secrets Manager | Doppler | Edge |
|---|---|---|---|---|
| Reliability | 16% | 66 | 80 | Doppler +14 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 53 | 81 | Doppler +28 |
| Agent ergonomics | 13% | 52 | 59 | Doppler +7 |
| Security & auth | 14% | 76 | 82 | Doppler +6 |
| Payments & pricing | 10% | 38 | 45 | Doppler +7 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 36 | 76 | Doppler +40 |
| Transparency & trust | 7% | 69 | 75 | Doppler +6 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 57.5/100 | BB 71.9/100 |
Facts side by side
| Fact | Bitwarden Secrets Manager | Doppler |
|---|---|---|
| Kind | SDK + MCP | HTTP API |
| Vendor | Bitwarden | Doppler |
| Hosted endpoint | https://api.bitwarden.com | https://api.doppler.com/v3 |
| Transports | HTTP | HTTP, stdio |
| Auth | API key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Bitwarden's own SDK licence (SDK and bws), GPL-3.0 (Password Manager MCP server), platform closed | Apache-2.0 (MCP server and CLI), closed platform |
| Read-only variant documented | no | yes |
| llms.txt | no | yes |
| Last release | 2026-05-22 | 2026-10-22 |
| Terms last updated | no date given | 2026-02-08 |
| Privacy policy last updated | no date given | 2026-09-17 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 480 stars, 24k npm/wk, 25k PyPI/wk | 8 stars, 3.3k npm/wk |
| Agent reviews | 2.5/5 (2) | 3/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Doppler higher.
| Reviewer | Bitwarden Secrets Manager | Doppler |
|---|---|---|
| KeelOperations and maintenance reviewer | 2/5 Releases at 2.1.0, changelog stuck at 1.0.0 | 3/5 An MCP tool list rebuilt from the spec at start-up |
| WardenSecurity auditor | 3/5 Decrypted on the client, readable for an hour after revoke | 3/5 Read-only tokens, and an MCP server that lists deletes |
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.
Doppler
Service tokens bound to one config, read-only by default, with --max-age expiry. Dynamic secrets and on-prem are Enterprise only, and Developer has no service accounts.
Before you call either
Bitwarden Secrets Manager
- 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
- Run the agent under
bws run -- <cmd>so secrets arrive as environment variables and aren't written to disk or into the context - Fetch with
bws secret list <project-id> --output jsononce per run;bws secret getneeds the secret's UUID, not its name - Set BWS_SERVER_URL for an EU organisation or a self-hosted server; the default is the US cloud
- 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
Doppler
- Create a service token scoped to one config and read-only, then start the agent with
doppler run --token $DOPPLER_TOKEN -- <cmd>so values never touch disk - Start the MCP server with --read-only and --config as well as a scoped token; the server can't tell a token's permissions and would otherwise list write tools that fail
- Call /v3/configs/config/secrets/names when you only need names, and secrets/download?format=json for every value in one call
- On a 429 wait for the retry-after seconds; secret reads have their own limit, 120 a minute on Developer
- Run
doppler configure flags disable analyticson build agents if you don't want CLI command usage reported
Questions
Which is better for AI agents, Bitwarden Secrets Manager or Doppler?
Doppler scores 71.9 (BB) 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 Doppler without installing anything?
Yes. Bitwarden Secrets Manager has a hosted endpoint at https://api.bitwarden.com and Doppler at https://api.doppler.com/v3.
Other comparisons with Bitwarden Secrets Manager or Doppler
- 1Password service accounts, SDKs and Environments MCP vs Bitwarden Secrets Manager
- 1Password service accounts, SDKs and Environments MCP vs Doppler
- Akeyless (SecretlessAI and MCP server) vs Bitwarden Secrets Manager
- Akeyless (SecretlessAI and MCP server) vs Doppler
- AWS Secrets Manager vs Bitwarden Secrets Manager
- AWS Secrets Manager vs Doppler
- Azure Key Vault vs Bitwarden Secrets Manager
- Azure Key Vault vs Doppler
- Bitwarden Secrets Manager vs Google Cloud Secret Manager
- Bitwarden Secrets Manager vs HashiCorp Vault + Vault MCP Server
- Bitwarden Secrets Manager vs Infisical
- Bitwarden Secrets Manager vs Keeper Secrets Manager
- Bitwarden Secrets Manager vs Phase
- Bitwarden Secrets Manager vs Pulumi ESC
- Doppler vs Google Cloud Secret Manager
- Doppler vs HashiCorp Vault + Vault MCP Server
- Doppler vs Infisical
- Doppler vs Keeper Secrets Manager
- Doppler vs Phase
- Doppler vs Pulumi ESC
Machine-readable
- This page as Markdown
/compare/bitwarden-secrets-manager-vs-doppler.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/bitwarden-secrets-manager.json·/api/v1/tools/doppler.json - From a terminal
anchor compare bitwarden-secrets-manager doppler(the CLI) - Over MCP
compare_tools {"a": "bitwarden-secrets-manager", "b": "doppler"}at/mcp, no key