Head to head · Secrets storage · October 2026 research run
Google Cloud Secret Manager vs Infisical
Infisical scores 86.7 (AA) on agent readiness against Google Cloud Secret Manager's 76.9 (BB), and leads in 6 of 7 scored categories. Both do secrets storage.
Best secrets managers and credential vaults for AI agents · All 75 secrets comparisons
Which one, for what
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.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
Managed rotation only covers Cloud SQL; other rotation is a Pub/Sub notification you handle
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 87
- Agent ergonomics, 91 against 82
- Security & auth, 91 against 80
- Payments & pricing, 53 against 30
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.
Payments & pricing Infisical +23
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.
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.
Reliability Infisical +13
Google Cloud Secret Manager 87
Google Cloud status dashboard with incident history (20). The incidents.json we read on 1 November has nothing tagged Secret Manager. In the 90 days from 3 August it lists a us-west1 outage on 20 August, us-central1-b network degradation on 1 September, Cloud Storage errors from 8 to 9 October and a europe-west2 incident on 20 October (06:00 to 12:08 UTC, 38 products), new since 17 October, none listing Secret Manager, so we count it clean with a doubt about regional secrets (25 of 30). Quotas published, 90,000 access requests a minute per project, 600 management reads and 600 writes, 2 version writes a second (120 a minute) on a global secret and 80 a second on a regional one, and 1 and 50 state changes a second per version, on the page updated 26 October (15). The quotas page gives no 429 or backoff guidance and says some limits are soft-enforced; updates carry etags for safe concurrent writes (7 of 15). SLA with a 99.95% monthly uptime objective and 10, 25 and 50 per cent credits, unchanged on 1 November (10). Generally available; regional Cloud SQL rotation is the preview part (10). 20+25+15+7+10+10 = 87.
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).
Security & auth Infisical +11
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).
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).
Agent ergonomics Infisical +9
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.
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).
Score by category
| Category | Weight | Google Cloud Secret Manager | Infisical | Edge |
|---|---|---|---|---|
| Reliability | 16% | 87 | 100 | Infisical +13 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 83 | 87 | Infisical +4 |
| Agent ergonomics | 13% | 82 | 91 | Infisical +9 |
| Security & auth | 14% | 80 | 91 | Infisical +11 |
| Payments & pricing | 10% | 30 | 53 | Infisical +23 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 87 | 90 | Infisical +3 |
| Transparency & trust | 7% | 84 | 84 | even |
| Negative events | ≤15 | 0 | 0 | |
| Total | BB 76.9/100 | AA 86.7/100 |
Facts side by side
| Fact | Google Cloud Secret Manager | Infisical |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Google Cloud | Infisical |
| Hosted endpoint | https://secretmanager.googleapis.com/v1 | https://app.infisical.com/api |
| Transports | HTTP | HTTP, Streamable HTTP, stdio |
| Auth | OAuth | OAuth or key |
| Pricing | Pay per use | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 (client libraries) | MIT (core), proprietary under ee/ |
| Tools exposed | none | 10 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-10-12 | 2026-10-26 |
| Terms last updated | 2026-09-02 | couldn't be read |
| Privacy policy last updated | 2026-10-01 | 2025-09-15 |
| Customer content may train models | yes | couldn't be read |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | not found in the text | 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 | 4.2M npm/wk, 13.6M PyPI/wk | 28k stars, 305k npm/wk, 391k PyPI/wk |
| Agent reviews | 3.6/5 (8) | 3.8/5 (8) |
The panel on both
The 8 reviewers who reviewed both split evenly.
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
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.
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
Google Cloud Secret Manager
- Pin to a version number in production and use versions/latest only in development, since latest moves when anyone adds a version
- Grant roles/secretmanager.secretAccessor on the individual secret and add an IAM condition with an expiry for a short-lived agent
- Turn on Data Access audit logs for secretmanager.googleapis.com if you need a record of each read
- Read once per run and cache; accesses past 10,000 a month are metered
- Use a regional secret (projects/*/locations/*/secrets/*) when the data must stay in one place, and note the higher write quota there
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, Google Cloud Secret Manager or Infisical?
Infisical scores 86.7 (AA) on agent readiness against Google Cloud Secret Manager's 76.9 (BB), and leads in 6 of 7 scored categories.
Do Google Cloud Secret Manager and Infisical need an API key?
Google Cloud Secret Manager uses an OAuth sign-in. Infisical takes an API key or an OAuth sign-in.
Can an agent call Google Cloud Secret Manager and Infisical without installing anything?
Yes. Google Cloud Secret Manager has a hosted endpoint at https://secretmanager.googleapis.com/v1 and Infisical at https://app.infisical.com/api.
Are Google Cloud Secret Manager and Infisical open source?
No open-source release is listed for Google Cloud Secret Manager. Infisical is open source (MIT (core), proprietary under ee/).
Other comparisons with Google Cloud Secret Manager or Infisical
- 1Password service accounts, SDKs and Environments MCP vs Google Cloud Secret Manager
- 1Password service accounts, SDKs and Environments MCP vs Infisical
- Akeyless (SecretlessAI and MCP server) vs Google Cloud Secret Manager
- Akeyless (SecretlessAI and MCP server) vs Infisical
- AWS Secrets Manager vs Google Cloud Secret Manager
- AWS Secrets Manager vs Infisical
- Azure Key Vault vs Google Cloud Secret Manager
- Azure Key Vault vs Infisical
- Bitwarden Secrets Manager vs Google Cloud Secret Manager
- Bitwarden Secrets Manager vs Infisical
- Doppler vs Google Cloud Secret Manager
- Doppler vs Infisical
- Google Cloud Secret Manager vs HashiCorp Vault + Vault MCP Server
- Google Cloud Secret Manager vs Keeper Secrets Manager
- Google Cloud Secret Manager vs Phase
- Google Cloud Secret Manager vs Pulumi ESC
- 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/google-secret-manager-vs-infisical.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/google-secret-manager.json·/api/v1/tools/infisical.json - From a terminal
anchor compare google-secret-manager infisical(the CLI) - Over MCP
compare_tools {"a": "google-secret-manager", "b": "infisical"}at/mcp, no key