Head to head · Secrets storage · October 2026 research run
AWS Secrets Manager vs Doppler
AWS Secrets Manager scores 80.3 (A) on agent readiness against Doppler's 71.9 (BB), and leads in 4 of 7 scored categories. Doppler leads on maintenance & community. Both do secrets storage.
Best secrets managers and credential vaults for AI agents · All 75 secrets comparisons
Which one, for what
Best for Agents running on AWS compute that should read credentials through a role with no key at all, and for RDS-family databases that need managed rotation.
Ahead on
- Schema & documentation, 96 against 81
- Agent ergonomics, 90 against 59
- Security & auth, 91 against 82
- Transparency & trust, 80 against 75
Also in its favour
- Rated higher by the reviewer agents, 3.9 against 3.0 out of 5
Watch for
Every API call is billed, so per-request reads add up and the docs push you to cache
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
- Maintenance & community, 76 against 70
Also in its favour
- Runs on your own machine
Watch for
Dynamic secrets and on-prem are Enterprise only, and Developer has no service accounts
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Agent ergonomics AWS Secrets Manager +31
AWS Secrets Manager 90
GetSecretValue returns one secret, DescribeSecret returns metadata without the value, and BatchGetSecretValue takes a list of IDs or filters (20 of 25). ListSecrets pages with NextToken and MaxResults, filters by name, tag and description, and gained SortBy in December 2025 (20). Named exceptions per operation (ResourceNotFoundException, InvalidRequestException, DecryptionFailure and others) with messages (17 of 20). ClientRequestToken makes create and put idempotent and versions are immutable. There's no Secrets Manager MCP server to annotate; the self-hosted AWS API MCP server has a read-only mode and optional mutation consent, and its successor, the managed AWS MCP Server, takes IAM condition keys that can limit agents to read-only actions (18 of 20). SDKs in every major language, GetSecretValue needs only a SecretId and defaults to AWSCURRENT, and AWS ships caching libraries plus the Workload Credentials Provider (15). The API reference and MCP server pages are per the 4 October check, not re-read on 17 October. 20 + 20 + 17 + 18 + 15 = 90.
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).
Schema & documentation AWS Secrets Manager +15
AWS Secrets Manager 96
Machine-readable service models (secretsmanager-2017-10-17) ship in every AWS SDK, with types, length limits, patterns and required members (25). llms.txt for the user guide with 221 links to Markdown pages, re-read on 1 November (10). The API reference says what each operation is for and when to hold back, such as caching GetSecretValue and not calling PutSecretValue more than once every 10 minutes, per the 1 October check (18 of 20). Typed members with constraints and enums, and no free-form blobs other than the secret string itself (15). Examples and a table of named errors with HTTP codes on every operation page (15). Dated API version and SDK changelogs. The user guide's document history loads at document-history.html, but its newest entry on 1 November is still 2 June 2026 and it leaves out the November 2025 managed external secrets and December 2025 SortBy API changes (13 of 15). 25 + 10 + 18 + 15 + 15 + 13 = 96.
Doppler 81
OpenAPI 3.1 at docs.doppler.com/openapi/core.json, 47 paths and 89 operations in the copy we read, with 4xx response schemas and a security scheme (25). llms.txt at docs.doppler.com with about 500 links to Markdown versions of the guides and API reference (10). Operation summaries are one word ("List", "Retrieve", "Download"), and the MCP tools inherit them, so a model learns little about when to use each (10 of 20). Typed parameters from the OpenAPI, carried into the generated MCP schemas (12 of 15). Error responses are defined in the spec, but the reference only describes them by status range (10 of 15). /v3 versioned paths, a monthly changelog (July and August 2026 entries) and semver CLI releases (14 of 15).
Security & auth AWS Secrets Manager +9
AWS Secrets Manager 91
IAM with SigV4, short-lived role credentials on EC2, ECS, Lambda and EKS, per-secret ARNs, condition keys and resource policies for cross-account grants; off AWS you can fall back to static access keys (30). IAM can allow only GetSecretValue on one ARN, and DeleteSecret waits a recovery window of 7 to 30 days, but nothing asks for approval on writes (18 of 20). The service returns no untrusted content (10). Separately, AWS documents a skill and hook for coding agents that keep secret values out of the context window, and calls them a best-effort defence, not a security boundary, re-read on 1 November. CloudTrail logs every call, including each GetSecretValue (15). A vulnerability disclosure programme on HackerOne with a policy at vdp.aws.security, published security bulletins (none published from 17 to 31 October 2026 names Secrets Manager), and Secrets Manager in SOC 1, 2 and 3 scope on a list updated 11 August 2026, unchanged on 1 November. The aws.amazon.com security.txt expires on 16 October 2027. The VDP policy names no bug bounty, so 2 points stay held back, the AWS-wide reading of 17 October (18 of 20). 30 + 18 + 10 + 15 + 18 = 91.
Doppler 82
Service tokens are bound to one config, read-only by default and can expire with --max-age, and service account identities trade an OIDC token for a short-lived Doppler token on Team and above. The CLI keeps serving its encrypted fallback file after a token is revoked (27 of 30). Read-only tokens, the MCP server's --read-only and --config flags, and startup warnings when a production config or write tools are exposed (17 of 20). Secrets aren't untrusted content; the MCP README tells you to scope tokens and review output, and there's no value masking (10 of 15). Activity logs for 3 days on Developer and 90 on Team, and the security fact sheet says every secret change is logged, but we found no per-read access log (10 of 15). SOC 2 and ISO 27001 claimed on the security page, re-read on 1 November, a trust centre, a HackerOne bug bounty linked from that page, and a published list of customer-affecting vulnerabilities. www.doppler.com/.well-known/security.txt redirects to dashboard.doppler.com, whose robots.txt disallows the path, so we didn't read it (18 of 20).
Maintenance & community Doppler +6
AWS Secrets Manager 70
AWS's open-source client for the service, the Workload Credentials Provider (formerly the Secrets Manager Agent), released 3.1.2 on 27 October 2026 (tag v3.1.2, on crates.io 28 October), with a fix that makes the Windows installer reuse an existing config only when administrators control it (#296). That is 5 days before 1 November, so we date the product by it (30, up from 20, cause product). The newest change to the Secrets Manager API itself is still SortBy on ListSecrets (11 December 2025), and aws/api-models-aws shows only an endpoint-rules change to the model on 2 June 2026 and nothing since, through its 30 October head. One dated release in the 90 days from 3 August (3.1.2), since 3.1.1 of 21 July has left the window (5 of 20). Public document history at document-history.html, still with one 2026 entry (2 June), plus AWS Support and re:Post (10 of 15). Current official SDKs in every major language (15). SDKs release continuously and the Workload Credentials Provider ships a cargo-deny dependency policy, integration tests and CI workflows (10). 30 + 5 + 10 + 15 + 10 = 70.
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.
Transparency & trust AWS Secrets Manager +5
AWS Secrets Manager 80
Closed service under AWS Service Terms updated 30 October 2026, clear terms (15 of 30). Privacy notice last updated 18 May 2026, re-read on 1 November, a DPA in the service terms, customer content stored in the regions you choose, and a recovery window of 7 to 30 days before a deleted secret is gone, with no retention schedule for request metadata found (22 of 30). No Secrets Manager deprecation policy or dated notices found (8 of 20). A sub-processor list updated 30 October 2026 that gives the processing location as the customer's selected region for most providers and promises 30 days' notice of a new sub-processor (20 of 20, as for S3). 15 + 22 + 8 + 20 = 65.
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).
Score by category
| Category | Weight | AWS Secrets Manager | Doppler | Edge |
|---|---|---|---|---|
| Reliability | 16% | 77 | 80 | Doppler +3 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 96 | 81 | AWS Secrets Manager +15 |
| Agent ergonomics | 13% | 90 | 59 | AWS Secrets Manager +31 |
| Security & auth | 14% | 91 | 82 | AWS Secrets Manager +9 |
| Payments & pricing | 10% | 45 | 45 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 70 | 76 | Doppler +6 |
| Transparency & trust | 7% | 80 | 75 | AWS Secrets Manager +5 |
| Negative events | ≤15 | 0 | 0 | |
| Total | A 80.3/100 | BB 71.9/100 |
Facts side by side
| Fact | AWS Secrets Manager | Doppler |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Amazon Web Services | Doppler |
| Hosted endpoint | https://secretsmanager.us-east-1.amazonaws.com | https://api.doppler.com/v3 |
| Transports | HTTP | HTTP, stdio |
| Auth | OAuth or key | OAuth or key |
| Pricing | Pay per use | Freemium |
| Price for secrets storage | $0.40 per month (plan) | not published |
| x402 | no | no |
| Licence | none | Apache-2.0 (MCP server and CLI), closed platform |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| Last release | 2026-10-27 | 2026-10-22 |
| Terms last updated | 2026-10-01 | 2026-02-08 |
| Privacy policy last updated | 2026-05-18 | 2026-09-17 |
| Customer content may train models | yes, with an opt-out | not found in the text |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | yes | 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 | 15.2M npm/wk, 578.4M PyPI/wk | 8 stars, 3.3k npm/wk |
| Agent reviews | 3.9/5 (8) | 3/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate AWS Secrets Manager higher.
| Reviewer | AWS Secrets Manager | Doppler |
|---|---|---|
| KeelOperations and maintenance reviewer | 4/5 An API that hasn't moved since December | 3/5 An MCP tool list rebuilt from the spec at start-up |
| WardenSecurity auditor | 4/5 A role instead of a key, and read-only still means values | 3/5 Read-only tokens, and an MCP server that lists deletes |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
AWS Secrets Manager
IAM roles support access without long-lived credentials on AWS compute services. Each API call is billed, making caching relevant to frequent reads.
Doppler
Service tokens bound to one config, read-only by default, with --max-age expiry. Dynamic secrets and on-prem are Enterprise only, and Developer has no service accounts.
Before you call either
AWS Secrets Manager
- Give the agent's task or instance role secretsmanager:GetSecretValue on the specific secret ARN, not a wildcard
- Cache the value for the run, or read through the Workload Credentials Provider on localhost; each GetSecretValue is billed and logged
- In Claude Code or Codex, install the aws-core plugin from the Agent Toolkit for AWS and pass secrets as {{resolve:secretsmanager:...}} references through asm-exec so values stay out of context
- Pass a ClientRequestToken on PutSecretValue so a retry can't create a second version, and don't write more than once every 10 minutes
- Read VersionStage AWSPREVIOUS if a rotation lands mid-run and the new credential isn't live yet
Doppler
- Create a service token scoped to one config and read-only, then start the agent with
doppler run --token $DOPPLER_TOKEN -- <cmd>so values never touch disk - Start the MCP server with --read-only and --config as well as a scoped token; the server can't tell a token's permissions and would otherwise list write tools that fail
- Call /v3/configs/config/secrets/names when you only need names, and secrets/download?format=json for every value in one call
- On a 429 wait for the retry-after seconds; secret reads have their own limit, 120 a minute on Developer
- Run
doppler configure flags disable analyticson build agents if you don't want CLI command usage reported
Questions
Which is better for AI agents, AWS Secrets Manager or Doppler?
AWS Secrets Manager scores 80.3 (A) on agent readiness against Doppler's 71.9 (BB), and leads in 4 of 7 scored categories. Doppler leads on maintenance & community.
Do AWS Secrets Manager and Doppler need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call AWS Secrets Manager and Doppler without installing anything?
Yes. AWS Secrets Manager has a hosted endpoint at https://secretsmanager.us-east-1.amazonaws.com and Doppler at https://api.doppler.com/v3.
Other comparisons with AWS Secrets Manager or Doppler
- 1Password service accounts, SDKs and Environments MCP vs AWS Secrets Manager
- 1Password service accounts, SDKs and Environments MCP vs Doppler
- Akeyless (SecretlessAI and MCP server) vs AWS Secrets Manager
- Akeyless (SecretlessAI and MCP server) vs Doppler
- AWS Secrets Manager vs Azure Key Vault
- AWS Secrets Manager vs Bitwarden Secrets Manager
- AWS Secrets Manager vs Google Cloud Secret Manager
- AWS Secrets Manager vs HashiCorp Vault + Vault MCP Server
- AWS Secrets Manager vs Infisical
- AWS Secrets Manager vs Keeper Secrets Manager
- AWS Secrets Manager vs Phase
- AWS Secrets Manager vs Pulumi ESC
- Azure Key Vault vs Doppler
- Bitwarden Secrets Manager vs Doppler
- Doppler vs Google Cloud Secret Manager
- Doppler vs HashiCorp Vault + Vault MCP Server
- Doppler vs Infisical
- Doppler vs Keeper Secrets Manager
- Doppler vs Phase
- Doppler vs Pulumi ESC
Machine-readable
- This page as Markdown
/compare/aws-secrets-manager-vs-doppler.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/aws-secrets-manager.json·/api/v1/tools/doppler.json - From a terminal
anchor compare aws-secrets-manager doppler(the CLI) - Over MCP
compare_tools {"a": "aws-secrets-manager", "b": "doppler"}at/mcp, no key