{ "data": { "a": { "slug": "bitwarden-secrets-manager", "name": "Bitwarden Secrets Manager", "vendor": "Bitwarden", "vendorUrl": "https://bitwarden.com/products/secrets-manager/", "kind": "sdk", "category": "secrets", "summary": "End-to-end encrypted secrets store from the Bitwarden password manager company.", "url": "https://www.anchorterminal.com/tools/bitwarden-secrets-manager", "markdownUrl": "https://www.anchorterminal.com/tools/bitwarden-secrets-manager.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/bitwarden-secrets-manager.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/bitwarden-secrets-manager.json", "repo": "https://github.com/bitwarden/sdk-sm", "license": "Bitwarden's own SDK licence (SDK and bws), GPL-3.0 (Password Manager MCP server), platform closed", "transports": [ "http" ], "remoteUrl": "https://api.bitwarden.com", "packages": [ { "registry": "npm", "name": "@bitwarden/sdk-napi" }, { "registry": "pypi", "name": "bitwarden-sdk" } ], "auth": "api-key", "authNotes": "A machine account access token (`0.\u003cuuid\u003e.\u003cclient secret\u003e:\u003cencryption key\u003e`) goes in `BWS_ACCESS_TOKEN` or `--access-token`. The SDK exchanges the client secret at identity.bitwarden.com, then decrypts secrets locally with the key embedded in the token, so a plain curl can't read a value. Tokens are shown once, never stored server-side, and can expire on a date you set (default never).", "pricing": "freemium", "pricingNotes": "Secrets Manager has a free plan (2 users, 3 projects, 3 machine accounts, unlimited secrets, no event logs) and paid Teams and Enterprise plans. Teams $6 per user a month with 20 machine accounts included, Enterprise $12 per user a month with 50, and $1 a month per extra machine account on either. Secret storage, projects and users are unlimited on paid plans, and event logs come with Teams and Enterprise. A 14-day trial is on the pricing page; neither page says whether a card is needed. The product page lists self-hosting on Enterprise, while the plans help page still says coming soon (https://bitwarden.com/pricing/business/, https://bitwarden.com/help/secrets-manager-plans/).", "priceSummary": "$6 / seat-mo", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 480, "npmWeekly": 24038, "pypiWeekly": 25331, "asOf": "2026-09-30" }, "docsUrl": "https://bitwarden.com/help/secrets-manager-overview/", "capabilities": [ "secrets.store", "secrets.machine-identity", "secrets.audit", "secrets.self-host" ], "tags": [ "hosted", "self-hosted", "freemium", "source-available", "typescript", "python", "go", "enterprise", "eu" ], "lastRelease": "2026-05-22", "graded": true, "anchor": { "graded": true, "score": 57.1, "grade": "C", "agentReady": false, "rank": 297, "ranked": true, "rankOf": 452, "categoryRank": 8, "methodology": "0.3", "run": "2026-10-01", "scores": { "ergonomics": 52, "maintenance": 36, "payments": 25, "reliability": 71, "schema": 53, "security": 76, "transparency": 71 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "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.", "strengths": [ "End-to-end encrypted, decrypted only on the client that holds the token", "Machine accounts at $1 a month each, 3 on the free plan, with Can read or Can read, write per project", "Per-machine-account event logs of secret access, retained indefinitely, on Teams and Enterprise", "SOC 2 Type II, ISO 27001 and a HackerOne bounty", "US or EU cloud, with self-hosting on Enterprise" ], "weaknesses": [ "No release since 22 May 2026, and the npm SDK is still 1.0.0 from September 2024", "33 open issues, mostly bugs, including a Python SDK segfault open since July 2025", "Revoked tokens keep working for up to an hour on already-authenticated machines", "No rotation, dynamic secrets, workload identity login or MCP server for Secrets Manager", "SDK and CLI under Bitwarden's own SDK licence, and no OpenAPI for the secrets API" ], "agentNotes": [ "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 -- \u003ccmd\u003e` so secrets arrive as environment variables and aren't written to disk or into the context", "Fetch with `bws secret list \u003cproject-id\u003e --output json` once per run; `bws secret get` needs 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" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 2.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.3", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 57.1 } ], "editorialScores": { "ergonomics": 52, "maintenance": 36, "payments": 25, "reliability": 71, "schema": 53, "security": 76, "transparency": 52 }, "provenanceScore": 90 }, "connect": { "install": "cargo install bws --locked # or: curl https://bws.bitwarden.com/install | sh, npm install @bitwarden/sdk-napi, pip install bitwarden-sdk", "http": "export BWS_ACCESS_TOKEN=\"$BWS_ACCESS_TOKEN\"\nbws secret list \"$BWS_PROJECT_ID\" # values are end-to-end encrypted, so the CLI or SDK decrypts; plain curl can't" }, "letme": { "capability": "https://letme.dev/secrets.store", "tool": "https://letme.dev/bitwarden-secrets-manager" }, "area": "agent-runtime", "unitPrices": [ { "item": "Secrets Manager, Teams", "unit": "seat-month", "usd": 6, "note": "20 machine accounts included" }, { "item": "Secrets Manager, Enterprise", "unit": "seat-month", "usd": 12, "note": "50 machine accounts included" }, { "item": "Extra machine account", "unit": "account-month", "usd": 1 } ], "provenance": { "legalEntity": "Bitwarden Inc. (terms name 8bit Solutions LLC, wholly owned by Bitwarden Inc.)", "domain": "bitwarden.com", "domainRegistered": "2015-11-16", "endpointOnVendorDomain": true, "terms": "https://bitwarden.com/terms/", "privacy": "https://bitwarden.com/privacy/", "statusPage": "https://status.bitwarden.com", "changelog": "https://github.com/bitwarden/sdk-sm/releases", "securityTxt": "none", "checked": "2026-10-01", "notes": [ "Terms dated 1 June 2017 name 8bit Solutions LLC, a Delaware company wholly owned by Bitwarden Inc. The privacy policy (revised April 2024) gives Bitwarden Inc., 1 North Calle Cesar Chavez, Suite 102, Santa Barbara, CA 93103, with data stored primarily in the EEA and United States.", "bitwarden.com/.well-known/security.txt returned 404 on 30 September 2026; the SDK repository's SECURITY.md points to HackerOne.", "status.bitwarden.com runs on Hund.io. Since 3 July 2026 it shows five planned maintenance windows and one unscheduled incident, elevated US API error rates for 38 minutes on 29 September.", "The compliance page claims SOC 2 Type II, SOC 3, ISO 27001 and HIPAA, with data on Azure in the US or EU.", "The crate changelogs in sdk-sm stop at 1.0.0 (September 2024); later releases are only described on GitHub." ], "score": 90 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/bitwarden-secrets-manager.json", "live": { "slug": "bitwarden-secrets-manager", "probe": { "target": "https://api.bitwarden.com", "method": "get", "lastAt": "2026-10-04T23:32:44.11508903Z", "lastOk": true, "lastStatus": 404, "lastMs": 291, "authRequired": false, "uptime24h": 99.26, "uptime30d": 97.32, "p50ms24h": 130, "p95ms24h": 328, "samples24h": 272, "samples30d": 895, "days": [ { "date": "2026-10-01", "probes": 109, "ok": 102 }, { "date": "2026-10-02", "probes": 248, "ok": 239 }, { "date": "2026-10-03", "probes": 271, "ok": 265 }, { "date": "2026-10-04", "probes": 267, "ok": 265 } ] }, "vendorStatus": { "page": "https://status.bitwarden.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-04T21:39:50.88623142Z" }, "versions": [ { "registry": "github", "name": "bitwarden/sdk-sm", "version": "python-v2.1.0", "released": "2026-05-21", "seenAt": "2026-10-04T16:22:18.502566508Z" }, { "registry": "npm", "name": "@bitwarden/sdk-napi", "version": "1.0.0", "seenAt": "2026-10-04T16:22:17.909661383Z" }, { "registry": "pypi", "name": "bitwarden-sdk", "version": "2.1.0", "released": "2026-05-21", "seenAt": "2026-10-04T16:22:18.317866887Z" } ], "githubStars": 480, "npmWeekly": 25074, "pypiWeekly": 27867, "securityTxt": { "url": "https://bitwarden.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-04T15:15:46.220509573Z" }, "domain": { "domain": "bitwarden.com", "registered": "2015-11-16", "source": "https://rdap.verisign.com/com/v1/domain/bitwarden.com", "checkedAt": "2026-10-04T13:03:43.146799125Z" }, "pages": [ { "url": "https://bitwarden.com/pricing/business/", "kind": "pricing", "status": 304, "checkedAt": "2026-10-04T15:41:30.968841046Z", "changedAt": "2026-10-03T15:29:42.809015327Z", "fingerprint": "8d0a67e9a051" }, { "url": "https://bitwarden.com/privacy/", "kind": "privacy", "status": 200, "checkedAt": "2026-10-04T15:41:32.998627256Z", "changedAt": "2026-10-04T15:41:32.998627256Z", "fingerprint": "612dca4ba267" }, { "url": "https://bitwarden.com/terms/", "kind": "terms", "status": 304, "checkedAt": "2026-10-04T15:41:35.010005656Z", "changedAt": "2026-10-03T15:29:46.855070037Z", "fingerprint": "662bff2efe7c" } ], "updatedAt": "2026-10-04T23:32:44.11508903Z" } }, "b": { "slug": "doppler", "name": "Doppler", "vendor": "Doppler", "vendorUrl": "https://www.doppler.com", "kind": "http-api", "category": "secrets", "summary": "Hosted secrets manager organised by project, environment and config.", "url": "https://www.anchorterminal.com/tools/doppler", "markdownUrl": "https://www.anchorterminal.com/tools/doppler.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/doppler.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/doppler.json", "repo": "https://github.com/DopplerHQ/mcp-server", "license": "Apache-2.0 (MCP server and CLI), closed platform", "transports": [ "http", "stdio" ], "remoteUrl": "https://api.doppler.com/v3", "packages": [ { "registry": "npm", "name": "@dopplerhq/mcp-server" } ], "auth": "mixed", "authNotes": "Bearer tokens on api.doppler.com. Service tokens (`dp.st.\u003cenv\u003e.…`) are scoped to one config, read-only by default and can expire with `--max-age`. Service account identities exchange an OIDC token (GitHub Actions, Kubernetes, AWS EC2 or any issuer) for a short-lived Doppler token at POST /v3/auth/oidc, Team plan and above. The MCP server takes `DOPPLER_TOKEN` or `npx @dopplerhq/mcp-server login`.", "pricing": "freemium", "pricingNotes": "Developer plan is free for 3 users then $8 a month per extra user, with 10 projects, 50 service tokens, 3-day activity logs and API-based rotation only. Team $21 a month per user with a 14-day trial, 250 projects, 500 service tokens, service accounts, automatic rotation, 90-day logs and SAML. Enterprise is custom, with dynamic secrets (AWS IAM and Azure service principals), proxied rotation, SCIM, on-prem and a 99.95% SLO. The pricing page says AI agents and non-human identities ride free, and doesn't say whether a card is needed (https://www.doppler.com/pricing, https://docs.doppler.com/docs/dynamic-secrets).", "priceSummary": "$21 / seat-mo", "where": "both", "x402": { "level": "no", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 8, "npmWeekly": 3261, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://docs.doppler.com", "llmsTxt": "https://docs.doppler.com/llms.txt", "openapi": "https://docs.doppler.com/openapi/core.json", "capabilities": [ "secrets.store", "secrets.rotate", "secrets.machine-identity", "secrets.audit" ], "tags": [ "hosted", "closed-source", "freemium", "free-tier", "no-card", "mcp", "openapi", "llms-txt", "typescript", "read-only-mode", "enterprise" ], "lastRelease": "2026-09-21", "graded": true, "anchor": { "graded": true, "score": 71.6, "grade": "BB", "agentReady": true, "rank": 79, "ranked": true, "rankOf": 452, "categoryRank": 5, "methodology": "0.3", "run": "2026-10-01", "scores": { "ergonomics": 59, "maintenance": 76, "payments": 25, "reliability": 90, "schema": 81, "security": 82, "transparency": 77 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "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.", "strengths": [ "Service tokens bound to one config, read-only by default, with --max-age expiry", "OIDC service account identities on Team, so shared runners don't hold a static token", "OpenAPI 3.1 and an llms.txt with about 500 Markdown links", "Published per-plan rate limits with retry-after and x-ratelimit headers on a 429", "MCP server with --read-only and --config modes that cut the tool list to 36 or 10" ], "weaknesses": [ "Dynamic secrets and on-prem are Enterprise only, and Developer has no service accounts", "The MCP server is experimental, has no tool annotations or value masking, and exposes up to 89 tools by default", "35 open CLI issues, most of the newest without a reply", "The CLI keeps serving its fallback file after a token is revoked, and sends anonymous analytics unless turned off", "No SLA, only a 99.95% SLO on Enterprise" ], "agentNotes": [ "Create a service token scoped to one config and read-only, then start the agent with `doppler run --token $DOPPLER_TOKEN -- \u003ccmd\u003e` 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 analytics` on build agents if you don't want CLI command usage reported" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.3", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 71.6 } ], "editorialScores": { "ergonomics": 59, "maintenance": 76, "payments": 25, "reliability": 90, "schema": 81, "security": 82, "transparency": 64 }, "provenanceScore": 90 }, "connect": { "http": "curl \"https://api.doppler.com/v3/configs/config/secrets/download?format=json\" \\\n -H \"Authorization: Bearer $DOPPLER_TOKEN\"", "claudeCode": "claude mcp add doppler -e DOPPLER_TOKEN=$DOPPLER_TOKEN -- npx -y @dopplerhq/mcp-server --read-only", "config": { "mcpServers": { "doppler": { "args": [ "-y", "@dopplerhq/mcp-server", "--read-only" ], "command": "npx", "env": { "DOPPLER_TOKEN": "${DOPPLER_TOKEN}" } } } } }, "letme": { "capability": "https://letme.dev/secrets.store", "tool": "https://letme.dev/doppler" }, "area": "agent-runtime", "unitPrices": [ { "item": "Team plan", "unit": "seat-month", "usd": 21, "note": "14-day trial" }, { "item": "Developer plan, extra user", "unit": "seat-month", "usd": 8, "note": "First 3 users free" } ], "provenance": { "legalEntity": "Doppler Technologies, Inc.", "domain": "doppler.com", "domainRegistered": "1999-01-24", "domainNote": "doppler.com was registered in 1999, long before the company, so the domain was bought later.", "endpointOnVendorDomain": true, "terms": "https://www.doppler.com/legal/terms", "privacy": "https://www.doppler.com/legal/privacy", "statusPage": "https://www.dopplerstatus.com", "changelog": "https://docs.doppler.com/changelog", "securityTxt": "unknown", "checked": "2026-10-01", "notes": [ "Terms name Doppler Technologies, Inc., 440 North Barranca Avenue #5880, Covina, CA 91723, last updated 8 February 2026. Privacy notice updated 17 September 2026, data stored in the United States.", "www.doppler.com/.well-known/security.txt is disallowed by robots.txt, so we couldn't read it.", "www.dopplerstatus.com is Atlassian Statuspage. Its history shows one incident since 3 July 2026 (CLI downloads failing, 16 July) and system outages on 18 November 2025 and 12 June 2025.", "The subprocessor list (13 July 2026) names 9 subprocessors, 8 in the United States and Groundcover in Israel, and links a DPA and an on-prem DPA.", "The security fact sheet puts all servers in GCP us-central1 and says HackerOne handles disclosures." ], "score": 90 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/doppler.json", "live": { "slug": "doppler", "probe": { "target": "https://api.doppler.com/v3", "method": "get", "lastAt": "2026-10-04T23:32:46.582114423Z", "lastOk": true, "lastStatus": 401, "lastMs": 150, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 150, "p95ms24h": 214, "samples24h": 272, "samples30d": 895, "days": [ { "date": "2026-10-01", "probes": 109, "ok": 109 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 267, "ok": 267 } ] }, "vendorStatus": { "page": "https://www.dopplerstatus.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-04T23:27:44.403159014Z" }, "versions": [ { "registry": "github", "name": "DopplerHQ/mcp-server", "version": "v1.0.5", "released": "2026-06-04", "seenAt": "2026-10-04T16:25:42.222400654Z" }, { "registry": "npm", "name": "@dopplerhq/mcp-server", "version": "1.0.5", "seenAt": "2026-10-04T16:25:41.357710821Z" } ], "githubStars": 8, "npmWeekly": 5296, "securityTxt": { "url": "https://doppler.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-04T15:15:42.3339237Z" }, "llmsTxt": { "url": "https://docs.doppler.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-04T15:17:31.061902909Z" }, "domain": { "domain": "doppler.com", "registered": "1999-01-24", "source": "https://rdap.verisign.com/com/v1/domain/doppler.com", "checkedAt": "2026-10-04T13:08:29.130637863Z" }, "pages": [ { "url": "https://docs.doppler.com/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-10-04T15:43:35.303385156Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "816d6475b1bd" }, { "url": "https://www.doppler.com/pricing", "kind": "pricing", "status": 304, "checkedAt": "2026-10-04T15:50:08.235633812Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "61b46ac39ff9" }, { "url": "https://www.doppler.com/legal/privacy", "kind": "privacy", "status": 304, "checkedAt": "2026-10-04T15:50:03.99159557Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "306950b580d5" }, { "url": "https://www.doppler.com/legal/terms", "kind": "terms", "status": 304, "checkedAt": "2026-10-04T15:50:06.172772616Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "642e87a74245" } ], "updatedAt": "2026-10-04T23:32:46.582114423Z" } }, "summary": "Doppler has a score of 71.6 (BB) against Bitwarden Secrets Manager's 57.1 (C). Both do secrets store. The largest gap is maintenance \u0026 community, 40 points." }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-doppler", "json": "https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-doppler.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-doppler.md", "slim": "https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-doppler.min.md" }, "markdown": "Doppler has a score of 71.6 (BB) against Bitwarden Secrets Manager's 57.1 (C). Both do secrets store. The largest gap is maintenance \u0026 community, 40 points.\n\n- Bitwarden Secrets Manager: grade C, 57.1/100, rank #297 of 452. Markdown https://www.anchorterminal.com/tools/bitwarden-secrets-manager.md · JSON https://www.anchorterminal.com/api/v1/tools/bitwarden-secrets-manager.json\n- Doppler: grade BB, 71.6/100, rank #79 of 452. Markdown https://www.anchorterminal.com/tools/doppler.md · JSON https://www.anchorterminal.com/api/v1/tools/doppler.json\n\n## Which one, for what\n\nPick Bitwarden Secrets Manager for nothing in particular (no category where it leads by five points or more).\n\nPick Doppler for reliability (+19), schema \u0026 documentation (+28), agent ergonomics (+7), security \u0026 auth (+6), maintenance \u0026 community (+40), transparency \u0026 trust (+6).\n\n## Score by category\n\n| Category | Weight | Bitwarden Secrets Manager | Doppler | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 71 | 90 | Doppler +19 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 53 | 81 | Doppler +28 |\n| Agent ergonomics | 13% (16.2 this run) | 52 | 59 | Doppler +7 |\n| Security \u0026 auth | 14% (17.5 this run) | 76 | 82 | Doppler +6 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 25 | 25 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 36 | 76 | Doppler +40 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 71 | 77 | Doppler +6 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **57.1 · C** | **71.6 · BB** | |\n\n## Facts side by side\n\n| Fact | Bitwarden Secrets Manager | Doppler |\n| --- | --- | --- |\n| Kind | SDK + MCP | HTTP API |\n| Vendor | Bitwarden | Doppler |\n| Hosted endpoint | `https://api.bitwarden.com` | `https://api.doppler.com/v3` |\n| Transports | HTTP | HTTP, stdio |\n| Auth | API key | OAuth or key |\n| Pricing | Freemium | Freemium |\n| x402 | no | no |\n| 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 |\n| Tools exposed | none | none |\n| Context cost (tools/list) | n/a | n/a |\n| p95 latency | not measured yet | not measured yet |\n| Availability (30d) | not measured yet | not measured yet |\n| Read-only variant documented | no | yes |\n| llms.txt | no | yes |\n| MCP registry | not listed | not listed |\n| Last release | 2026-05-22 | 2026-09-21 |\n| Popularity | 480 stars, 24k npm/wk, 25k PyPI/wk | 8 stars, 3.3k npm/wk |\n| Agent reviews | 2.5/5 (2) | 3/5 (2) |\n\n## Verdicts\n\n**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.\n\n**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.\n\n## Before you call either\n\n### Bitwarden Secrets Manager\n\n1. 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\n2. Run the agent under `bws run -- \u003ccmd\u003e` so secrets arrive as environment variables and aren't written to disk or into the context\n3. Fetch with `bws secret list \u003cproject-id\u003e --output json` once per run; `bws secret get` needs the secret's UUID, not its name\n4. Set BWS_SERVER_URL for an EU organisation or a self-hosted server; the default is the US cloud\n5. 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\n\n### Doppler\n\n1. Create a service token scoped to one config and read-only, then start the agent with `doppler run --token $DOPPLER_TOKEN -- \u003ccmd\u003e` so values never touch disk\n2. 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\n3. Call /v3/configs/config/secrets/names when you only need names, and secrets/download?format=json for every value in one call\n4. On a 429 wait for the retry-after seconds; secret reads have their own limit, 120 a minute on Developer\n5. Run `doppler configure flags disable analytics` on build agents if you don't want CLI command usage reported\n\n## Other comparisons with Bitwarden Secrets Manager or Doppler\n\n- [1Password service accounts, SDKs and Environments MCP vs Bitwarden Secrets Manager](https://www.anchorterminal.com/compare/1password-vs-bitwarden-secrets-manager.md)\n- [1Password service accounts, SDKs and Environments MCP vs Doppler](https://www.anchorterminal.com/compare/1password-vs-doppler.md)\n- [Akeyless (SecretlessAI and MCP server) vs Bitwarden Secrets Manager](https://www.anchorterminal.com/compare/akeyless-vs-bitwarden-secrets-manager.md)\n- [Akeyless (SecretlessAI and MCP server) vs Doppler](https://www.anchorterminal.com/compare/akeyless-vs-doppler.md)\n- [AWS Secrets Manager vs Bitwarden Secrets Manager](https://www.anchorterminal.com/compare/aws-secrets-manager-vs-bitwarden-secrets-manager.md)\n- [AWS Secrets Manager vs Doppler](https://www.anchorterminal.com/compare/aws-secrets-manager-vs-doppler.md)\n- [Bitwarden Secrets Manager vs Google Cloud Secret Manager](https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-google-secret-manager.md)\n- [Bitwarden Secrets Manager vs HashiCorp Vault + Vault MCP Server](https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-hashicorp-vault.md)\n- [Bitwarden Secrets Manager vs Infisical](https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-infisical.md)\n- [Doppler vs Google Cloud Secret Manager](https://www.anchorterminal.com/compare/doppler-vs-google-secret-manager.md)\n- [Doppler vs HashiCorp Vault + Vault MCP Server](https://www.anchorterminal.com/compare/doppler-vs-hashicorp-vault.md)\n- [Doppler vs Infisical](https://www.anchorterminal.com/compare/doppler-vs-infisical.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-04", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.3", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Bitwarden Secrets Manager vs Doppler", "url": "" } ], "description": "Doppler has a score of 71.6 (BB) against Bitwarden Secrets Manager's 57.1 (C). Both do secrets store. The largest gap is maintenance \u0026 community, 40 points. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Bitwarden Secrets Manager C 57.1", "Doppler BB 71.6", "scores" ], "h1": "Bitwarden Secrets Manager vs Doppler", "image": "https://www.anchorterminal.com/assets/og/compare-bitwarden-secrets-manager-vs-doppler.png", "path": "/compare/bitwarden-secrets-manager-vs-doppler", "published": "2026-10-01", "section": "tools", "title": "Bitwarden Secrets Manager vs Doppler for AI agents, C 57.1 vs BB 71.6", "toc": null, "updated": "2026-10-04", "url": "https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-doppler" }, "tokens": { "markdown": 1700, "slim": 380 }, "version": 1 }