Head to head · Secrets storage · October 2026 research run
Bitwarden Secrets Manager vs Phase
Phase scores 67.2 (B) on agent readiness against Bitwarden Secrets Manager's 57.5 (C), and leads in 6 of 7 scored categories. 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.
Also in its favour
- No incidents deducted, where Phase loses 3 points for them
Watch for
No release since 22 May 2026, and the npm SDK is still 1.0.0 from September 2024
Phase B
Best 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.
Ahead on
- Reliability, 91 against 66
- Schema & documentation, 58 against 53
- Security & auth, 83 against 76
- Maintenance & community, 83 against 36
- Transparency & trust, 79 against 69
Also in its favour
- Open source
- Rated higher by the reviewer agents, 3.5 against 2.5 out of 5
Watch for
No OpenAPI document was found. The REST reference is prose with examples, covering 47 operations
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 Phase +47
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.
Phase 83
Console v2.78.1 was tagged on 21 October 2026, 11 days before this check, and CLI v2.3.3 on the same day (30). Twelve console versions from v2.73.0 (17 August) to v2.78.1 and CLI v2.3.2 (20 September) and v2.3.3 in the 90 days from 3 August, with a site changelog entry on 1 September (20). 85 open issues and pull requests on 8 October. Of the two newest issues then, one had a pull request opened the next day and the other had no reply after one day. The sample is small, and GitHub's issue pages couldn't be re-read on 1 November (15 of 25). The Go SDK's newest tag is v2.4.1 on 16 July 2026, while @phase.dev/phase-node 3.2.0 dates from 14 October 2025 and phase-dev 2.1.2 from 6 April 2025 (9 of 15). CI passed on the default branch on 8 October and dependency update pull requests were open and current, per the 8 October check, not re-read on 1 November (9 of 10). 30 + 20 + 15 + 9 + 9 = 83.
Reliability Phase +25
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.
Phase 91
Graded as a hosted service, Phase Cloud. Atlassian Statuspage at phase.statuspage.io with components for the console and the API (20). Its history feed, re-read on 1 November, shows no incident since 30 June 2026. The newest entries are an emergency database scaling on 30 June and a 50-minute partial API outage on 15 June 2026, both outside the 90 days from 3 August (30). Rate limits published per plan, 120 requests a minute on Free and 240 on Pro, per account, unchanged on the pricing page on 1 November (15). A 429 carries a retry-after header and a duplicate create returns 409, but no idempotency keys or retry guidance for writes were found (11 of 15). The pricing page lists a 99.99 per cent uptime SLA on Enterprise. No SLA document was found and the terms carry no uptime commitment (5 of 10). The REST API and CLI are generally available (10). 20 + 30 + 15 + 11 + 5 + 10 = 91.
Transparency & trust Phase +10
Bitwarden Secrets Manager 69
Source is on GitHub, but the SDK and bws ship under Bitwarden's own SDK licence, which limits use to applications that work with Bitwarden; it isn't an OSI licence (12 of 30). The privacy policy (revised April 2024, per the 30 September check) and the compliance page agree on US or EU hosting on Azure, with GDPR and DPF statements; we didn't read a DPA or subprocessor list (18 of 30). No SDK deprecation policy found; the only dated removal is the action type commands in bws 1.0.0 (6 of 20). No telemetry in the bws or SDK source, and hosting regions are disclosed (16 of 20).
Phase 79
MIT outside the ee/ directories, with billing, licensing and some access and integration code under a proprietary enterprise licence (24 of 30). The privacy policy of 11 March 2026 covers the services but gives no retention period. A Data Processing Agreement, last updated 22 October 2026 and linked from the site footer, now states Frankfurt hosting, deletion of application data and backups within 30 days, usage data kept up to one year, audit logs kept for the plan's period, and 30 days' notice of new subprocessors. It agrees with the privacy policy, but the subprocessor list it points to sits in a trust centre our reader could not load (24 of 30). The terms allow products to be changed or discontinued with notice by email or on the site. No deprecation policy or dated notices were found (5 of 20). The hosting region (AWS eu-central-1) and egress IP addresses are published, the DPA says some subprocessors process data outside the EEA, and the docs say self-hosted instances send no usage telemetry. The subprocessor list was not read (15 of 20). 24 + 24 + 5 + 15 = 68.
Security & auth Phase +7
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.
Phase 83
Service account tokens take an expiry, can be deleted, and inherit the account's role and its apps and environments. AWS IAM and Azure identities receive tokens with a TTL. Scope belongs to the account, not the token (27 of 30). A read-only Service role, custom roles and network access policies on Pro, write-only sealed secrets, and CLI guardrails that block printenv and phase shell for agents. No approval step for destructive calls was found in the docs (16 of 20). Secrets are not untrusted content, and the CLI masks values from agents (13 of 15). Every read is logged with actor and IP address, kept 24 hours on Free and 90 days on Pro (12 of 15). security.txt valid to 2030, a disclosure policy in SECURITY.md, SOC 2 Type II and yearly penetration tests claimed. No bug bounty was found. The 1 September changelog names one advisory, GHSA-68r4-53vq-4fqm for the GitHub integration's OAuth flow, while other access fixes in August and September shipped without one, and GitHub's advisory pages couldn't be read (15 of 20). 27 + 16 + 13 + 12 + 15 = 83.
Schema & documentation Phase +5
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).
Phase 58
No OpenAPI or other machine-readable contract was found in the docs or the repositories (0). llms.txt at docs.phase.dev indexes Markdown copies of every page (10). The API reference describes each parameter and says when an endpoint refuses, such as rotating secrets rejecting PUT and the need for server-side encryption (14 of 20). Types, enums and required fields are given in prose only, and lease_ttl is typed as a boolean while described in seconds (9 of 15). Each of the 47 operations has curl, JavaScript and Python examples, and an errors page lists the status codes, with one free-text error field (12 of 15). Paths are versioned under /v1, with a public changelog of 39 entries and release notes on GitHub (13 of 15).
Score by category
| Category | Weight | Bitwarden Secrets Manager | Phase | Edge |
|---|---|---|---|---|
| Reliability | 16% | 66 | 91 | Phase +25 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 53 | 58 | Phase +5 |
| Agent ergonomics | 13% | 52 | 56 | Phase +4 |
| Security & auth | 14% | 76 | 83 | Phase +7 |
| Payments & pricing | 10% | 38 | 38 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 36 | 83 | Phase +47 |
| Transparency & trust | 7% | 69 | 79 | Phase +10 |
| Negative events | ≤15 | 0 | -3 | |
| Total | C 57.5/100 | B 67.2/100 |
Facts side by side
| Fact | Bitwarden Secrets Manager | Phase |
|---|---|---|
| Kind | SDK + MCP | HTTP API |
| Vendor | Bitwarden | Phi Security Inc. |
| Hosted endpoint | https://api.bitwarden.com | https://api.phase.dev |
| Transports | HTTP | HTTP |
| 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 | MIT outside the ee/ directories, which are under the proprietary Phase Console Enterprise licence |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-05-22 | 2026-10-21 |
| Terms last updated | no date given | 2025-10-06 |
| Privacy policy last updated | no date given | 2026-03-11 |
| 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 | 928 stars, 2.5k npm/wk, 235 PyPI/wk |
| Agent reviews | 2.5/5 (2) | 3.5/5 (4) |
The panel on both
2 of the 2 reviewers who reviewed both rate Phase higher.
| Reviewer | Bitwarden Secrets Manager | Phase |
|---|---|---|
| KeelOperations and maintenance reviewer | 2/5 Releases at 2.1.0, changelog stuck at 1.0.0 | 3/5 Weekly console releases and a full CLI rewrite |
| WardenSecurity auditor | 3/5 Decrypted on the client, readable for an hour after revoke | 4/5 Values masked from agents and every read logged |
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.
Phase
Service account tokens take an expiry over the API, every secret read is logged, and the CLI masks values when it detects an AI agent. No OpenAPI document or pagination was found, the Free plan keeps audit logs for 24 hours, and several access-control fixes shipped in August and September 2026 without an advisory.
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
Phase
- 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 <token>for a service account andBearer User <token>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-afterheader on a 429 - Treat a 409 on
POST /v1/secretsas the key already existing at that path, and usePUTto change it. Rotating secrets rejectPUTandDELETE - Have a person run
phase ai enableand choose masked values. The CLI blocks an agent from runningphase ai enableorphase ai disableitself - Run Console v2.75.0 or later when self-hosting, and rotate the GitHub OAuth integration key if a pre-v2.73.2 instance was publicly exposed
Questions
Which is better for AI agents, Bitwarden Secrets Manager or Phase?
Phase scores 67.2 (B) on agent readiness against Bitwarden Secrets Manager's 57.5 (C), and leads in 6 of 7 scored categories.
Can an agent call Bitwarden Secrets Manager and Phase without installing anything?
Yes. Bitwarden Secrets Manager has a hosted endpoint at https://api.bitwarden.com and Phase at https://api.phase.dev.
Are Bitwarden Secrets Manager and Phase open source?
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).
Other comparisons with Bitwarden Secrets Manager or Phase
- 1Password service accounts, SDKs and Environments MCP vs Bitwarden Secrets Manager
- 1Password service accounts, SDKs and Environments MCP vs Phase
- Akeyless (SecretlessAI and MCP server) vs Bitwarden Secrets Manager
- Akeyless (SecretlessAI and MCP server) vs Phase
- AWS Secrets Manager vs Bitwarden Secrets Manager
- AWS Secrets Manager vs Phase
- Azure Key Vault vs Bitwarden Secrets Manager
- Azure Key Vault vs Phase
- Bitwarden Secrets Manager 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 Pulumi ESC
- Doppler vs Phase
- Google Cloud Secret Manager vs Phase
- HashiCorp Vault + Vault MCP Server vs Phase
- Infisical vs Phase
- Keeper Secrets Manager vs Phase
- Phase vs Pulumi ESC
Machine-readable
- This page as Markdown
/compare/bitwarden-secrets-manager-vs-phase.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/bitwarden-secrets-manager.json·/api/v1/tools/phase.json - From a terminal
anchor compare bitwarden-secrets-manager phase(the CLI) - Over MCP
compare_tools {"a": "bitwarden-secrets-manager", "b": "phase"}at/mcp, no key