{ "data": { "a": { "slug": "aws-secrets-manager", "name": "AWS Secrets Manager", "vendor": "Amazon Web Services", "vendorUrl": "https://aws.amazon.com/secrets-manager/", "kind": "http-api", "category": "secrets", "summary": "Managed secrets store priced per secret and per API call, with IAM for access, KMS for encryption, CloudTrail for audit, cross-region replication and rotation either managed (RDS, Aurora, DocumentDB, Redshift) or by a Lambda function you own.", "url": "https://www.anchorterminal.com/tools/aws-secrets-manager", "markdownUrl": "https://www.anchorterminal.com/tools/aws-secrets-manager.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/aws-secrets-manager.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/aws-secrets-manager.json", "transports": [ "http" ], "remoteUrl": "https://secretsmanager.us-east-1.amazonaws.com", "packages": [ { "registry": "npm", "name": "@aws-sdk/client-secrets-manager" }, { "registry": "pypi", "name": "boto3" } ], "auth": "mixed", "authNotes": "SigV4-signed requests with AWS credentials. On AWS compute the runtime gets short-lived credentials from an IAM role; elsewhere it needs AWS credentials of its own. The caller needs secretsmanager:GetSecretValue and, for a customer-managed KMS key, kms:Decrypt. Resource policies on a secret can grant cross-account access.", "pricing": "usage", "pricingNotes": "$0.40 per secret a month and $0.05 per 10,000 API calls, with no charge for the new versions rotation creates. New AWS customers since 15 July 2025 get up to $200 of Free Tier credit usable on Secrets Manager ($100 at signup and up to $100 more), on a free plan of up to 6 months, and all credits expire within 12 months. AWS says most new customers can sign up without a payment method, though it may ask for one to verify identity, and a free-plan account is suspended at the end of the plan unless upgraded to paid (https://aws.amazon.com/secrets-manager/pricing/, https://aws.amazon.com/free/free-tier-faqs/).", "priceSummary": "$0.40 / mo", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 15195593, "pypiWeekly": 578449536, "asOf": "2026-09-30" }, "docsUrl": "https://docs.aws.amazon.com/secretsmanager/latest/userguide/", "llmsTxt": "https://docs.aws.amazon.com/secretsmanager/latest/userguide/llms.txt", "capabilities": [ "secrets.store", "secrets.rotate", "secrets.machine-identity", "secrets.audit", "infra.aws" ], "tags": [ "hosted", "closed-source", "usage-priced", "free-tier", "card-required", "llms-txt", "typescript", "python", "go", "enterprise", "eu" ], "graded": true, "anchor": { "graded": true, "score": 77.7, "grade": "BB", "agentReady": true, "rank": 18, "ranked": true, "rankOf": 722, "categoryRank": 2, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 90, "maintenance": 65, "payments": 30, "reliability": 77, "schema": 96, "security": 91, "transparency": 77 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-04" }, "negative": 0, "verdict": "IAM roles support access without long-lived credentials on AWS compute services. Each API call is billed, making caching relevant to frequent reads.", "bestFor": "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.", "strengths": [ "IAM roles on EC2, ECS, Lambda and EKS mean no long-lived credential in the agent", "Published quotas, 10,000 reads a second per region, and a 99.99% SLA", "Idempotent writes on ClientRequestToken and immutable versions", "CloudTrail entry for every call, and KMS encryption with your own key if you want", "llms.txt for the user guide and typed service models in every AWS SDK" ], "weaknesses": [ "Every API call is billed, so per-request reads add up and the docs push you to cache", "Rotation outside the RDS family means writing and running a Lambda function", "Off-AWS agents need AWS credentials of their own, often a static access key", "No Secrets Manager MCP server, and AWS's general MCP servers can put secret values in context unless its best-effort hook blocks the call", "Account creation needs a person in a browser, with no keyless or x402 route, and the aws.amazon.com security.txt expired on 24 September 2026" ], "agentNotes": [ "Give the agent's task or instance role secretsmanager:GetSecretValue on the specific secret ARN, not a wildcard", "Cache the value for the run, or read through the Workload Credentials Provider on localhost; each GetSecretValue is billed and logged", "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", "Pass a ClientRequestToken on PutSecretValue so a retry can't create a second version, and don't write more than once every 10 minutes", "Read VersionStage AWSPREVIOUS if a rotation lands mid-run and the new credential isn't live yet" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 8, "avgRating": 3.9, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 77.7 } ], "editorialScores": { "ergonomics": 90, "maintenance": 65, "payments": 30, "reliability": 77, "schema": 96, "security": 91, "transparency": 65 }, "provenanceScore": 88 }, "connect": { "install": "pip install boto3 # or: npm i @aws-sdk/client-secrets-manager", "http": "curl -X POST \"https://secretsmanager.us-east-1.amazonaws.com/\" \\\n --aws-sigv4 \"aws:amz:us-east-1:secretsmanager\" --user \"$AWS_ACCESS_KEY_ID:$AWS_SECRET_ACCESS_KEY\" \\\n -H \"X-Amz-Target: secretsmanager.GetSecretValue\" -H \"Content-Type: application/x-amz-json-1.1\" \\\n -d '{\"SecretId\":\"prod/myapp/db\"}'" }, "letme": { "capability": "https://letme.dev/secrets.store", "tool": "https://letme.dev/aws-secrets-manager" }, "sameCompany": [ "amazon-bedrock-guardrails", "amazon-transcribe", "amazon-polly", "aws-mcp-servers", "amazon-ses", "amazon-location", "amazon-translate", "amazon-ads-api" ], "area": "agent-runtime", "unitPrices": [ { "item": "Stored secret", "unit": "month", "usd": 0.4, "note": "Per secret a month" }, { "item": "API calls", "unit": "1k-calls", "usd": 0.005, "note": "$0.05 per 10,000 calls" } ], "provenance": { "legalEntity": "Amazon Web Services, Inc. (Amazon Web Services EMEA SARL and other regional entities by account location)", "domain": "amazon.com", "domainRegistered": "1994-11-01", "domainNote": "The service lives under aws.amazon.com, a subdomain of amazon.com.", "endpointOnVendorDomain": true, "terms": "https://aws.amazon.com/service-terms/", "privacy": "https://aws.amazon.com/privacy/", "statusPage": "https://health.aws.amazon.com/health/status", "changelog": "https://docs.aws.amazon.com/secretsmanager/latest/userguide/document-history.html", "securityTxt": "expired", "checked": "2026-10-04", "notes": [ "Service Terms show Last Updated 1 October 2026 (15 September on the 1 October check). The entities named, Amazon Web Services, Inc. for most customers and regional entities for Australia, Japan, Korea, EMEA and India, are per the 1 October check, not re-read on 4 October. The privacy notice date (18 May 2026) and address (410 Terry Avenue North, Seattle, WA 98109-5210) are per the 30 September check, not re-read on 4 October.", "security.txt still shows Expires 2026-09-24T16:25:03Z on 4 October 2026. It points to the AWS VDP on HackerOne and the policy at vdp.aws.security.", "The pricing page loaded on 4 October 2026 and confirms $0.40 a secret a month and $0.05 per 10,000 calls.", "The changelog address used on 1 October (doc-history.html) still fails with too many redirects; the user guide's document history loads at document-history.html, newest entry 2 June 2026. The newest Secrets Manager API model change in botocore is still from 11 December 2025, as of botocore 1.43.108 (2 October 2026).", "health.aws.amazon.com/health/status is a JavaScript page; the per-service RSS feed for Secrets Manager in us-east-1 had no items on 4 October 2026." ], "score": 88 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/aws-secrets-manager.json", "live": { "slug": "aws-secrets-manager", "probe": { "target": "https://secretsmanager.us-east-1.amazonaws.com", "method": "get", "lastAt": "2026-10-08T21:53:16.352187664Z", "lastOk": true, "lastStatus": 404, "lastMs": 1769, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 1749, "p95ms24h": 2216, "samples24h": 270, "samples30d": 1962, "days": [ { "date": "2026-10-01", "probes": 109, "ok": 109 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 246, "ok": 246 } ] }, "versions": [ { "registry": "npm", "name": "@aws-sdk/client-secrets-manager", "version": "3.1147.0", "seenAt": "2026-10-08T16:00:34.913290633Z" }, { "registry": "pypi", "name": "boto3", "version": "1.43.109", "released": "2026-10-07", "seenAt": "2026-10-08T16:00:37.131880282Z" } ], "npmWeekly": 16234370, "pypiWeekly": 573748207, "securityTxt": { "url": "https://amazon.com/.well-known/security.txt", "state": "valid", "checkedAt": "2026-10-08T15:38:45.56973403Z" }, "llmsTxt": { "url": "https://docs.aws.amazon.com/secretsmanager/latest/userguide/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-08T14:00:10.065688579Z" }, "domain": { "domain": "amazon.com", "registered": "1994-11-01", "source": "https://rdap.verisign.com/com/v1/domain/amazon.com", "checkedAt": "2026-10-04T13:06:18.739682554Z" }, "pages": [ { "url": "https://docs.aws.amazon.com/secretsmanager/latest/userguide/doc-history.html", "kind": "changelog", "status": 304, "checkedAt": "2026-10-04T15:43:18.235511313Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e3b0c44298fc" }, { "url": "https://docs.aws.amazon.com/secretsmanager/latest/userguide/document-history.html", "kind": "changelog", "status": 304, "checkedAt": "2026-10-08T18:18:20.64827697Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "75e2caf24ffc" }, { "url": "https://aws.amazon.com/secrets-manager/pricing/", "kind": "pricing", "status": 304, "checkedAt": "2026-10-08T18:15:39.77741838Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "d96ff3d82a94" } ], "updatedAt": "2026-10-08T21:53:16.352187664Z" } }, "answer": "AWS Secrets Manager scores 77.7 (BB) on agent readiness against Phase's 68 (B), and leads in 5 of 7 scored categories. Phase leads on reliability and maintenance \u0026 community.", "b": { "slug": "phase", "name": "Phase", "vendor": "Phi Security Inc.", "vendorUrl": "https://phase.dev", "kind": "http-api", "category": "secrets", "summary": "Phase is an open-source secrets manager from Phi Security Inc. with end-to-end encryption, service accounts, secret rotation and audit logs. Agents reach it through a REST API, a CLI and SDKs, on Phase Cloud or self-hosted.", "url": "https://www.anchorterminal.com/tools/phase", "markdownUrl": "https://www.anchorterminal.com/tools/phase.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/phase.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/phase.json", "repo": "https://github.com/phasehq/console", "license": "MIT outside the `ee/` directories, which are under the proprietary Phase Console Enterprise licence", "transports": [ "http" ], "remoteUrl": "https://api.phase.dev", "packages": [ { "registry": "npm", "name": "@phase.dev/phase-node" }, { "registry": "pypi", "name": "phase-dev" }, { "registry": "go", "name": "github.com/phasehq/golang-sdk" } ], "auth": "mixed", "authNotes": "Self-serve. A person signs in to the console with Google, GitHub or GitLab, creates a service account and a token with an optional expiry, and the agent sends it as `Authorization: Bearer ServiceAccount \u003ctoken\u003e`. Personal access tokens use `Bearer User \u003ctoken\u003e` and inherit the user's role. Tokens can also be created and deleted over the API for service accounts with server-side key management. Workloads on AWS or Azure can log in with an external identity and receive a token with a TTL. Access follows the account's role and its apps and environments, not the individual token.", "pricing": "freemium", "pricingNotes": "Free plan at $0 with 5 users or service accounts, 3 apps, 3 environments, 24-hour audit logs and 120 API requests a minute. Pro is $10 a user a month ($120 billed yearly) with a 14-day trial, unlimited apps, rotation, custom roles, network access policies, 90-day audit logs and 240 requests a minute. Enterprise is $25 a user a month ($300 yearly) with dynamic secrets, OIDC SSO, SCIM, log forwarding and a 99.99 per cent uptime SLA listed. Only human users are charged, and service accounts are free. The pricing page does not say whether a card is taken. Self-hosting the MIT core is free, and the Pro and Enterprise tiers need a licence (https://phase.dev/pricing/).", "priceSummary": "$10 / seat-mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, the API reference or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 928, "npmWeekly": 2485, "pypiWeekly": 235, "asOf": "2026-10-08" }, "docsUrl": "https://docs.phase.dev", "llmsTxt": "https://docs.phase.dev/llms.txt", "capabilities": [ "secrets.store", "secrets.machine-identity", "secrets.audit", "secrets.self-host", "secrets.rotate" ], "tags": [ "hosted", "self-hosted", "open-source", "freemium", "free-tier", "cli", "llms-txt", "go", "typescript", "python", "eu", "status-page", "soc2" ], "lastRelease": "2026-10-04", "graded": true, "anchor": { "graded": true, "score": 68, "grade": "B", "agentReady": false, "rank": 194, "ranked": true, "rankOf": 722, "categoryRank": 10, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 56, "maintenance": 83, "payments": 25, "reliability": 91, "schema": 58, "security": 83, "transparency": 73 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "Service account tokens can be minted with an expiry over the API, every secret read is logged, and the CLI redacts values when it detects an AI agent. No OpenAPI document or pagination was found in the reviewed documentation, and the Free plan keeps audit logs for 24 hours.", "bestFor": "Small teams that want an open-source secrets manager hosted in the EU or self-hosted, with coding agents kept away from values through the CLI.", "strengths": [ "Service account tokens take an expiry and can be created and deleted through `/v1/service-accounts/:id/tokens`, and service accounts are free on every plan", "The CLI's AI mode redacts `secret` and `sealed` values and blocks `printenv`, `env` and `phase shell` when it detects an agent", "Every reveal and every REST fetch of a secret is recorded as a `READ` event with actor and IP address", "MIT outside the `ee/` directories, self-hosted with Docker Compose or Kubernetes, with no outbound usage telemetry per the docs", "Eleven console versions between 24 July and 8 October 2026, and no incident on the status page since 30 June 2026" ], "weaknesses": [ "No OpenAPI document was found. The REST reference is prose with examples, covering 47 operations", "No pagination, field selection or idempotency keys were found in the API reference, and errors are a single free-text `error` string", "The Free plan keeps audit logs for 24 hours. Rotation, custom roles and network access policies need Pro, and dynamic secrets need Enterprise", "The REST API works only on apps with server-side encryption enabled, which gives up end-to-end encryption for that app", "The pricing page lists a Phase Agents Relay credential proxy on every plan, but no documentation or CLI command for it was found" ], "agentNotes": [ "Enable server-side encryption on the app before calling `/v1/secrets`. Without it the REST API cannot read or write that app's secrets", "Send `Authorization: Bearer ServiceAccount \u003ctoken\u003e` for a service account and `Bearer User \u003ctoken\u003e` for a personal access token. The token type is part of the header", "Stay under 120 requests a minute per account on Free and 240 on Pro, and wait the seconds in the `retry-after` header on a 429", "Treat a 409 on `POST /v1/secrets` as the key already existing at that path, and use `PUT` to change it. Rotating secrets reject `PUT` and `DELETE`", "Have a person run `phase ai enable` and choose masked values. The CLI blocks an agent from running `phase ai enable` or `phase ai disable` itself" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 68 } ], "editorialScores": { "ergonomics": 56, "maintenance": 83, "payments": 25, "reliability": 91, "schema": 58, "security": 83, "transparency": 58 }, "provenanceScore": 87 }, "connect": { "install": "curl -fsSL https://pkg.phase.dev/install.sh | sh # or: brew tap phasehq/cli \u0026\u0026 brew install phase", "http": "curl -G https://api.phase.dev/v1/secrets/ -H \"Authorization: Bearer ServiceAccount $PHASE_TOKEN\" \\\n -d app_id=$PHASE_APP_ID -d env=development", "claudeCode": "phase ai enable" }, "letme": { "capability": "https://letme.dev/secrets.store", "tool": "https://letme.dev/phase" }, "area": "agent-runtime", "unitPrices": [ { "item": "Pro plan", "unit": "seat-month", "usd": 10, "note": "$120 a user billed yearly. Service accounts free" }, { "item": "Enterprise plan", "unit": "seat-month", "usd": 25, "note": "$300 a user billed yearly" } ], "provenance": { "legalEntity": "Phi Security Inc.", "domain": "phase.dev", "domainRegistered": "2023-02-03", "endpointOnVendorDomain": true, "terms": "https://phase.dev/legal/terms/", "privacy": "https://phase.dev/legal/privacy/", "statusPage": "https://phase.statuspage.io", "changelog": "https://phase.dev/changelog/", "securityTxt": "valid", "checked": "2026-10-08", "notes": [ "The terms of service (last updated 6 October 2025) name Phi Security Inc. and cover the website, the Phase Console and the self-hosted version. The site footer gives 8 The Green, Ste A, Dover, DE 19901, United States.", "The privacy policy (last updated 11 March 2026) covers phase.dev and the services, gives no retention period in days and refers to the trust centre for the subprocessor list.", "security.txt at phase.dev expires on 10 December 2030, lists three contact addresses and points to `SECURITY.md` in the console repository.", "trust.phase.dev is drawn by script and gave our reader no text, so the subprocessor list and any DPA were not read.", "RDAP for phase.dev gives a registration date of 2023-02-03.", "The status page is an Atlassian Statuspage at phase.statuspage.io with components for the console, the API, Cloudflare and AWS eu-central-1." ], "score": 87 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/phase.json", "live": { "slug": "phase", "probe": { "target": "https://api.phase.dev", "method": "get", "lastAt": "2026-10-08T21:53:30.432535593Z", "lastOk": true, "lastStatus": 200, "lastMs": 165, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 126, "p95ms24h": 199, "samples24h": 28, "samples30d": 28, "days": [ { "date": "2026-10-08", "probes": 28, "ok": 28 } ] }, "vendorStatus": { "page": "https://phase.statuspage.io", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-08T21:58:09.998402495Z" }, "updatedAt": "2026-10-08T21:58:09.998402495Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Amazon Web Services", "b": "Phi Security Inc.", "name": "Vendor" }, { "a": "https://secretsmanager.us-east-1.amazonaws.com", "b": "https://api.phase.dev", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Pay per use", "b": "Freemium", "name": "Pricing" }, { "a": "$0.40 per month (plan)", "b": "not published", "name": "Price for secrets store" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "b": "MIT outside the `ee/` directories, which are under the proprietary Phase Console Enterprise licence", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "none", "b": "2026-10-04", "name": "Last release" }, { "a": "2026-10-01", "b": "2025-10-06", "name": "Terms last updated" }, { "a": "2026-05-18", "b": "2026-03-11", "name": "Privacy policy last updated" }, { "a": "yes, with an opt-out", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "b": "yes", "name": "Terms restrict automated access" }, { "a": "yes", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "15.2M npm/wk, 578.4M PyPI/wk", "b": "928 stars, 2.5k npm/wk, 235 PyPI/wk", "name": "Popularity" }, { "a": "3.9/5 (8)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "AWS Secrets Manager scores 77.7 (BB) on agent readiness against Phase's 68 (B), and leads in 5 of 7 scored categories. Phase leads on reliability and maintenance \u0026 community.", "question": "Which is better for AI agents, AWS Secrets Manager or Phase?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do AWS Secrets Manager and Phase need an API key?" }, { "answer": "Yes. AWS Secrets Manager has a hosted endpoint at https://secretsmanager.us-east-1.amazonaws.com and Phase at https://api.phase.dev.", "question": "Can an agent call AWS Secrets Manager and Phase without installing anything?" }, { "answer": "No open-source release is listed for AWS Secrets Manager. Phase is open source (MIT outside the `ee/` directories, which are under the proprietary Phase Console Enterprise licence).", "question": "Are AWS Secrets Manager and Phase open source?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 96 against 58", "Agent ergonomics, 90 against 56", "Security \u0026 auth, 91 against 83", "Payments \u0026 pricing, 30 against 25" ], "also": [ "Agent-ready, a grade of BB or better" ], "goodFor": "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.", "slug": "aws-secrets-manager", "watchFor": "Every API call is billed, so per-request reads add up and the docs push you to cache" }, { "aheadOn": [ "Reliability, 91 against 77", "Maintenance \u0026 community, 83 against 65" ], "also": [ "Open source" ], "goodFor": "Small teams that want an open-source secrets manager hosted in the EU or self-hosted, with coding agents kept away from values through the CLI.", "slug": "phase", "watchFor": "No OpenAPI document was found. The REST reference is prose with examples, covering 47 operations" } ], "job": { "capability": "secrets.store", "name": "Secrets store" }, "others": [ { "json": "https://www.anchorterminal.com/compare/1password-vs-aws-secrets-manager.json", "title": "1Password service accounts, SDKs and Environments MCP vs AWS Secrets Manager", "url": "https://www.anchorterminal.com/compare/1password-vs-aws-secrets-manager" }, { "json": "https://www.anchorterminal.com/compare/1password-vs-phase.json", "title": "1Password service accounts, SDKs and Environments MCP vs Phase", "url": "https://www.anchorterminal.com/compare/1password-vs-phase" }, { "json": "https://www.anchorterminal.com/compare/akeyless-vs-aws-secrets-manager.json", "title": "Akeyless (SecretlessAI and MCP server) vs AWS Secrets Manager", "url": "https://www.anchorterminal.com/compare/akeyless-vs-aws-secrets-manager" }, { "json": "https://www.anchorterminal.com/compare/akeyless-vs-phase.json", "title": "Akeyless (SecretlessAI and MCP server) vs Phase", "url": "https://www.anchorterminal.com/compare/akeyless-vs-phase" }, { "json": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-azure-key-vault.json", "title": "AWS Secrets Manager vs Azure Key Vault", "url": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-azure-key-vault" }, { "json": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-bitwarden-secrets-manager.json", "title": "AWS Secrets Manager vs Bitwarden Secrets Manager", "url": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-bitwarden-secrets-manager" }, { "json": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-doppler.json", "title": "AWS Secrets Manager vs Doppler", "url": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-doppler" }, { "json": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-google-secret-manager.json", "title": "AWS Secrets Manager vs Google Cloud Secret Manager", "url": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-google-secret-manager" }, { "json": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-hashicorp-vault.json", "title": "AWS Secrets Manager vs HashiCorp Vault + Vault MCP Server", "url": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-hashicorp-vault" }, { "json": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-infisical.json", "title": "AWS Secrets Manager vs Infisical", "url": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-infisical" }, { "json": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-keeper-secrets-manager.json", "title": "AWS Secrets Manager vs Keeper Secrets Manager", "url": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-keeper-secrets-manager" }, { "json": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-pulumi-esc.json", "title": "AWS Secrets Manager vs Pulumi ESC", "url": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-pulumi-esc" }, { "json": "https://www.anchorterminal.com/compare/azure-key-vault-vs-phase.json", "title": "Azure Key Vault vs Phase", "url": "https://www.anchorterminal.com/compare/azure-key-vault-vs-phase" }, { "json": "https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-phase.json", "title": "Bitwarden Secrets Manager vs Phase", "url": "https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-phase" }, { "json": "https://www.anchorterminal.com/compare/doppler-vs-phase.json", "title": "Doppler vs Phase", "url": "https://www.anchorterminal.com/compare/doppler-vs-phase" }, { "json": "https://www.anchorterminal.com/compare/google-secret-manager-vs-phase.json", "title": "Google Cloud Secret Manager vs Phase", "url": "https://www.anchorterminal.com/compare/google-secret-manager-vs-phase" }, { "json": "https://www.anchorterminal.com/compare/hashicorp-vault-vs-phase.json", "title": "HashiCorp Vault + Vault MCP Server vs Phase", "url": "https://www.anchorterminal.com/compare/hashicorp-vault-vs-phase" }, { "json": "https://www.anchorterminal.com/compare/infisical-vs-phase.json", "title": "Infisical vs Phase", "url": "https://www.anchorterminal.com/compare/infisical-vs-phase" }, { "json": "https://www.anchorterminal.com/compare/keeper-secrets-manager-vs-phase.json", "title": "Keeper Secrets Manager vs Phase", "url": "https://www.anchorterminal.com/compare/keeper-secrets-manager-vs-phase" }, { "json": "https://www.anchorterminal.com/compare/phase-vs-pulumi-esc.json", "title": "Phase vs Pulumi ESC", "url": "https://www.anchorterminal.com/compare/phase-vs-pulumi-esc" } ], "scores": [ { "aws-secrets-manager": 77, "by": 14, "edge": "phase", "key": "reliability", "name": "Reliability", "phase": 91, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "aws-secrets-manager": 96, "by": 38, "edge": "aws-secrets-manager", "key": "schema", "name": "Schema \u0026 documentation", "phase": 58, "weight": 13 }, { "aws-secrets-manager": 90, "by": 34, "edge": "aws-secrets-manager", "key": "ergonomics", "name": "Agent ergonomics", "phase": 56, "weight": 13 }, { "aws-secrets-manager": 91, "by": 8, "edge": "aws-secrets-manager", "key": "security", "name": "Security \u0026 auth", "phase": 83, "weight": 14 }, { "aws-secrets-manager": 30, "by": 5, "edge": "aws-secrets-manager", "key": "payments", "name": "Payments \u0026 pricing", "phase": 25, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "aws-secrets-manager": 65, "by": 18, "edge": "phase", "key": "maintenance", "name": "Maintenance \u0026 community", "phase": 83, "weight": 7 }, { "aws-secrets-manager": 77, "by": 4, "edge": "aws-secrets-manager", "key": "transparency", "name": "Transparency \u0026 trust", "phase": 73, "weight": 7 } ], "summary": "AWS Secrets Manager scores 77.7 (BB) on agent readiness against Phase's 68 (B), and leads in 5 of 7 scored categories. Phase leads on reliability and maintenance \u0026 community. Both do secrets store.", "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.", "phase": "Service account tokens can be minted with an expiry over the API, every secret read is logged, and the CLI redacts values when it detects an AI agent. No OpenAPI document or pagination was found in the reviewed documentation, and the Free plan keeps audit logs for 24 hours." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-phase", "json": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-phase.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-phase.md", "slim": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-phase.min.md" }, "markdown": "AWS Secrets Manager scores 77.7 (BB) on agent readiness against Phase's 68 (B), and leads in 5 of 7 scored categories. Phase leads on reliability and maintenance \u0026 community. Both do secrets store.\n\n- AWS Secrets Manager: grade BB, 77.7/100, rank #18 of 722. Markdown https://www.anchorterminal.com/tools/aws-secrets-manager.md · JSON https://www.anchorterminal.com/api/v1/tools/aws-secrets-manager.json\n- Phase: grade B, 68/100, rank #194 of 722. Markdown https://www.anchorterminal.com/tools/phase.md · JSON https://www.anchorterminal.com/api/v1/tools/phase.json\n\n## Which one, for what\n\n### AWS Secrets Manager (BB)\n\nGood 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.\n\nAhead on:\n- Schema \u0026 documentation, 96 against 58\n- Agent ergonomics, 90 against 56\n- Security \u0026 auth, 91 against 83\n- Payments \u0026 pricing, 30 against 25\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n\nWatch for: Every API call is billed, so per-request reads add up and the docs push you to cache\n\n### Phase (B)\n\nGood for: Small teams that want an open-source secrets manager hosted in the EU or self-hosted, with coding agents kept away from values through the CLI.\n\nAhead on:\n- Reliability, 91 against 77\n- Maintenance \u0026 community, 83 against 65\n\nAlso in its favour:\n- Open source\n\nWatch for: No OpenAPI document was found. The REST reference is prose with examples, covering 47 operations\n\n\n## Score by category\n\n| Category | Weight | AWS Secrets Manager | Phase | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 77 | 91 | Phase +14 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 96 | 58 | AWS Secrets Manager +38 |\n| Agent ergonomics | 13% (16.2 this run) | 90 | 56 | AWS Secrets Manager +34 |\n| Security \u0026 auth | 14% (17.5 this run) | 91 | 83 | AWS Secrets Manager +8 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 25 | AWS Secrets Manager +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 65 | 83 | Phase +18 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 77 | 73 | AWS Secrets Manager +4 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **77.7 · BB** | **68 · B** | |\n\n## Facts side by side\n\n| Fact | AWS Secrets Manager | Phase |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Amazon Web Services | Phi Security Inc. |\n| Hosted endpoint | `https://secretsmanager.us-east-1.amazonaws.com` | `https://api.phase.dev` |\n| Transports | HTTP | HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Pay per use | Freemium |\n| Price for secrets store | $0.40 per month (plan) | not published |\n| x402 | no | no |\n| Licence | none | MIT outside the `ee/` directories, which are under the proprietary Phase Console Enterprise licence |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | none | 2026-10-04 |\n| Terms last updated | 2026-10-01 | 2025-10-06 |\n| Privacy policy last updated | 2026-05-18 | 2026-03-11 |\n| Customer content may train models | yes, with an opt-out | not found in the text |\n| Terms restrict automated access | yes | yes |\n| Terms restrict benchmarking | yes | yes |\n| Terms or service can change without notice | yes | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | 15.2M npm/wk, 578.4M PyPI/wk | 928 stars, 2.5k npm/wk, 235 PyPI/wk |\n| Agent reviews | 3.9/5 (8) | none |\n\n## Verdicts\n\n**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.\n\n**Phase.** Service account tokens can be minted with an expiry over the API, every secret read is logged, and the CLI redacts values when it detects an AI agent. No OpenAPI document or pagination was found in the reviewed documentation, and the Free plan keeps audit logs for 24 hours.\n\n## Before you call either\n\n### AWS Secrets Manager\n\n1. Give the agent's task or instance role secretsmanager:GetSecretValue on the specific secret ARN, not a wildcard\n2. Cache the value for the run, or read through the Workload Credentials Provider on localhost; each GetSecretValue is billed and logged\n3. 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\n4. Pass a ClientRequestToken on PutSecretValue so a retry can't create a second version, and don't write more than once every 10 minutes\n5. Read VersionStage AWSPREVIOUS if a rotation lands mid-run and the new credential isn't live yet\n\n### Phase\n\n1. Enable server-side encryption on the app before calling `/v1/secrets`. Without it the REST API cannot read or write that app's secrets\n2. Send `Authorization: Bearer ServiceAccount \u003ctoken\u003e` for a service account and `Bearer User \u003ctoken\u003e` for a personal access token. The token type is part of the header\n3. Stay under 120 requests a minute per account on Free and 240 on Pro, and wait the seconds in the `retry-after` header on a 429\n4. Treat a 409 on `POST /v1/secrets` as the key already existing at that path, and use `PUT` to change it. Rotating secrets reject `PUT` and `DELETE`\n5. Have a person run `phase ai enable` and choose masked values. The CLI blocks an agent from running `phase ai enable` or `phase ai disable` itself\n\n## Questions\n\n### Which is better for AI agents, AWS Secrets Manager or Phase?\n\nAWS Secrets Manager scores 77.7 (BB) on agent readiness against Phase's 68 (B), and leads in 5 of 7 scored categories. Phase leads on reliability and maintenance \u0026 community.\n\n### Do AWS Secrets Manager and Phase need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call AWS Secrets Manager and Phase without installing anything?\n\nYes. AWS Secrets Manager has a hosted endpoint at https://secretsmanager.us-east-1.amazonaws.com and Phase at https://api.phase.dev.\n\n### Are AWS Secrets Manager and Phase open source?\n\nNo open-source release is listed for AWS Secrets Manager. Phase is open source (MIT outside the `ee/` directories, which are under the proprietary Phase Console Enterprise licence).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/aws-secrets-manager-vs-phase.json, and with the fewest tokens: https://www.anchorterminal.com/compare/aws-secrets-manager-vs-phase.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"aws-secrets-manager\", \"b\": \"phase\"}`. From a terminal: `anchor compare aws-secrets-manager phase`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/aws-secrets-manager.json and https://www.anchorterminal.com/api/v1/tools/phase.json\n\n## Other comparisons with AWS Secrets Manager or Phase\n\n- [1Password service accounts, SDKs and Environments MCP vs AWS Secrets Manager](https://www.anchorterminal.com/compare/1password-vs-aws-secrets-manager.md)\n- [1Password service accounts, SDKs and Environments MCP vs Phase](https://www.anchorterminal.com/compare/1password-vs-phase.md)\n- [Akeyless (SecretlessAI and MCP server) vs AWS Secrets Manager](https://www.anchorterminal.com/compare/akeyless-vs-aws-secrets-manager.md)\n- [Akeyless (SecretlessAI and MCP server) vs Phase](https://www.anchorterminal.com/compare/akeyless-vs-phase.md)\n- [AWS Secrets Manager vs Azure Key Vault](https://www.anchorterminal.com/compare/aws-secrets-manager-vs-azure-key-vault.md)\n- [AWS Secrets Manager vs Bitwarden Secrets Manager](https://www.anchorterminal.com/compare/aws-secrets-manager-vs-bitwarden-secrets-manager.md)\n- [AWS Secrets Manager vs Doppler](https://www.anchorterminal.com/compare/aws-secrets-manager-vs-doppler.md)\n- [AWS Secrets Manager vs Google Cloud Secret Manager](https://www.anchorterminal.com/compare/aws-secrets-manager-vs-google-secret-manager.md)\n- [AWS Secrets Manager vs HashiCorp Vault + Vault MCP Server](https://www.anchorterminal.com/compare/aws-secrets-manager-vs-hashicorp-vault.md)\n- [AWS Secrets Manager vs Infisical](https://www.anchorterminal.com/compare/aws-secrets-manager-vs-infisical.md)\n- [AWS Secrets Manager vs Keeper Secrets Manager](https://www.anchorterminal.com/compare/aws-secrets-manager-vs-keeper-secrets-manager.md)\n- [AWS Secrets Manager vs Pulumi ESC](https://www.anchorterminal.com/compare/aws-secrets-manager-vs-pulumi-esc.md)\n- [Azure Key Vault vs Phase](https://www.anchorterminal.com/compare/azure-key-vault-vs-phase.md)\n- [Bitwarden Secrets Manager vs Phase](https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-phase.md)\n- [Doppler vs Phase](https://www.anchorterminal.com/compare/doppler-vs-phase.md)\n- [Google Cloud Secret Manager vs Phase](https://www.anchorterminal.com/compare/google-secret-manager-vs-phase.md)\n- [HashiCorp Vault + Vault MCP Server vs Phase](https://www.anchorterminal.com/compare/hashicorp-vault-vs-phase.md)\n- [Infisical vs Phase](https://www.anchorterminal.com/compare/infisical-vs-phase.md)\n- [Keeper Secrets Manager vs Phase](https://www.anchorterminal.com/compare/keeper-secrets-manager-vs-phase.md)\n- [Phase vs Pulumi ESC](https://www.anchorterminal.com/compare/phase-vs-pulumi-esc.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-08", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "AWS Secrets Manager vs Phase", "url": "" } ], "description": "AWS Secrets Manager scores 77.7 (BB) on agent readiness against Phase's 68 (B), and leads in 5 of 7 scored categories. Phase leads on reliability and maintenance \u0026 community. Both do secrets store. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "AWS Secrets Manager BB 77.7", "Phase B 68", "scores" ], "h1": "AWS Secrets Manager vs Phase", "image": "https://www.anchorterminal.com/assets/og/compare-aws-secrets-manager-vs-phase.png", "path": "/compare/aws-secrets-manager-vs-phase", "published": "2026-10-01", "section": "tools", "title": "AWS Secrets Manager vs Phase for AI agents, BB 77.7 vs B 68", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-phase" }, "tokens": { "markdown": 2500, "slim": 680 }, "version": 1 }