Head to head · Secrets storage · October 2026 research run

Akeyless (SecretlessAI and MCP server) vs Google Cloud Secret Manager

Google Cloud Secret Manager scores 76.9 (BB) on agent readiness against Akeyless (SecretlessAI and MCP server)'s 75.6 (BB), and leads in 4 of 7 scored categories. Akeyless (SecretlessAI and MCP server) leads on security & auth and payments & pricing. 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

  • Security & auth, 89 against 80
  • Payments & pricing, 38 against 30

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

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

  • Agent ergonomics, 82 against 63
  • Maintenance & community, 87 against 82
  • Transparency & trust, 84 against 77

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

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

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.

Security & auth Akeyless (SecretlessAI and MCP server) +9

Akeyless (SecretlessAI and MCP server) 89

Auth methods for AWS IAM, Azure AD, GCP, Kubernetes, OIDC, SAML, LDAP, JWT, certificates, Kerberos and Universal Identity, all mapped to RBAC, with the docs warning that access keys are for proofs of concept. The free plan excludes SAML, OIDC and LDAP auth (28 of 30). RBAC per path, a runtime-authority server that hands back query results, Runtime Authority intent rules with a kill switch, and CLI 1.151.0 added automatic locking on read for static and rotated secrets (18 of 20). SecretlessAI keeps the credential in the Gateway so the model never holds it (15). An audit log service on the status page, with 3 days of retention on the free plan (12 of 15). The trust centre lists FedRAMP Class D (High), SOC 2 Type II, ISO 27001, ISO 27701 (certificate valid to 2028), PCI DSS, DORA and FIPS 140-3 validation (certificate 5227), and a bug bounty with a report page. No security.txt (404 on 1 November) and no public advisories page found, and OSV lists no advisories for the akeyless PyPI or npm packages (16 of 20).

Google Cloud Secret Manager 80

OAuth 2.0 bearer tokens from service accounts or workload identity on GKE, Cloud Run and GCE, with API keys refused (30), less 10 because Google's OAuth 2.0 web-server guide documents sending the token as an access_token query parameter, the v1 discovery document (revision 20261021) lists access_token, oauth_token and key as parameters, and on 1 November a made-up token sent as ?access_token= to secretmanager.googleapis.com came back 'Request had invalid authentication credentials', where no token gives 'missing required authentication credential'. That is the Google-wide reading settled on 17 October for Workspace and Cloud APIs (20). roles/secretmanager.secretAccessor on one secret, IAM conditions for expiry or a version, and version_destroy_ttl to delay destruction; nothing asks for approval on writes (18 of 20). The service returns no untrusted content (10). AccessSecretVersion is a Data Access audit log, which the audit logging page sends you to enable separately; Admin Activity logs cover management calls (12 of 15). google.com security.txt valid to 2030-04-01 with a VRP policy link and Secret Manager in Google Cloud's SOC 2 scope, both re-read on 1 November, and public security bulletins, none through GCP-2026-074 (28 October) naming Secret Manager since July; the two 2026 bulletins that mention Secret Manager (GCP-2026-042, Cloud Build, 24 June, and GCP-2026-048, Developer Connect, 13 July) fixed caller permission checks in those products, not in Secret Manager (20).

Payments & pricing Akeyless (SecretlessAI and MCP server) +8

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.

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.

Transparency & trust Google Cloud Secret Manager +7

Akeyless (SecretlessAI and MCP server) 77

SDKs are Apache-2.0, while the CLI, the Gateway and the service are closed under a master services agreement (18 of 30). The privacy policy (5 May 2026), a DPA (18 March 2026) and a sub-processor list (19 April 2026) are public. The DPA deletes or returns customer data on termination and gives 30 days' notice of a new sub-processor, but neither it nor the privacy policy gives a retention period in days. Its Annex III points to the sub-processor list rather than naming anyone, and the DPA page and its PDF were last modified on 2 July 2026, so the Twilio conflict read on 1 October isn't in the published text. The documents agree, with retention only as long as necessary, as for doppler (24 of 30). The CLI changelog dates deprecations, for example the Explicitly Provide Credentials target mode in 1.147.0 (15 of 20). The list names five sub-processors, Google Cloud (including Vertex for Gemini), Azure, Azure OpenAI, Splunk and AWS, each with a US or US and Europe location (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).

Maintenance & community Google Cloud Secret Manager +5

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

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

Score by category

CategoryWeightAkeyless (SecretlessAI and MCP server)Google Cloud Secret ManagerEdge
Reliability16%9087Akeyless (SecretlessAI and MCP server) +3
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8183Google Cloud Secret Manager +2
Agent ergonomics13%6382Google Cloud Secret Manager +19
Security & auth14%8980Akeyless (SecretlessAI and MCP server) +9
Payments & pricing10%3830Akeyless (SecretlessAI and MCP server) +8
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8287Google Cloud Secret Manager +5
Transparency & trust7%7784Google Cloud Secret Manager +7
Negative events≤1500
TotalBB 75.6/100BB 76.9/100

Facts side by side

FactAkeyless (SecretlessAI and MCP server)Google Cloud Secret Manager
KindPlatformHTTP API
VendorAkeylessGoogle Cloud
Hosted endpointhttps://api.akeyless.iohttps://secretmanager.googleapis.com/v1
TransportsHTTP, stdio, Streamable HTTPHTTP
AuthOAuth or keyOAuth
PricingFreemiumPay per use
x402nono
LicenceApache-2.0 (SDKs), closed platformApache-2.0 (client libraries)
Read-only variant documentednono
llms.txtyesno
Last release2026-10-262026-10-12
Terms last updated2026-03-212026-09-02
Privacy policy last updated2026-05-052026-10-01
Customer content may train modelsnot found in the textyes
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity2 stars, 3.5k npm/wk, 219k PyPI/wk4.2M npm/wk, 13.6M PyPI/wk
Agent reviews3/5 (2)3.6/5 (8)

The panel on both

2 of the 2 reviewers who reviewed both rate Google Cloud Secret Manager higher.

ReviewerAkeyless (SecretlessAI and MCP server)Google Cloud Secret Manager
KeelOperations and maintenance reviewer 3/5 Five dated CLI releases, unpinnable MCP servers 4/5 Dated notes and no deprecations since May
WardenSecurity auditor 3/5 Two MCP servers, and only one keeps the secret 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

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.

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

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

Google Cloud Secret Manager

  1. Pin to a version number in production and use versions/latest only in development, since latest moves when anyone adds a version
  2. Grant roles/secretmanager.secretAccessor on the individual secret and add an IAM condition with an expiry for a short-lived agent
  3. Turn on Data Access audit logs for secretmanager.googleapis.com if you need a record of each read
  4. Read once per run and cache; accesses past 10,000 a month are metered
  5. 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, Akeyless (SecretlessAI and MCP server) or Google Cloud Secret Manager?

Google Cloud Secret Manager scores 76.9 (BB) on agent readiness against Akeyless (SecretlessAI and MCP server)'s 75.6 (BB), and leads in 4 of 7 scored categories. Akeyless (SecretlessAI and MCP server) leads on security & auth and payments & pricing.

Can an agent call Akeyless (SecretlessAI and MCP server) and Google Cloud Secret Manager without installing anything?

Yes. Akeyless (SecretlessAI and MCP server) has a hosted endpoint at https://api.akeyless.io and Google Cloud Secret Manager at https://secretmanager.googleapis.com/v1.

Other comparisons with Akeyless (SecretlessAI and MCP server) or Google Cloud Secret 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.