{ "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": 56.8, "grade": "C", "agentReady": false, "rank": 485, "ranked": true, "rankOf": 722, "categoryRank": 12, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 52, "maintenance": 36, "payments": 25, "reliability": 71, "schema": 53, "security": 76, "transparency": 68 }, "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.", "bestFor": "Teams already on Bitwarden who want cheap, end-to-end encrypted, project-scoped machine identities for a few agents, injected with bws run.", "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.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 56.8 } ], "editorialScores": { "ergonomics": 52, "maintenance": 36, "payments": 25, "reliability": 71, "schema": 53, "security": 76, "transparency": 52 }, "provenanceScore": 84 }, "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": 84 }, "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-08T21:53:17.410604134Z", "lastOk": true, "lastStatus": 404, "lastMs": 300, "authRequired": false, "uptime24h": 100, "uptime30d": 98.78, "p50ms24h": 133, "p95ms24h": 313, "samples24h": 270, "samples30d": 1962, "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": 272, "ok": 270 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 246, "ok": 246 } ] }, "vendorStatus": { "page": "https://status.bitwarden.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-08T19:38:16.898427121Z" }, "versions": [ { "registry": "github", "name": "bitwarden/sdk-sm", "version": "python-v2.1.0", "released": "2026-05-21", "seenAt": "2026-10-08T16:02:40.627075558Z" }, { "registry": "npm", "name": "@bitwarden/sdk-napi", "version": "1.0.0", "seenAt": "2026-10-08T16:02:33.051154571Z" }, { "registry": "pypi", "name": "bitwarden-sdk", "version": "2.1.0", "released": "2026-05-21", "seenAt": "2026-10-08T16:02:37.126897729Z" } ], "githubStars": 480, "npmWeekly": 24793, "pypiWeekly": 27508, "securityTxt": { "url": "https://bitwarden.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-08T15:38:59.925999921Z" }, "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-08T18:15:41.604041505Z", "changedAt": "2026-10-03T15:29:42.809015327Z", "fingerprint": "8d0a67e9a051" }, { "url": "https://bitwarden.com/privacy/", "kind": "privacy", "status": 304, "checkedAt": "2026-10-08T18:15:43.614322059Z", "changedAt": "2026-10-05T15:53:46.653942518Z", "fingerprint": "c466a72d860e" }, { "url": "https://bitwarden.com/terms/", "kind": "terms", "status": 200, "checkedAt": "2026-10-08T18:15:45.610985937Z", "changedAt": "2026-10-03T15:29:46.855070037Z", "fingerprint": "662bff2efe7c" } ], "updatedAt": "2026-10-08T21:53:17.410604134Z" } }, "answer": "Phase scores 68 (B) on agent readiness against Bitwarden Secrets Manager's 56.8 (C), and leads in 6 of 7 scored categories.", "b": { "slug": "phase", "name": "Phase", "vendor": "Phi Security Inc.", "vendorUrl": "https://phase.dev", "kind": "http-api", "category": "secrets", "summary": "Phase is an open-source secrets manager from Phi Security Inc. with end-to-end encryption, service accounts, secret rotation and audit logs. Agents reach it through a REST API, a CLI and SDKs, on Phase Cloud or self-hosted.", "url": "https://www.anchorterminal.com/tools/phase", "markdownUrl": "https://www.anchorterminal.com/tools/phase.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/phase.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/phase.json", "repo": "https://github.com/phasehq/console", "license": "MIT outside the `ee/` directories, which are under the proprietary Phase Console Enterprise licence", "transports": [ "http" ], "remoteUrl": "https://api.phase.dev", "packages": [ { "registry": "npm", "name": "@phase.dev/phase-node" }, { "registry": "pypi", "name": "phase-dev" }, { "registry": "go", "name": "github.com/phasehq/golang-sdk" } ], "auth": "mixed", "authNotes": "Self-serve. A person signs in to the console with Google, GitHub or GitLab, creates a service account and a token with an optional expiry, and the agent sends it as `Authorization: Bearer ServiceAccount \u003ctoken\u003e`. Personal access tokens use `Bearer User \u003ctoken\u003e` and inherit the user's role. Tokens can also be created and deleted over the API for service accounts with server-side key management. Workloads on AWS or Azure can log in with an external identity and receive a token with a TTL. Access follows the account's role and its apps and environments, not the individual token.", "pricing": "freemium", "pricingNotes": "Free plan at $0 with 5 users or service accounts, 3 apps, 3 environments, 24-hour audit logs and 120 API requests a minute. Pro is $10 a user a month ($120 billed yearly) with a 14-day trial, unlimited apps, rotation, custom roles, network access policies, 90-day audit logs and 240 requests a minute. Enterprise is $25 a user a month ($300 yearly) with dynamic secrets, OIDC SSO, SCIM, log forwarding and a 99.99 per cent uptime SLA listed. Only human users are charged, and service accounts are free. The pricing page does not say whether a card is taken. Self-hosting the MIT core is free, and the Pro and Enterprise tiers need a licence (https://phase.dev/pricing/).", "priceSummary": "$10 / seat-mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, the API reference or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 928, "npmWeekly": 2485, "pypiWeekly": 235, "asOf": "2026-10-08" }, "docsUrl": "https://docs.phase.dev", "llmsTxt": "https://docs.phase.dev/llms.txt", "capabilities": [ "secrets.store", "secrets.machine-identity", "secrets.audit", "secrets.self-host", "secrets.rotate" ], "tags": [ "hosted", "self-hosted", "open-source", "freemium", "free-tier", "cli", "llms-txt", "go", "typescript", "python", "eu", "status-page", "soc2" ], "lastRelease": "2026-10-04", "graded": true, "anchor": { "graded": true, "score": 68, "grade": "B", "agentReady": false, "rank": 194, "ranked": true, "rankOf": 722, "categoryRank": 10, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 56, "maintenance": 83, "payments": 25, "reliability": 91, "schema": 58, "security": 83, "transparency": 73 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "Service account tokens can be minted with an expiry over the API, every secret read is logged, and the CLI redacts values when it detects an AI agent. No OpenAPI document or pagination was found in the reviewed documentation, and the Free plan keeps audit logs for 24 hours.", "bestFor": "Small teams that want an open-source secrets manager hosted in the EU or self-hosted, with coding agents kept away from values through the CLI.", "strengths": [ "Service account tokens take an expiry and can be created and deleted through `/v1/service-accounts/:id/tokens`, and service accounts are free on every plan", "The CLI's AI mode redacts `secret` and `sealed` values and blocks `printenv`, `env` and `phase shell` when it detects an agent", "Every reveal and every REST fetch of a secret is recorded as a `READ` event with actor and IP address", "MIT outside the `ee/` directories, self-hosted with Docker Compose or Kubernetes, with no outbound usage telemetry per the docs", "Eleven console versions between 24 July and 8 October 2026, and no incident on the status page since 30 June 2026" ], "weaknesses": [ "No OpenAPI document was found. The REST reference is prose with examples, covering 47 operations", "No pagination, field selection or idempotency keys were found in the API reference, and errors are a single free-text `error` string", "The Free plan keeps audit logs for 24 hours. Rotation, custom roles and network access policies need Pro, and dynamic secrets need Enterprise", "The REST API works only on apps with server-side encryption enabled, which gives up end-to-end encryption for that app", "The pricing page lists a Phase Agents Relay credential proxy on every plan, but no documentation or CLI command for it was found" ], "agentNotes": [ "Enable server-side encryption on the app before calling `/v1/secrets`. Without it the REST API cannot read or write that app's secrets", "Send `Authorization: Bearer ServiceAccount \u003ctoken\u003e` for a service account and `Bearer User \u003ctoken\u003e` for a personal access token. The token type is part of the header", "Stay under 120 requests a minute per account on Free and 240 on Pro, and wait the seconds in the `retry-after` header on a 429", "Treat a 409 on `POST /v1/secrets` as the key already existing at that path, and use `PUT` to change it. Rotating secrets reject `PUT` and `DELETE`", "Have a person run `phase ai enable` and choose masked values. The CLI blocks an agent from running `phase ai enable` or `phase ai disable` itself" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 68 } ], "editorialScores": { "ergonomics": 56, "maintenance": 83, "payments": 25, "reliability": 91, "schema": 58, "security": 83, "transparency": 58 }, "provenanceScore": 87 }, "connect": { "install": "curl -fsSL https://pkg.phase.dev/install.sh | sh # or: brew tap phasehq/cli \u0026\u0026 brew install phase", "http": "curl -G https://api.phase.dev/v1/secrets/ -H \"Authorization: Bearer ServiceAccount $PHASE_TOKEN\" \\\n -d app_id=$PHASE_APP_ID -d env=development", "claudeCode": "phase ai enable" }, "letme": { "capability": "https://letme.dev/secrets.store", "tool": "https://letme.dev/phase" }, "area": "agent-runtime", "unitPrices": [ { "item": "Pro plan", "unit": "seat-month", "usd": 10, "note": "$120 a user billed yearly. Service accounts free" }, { "item": "Enterprise plan", "unit": "seat-month", "usd": 25, "note": "$300 a user billed yearly" } ], "provenance": { "legalEntity": "Phi Security Inc.", "domain": "phase.dev", "domainRegistered": "2023-02-03", "endpointOnVendorDomain": true, "terms": "https://phase.dev/legal/terms/", "privacy": "https://phase.dev/legal/privacy/", "statusPage": "https://phase.statuspage.io", "changelog": "https://phase.dev/changelog/", "securityTxt": "valid", "checked": "2026-10-08", "notes": [ "The terms of service (last updated 6 October 2025) name Phi Security Inc. and cover the website, the Phase Console and the self-hosted version. The site footer gives 8 The Green, Ste A, Dover, DE 19901, United States.", "The privacy policy (last updated 11 March 2026) covers phase.dev and the services, gives no retention period in days and refers to the trust centre for the subprocessor list.", "security.txt at phase.dev expires on 10 December 2030, lists three contact addresses and points to `SECURITY.md` in the console repository.", "trust.phase.dev is drawn by script and gave our reader no text, so the subprocessor list and any DPA were not read.", "RDAP for phase.dev gives a registration date of 2023-02-03.", "The status page is an Atlassian Statuspage at phase.statuspage.io with components for the console, the API, Cloudflare and AWS eu-central-1." ], "score": 87 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/phase.json", "live": { "slug": "phase", "probe": { "target": "https://api.phase.dev", "method": "get", "lastAt": "2026-10-08T21:53:30.432535593Z", "lastOk": true, "lastStatus": 200, "lastMs": 165, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 126, "p95ms24h": 199, "samples24h": 28, "samples30d": 28, "days": [ { "date": "2026-10-08", "probes": 28, "ok": 28 } ] }, "vendorStatus": { "page": "https://phase.statuspage.io", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-08T21:58:09.998402495Z" }, "updatedAt": "2026-10-08T21:58:09.998402495Z" } }, "facts": [ { "a": "SDK + MCP", "b": "HTTP API", "name": "Kind" }, { "a": "Bitwarden", "b": "Phi Security Inc.", "name": "Vendor" }, { "a": "https://api.bitwarden.com", "b": "https://api.phase.dev", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Bitwarden's own SDK licence (SDK and bws), GPL-3.0 (Password Manager MCP server), platform closed", "b": "MIT outside the `ee/` directories, which are under the proprietary Phase Console Enterprise licence", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "2026-05-22", "b": "2026-10-04", "name": "Last release" }, { "a": "no date given", "b": "2025-10-06", "name": "Terms last updated" }, { "a": "no date given", "b": "2026-03-11", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "b": "yes", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "480 stars, 24k npm/wk, 25k PyPI/wk", "b": "928 stars, 2.5k npm/wk, 235 PyPI/wk", "name": "Popularity" }, { "a": "2.5/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Phase scores 68 (B) on agent readiness against Bitwarden Secrets Manager's 56.8 (C), and leads in 6 of 7 scored categories.", "question": "Which is better for AI agents, Bitwarden Secrets Manager or Phase?" }, { "answer": "Yes. Bitwarden Secrets Manager has a hosted endpoint at https://api.bitwarden.com and Phase at https://api.phase.dev.", "question": "Can an agent call Bitwarden Secrets Manager and Phase without installing anything?" }, { "answer": "No open-source release is listed for Bitwarden Secrets Manager. Phase is open source (MIT outside the `ee/` directories, which are under the proprietary Phase Console Enterprise licence).", "question": "Are Bitwarden Secrets Manager and Phase open source?" } ], "goodFor": [ { "aheadOn": null, "also": null, "goodFor": "Teams already on Bitwarden who want cheap, end-to-end encrypted, project-scoped machine identities for a few agents, injected with bws run.", "slug": "bitwarden-secrets-manager", "watchFor": "No release since 22 May 2026, and the npm SDK is still 1.0.0 from September 2024" }, { "aheadOn": [ "Reliability, 91 against 71", "Schema \u0026 documentation, 58 against 53", "Security \u0026 auth, 83 against 76", "Maintenance \u0026 community, 83 against 36", "Transparency \u0026 trust, 73 against 68" ], "also": [ "Open source" ], "goodFor": "Small teams that want an open-source secrets manager hosted in the EU or self-hosted, with coding agents kept away from values through the CLI.", "slug": "phase", "watchFor": "No OpenAPI document was found. The REST reference is prose with examples, covering 47 operations" } ], "job": { "capability": "secrets.store", "name": "Secrets store" }, "others": [ { "json": "https://www.anchorterminal.com/compare/1password-vs-bitwarden-secrets-manager.json", "title": "1Password service accounts, SDKs and Environments MCP vs Bitwarden Secrets Manager", "url": "https://www.anchorterminal.com/compare/1password-vs-bitwarden-secrets-manager" }, { "json": "https://www.anchorterminal.com/compare/1password-vs-phase.json", "title": "1Password service accounts, SDKs and Environments MCP vs Phase", "url": "https://www.anchorterminal.com/compare/1password-vs-phase" }, { "json": "https://www.anchorterminal.com/compare/akeyless-vs-bitwarden-secrets-manager.json", "title": "Akeyless (SecretlessAI and MCP server) vs Bitwarden Secrets Manager", "url": "https://www.anchorterminal.com/compare/akeyless-vs-bitwarden-secrets-manager" }, { "json": "https://www.anchorterminal.com/compare/akeyless-vs-phase.json", "title": "Akeyless (SecretlessAI and MCP server) vs Phase", "url": "https://www.anchorterminal.com/compare/akeyless-vs-phase" }, { "json": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-bitwarden-secrets-manager.json", "title": "AWS Secrets Manager vs Bitwarden Secrets Manager", "url": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-bitwarden-secrets-manager" }, { "json": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-phase.json", "title": "AWS Secrets Manager vs Phase", "url": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-phase" }, { "json": "https://www.anchorterminal.com/compare/azure-key-vault-vs-bitwarden-secrets-manager.json", "title": "Azure Key Vault vs Bitwarden Secrets Manager", "url": "https://www.anchorterminal.com/compare/azure-key-vault-vs-bitwarden-secrets-manager" }, { "json": "https://www.anchorterminal.com/compare/azure-key-vault-vs-phase.json", "title": "Azure Key Vault vs Phase", "url": "https://www.anchorterminal.com/compare/azure-key-vault-vs-phase" }, { "json": "https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-doppler.json", "title": "Bitwarden Secrets Manager vs Doppler", "url": "https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-doppler" }, { "json": "https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-google-secret-manager.json", "title": "Bitwarden Secrets Manager vs Google Cloud Secret Manager", "url": "https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-google-secret-manager" }, { "json": "https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-hashicorp-vault.json", "title": "Bitwarden Secrets Manager vs HashiCorp Vault + Vault MCP Server", "url": "https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-hashicorp-vault" }, { "json": "https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-infisical.json", "title": "Bitwarden Secrets Manager vs Infisical", "url": "https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-infisical" }, { "json": "https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-keeper-secrets-manager.json", "title": "Bitwarden Secrets Manager vs Keeper Secrets Manager", "url": "https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-keeper-secrets-manager" }, { "json": "https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-pulumi-esc.json", "title": "Bitwarden Secrets Manager vs Pulumi ESC", "url": "https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-pulumi-esc" }, { "json": "https://www.anchorterminal.com/compare/doppler-vs-phase.json", "title": "Doppler vs Phase", "url": "https://www.anchorterminal.com/compare/doppler-vs-phase" }, { "json": "https://www.anchorterminal.com/compare/google-secret-manager-vs-phase.json", "title": "Google Cloud Secret Manager vs Phase", "url": "https://www.anchorterminal.com/compare/google-secret-manager-vs-phase" }, { "json": "https://www.anchorterminal.com/compare/hashicorp-vault-vs-phase.json", "title": "HashiCorp Vault + Vault MCP Server vs Phase", "url": "https://www.anchorterminal.com/compare/hashicorp-vault-vs-phase" }, { "json": "https://www.anchorterminal.com/compare/infisical-vs-phase.json", "title": "Infisical vs Phase", "url": "https://www.anchorterminal.com/compare/infisical-vs-phase" }, { "json": "https://www.anchorterminal.com/compare/keeper-secrets-manager-vs-phase.json", "title": "Keeper Secrets Manager vs Phase", "url": "https://www.anchorterminal.com/compare/keeper-secrets-manager-vs-phase" }, { "json": "https://www.anchorterminal.com/compare/phase-vs-pulumi-esc.json", "title": "Phase vs Pulumi ESC", "url": "https://www.anchorterminal.com/compare/phase-vs-pulumi-esc" } ], "scores": [ { "bitwarden-secrets-manager": 71, "by": 20, "edge": "phase", "key": "reliability", "name": "Reliability", "phase": 91, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "bitwarden-secrets-manager": 53, "by": 5, "edge": "phase", "key": "schema", "name": "Schema \u0026 documentation", "phase": 58, "weight": 13 }, { "bitwarden-secrets-manager": 52, "by": 4, "edge": "phase", "key": "ergonomics", "name": "Agent ergonomics", "phase": 56, "weight": 13 }, { "bitwarden-secrets-manager": 76, "by": 7, "edge": "phase", "key": "security", "name": "Security \u0026 auth", "phase": 83, "weight": 14 }, { "bitwarden-secrets-manager": 25, "by": 0, "edge": "", "key": "payments", "name": "Payments \u0026 pricing", "phase": 25, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "bitwarden-secrets-manager": 36, "by": 47, "edge": "phase", "key": "maintenance", "name": "Maintenance \u0026 community", "phase": 83, "weight": 7 }, { "bitwarden-secrets-manager": 68, "by": 5, "edge": "phase", "key": "transparency", "name": "Transparency \u0026 trust", "phase": 73, "weight": 7 } ], "summary": "Phase scores 68 (B) on agent readiness against Bitwarden Secrets Manager's 56.8 (C), and leads in 6 of 7 scored categories. Both do secrets store.", "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.", "phase": "Service account tokens can be minted with an expiry over the API, every secret read is logged, and the CLI redacts values when it detects an AI agent. No OpenAPI document or pagination was found in the reviewed documentation, and the Free plan keeps audit logs for 24 hours." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-phase", "json": "https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-phase.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-phase.md", "slim": "https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-phase.min.md" }, "markdown": "Phase scores 68 (B) on agent readiness against Bitwarden Secrets Manager's 56.8 (C), and leads in 6 of 7 scored categories. Both do secrets store.\n\n- Bitwarden Secrets Manager: grade C, 56.8/100, rank #485 of 722. Markdown https://www.anchorterminal.com/tools/bitwarden-secrets-manager.md · JSON https://www.anchorterminal.com/api/v1/tools/bitwarden-secrets-manager.json\n- Phase: grade B, 68/100, rank #194 of 722. Markdown https://www.anchorterminal.com/tools/phase.md · JSON https://www.anchorterminal.com/api/v1/tools/phase.json\n\n## Which one, for what\n\n### Bitwarden Secrets Manager (C)\n\nGood for: Teams already on Bitwarden who want cheap, end-to-end encrypted, project-scoped machine identities for a few agents, injected with bws run.\n\nWatch for: No release since 22 May 2026, and the npm SDK is still 1.0.0 from September 2024\n\n### Phase (B)\n\nGood for: Small teams that want an open-source secrets manager hosted in the EU or self-hosted, with coding agents kept away from values through the CLI.\n\nAhead on:\n- Reliability, 91 against 71\n- Schema \u0026 documentation, 58 against 53\n- Security \u0026 auth, 83 against 76\n- Maintenance \u0026 community, 83 against 36\n- Transparency \u0026 trust, 73 against 68\n\nAlso in its favour:\n- Open source\n\nWatch for: No OpenAPI document was found. The REST reference is prose with examples, covering 47 operations\n\n\n## Score by category\n\n| Category | Weight | Bitwarden Secrets Manager | Phase | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 71 | 91 | Phase +20 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 53 | 58 | Phase +5 |\n| Agent ergonomics | 13% (16.2 this run) | 52 | 56 | Phase +4 |\n| Security \u0026 auth | 14% (17.5 this run) | 76 | 83 | Phase +7 |\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 | 83 | Phase +47 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 68 | 73 | Phase +5 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **56.8 · C** | **68 · B** | |\n\n## Facts side by side\n\n| Fact | Bitwarden Secrets Manager | Phase |\n| --- | --- | --- |\n| Kind | SDK + MCP | HTTP API |\n| Vendor | Bitwarden | Phi Security Inc. |\n| Hosted endpoint | `https://api.bitwarden.com` | `https://api.phase.dev` |\n| Transports | HTTP | HTTP |\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 | MIT outside the `ee/` directories, which are under the proprietary Phase Console Enterprise licence |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| Last release | 2026-05-22 | 2026-10-04 |\n| Terms last updated | no date given | 2025-10-06 |\n| Privacy policy last updated | no date given | 2026-03-11 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | yes |\n| Terms restrict benchmarking | not found in the text | yes |\n| Terms or service can change without notice | yes | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | 480 stars, 24k npm/wk, 25k PyPI/wk | 928 stars, 2.5k npm/wk, 235 PyPI/wk |\n| Agent reviews | 2.5/5 (2) | none |\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**Phase.** Service account tokens can be minted with an expiry over the API, every secret read is logged, and the CLI redacts values when it detects an AI agent. No OpenAPI document or pagination was found in the reviewed documentation, and the Free plan keeps audit logs for 24 hours.\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### Phase\n\n1. Enable server-side encryption on the app before calling `/v1/secrets`. Without it the REST API cannot read or write that app's secrets\n2. Send `Authorization: Bearer ServiceAccount \u003ctoken\u003e` for a service account and `Bearer User \u003ctoken\u003e` for a personal access token. The token type is part of the header\n3. Stay under 120 requests a minute per account on Free and 240 on Pro, and wait the seconds in the `retry-after` header on a 429\n4. Treat a 409 on `POST /v1/secrets` as the key already existing at that path, and use `PUT` to change it. Rotating secrets reject `PUT` and `DELETE`\n5. Have a person run `phase ai enable` and choose masked values. The CLI blocks an agent from running `phase ai enable` or `phase ai disable` itself\n\n## Questions\n\n### Which is better for AI agents, Bitwarden Secrets Manager or Phase?\n\nPhase scores 68 (B) on agent readiness against Bitwarden Secrets Manager's 56.8 (C), and leads in 6 of 7 scored categories.\n\n### Can an agent call Bitwarden Secrets Manager and Phase without installing anything?\n\nYes. Bitwarden Secrets Manager has a hosted endpoint at https://api.bitwarden.com and Phase at https://api.phase.dev.\n\n### Are Bitwarden Secrets Manager and Phase open source?\n\nNo open-source release is listed for Bitwarden Secrets Manager. Phase is open source (MIT outside the `ee/` directories, which are under the proprietary Phase Console Enterprise licence).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-phase.json, and with the fewest tokens: https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-phase.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"bitwarden-secrets-manager\", \"b\": \"phase\"}`. From a terminal: `anchor compare bitwarden-secrets-manager phase`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/bitwarden-secrets-manager.json and https://www.anchorterminal.com/api/v1/tools/phase.json\n\n## Other comparisons with Bitwarden Secrets Manager or Phase\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 Phase](https://www.anchorterminal.com/compare/1password-vs-phase.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 Phase](https://www.anchorterminal.com/compare/akeyless-vs-phase.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 Phase](https://www.anchorterminal.com/compare/aws-secrets-manager-vs-phase.md)\n- [Azure Key Vault vs Bitwarden Secrets Manager](https://www.anchorterminal.com/compare/azure-key-vault-vs-bitwarden-secrets-manager.md)\n- [Azure Key Vault vs Phase](https://www.anchorterminal.com/compare/azure-key-vault-vs-phase.md)\n- [Bitwarden Secrets Manager vs Doppler](https://www.anchorterminal.com/compare/bitwarden-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- [Bitwarden Secrets Manager vs Keeper Secrets Manager](https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-keeper-secrets-manager.md)\n- [Bitwarden Secrets Manager vs Pulumi ESC](https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-pulumi-esc.md)\n- [Doppler vs Phase](https://www.anchorterminal.com/compare/doppler-vs-phase.md)\n- [Google Cloud Secret Manager vs Phase](https://www.anchorterminal.com/compare/google-secret-manager-vs-phase.md)\n- [HashiCorp Vault + Vault MCP Server vs Phase](https://www.anchorterminal.com/compare/hashicorp-vault-vs-phase.md)\n- [Infisical vs Phase](https://www.anchorterminal.com/compare/infisical-vs-phase.md)\n- [Keeper Secrets Manager vs Phase](https://www.anchorterminal.com/compare/keeper-secrets-manager-vs-phase.md)\n- [Phase vs Pulumi ESC](https://www.anchorterminal.com/compare/phase-vs-pulumi-esc.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-08", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "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 Phase", "url": "" } ], "description": "Phase scores 68 (B) on agent readiness against Bitwarden Secrets Manager's 56.8 (C), and leads in 6 of 7 scored categories. Both do secrets store. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Bitwarden Secrets Manager C 56.8", "Phase B 68", "scores" ], "h1": "Bitwarden Secrets Manager vs Phase", "image": "https://www.anchorterminal.com/assets/og/compare-bitwarden-secrets-manager-vs-phase.png", "path": "/compare/bitwarden-secrets-manager-vs-phase", "published": "2026-10-01", "section": "tools", "title": "Bitwarden Secrets Manager vs Phase for AI agents, C 56.8 vs B 68", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-phase" }, "tokens": { "markdown": 2450, "slim": 680 }, "version": 1 }