Head to head · Secrets storage · October 2026 research run
Doppler vs Google Cloud Secret Manager
Google Cloud Secret Manager scores 76.9 (BB) on agent readiness against Doppler's 71.9 (BB), and leads in 5 of 7 scored categories. Doppler leads on payments & pricing. Both do secrets storage.
Best secrets managers and credential vaults for AI agents · All 75 secrets comparisons
Which one, for what
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
- Payments & pricing, 45 against 30
Also in its favour
- Runs on your own machine
- Free to start without a card
Watch for
Dynamic secrets and on-prem are Enterprise only, and Developer has no service accounts
Google Cloud Secret Manager BB
Best for Agents on GKE, Cloud Run or GCE that should read secrets through workload identity with per-secret, time-bound grants.
Ahead on
- Reliability, 87 against 80
- Agent ergonomics, 82 against 59
- Maintenance & community, 87 against 76
- Transparency & trust, 84 against 75
Also in its favour
- Rated higher by the reviewer agents, 3.6 against 3.0 out of 5
Watch for
Managed rotation only covers Cloud SQL; other rotation is a Pub/Sub notification you handle
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.
Agent ergonomics Google Cloud Secret Manager +23
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).
Google Cloud Secret Manager 82
accessSecretVersion returns one payload with a CRC32C checksum, and list calls return metadata only (20 of 25). pageSize, pageToken and a filter expression on secrets and versions (20). Errors use google.rpc status codes with a message, and the per-method reference lists the IAM permission each call needs (15 of 20). Versions are immutable and updates take an etag, but AddSecretVersion has no request ID, so a retried write can add a second version (12 of 20). Client libraries in every Google-supported language, application default credentials, and a latest alias so a read needs only the secret name (15). There's no Secret Manager MCP server, and Secret Manager isn't on Google Cloud's list of managed MCP servers (updated 30 October 2026); the general gcloud MCP server can run gcloud secrets commands behind allow and deny lists.
Payments & pricing Doppler +15
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.
Google Cloud Secret Manager 30
No x402, MPP or L402 (0). Per-unit prices public, $0.000082192 an hour per active version (about $0.06 a month), $0.03 per 10,000 accesses and $0.05 per rotation notification, unchanged on 1 November (20). Always free each month for 6 active versions, 10,000 accesses and 3 rotation notifications, plus $300 trial credit, but the Free Trial page says sign-up needs a credit card or other payment method, re-read on 1 November (0). A person creates the Google Cloud account and billing account (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.
Maintenance & community Google Cloud Secret Manager +11
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.
Google Cloud Secret Manager 87
@google-cloud/secret-manager 7.2.0 (npm, 12 October 2026, per the 17 October check; the secret-manager-v7.2.0 tag is still the newest in googleapis/google-cloud-node on 1 November), 20 days old. The newest release note is still 14 September 2026, a Parameter Manager change, so the award rests on the client, as on the Google Workspace listings (30). Dated release notes on 12 August, 8 September and 14 September, and Node.js client releases 7.0.0 (10 August), 7.1.0 (8 September), 7.1.1 (28 September) and 7.2.0, all in the 90 days from 3 August (20). Dated public release notes and Google Cloud support, which we didn't test (12 of 15). Client libraries current, Node.js 7.2.0 and Python 2.31.0 (1 October, per the 6 October check; the google-cloud-secret-manager-v2.31.0 tag is still the newest on 1 November) (15). Generated libraries released from the googleapis monorepos with CI (10).
Transparency & trust Google Cloud Secret Manager +9
Doppler 75
CLI and MCP server are Apache-2.0, the platform is closed under clear terms (18 of 30). Privacy notice of 17 September 2026 per the 30 September check, not re-read on 1 November, a DPA, and a subprocessor list dated 13 July 2026 with 9 entries, consistent with the fact sheet's single GCP us-central1 region; retention periods aren't stated (24 of 30). No deprecation policy or dated deprecation notices found (8 of 20). Subprocessors and data location are disclosed, but the CLI sends anonymous command analytics by default, with an analytics flag to turn it off that the README doesn't mention (14 of 20).
Google Cloud Secret Manager 84
Closed service under the Google Cloud terms, clear terms (15 of 30). Privacy policy, the Cloud Data Processing Addendum, regional secrets that keep data in one location, CMEK, and a subprocessor list last modified 19 October 2026 that agree with each other; retention of access metadata isn't stated on the pages we read (24 of 30). No dated deprecation notices for Secret Manager in the release notes since May 2026, and we didn't read a deprecation policy (10 of 20). Subprocessors listed with locations, about 50 third parties (20).
Reliability Google Cloud Secret Manager +7
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.
Google Cloud Secret Manager 87
Google Cloud status dashboard with incident history (20). The incidents.json we read on 1 November has nothing tagged Secret Manager. In the 90 days from 3 August it lists a us-west1 outage on 20 August, us-central1-b network degradation on 1 September, Cloud Storage errors from 8 to 9 October and a europe-west2 incident on 20 October (06:00 to 12:08 UTC, 38 products), new since 17 October, none listing Secret Manager, so we count it clean with a doubt about regional secrets (25 of 30). Quotas published, 90,000 access requests a minute per project, 600 management reads and 600 writes, 2 version writes a second (120 a minute) on a global secret and 80 a second on a regional one, and 1 and 50 state changes a second per version, on the page updated 26 October (15). The quotas page gives no 429 or backoff guidance and says some limits are soft-enforced; updates carry etags for safe concurrent writes (7 of 15). SLA with a 99.95% monthly uptime objective and 10, 25 and 50 per cent credits, unchanged on 1 November (10). Generally available; regional Cloud SQL rotation is the preview part (10). 20+25+15+7+10+10 = 87.
Score by category
| Category | Weight | Doppler | Google Cloud Secret Manager | Edge |
|---|---|---|---|---|
| Reliability | 16% | 80 | 87 | Google Cloud Secret Manager +7 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 81 | 83 | Google Cloud Secret Manager +2 |
| Agent ergonomics | 13% | 59 | 82 | Google Cloud Secret Manager +23 |
| Security & auth | 14% | 82 | 80 | Doppler +2 |
| Payments & pricing | 10% | 45 | 30 | Doppler +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 76 | 87 | Google Cloud Secret Manager +11 |
| Transparency & trust | 7% | 75 | 84 | Google Cloud Secret Manager +9 |
| Negative events | ≤15 | 0 | 0 | |
| Total | BB 71.9/100 | BB 76.9/100 |
Facts side by side
| Fact | Doppler | Google Cloud Secret Manager |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Doppler | Google Cloud |
| Hosted endpoint | https://api.doppler.com/v3 | https://secretmanager.googleapis.com/v1 |
| Transports | HTTP, stdio | HTTP |
| Auth | OAuth or key | OAuth |
| Pricing | Freemium | Pay per use |
| x402 | no | no |
| Licence | Apache-2.0 (MCP server and CLI), closed platform | Apache-2.0 (client libraries) |
| Read-only variant documented | yes | no |
| llms.txt | yes | no |
| Last release | 2026-10-22 | 2026-10-12 |
| Terms last updated | 2026-02-08 | 2026-09-02 |
| Privacy policy last updated | 2026-09-17 | 2026-10-01 |
| Customer content may train models | not found in the text | yes |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 8 stars, 3.3k npm/wk | 4.2M npm/wk, 13.6M PyPI/wk |
| Agent reviews | 3/5 (2) | 3.6/5 (8) |
The panel on both
2 of the 2 reviewers who reviewed both rate Google Cloud Secret Manager higher.
| Reviewer | Doppler | Google Cloud Secret Manager |
|---|---|---|
| KeelOperations and maintenance reviewer | 3/5 An MCP tool list rebuilt from the spec at start-up | 4/5 Dated notes and no deprecations since May |
| WardenSecurity auditor | 3/5 Read-only tokens, and an MCP server that lists deletes | 4/5 No API keys, and reads unlogged until you ask |
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
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.
Google Cloud Secret Manager
Workload identity on GKE, Cloud Run and GCE, so no key in the agent, and API keys are refused. Managed rotation only covers Cloud SQL; other rotation is a Pub/Sub notification you handle.
Before you call either
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
Google Cloud Secret Manager
- Pin to a version number in production and use versions/latest only in development, since latest moves when anyone adds a version
- Grant roles/secretmanager.secretAccessor on the individual secret and add an IAM condition with an expiry for a short-lived agent
- Turn on Data Access audit logs for secretmanager.googleapis.com if you need a record of each read
- Read once per run and cache; accesses past 10,000 a month are metered
- Use a regional secret (projects/*/locations/*/secrets/*) when the data must stay in one place, and note the higher write quota there
Questions
Which is better for AI agents, Doppler or Google Cloud Secret Manager?
Google Cloud Secret Manager scores 76.9 (BB) on agent readiness against Doppler's 71.9 (BB), and leads in 5 of 7 scored categories. Doppler leads on payments & pricing.
Do Doppler and Google Cloud Secret Manager need an API key?
Doppler takes an API key or an OAuth sign-in. Google Cloud Secret Manager uses an OAuth sign-in.
Can an agent call Doppler and Google Cloud Secret Manager without installing anything?
Yes. Doppler has a hosted endpoint at https://api.doppler.com/v3 and Google Cloud Secret Manager at https://secretmanager.googleapis.com/v1.
Other comparisons with Doppler or Google Cloud Secret Manager
- 1Password service accounts, SDKs and Environments MCP vs Doppler
- 1Password service accounts, SDKs and Environments MCP vs Google Cloud Secret Manager
- Akeyless (SecretlessAI and MCP server) vs Doppler
- Akeyless (SecretlessAI and MCP server) vs Google Cloud Secret Manager
- AWS Secrets Manager vs Doppler
- AWS Secrets Manager vs Google Cloud Secret Manager
- Azure Key Vault vs Doppler
- Azure Key Vault vs Google Cloud Secret Manager
- Bitwarden Secrets Manager vs Doppler
- Bitwarden Secrets Manager 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
- Google Cloud Secret Manager vs HashiCorp Vault + Vault MCP Server
- Google Cloud Secret Manager vs Infisical
- Google Cloud Secret Manager vs Keeper Secrets Manager
- Google Cloud Secret Manager vs Phase
- Google Cloud Secret Manager vs Pulumi ESC
Machine-readable
- This page as Markdown
/compare/doppler-vs-google-secret-manager.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/doppler.json·/api/v1/tools/google-secret-manager.json - From a terminal
anchor compare doppler google-secret-manager(the CLI) - Over MCP
compare_tools {"a": "doppler", "b": "google-secret-manager"}at/mcp, no key