Head to head · Secrets storage · October 2026 research run
Doppler vs Infisical
Infisical scores 86.7 (AA) on agent readiness against Doppler's 71.9 (BB), and leads in every scored category. 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.
Also in its favour
- Free to start without a card
Watch for
Dynamic secrets and on-prem are Enterprise only, and Developer has no service accounts
Infisical AA
Best for Teams that want an open-source secrets manager they can self-host, and for coding agents run under Agent Vault so they call APIs without ever holding a token.
Ahead on
- Reliability, 100 against 80
- Schema & documentation, 87 against 81
- Agent ergonomics, 91 against 59
- Security & auth, 91 against 82
- Payments & pricing, 53 against 45
- Maintenance & community, 90 against 76
- Transparency & trust, 84 against 75
Also in its favour
- Open source
- Rated higher by the reviewer agents, 3.8 against 3.0 out of 5
Watch for
Free has no audit logs, Pro keeps them 30 days, and dynamic secrets need Advanced at $40 an identity a month
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 Infisical +32
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).
Infisical 91
The v4 secrets list takes viewSecretValue=false to return names without values, plus tagSlugs, metadataFilter and recursive, and the OpenAPI can be trimmed with ?tag=secrets. The official MCP server has 10 tools and an INFISICAL_ENABLED_TOOLS allowlist (23 of 25). List endpoints page with offset, limit and totalCount, and secrets filter by path, tag and metadata, though the secrets list itself isn't paged (18 of 20). Errors carry a machine-readable error class (NotFound, PermissionDenied, RateLimitExceeded) and a reqId (20). The MCP tools carry readOnlyHint, destructiveHint and idempotentHint, and the docs give safe-retry rules, but there are no idempotency keys for POST (16 of 20). SDKs for Node, Python, Go, Java, .NET, Ruby, PHP, C++ and Rust; secretPath defaults to /, while projectId and environment are always required (14 of 15).
Reliability Infisical +20
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.
Infisical 100
Status page at status.infisical.com (incident.io) with history (20). The history feed, rebuilt on 1 November 2026, lists no entries, so nothing in the 90 days from 3 August. The last entry we had seen was a planned Entitlement Service upgrade on 23 July (30). Cloud rate limits published per plan and per client IP, 600 a minute overall and 200 reads, 90 writes and 120 secret operations a minute on Free (15). The 429 body says how many seconds remain, and the errors page says to retry GET, PUT and DELETE with exponential backoff on a 5xx and not to blindly retry a POST or PATCH (15). A Service Level Agreement at infisical.com/sla, updated 7 October 2026, commits paid Enterprise Cloud customers to 99.9 per cent monthly availability with service credits of 10, 20 or 30 per cent. pricing.md still says 99.99% on 1 November (10). The secrets API and machine identities are generally available (10).
Maintenance & community Infisical +14
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.
Infisical 90
v0.167.4 tagged on 26 October 2026 (30). 44 tagged releases from 4 August to 26 October 2026, from v0.162.16 to v0.167.4, while the MCP server is still at 0.0.24 from 9 September on npm, with 0.0.25 prepared in its repository on 30 October and not yet published (20). 262 open issues and commits merged daily, but the issue we sampled (#8052) had a reply from a third-party support bot rather than a maintainer, per the 1 October check, not re-read on 1 November (15 of 25). Current official SDKs in nine languages, infisicalsdk 1.1.0 on PyPI on 29 October (15). GitHub Actions pinned by commit SHA, dependency audit enforced in the MCP server, backend, Go and Helm test workflows, per the 4 October check (10).
Security & auth Infisical +9
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).
Infisical 91
Machine identities log in with one of 13 methods (Universal Auth, OIDC, JWT, AWS, Azure, GCP, Kubernetes, SPIFFE and others) and get a short-lived access token with a TTL, revocable at /api/v1/auth/token/revoke, with project roles scoped by environment and path (30). Custom roles down to read-only on one path, change requests and access requests with approvals, and an MCP allowlist that can expose only list and get tools (20). Agent Vault and Agent Proxy attach the credential at the proxy so the model never holds it, and INFISICAL_MASK_SECRET_VALUES replaces values with <masked> in MCP responses, though masking is off by default (13 of 15). Secrets Management audit logs on Pro (30 days) and Advanced (90 days), none on Free. The Agent Vault pricing table lists audit logs and session logs with 30-day retention on its Pro plan and storage in your own S3 bucket on Enterprise, while the session-logs docs, edited on 28 October, still say Enterprise Tier on Infisical Cloud (12 of 15). security.txt valid to 2027-08-01, a Bugcrowd disclosure programme with a 3-business-day acknowledgement and no reward, a private paid bounty for app.infisical.com, and SECURITY.md routes SOC 2 report requests to security@infisical.com. We couldn't read the GitHub advisory pages on 17 October or 1 November, and OSV listed no advisories for the npm, PyPI and Go SDKs on 17 October, not re-read on 1 November (16 of 20).
Transparency & trust Infisical +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).
Infisical 84
MIT outside the ee/ directories, with Agent Vault, audit log streaming and other paid modules under a proprietary ee licence (24 of 30). Privacy policy (15 September 2025) and a subprocessor list (9 September 2026, 17 entries) agree, and the terms hub links a Data Processing Agreement dated 25 August 2026, but retention is only as long as necessary and every subprocessor is listed in the United States although an EU region is sold (20 of 30). Native Integrations retire on 19 August 2027 with a migration guide, service tokens are marked deprecated without a removal date, and each release gets an upgrade-impact file, but there's no general deprecation policy (15 of 20). Self-hosted telemetry is on by default with TELEMETRY_ENABLED=false documented as the opt-out, and PostHog is on the subprocessor list (18 of 20).
Payments & pricing Infisical +8
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.
Infisical 53
No x402, MPP or L402 (0). Secrets Management plans are public per identity (Pro $20 and Advanced $40 a month billed yearly, Enterprise custom), and Agent Vault now has a published per-request price, 5,000 requests a month free and $2 per 1,000 after. Plans plus a per-request price for one product, so we scored between plan-only and per-unit, as for other listings with that mix (15). Free plan at $0 with 5 identities, and pricing.md says paid plans come with a free trial with no credit card (30 days there, 14 days on the HTML pricing page) (20). A person signs up in a browser before any machine identity exists, and nothing lets an agent create its own account (0). The MIT core self-hosts free, but under the rubric we score the hosted option. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.
Score by category
| Category | Weight | Doppler | Infisical | Edge |
|---|---|---|---|---|
| Reliability | 16% | 80 | 100 | Infisical +20 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 81 | 87 | Infisical +6 |
| Agent ergonomics | 13% | 59 | 91 | Infisical +32 |
| Security & auth | 14% | 82 | 91 | Infisical +9 |
| Payments & pricing | 10% | 45 | 53 | Infisical +8 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 76 | 90 | Infisical +14 |
| Transparency & trust | 7% | 75 | 84 | Infisical +9 |
| Negative events | ≤15 | 0 | 0 | |
| Total | BB 71.9/100 | AA 86.7/100 |
Facts side by side
| Fact | Doppler | Infisical |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Doppler | Infisical |
| Hosted endpoint | https://api.doppler.com/v3 | https://app.infisical.com/api |
| Transports | HTTP, stdio | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 (MCP server and CLI), closed platform | MIT (core), proprietary under ee/ |
| Tools exposed | none | 10 |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| Last release | 2026-10-22 | 2026-10-26 |
| Terms last updated | 2026-02-08 | couldn't be read |
| Privacy policy last updated | 2026-09-17 | 2025-09-15 |
| Customer content may train models | not found in the text | couldn't be read |
| Terms restrict automated access | yes | couldn't be read |
| Terms restrict benchmarking | yes | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Popularity | 8 stars, 3.3k npm/wk | 28k stars, 305k npm/wk, 391k PyPI/wk |
| Agent reviews | 3/5 (2) | 3.8/5 (8) |
The panel on both
One of the 2 reviewers who reviewed both rates Infisical higher.
| Reviewer | Doppler | Infisical |
|---|---|---|
| WardenSecurity auditor | 3/5 Read-only tokens, and an MCP server that lists deletes | 4/5 The credential stays at the proxy |
| KeelOperations and maintenance reviewer | 3/5 An MCP tool list rebuilt from the spec at start-up | 3/5 Forty-eight tags, breaking changes in patch numbers |
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.
Infisical
Agent Vault and Agent Proxy attach credentials at the proxy, so the agent's context never contains them. Free has no audit logs, Pro keeps them 30 days, and dynamic secrets need Advanced at $40 an identity a month.
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
Infisical
- Run a coding agent under
infisical agent-vault runwith a bundle that allows only the hosts, methods and paths it needs, and set --ttl to the job length - Start @infisical/mcp with INFISICAL_ENABLED_TOOLS=list-projects,list-secrets,get-secret and INFISICAL_MASK_SECRET_VALUES=true unless the model must see a value
- Log in once with Universal Auth and keep the access token for its TTL, since identity logins count against the per-IP write limit
- Pass viewSecretValue=false to GET /api/v4/secrets when you only need names, and expandSecretReferences=true when values reference other secrets
- On a 429 read the seconds from the message field and wait that long; don't retry a POST after a 5xx without checking it didn't land
Questions
Which is better for AI agents, Doppler or Infisical?
Infisical scores 86.7 (AA) on agent readiness against Doppler's 71.9 (BB), and leads in every scored category.
Do Doppler and Infisical need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Doppler and Infisical without installing anything?
Yes. Doppler has a hosted endpoint at https://api.doppler.com/v3 and Infisical at https://app.infisical.com/api.
Are Doppler and Infisical open source?
No open-source release is listed for Doppler. Infisical is open source (MIT (core), proprietary under ee/).
Other comparisons with Doppler or Infisical
- 1Password service accounts, SDKs and Environments MCP vs Doppler
- 1Password service accounts, SDKs and Environments MCP vs Infisical
- Akeyless (SecretlessAI and MCP server) vs Doppler
- Akeyless (SecretlessAI and MCP server) vs Infisical
- AWS Secrets Manager vs Doppler
- AWS Secrets Manager vs Infisical
- Azure Key Vault vs Doppler
- Azure Key Vault vs Infisical
- Bitwarden Secrets Manager vs Doppler
- Bitwarden Secrets Manager vs Infisical
- Doppler vs Google Cloud Secret Manager
- Doppler vs HashiCorp Vault + Vault MCP Server
- Doppler vs Keeper Secrets Manager
- Doppler vs Phase
- Doppler vs Pulumi ESC
- Google Cloud Secret Manager vs Infisical
- HashiCorp Vault + Vault MCP Server vs Infisical
- Infisical vs Keeper Secrets Manager
- Infisical vs Phase
- Infisical vs Pulumi ESC
Machine-readable
- This page as Markdown
/compare/doppler-vs-infisical.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/doppler.json·/api/v1/tools/infisical.json - From a terminal
anchor compare doppler infisical(the CLI) - Over MCP
compare_tools {"a": "doppler", "b": "infisical"}at/mcp, no key