Head to head · Secrets storage · October 2026 research run

Akeyless (SecretlessAI and MCP server) vs AWS Secrets Manager

AWS Secrets Manager scores 80.3 (A) on agent readiness against Akeyless (SecretlessAI and MCP server)'s 75.6 (BB), and leads in 5 of 7 scored categories. Akeyless (SecretlessAI and MCP server) leads on reliability and maintenance & community. Both do secrets storage.

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

Which one, for what

Akeyless (SecretlessAI and MCP server) BB

Best for Enterprises that want agents to use credentials without holding them, through a Gateway they run, and who will sign a quoted contract.

Ahead on

  • Reliability, 90 against 77
  • Maintenance & community, 82 against 70

Also in its favour

  • Runs on your own machine

Watch for

No published prices above the free plan; clients and transactions are metered with overage billed at the end of a 12-month contract

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 81
  • Agent ergonomics, 90 against 63
  • Payments & pricing, 45 against 38

Also in its favour

  • Free to start without a card
  • 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

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

Akeyless (SecretlessAI and MCP server) 63

akeyless mcp-runtime-authority has 4 tools, and akeyless mcp lists 9 and says there are more, with no full count published (18 of 25). /list-items takes a pagination token and filters by path, type, tag and modification date, with a minimal-view flag, per the OpenAPI document (20). Errors come back as one error string with no code for an agent to branch on (8 of 20). No tool annotations or idempotency guidance found, though the runtime-authority tools return results rather than secrets (5 of 20). SDKs for Python, Go, Node, Ruby and more, but every call needs a token in the body and many parameters (12 of 15).

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.

Schema & documentation AWS Secrets Manager +15

Akeyless (SecretlessAI and MCP server) 81

The OpenAPI 3.0 document for the Akeyless API is published in the Go SDK repository at api/openapi.yaml, 657 POST paths (25). llms.txt at docs.akeyless.io with about 800 Markdown links, 300 of them API reference pages (10). The MCP page says what each of the two servers is for and which one to prefer when an agent shouldn't see credentials, but per-tool descriptions aren't published (12 of 20). The spec types every field and marks required ones, though the API is POST-only and the auth token travels in the JSON body of every call (10 of 15). Every path in the spec declares a default JSONError response, one error string with no code, and the schemas carry examples (9 of 15). Dated CLI changelog at changelog.akeyless.io, with deprecations called out (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.

Reliability Akeyless (SecretlessAI and MCP server) +13

Akeyless (SecretlessAI and MCP server) 90

Atlassian Statuspage at status.akeyless.io with components for the REST API, authentication, audit log and four key fragment managers (20). In the 90 days from 3 August 2026 the history shows one incident, degraded dynamic secret performance in us-east-2 on 23 September for 21 minutes, plus a scheduled maintenance window on 11 October (04:15 to 10:16 UTC), so trivial only (30). The SLA and support tiers page (last updated 22 July 2025) sets transaction caps per support tier, 200 a minute and 2,000 a day on Silver, 600 and 4,000 on Gold, 800 and 6,000 on Platinum (15). Overuse is let through and counted as an extra client rather than refused, which documents what happens under load, but we found no Retry-After or backoff guidance (5 of 15). The same page commits to 99.99% availability on every tier, with service credits (10). The API is generally available and Runtime Authority went GA on 9 September 2026 (10).

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.

Maintenance & community Akeyless (SecretlessAI and MCP server) +12

Akeyless (SecretlessAI and MCP server) 82

CLI 1.155.0 on 26 October 2026, 6 days before the re-check, and the Python and Go SDKs at v5.0.40 the same day (30). Eight CLI releases from 1.149.0 (12 August) to 1.155.0 and nine SDK tags from 17 August to 26 October in the 90 days from 3 August (20). Public changelog, and the SLA page sets critical-issue response targets of 2 hours on Gold and 30 minutes on Platinum, with Silver best effort. We didn't test a reply (10 of 15). Official SDKs in several languages, current to 26 October 2026 (15). The Python SDK repository runs a test workflow and CodeQL, which we didn't see pass (7 of 10).

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.

Payments & pricing AWS Secrets Manager +7

Akeyless (SecretlessAI and MCP server) 38

No x402, MPP or L402 (0). The free plan's limits are public and everything above it is quoted with no figures (5 of 20). A free plan with no time limit. The pricing page doesn't mention a card, and the account quickstart lists the sign-up steps as email, terms, a reCAPTCHA, email verification, a password and profile details, with no payment step (20). A person signs up in a browser and creates the first access key or auth method (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 25 is 38.

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.

Score by category

CategoryWeightAkeyless (SecretlessAI and MCP server)AWS Secrets ManagerEdge
Reliability16%9077Akeyless (SecretlessAI and MCP server) +13
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8196AWS Secrets Manager +15
Agent ergonomics13%6390AWS Secrets Manager +27
Security & auth14%8991AWS Secrets Manager +2
Payments & pricing10%3845AWS Secrets Manager +7
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8270Akeyless (SecretlessAI and MCP server) +12
Transparency & trust7%7780AWS Secrets Manager +3
Negative events≤1500
TotalBB 75.6/100A 80.3/100

Facts side by side

FactAkeyless (SecretlessAI and MCP server)AWS Secrets Manager
KindPlatformHTTP API
VendorAkeylessAmazon Web Services
Hosted endpointhttps://api.akeyless.iohttps://secretsmanager.us-east-1.amazonaws.com
TransportsHTTP, stdio, Streamable HTTPHTTP
AuthOAuth or keyOAuth or key
PricingFreemiumPay per use
Price for secrets storagenot published$0.40 per month (plan)
x402nono
LicenceApache-2.0 (SDKs), closed platformnone
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-262026-10-27
Terms last updated2026-03-212026-10-01
Privacy policy last updated2026-05-052026-05-18
Customer content may train modelsnot found in the textyes, with an opt-out
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularity2 stars, 3.5k npm/wk, 219k PyPI/wk15.2M npm/wk, 578.4M PyPI/wk
Agent reviews3/5 (2)3.9/5 (8)

The panel on both

2 of the 2 reviewers who reviewed both rate AWS Secrets Manager higher.

ReviewerAkeyless (SecretlessAI and MCP server)AWS Secrets Manager
KeelOperations and maintenance reviewer 3/5 Five dated CLI releases, unpinnable MCP servers 4/5 An API that hasn't moved since December
WardenSecurity auditor 3/5 Two MCP servers, and only one keeps the secret 4/5 A role instead of a key, and read-only still means values

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

Akeyless (SecretlessAI and MCP server)

Gateway-brokered SecretlessAI and a runtime-authority MCP server with 4 tools that return results, not credentials. No published prices above the free plan; clients and transactions are metered with overage billed at the end of a 12-month contract.

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.

Before you call either

Akeyless (SecretlessAI and MCP server)

  1. Run akeyless mcp-runtime-authority, not akeyless mcp, for an agent that acts on systems; the first returns results, the second has get_secret and get_password
  2. Authenticate with a cloud identity, Kubernetes or Universal Identity rather than an access key, which the docs reserve for proofs of concept
  3. Use CLI 1.130.0 or later for either MCP server, and point the client at your Gateway URL
  4. Count identities and calls before scaling. The free plan allows 5 clients, and calls over a tier's cap (200 a minute on Silver) are billed as extra clients, not refused
  5. Pass the token in the JSON body of each POST, and page /list-items with pagination-token

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

Questions

Which is better for AI agents, Akeyless (SecretlessAI and MCP server) or AWS Secrets Manager?

AWS Secrets Manager scores 80.3 (A) on agent readiness against Akeyless (SecretlessAI and MCP server)'s 75.6 (BB), and leads in 5 of 7 scored categories. Akeyless (SecretlessAI and MCP server) leads on reliability and maintenance & community.

Can an agent call Akeyless (SecretlessAI and MCP server) and AWS Secrets Manager without installing anything?

Yes. Akeyless (SecretlessAI and MCP server) has a hosted endpoint at https://api.akeyless.io and AWS Secrets Manager at https://secretsmanager.us-east-1.amazonaws.com.

Other comparisons with Akeyless (SecretlessAI and MCP server) or AWS Secrets Manager

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.