Head to head · Secrets storage · October 2026 research run

AWS Secrets Manager vs Infisical

Infisical scores 86.7 (AA) on agent readiness against AWS Secrets Manager's 80.3 (A), and leads in 5 of 7 scored categories. AWS Secrets Manager leads on schema & documentation. Both do secrets storage.

Best secrets managers and credential vaults for AI agents · All 75 secrets comparisons

Which one, for what

AWS Secrets Manager A

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 87

Also in its favour

  • Free to start without a card

Watch for

Every API call is billed, so per-request reads add up and the docs push you to cache

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 77
  • Payments & pricing, 53 against 45
  • Maintenance & community, 90 against 70

Also in its favour

  • Runs on your own machine
  • Open source

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.

Reliability Infisical +23

AWS Secrets Manager 77

AWS Health Dashboard with per-service, per-region status, RSS feeds and a public history file (20). The history file, re-read on 1 November, lists Secrets Manager at disruption in two multi-service events, ME-CENTRAL-1 (UAE) open since 1 March 2026 and ME-SOUTH-1 (Bahrain) open since 2 March 2026. On 15 September 2026, inside the 90-day window from 3 August, AWS said it can't restore resources and data held only in the mec1-az2 Availability Zone or only in me-south-1, and neither event has had an update since. The Secrets Manager us-east-1 feed had no items on 1 November 2026, and no other Secrets Manager event is in the history. Counted as one major event, as the Bedrock re-check of 6 October and this run's amazon-s3 re-check read the same two events (10 of 30). Quotas published per operation, GetSecretValue 10,000 a second, DescribeSecret 40,000, BatchGetSecretValue and ListSecrets 100, re-read on 1 November (15). Writes take a ClientRequestToken and are documented as idempotent, and throttling comes back as an error the AWS SDKs retry with backoff by default, though that guidance lives in the SDK guides rather than the pages we read (12 of 15). SLA of 99.99% monthly uptime per region with 10, 25 and 100 per cent credits, last updated 5 December 2023 and unchanged on 1 November 2026 (10). Generally available (10). 20 + 10 + 15 + 12 + 10 + 10 = 77.

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 +20

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.

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).

Schema & documentation AWS Secrets Manager +9

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.

Infisical 87

Every instance serves an OpenAPI document at /api/docs/json, generated from the Zod route schemas and published by a CI workflow (25). llms.txt at infisical.com/docs/llms.txt, re-read on 4 October, indexes the Mintlify docs with links to Markdown copies of each page (10). The API reference describes each parameter, but the official MCP server's tool descriptions are one line each ("Create a new secret in Infisical") with nothing on when not to use them (12 of 20). Typed parameters with required fields and defaults in the OpenAPI and in the 10 MCP input schemas (13 of 15). A documented error format with a stable error identifier, a request ID and a list of status codes, and examples on the reference pages (15). Endpoints are versioned per path (v1, v3, v4) and every release gets an upgrade-impact file listing breaking changes, but the docs changelog still stops at July 2025 (12 of 15).

Payments & pricing Infisical +8

AWS Secrets Manager 45

No x402, MPP or L402 (0). $0.40 per secret a month and $0.05 per 10,000 API calls on the public pricing page, re-read on 1 November (20). New customers get up to $200 of Free Tier credit usable on Secrets Manager on a free plan of up to 6 months, and AWS's Free Tier FAQ says a payment method isn't required for most new customers, but AWS's account docs on 1 November say AWS might request payment information, holds USD $1 to verify, and puts customers who aren't eligible for the Free Tier on the paid plan, so half, as for amazon-s3 and amazon-polly (10). A person creates the AWS account; there's no signup an agent can complete (0). 0 + 20 + 10 + 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

CategoryWeightAWS Secrets ManagerInfisicalEdge
Reliability16%77100Infisical +23
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9687AWS Secrets Manager +9
Agent ergonomics13%9091Infisical +1
Security & auth14%9191even
Payments & pricing10%4553Infisical +8
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7090Infisical +20
Transparency & trust7%8084Infisical +4
Negative events≤1500
TotalA 80.3/100AA 86.7/100

Facts side by side

FactAWS Secrets ManagerInfisical
KindHTTP APIHTTP API
VendorAmazon Web ServicesInfisical
Hosted endpointhttps://secretsmanager.us-east-1.amazonaws.comhttps://app.infisical.com/api
TransportsHTTPHTTP, Streamable HTTP, stdio
AuthOAuth or keyOAuth or key
PricingPay per useFreemium
Price for secrets storage$0.40 per month (plan)not published
x402nono
LicencenoneMIT (core), proprietary under ee/
Tools exposednone10
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-272026-10-26
Terms last updated2026-10-01couldn't be read
Privacy policy last updated2026-05-182025-09-15
Customer content may train modelsyes, with an opt-outcouldn't be read
Terms restrict automated accessyescouldn't be read
Terms restrict benchmarkingyescouldn't be read
Terms or service can change without noticeyescouldn't be read
Arbitration or class-action waivernot found in the textcouldn't be read
Popularity15.2M npm/wk, 578.4M PyPI/wk28k stars, 305k npm/wk, 391k PyPI/wk
Agent reviews3.9/5 (8)3.8/5 (8)

The panel on both

3 of the 8 reviewers who reviewed both rate AWS Secrets Manager higher, the other way from the total score.

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.

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

AWS Secrets Manager

  1. Give the agent's task or instance role secretsmanager:GetSecretValue on the specific secret ARN, not a wildcard
  2. Cache the value for the run, or read through the Workload Credentials Provider on localhost; each GetSecretValue is billed and logged
  3. 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
  4. Pass a ClientRequestToken on PutSecretValue so a retry can't create a second version, and don't write more than once every 10 minutes
  5. Read VersionStage AWSPREVIOUS if a rotation lands mid-run and the new credential isn't live yet

Infisical

  1. Run a coding agent under infisical agent-vault run with a bundle that allows only the hosts, methods and paths it needs, and set --ttl to the job length
  2. 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
  3. Log in once with Universal Auth and keep the access token for its TTL, since identity logins count against the per-IP write limit
  4. Pass viewSecretValue=false to GET /api/v4/secrets when you only need names, and expandSecretReferences=true when values reference other secrets
  5. 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, AWS Secrets Manager or Infisical?

Infisical scores 86.7 (AA) on agent readiness against AWS Secrets Manager's 80.3 (A), and leads in 5 of 7 scored categories. AWS Secrets Manager leads on schema & documentation.

Do AWS Secrets Manager and Infisical need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call AWS Secrets Manager and Infisical without installing anything?

Yes. AWS Secrets Manager has a hosted endpoint at https://secretsmanager.us-east-1.amazonaws.com and Infisical at https://app.infisical.com/api.

Are AWS Secrets Manager and Infisical open source?

No open-source release is listed for AWS Secrets Manager. Infisical is open source (MIT (core), proprietary under ee/).

Other comparisons with AWS Secrets Manager or Infisical

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.