{ "data": { "a": { "slug": "azure-key-vault", "name": "Azure Key Vault", "vendor": "Microsoft Corporation", "vendorUrl": "https://azure.microsoft.com/en-us/products/key-vault", "kind": "http-api", "category": "secrets", "summary": "Microsoft Azure's managed store for secrets, encryption keys and TLS certificates. Applications read secrets over a REST API or the Azure SDKs and CLI, signing in with Microsoft Entra ID and authorised by Azure role assignments.", "url": "https://www.anchorterminal.com/tools/azure-key-vault", "markdownUrl": "https://www.anchorterminal.com/tools/azure-key-vault.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/azure-key-vault.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/azure-key-vault.json", "repo": "https://github.com/Azure/azure-rest-api-specs", "license": "Proprietary service under Microsoft's Product Terms. The Azure SDK client libraries are MIT", "transports": [ "http" ], "remoteUrl": "https://\u003cvault-name\u003e.vault.azure.net", "packages": [ { "registry": "pypi", "name": "azure-keyvault-secrets" }, { "registry": "npm", "name": "@azure/keyvault-secrets" }, { "registry": "go", "name": "github.com/Azure/azure-sdk-for-go/sdk/security/keyvault/azsecrets" } ], "auth": "oauth", "authNotes": "Every data plane call carries a Microsoft Entra ID OAuth 2.0 bearer token for the scope https://vault.azure.net/.default. There are no API keys. A workload on Azure uses a managed identity, and anything else uses a service principal registered in the vault's Entra tenant. Access is self-serve inside an Azure subscription. An owner assigns a role such as Key Vault Secrets User (read secret contents) or Key Vault Secrets Officer at subscription, resource group, vault or single-secret scope. Legacy vault access policies still work, and Microsoft's guidance says not to use them for critical data (https://learn.microsoft.com/en-us/azure/key-vault/general/authentication, https://learn.microsoft.com/en-us/azure/key-vault/general/rbac-guide).", "pricing": "usage", "pricingNotes": "$0.03 per 10,000 operations on secrets in both the Standard and Premium tiers in East US, with no charge per stored secret. Renewal of a managed storage account key is metered at $1, and a certificate renewal request at $3. The pricing page draws its numbers by script, so these come from the Azure Retail Prices API (https://prices.azure.com/api/retail/prices?$filter=serviceName%20eq%20%27Key%20Vault%27%20and%20armRegionName%20eq%20%27eastus%27). No free allowance for Key Vault was found on the free services page. A new Azure account gets $200 of credit for 30 days and needs a phone number and a credit or debit card (https://azure.microsoft.com/en-us/pricing/purchase-options/azure-account).", "priceSummary": "$0.003 / 1k calls", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the Key Vault docs, the REST reference or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 2598246, "pypiWeekly": 9507749, "asOf": "2026-10-08" }, "docsUrl": "https://learn.microsoft.com/en-us/azure/key-vault/", "openapi": "https://raw.githubusercontent.com/Azure/azure-rest-api-specs/main/specification/keyvault/data-plane/Secrets/stable/2025-07-01/secrets.json", "capabilities": [ "secrets.store", "secrets.machine-identity", "secrets.audit", "secrets.rotate", "infra.azure" ], "tags": [ "hosted", "closed-source", "usage-priced", "card-required", "openapi", "oauth", "python", "typescript", "go", "dotnet", "java", "enterprise", "sla", "eu" ], "lastRelease": "2026-10-02", "graded": true, "anchor": { "graded": true, "score": 74.7, "grade": "BB", "agentReady": true, "rank": 60, "ranked": true, "rankOf": 722, "categoryRank": 4, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 75, "maintenance": 80, "payments": 20, "reliability": 87, "schema": 85, "security": 86, "transparency": 77 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "Access runs on Microsoft Entra ID tokens and Azure roles that can be scoped to one secret, with soft delete, a 99.99 per cent SLA and a public OpenAPI contract. Secret rotation needs an Event Grid trigger and a function the owner writes, audit logging is off until enabled, and an Azure subscription needs a person and a payment card.", "bestFor": "Agents and runtimes already on Azure, where a managed identity reads a secret with no stored credential.", "strengths": [ "No API keys. Every call carries a Microsoft Entra ID bearer token, and managed identities remove stored credentials for workloads on Azure", "Azure roles can be assigned on a vault or one secret, with Key Vault Secrets User limited to reading secret contents", "Deleted secrets stay recoverable for 7 to 90 days, and purging needs a separate permission", "SLA of 99.99 per cent uptime for read transactions, with 10 and 25 per cent credits, in the 1 October 2026 SLA document", "Public OpenAPI 2.0 contract for the 12 secrets operations, and Learn pages returned as Markdown on request" ], "weaknesses": [ "No managed rotation for secrets. Key Vault raises a near-expiry event 30 days ahead and the owner's Azure Function does the rotation", "Audit logging is off until a diagnostic setting sends AuditEvent logs to a storage account, event hub or Azure Monitor", "Set Secret has no idempotency key, so a retried write adds another version", "Listing returns at most 25 secrets a page with no name or tag filter", "No free allowance for Key Vault was found, and an Azure account needs a phone number and a credit or debit card" ], "agentNotes": [ "Request a token for the resource https://vault.azure.net and send it as a Bearer header. Every call must carry `api-version`, such as 2025-07-01, because there is no default", "Ask for the Key Vault Secrets User role on the vault or the single secret. Key Vault Reader returns metadata only, not values", "Cache secret values in memory. A vault allows 4,000 reads and 300 secret creations per 10 seconds, and a subscription five times that", "On 429 wait 1, 2, 4, 8 then 16 seconds. Throttled requests do not count against the limit", "Don't retry Set Secret blindly. Each successful call creates a new version of the secret" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 74.7 } ], "editorialScores": { "ergonomics": 75, "maintenance": 80, "payments": 20, "reliability": 87, "schema": 85, "security": 86, "transparency": 67 }, "provenanceScore": 86 }, "connect": { "install": "pip install azure-keyvault-secrets azure-identity # or: npm i @azure/keyvault-secrets @azure/identity", "http": "GET https://\u003cvault-name\u003e.vault.azure.net/secrets/\u003csecret-name\u003e?api-version=2025-07-01\nAuthorization: Bearer \u003cEntra ID access token for https://vault.azure.net\u003e" }, "letme": { "capability": "https://letme.dev/secrets.store", "tool": "https://letme.dev/azure-key-vault" }, "sameCompany": [ "azure-foundry-fine-tuning", "azure-ai-content-safety", "azure-speech-to-text", "azure-text-to-speech", "microsoft-agent-framework", "microsoft-execution-containers", "microsoft-entra-agent-id", "azure-devops-mcp", "microsoft-learn-mcp", "playwright-mcp", "azure-mcp", "azure-maps", "azure-translator", "microsoft-graph-calendar", "microsoft-teams", "dynamics-365-sales", "power-automate", "microsoft-advertising-api", "microsoft-excel-graph", "outlook-mail-graph" ], "area": "agent-runtime", "unitPrices": [ { "item": "Secrets operations", "unit": "1k-calls", "usd": 0.003, "note": "$0.03 per 10,000 operations, East US, Standard and Premium" }, { "item": "Certificate renewal request", "unit": "tx", "usd": 3, "note": "Per renewal request" } ], "provenance": { "legalEntity": "Microsoft Corporation", "domain": "microsoft.com", "domainRegistered": "1991-05-02", "domainNote": "Vaults answer at \u003cvault-name\u003e.vault.azure.net and management calls at management.azure.com, both Microsoft domains. Docs are on learn.microsoft.com.", "endpointOnVendorDomain": true, "terms": "https://www.microsoft.com/licensing/terms/product/ForOnlineServices/all", "privacy": "https://www.microsoft.com/en-us/privacy/privacystatement", "statusPage": "https://azure.status.microsoft/en-us/status", "changelog": "https://learn.microsoft.com/en-us/azure/key-vault/general/whats-new", "securityTxt": "expired", "checked": "2026-10-08", "notes": [ "The Product Terms for Online Services cover Microsoft Azure, point to the Data Protection Addendum for customer data and to aka.ms/CSLA for the SLA. The page showed no effective date when read on 8 October 2026.", "Self-serve Azure accounts also accept the Microsoft Online Subscription Agreement (last updated March 2019, Microsoft Corporation, Washington law) at https://azure.microsoft.com/en-us/support/legal/subscription-agreement/, which incorporates the Online Services Terms and the SLAs.", "The privacy statement (last updated September 2026) names Microsoft Corporation, One Microsoft Way, Redmond, Washington 98052, and Microsoft Ireland Operations Limited in Dublin. It lists Microsoft Azure among the enterprise online services and says the customer's agreement controls where the two conflict.", "https://www.microsoft.com/.well-known/security.txt shows Expires 2026-09-23T16:00:00.000Z. It points to the MSRC researcher portal, the bounty policy and the coordinated disclosure policy.", "RDAP for microsoft.com gives a registration date of 1991-05-02.", "The what's new page is dated 8 September 2026 and its newest entry is March 2026." ], "score": 86 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/azure-key-vault.json", "live": { "slug": "azure-key-vault", "probe": { "target": "https://\u003cvault-name\u003e.vault.azure.net", "method": "get", "lastAt": "2026-10-08T21:12:04.826805764Z", "lastOk": false, "lastStatus": 0, "lastMs": 0, "lastNote": "DNS lookup failed", "authRequired": false, "uptime24h": 0, "uptime30d": 0, "p50ms24h": 0, "p95ms24h": 0, "samples24h": 41, "samples30d": 41, "days": [ { "date": "2026-10-08", "probes": 41, "ok": 0 } ], "outages": [ { "start": "2026-10-08T17:31:30.488017607Z", "end": "0001-01-01T00:00:00Z", "note": "DNS lookup failed" } ] }, "pages": [ { "url": "https://learn.microsoft.com/en-us/azure/key-vault/general/whats-new", "kind": "changelog", "status": 200, "checkedAt": "2026-10-08T18:21:34.108322139Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "8d3dc460aaab" }, { "url": "https://azure.microsoft.com/en-us/pricing/purchase-options/azure-account", "kind": "pricing", "status": 200, "checkedAt": "2026-10-08T18:15:36.079506243Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "7a404bea65bc" }, { "url": "https://prices.azure.com/api/retail/prices?$filter=serviceName%20eq%20%27Key%20Vault%27%20and%20armRegionName%20eq%20%27eastus%27", "kind": "pricing", "status": 200, "checkedAt": "2026-10-08T18:23:22.816237311Z", "changedAt": "0001-01-01T00:00:00Z" } ], "updatedAt": "2026-10-08T21:12:04.826805764Z" } }, "answer": "Azure Key Vault scores 74.7 (BB) on agent readiness against Keeper Secrets Manager's 69.4 (B), and leads in 3 of 7 scored categories. Keeper Secrets Manager leads on maintenance \u0026 community.", "b": { "slug": "keeper-secrets-manager", "name": "Keeper Secrets Manager", "vendor": "Keeper Security, Inc.", "vendorUrl": "https://www.keepersecurity.com/secrets-manager.html", "kind": "http-api", "category": "secrets", "summary": "Keeper Secrets Manager is a cloud vault for infrastructure secrets, sold as an add-on to Keeper Security's business password manager. Applications read secrets through SDKs in seven languages, the `ksm` CLI or a local MCP server, decrypting on the client.", "url": "https://www.anchorterminal.com/tools/keeper-secrets-manager", "markdownUrl": "https://www.anchorterminal.com/tools/keeper-secrets-manager.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/keeper-secrets-manager.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/keeper-secrets-manager.json", "repo": "https://github.com/Keeper-Security/secrets-manager", "license": "Proprietary service under Keeper's SaaS Terms of Use. The SDKs, CLI, MCP server and agent kit on GitHub are MIT", "transports": [ "http", "stdio" ], "packages": [ { "registry": "pypi", "name": "keeper-secrets-manager-core" }, { "registry": "pypi", "name": "keeper-secrets-manager-cli" }, { "registry": "npm", "name": "@keeper-security/secrets-manager-core" } ], "auth": "api-key", "authNotes": "Access is granted by a person. A vault user whose role allows it creates a Secrets Manager application, shares folders or records with it, and adds a client device, which yields a one-time access token or a Base64 configuration. The client redeems the token once, registers its own ECC public key and signs every later request with the private key, so no bearer secret is reused. Devices are IP-locked by default, can be given an access expiry and are revoked individually.", "pricing": "paid", "pricingNotes": "Secrets Manager is an add-on to Keeper's business password manager plans, licensed per user per year, and included with KeeperPAM. The add-ons page shows Custom Pricing and Request a Quote for it, so there is no public figure. A 14-day business trial needs no credit card and can enable Secrets Manager, so an agent's owner can start without a contract. Base plan prices are drawn by script and were blank to our reader (https://www.keepersecurity.com/pricing/business-add-ons/, https://www.keepersecurity.com/trial/keeper-free-trial/, checked 2026-10-08).", "priceSummary": "Paid", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the Secrets Manager docs, the SDK repository or the pricing pages (checked 2026-10-08).", "endpoints": [] }, "toolCount": 19, "popularity": { "githubStars": 117, "npmWeekly": 52332, "pypiWeekly": 45154, "asOf": "2026-10-08" }, "docsUrl": "https://docs.keeper.io/en/keeperpam/secrets-manager/overview", "llmsTxt": "https://docs.keeper.io/llms.txt", "capabilities": [ "secrets.store", "secrets.machine-identity", "secrets.audit", "secrets.rotate" ], "tags": [ "hosted", "enterprise", "zero-knowledge", "mcp", "cli", "python", "javascript", "java", "go", "dotnet", "ruby", "rust", "llms-txt", "sales-led", "status-page", "bug-bounty", "soc2", "fedramp" ], "lastRelease": "2026-10-06", "graded": true, "anchor": { "graded": true, "score": 69.4, "grade": "B", "agentReady": false, "rank": 159, "ranked": true, "rankOf": 722, "categoryRank": 9, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 63, "maintenance": 92, "payments": 20, "reliability": 76, "schema": 71, "security": 86, "transparency": 78 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "Each client device signs requests with its own key, is locked to an IP address by default and can be revoked alone, and secrets decrypt only on the client. The add-on has no public price, no request limits were found in the reviewed documentation, and a person must create the application and device in the vault.", "bestFor": "Companies already on Keeper's business vault that want per-device machine identities with client-side decryption and an official MCP server.", "strengths": [ "Each device registers its own ECC key from a one-time token, is IP-locked by default and can be revoked alone", "Secrets decrypt on the client. Keeper's cloud stores and sends ciphertext only, per the encryption model page", "An application sees only the shared folders and records assigned to it, read-only unless shared as editable", "Official MIT MCP server with 19 typed tools, masked values by default and confirmation for writes, deletes and unmasking", "SDKs for Python, Java, JavaScript, .NET, Go, Ruby and Rust in one MIT repository, with 5 tagged releases since 15 September 2026" ], "weaknesses": [ "Secrets Manager is priced by quote. The add-ons page shows Custom Pricing and Request a Quote", "No request limits were found in the reviewed documentation. Throttling arrives as HTTP 403 with `{\"error\":\"throttled\"}`", "No OpenAPI or documented raw HTTP use for `/api/rest/sm/v1`. The SDKs are the only supported route", "The Node MCP guide links a GitHub repository that returned 404 on 8 October 2026", "Rotation needs a KeeperPAM licence and a Keeper Gateway, and access events are read in the separately sold reporting module" ], "agentNotes": [ "Ask the vault owner for a new device on an application that holds only the folders the task needs. Use the Base64 configuration, not the first one-time token", "Run commands under `ksm exec` so secrets arrive as environment variables and stay out of the model's context", "Expect HTTP 403 with `{\"error\":\"throttled\"}` under load. The Python SDK retries five times from 11 seconds, so allow for long waits", "A device is locked to the IP address it first connects from unless it was created with `--unlock-ip`. Check this before running from a dynamic address", "Leave `--auto-approve` off on the MCP server. It removes confirmation for deletes and for unmasking values" ], "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": 69.4 } ], "editorialScores": { "ergonomics": 63, "maintenance": 92, "payments": 20, "reliability": 76, "schema": 71, "security": 86, "transparency": 58 }, "provenanceScore": 98 }, "connect": { "install": "pip3 install keeper-secrets-manager-cli # or: pip3 install keeper-secrets-manager-core, npm install @keeper-security/secrets-manager-core", "http": "ksm profile init XX:XXXX # one-time access token from the vault\nksm secret list # values decrypt on the client, so plain curl can't read them", "claudeCode": "/plugin marketplace add Keeper-Security/keeper-agent-kit\n/plugin install keeper-secrets@keeper-security", "config": { "mcpServers": { "ksm": { "args": [ "run", "-i", "--rm", "-e", "KSM_CONFIG_BASE64=YOUR_BASE64_CONFIG_STRING_HERE", "keeper/keeper-mcp-server:latest" ], "command": "docker" } } } }, "letme": { "capability": "https://letme.dev/secrets.store", "tool": "https://letme.dev/keeper-secrets-manager" }, "area": "agent-runtime", "provenance": { "legalEntity": "Keeper Security, Inc.", "domain": "keepersecurity.com", "domainRegistered": "2007-04-12", "endpointOnVendorDomain": true, "terms": "https://www.keepersecurity.com/legal/terms-of-use/#saas-terms", "privacy": "https://www.keepersecurity.com/legal/terms-of-use/?s=privacy", "statusPage": "https://statuspage.keeper.io", "changelog": "https://docs.keeper.io/release-notes/enterprise/keeper-secrets-manager/2026", "securityTxt": "valid", "checked": "2026-10-08", "notes": [ "Keeper publishes its website terms, SaaS Terms of Use, partner terms, privacy policy and Service Level Objectives as sections of one page at www.keepersecurity.com/legal/terms-of-use/. The SaaS section governs the service and the `?s=privacy` view is the privacy policy. The old `/termsofuse.html` and `/privacypolicy.html` addresses redirect there.", "The SaaS terms name Keeper Security, Inc., 311 W. Monroe Street, Suite 406, Chicago, IL 60606, with Keeper Security EMEA Limited and Keeper Security APAC KK for other regions. The page links legacy terms for the period before 9 March 2026.", "The SaaS terms forbid a customer to perform penetration or load testing on the services, and the website terms prohibit scraping or automated data collection on the website.", "www.keepersecurity.com/.well-known/security.txt answers with a Bugcrowd contact and Expires 2026-12-31T23:59:59Z.", "The SDKs call https://\u003cregion host\u003e/api/rest/sm/v1, where the host is keepersecurity.com, keepersecurity.eu, keepersecurity.com.au, keepersecurity.ca, keepersecurity.jp or govcloud.keepersecurity.us.", "The status page and the docs sit on keeper.io. statuspage.keeper.io is Atlassian Statuspage with a Keeper Secrets Manager component.", "RDAP for keepersecurity.com gives a registration date of 2007-04-12." ], "score": 98 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/keeper-secrets-manager.json", "live": { "slug": "keeper-secrets-manager", "vendorStatus": { "page": "https://statuspage.keeper.io", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-08T21:06:10.265244465Z" }, "updatedAt": "2026-10-08T21:06:10.265244465Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Microsoft Corporation", "b": "Keeper Security, Inc.", "name": "Vendor" }, { "a": "https://\u003cvault-name\u003e.vault.azure.net", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, stdio", "name": "Transports" }, { "a": "OAuth", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Microsoft's Product Terms. The Azure SDK client libraries are MIT", "b": "Proprietary service under Keeper's SaaS Terms of Use. The SDKs, CLI, MCP server and agent kit on GitHub are MIT", "name": "Licence" }, { "a": "none", "b": "19", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-02", "b": "2026-10-06", "name": "Last release" }, { "a": "no date given", "b": "no date given", "name": "Terms last updated" }, { "a": "2026-09-01", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "yes", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "2.6M npm/wk, 9.5M PyPI/wk", "b": "117 stars, 52k npm/wk, 45k PyPI/wk", "name": "Popularity" } ], "faq": [ { "answer": "Azure Key Vault scores 74.7 (BB) on agent readiness against Keeper Secrets Manager's 69.4 (B), and leads in 3 of 7 scored categories. Keeper Secrets Manager leads on maintenance \u0026 community.", "question": "Which is better for AI agents, Azure Key Vault or Keeper Secrets Manager?" }, { "answer": "Azure Key Vault uses an OAuth sign-in. Keeper Secrets Manager needs an API key.", "question": "Do Azure Key Vault and Keeper Secrets Manager need an API key?" }, { "answer": "Azure Key Vault has a hosted endpoint at https://\u003cvault-name\u003e.vault.azure.net. Keeper Secrets Manager runs on your own machine, with no hosted endpoint listed.", "question": "Can an agent call Azure Key Vault and Keeper Secrets Manager without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 87 against 76", "Schema \u0026 documentation, 85 against 71", "Agent ergonomics, 75 against 63" ], "also": [ "Agent-ready, a grade of BB or better", "A hosted endpoint, with nothing to install" ], "goodFor": "Agents and runtimes already on Azure, where a managed identity reads a secret with no stored credential.", "slug": "azure-key-vault", "watchFor": "No managed rotation for secrets. Key Vault raises a near-expiry event 30 days ahead and the owner's Azure Function does the rotation" }, { "aheadOn": [ "Maintenance \u0026 community, 92 against 80" ], "also": [ "Runs on your own machine" ], "goodFor": "Companies already on Keeper's business vault that want per-device machine identities with client-side decryption and an official MCP server.", "slug": "keeper-secrets-manager", "watchFor": "Secrets Manager is priced by quote. The add-ons page shows Custom Pricing and Request a Quote" } ], "job": { "capability": "secrets.store", "name": "Secrets store" }, "others": [ { "json": "https://www.anchorterminal.com/compare/1password-vs-azure-key-vault.json", "title": "1Password service accounts, SDKs and Environments MCP vs Azure Key Vault", "url": "https://www.anchorterminal.com/compare/1password-vs-azure-key-vault" }, { "json": "https://www.anchorterminal.com/compare/1password-vs-keeper-secrets-manager.json", "title": "1Password service accounts, SDKs and Environments MCP vs Keeper Secrets Manager", "url": "https://www.anchorterminal.com/compare/1password-vs-keeper-secrets-manager" }, { "json": "https://www.anchorterminal.com/compare/akeyless-vs-azure-key-vault.json", "title": "Akeyless (SecretlessAI and MCP server) vs Azure Key Vault", "url": "https://www.anchorterminal.com/compare/akeyless-vs-azure-key-vault" }, { "json": "https://www.anchorterminal.com/compare/akeyless-vs-keeper-secrets-manager.json", "title": "Akeyless (SecretlessAI and MCP server) vs Keeper Secrets Manager", "url": "https://www.anchorterminal.com/compare/akeyless-vs-keeper-secrets-manager" }, { "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-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/azure-key-vault-vs-bitwarden-secrets-manager.json", "title": "Azure Key Vault vs Bitwarden Secrets Manager", "url": "https://www.anchorterminal.com/compare/azure-key-vault-vs-bitwarden-secrets-manager" }, { "json": "https://www.anchorterminal.com/compare/azure-key-vault-vs-doppler.json", "title": "Azure Key Vault vs Doppler", "url": "https://www.anchorterminal.com/compare/azure-key-vault-vs-doppler" }, { "json": "https://www.anchorterminal.com/compare/azure-key-vault-vs-google-secret-manager.json", "title": "Azure Key Vault vs Google Cloud Secret Manager", "url": "https://www.anchorterminal.com/compare/azure-key-vault-vs-google-secret-manager" }, { "json": "https://www.anchorterminal.com/compare/azure-key-vault-vs-hashicorp-vault.json", "title": "Azure Key Vault vs HashiCorp Vault + Vault MCP Server", "url": "https://www.anchorterminal.com/compare/azure-key-vault-vs-hashicorp-vault" }, { "json": "https://www.anchorterminal.com/compare/azure-key-vault-vs-infisical.json", "title": "Azure Key Vault vs Infisical", "url": "https://www.anchorterminal.com/compare/azure-key-vault-vs-infisical" }, { "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/azure-key-vault-vs-pulumi-esc.json", "title": "Azure Key Vault vs Pulumi ESC", "url": "https://www.anchorterminal.com/compare/azure-key-vault-vs-pulumi-esc" }, { "json": "https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-keeper-secrets-manager.json", "title": "Bitwarden Secrets Manager vs Keeper Secrets Manager", "url": "https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-keeper-secrets-manager" }, { "json": "https://www.anchorterminal.com/compare/doppler-vs-keeper-secrets-manager.json", "title": "Doppler vs Keeper Secrets Manager", "url": "https://www.anchorterminal.com/compare/doppler-vs-keeper-secrets-manager" }, { "json": "https://www.anchorterminal.com/compare/google-secret-manager-vs-keeper-secrets-manager.json", "title": "Google Cloud Secret Manager vs Keeper Secrets Manager", "url": "https://www.anchorterminal.com/compare/google-secret-manager-vs-keeper-secrets-manager" }, { "json": "https://www.anchorterminal.com/compare/hashicorp-vault-vs-keeper-secrets-manager.json", "title": "HashiCorp Vault + Vault MCP Server vs Keeper Secrets Manager", "url": "https://www.anchorterminal.com/compare/hashicorp-vault-vs-keeper-secrets-manager" }, { "json": "https://www.anchorterminal.com/compare/infisical-vs-keeper-secrets-manager.json", "title": "Infisical vs Keeper Secrets Manager", "url": "https://www.anchorterminal.com/compare/infisical-vs-keeper-secrets-manager" }, { "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/keeper-secrets-manager-vs-pulumi-esc.json", "title": "Keeper Secrets Manager vs Pulumi ESC", "url": "https://www.anchorterminal.com/compare/keeper-secrets-manager-vs-pulumi-esc" } ], "scores": [ { "azure-key-vault": 87, "by": 11, "edge": "azure-key-vault", "keeper-secrets-manager": 76, "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "azure-key-vault": 85, "by": 14, "edge": "azure-key-vault", "keeper-secrets-manager": 71, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "azure-key-vault": 75, "by": 12, "edge": "azure-key-vault", "keeper-secrets-manager": 63, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "azure-key-vault": 86, "by": 0, "edge": "", "keeper-secrets-manager": 86, "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "azure-key-vault": 20, "by": 0, "edge": "", "keeper-secrets-manager": 20, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "azure-key-vault": 80, "by": 12, "edge": "keeper-secrets-manager", "keeper-secrets-manager": 92, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "azure-key-vault": 77, "by": 1, "edge": "keeper-secrets-manager", "keeper-secrets-manager": 78, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Azure Key Vault scores 74.7 (BB) on agent readiness against Keeper Secrets Manager's 69.4 (B), and leads in 3 of 7 scored categories. Keeper Secrets Manager leads on maintenance \u0026 community. Both do secrets store.", "verdicts": { "azure-key-vault": "Access runs on Microsoft Entra ID tokens and Azure roles that can be scoped to one secret, with soft delete, a 99.99 per cent SLA and a public OpenAPI contract. Secret rotation needs an Event Grid trigger and a function the owner writes, audit logging is off until enabled, and an Azure subscription needs a person and a payment card.", "keeper-secrets-manager": "Each client device signs requests with its own key, is locked to an IP address by default and can be revoked alone, and secrets decrypt only on the client. The add-on has no public price, no request limits were found in the reviewed documentation, and a person must create the application and device in the vault." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/azure-key-vault-vs-keeper-secrets-manager", "json": "https://www.anchorterminal.com/compare/azure-key-vault-vs-keeper-secrets-manager.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/azure-key-vault-vs-keeper-secrets-manager.md", "slim": "https://www.anchorterminal.com/compare/azure-key-vault-vs-keeper-secrets-manager.min.md" }, "markdown": "Azure Key Vault scores 74.7 (BB) on agent readiness against Keeper Secrets Manager's 69.4 (B), and leads in 3 of 7 scored categories. Keeper Secrets Manager leads on maintenance \u0026 community. Both do secrets store.\n\n- Azure Key Vault: grade BB, 74.7/100, rank #60 of 722. Markdown https://www.anchorterminal.com/tools/azure-key-vault.md · JSON https://www.anchorterminal.com/api/v1/tools/azure-key-vault.json\n- Keeper Secrets Manager: grade B, 69.4/100, rank #159 of 722. Markdown https://www.anchorterminal.com/tools/keeper-secrets-manager.md · JSON https://www.anchorterminal.com/api/v1/tools/keeper-secrets-manager.json\n\n## Which one, for what\n\n### Azure Key Vault (BB)\n\nGood for: Agents and runtimes already on Azure, where a managed identity reads a secret with no stored credential.\n\nAhead on:\n- Reliability, 87 against 76\n- Schema \u0026 documentation, 85 against 71\n- Agent ergonomics, 75 against 63\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- A hosted endpoint, with nothing to install\n\nWatch for: No managed rotation for secrets. Key Vault raises a near-expiry event 30 days ahead and the owner's Azure Function does the rotation\n\n### Keeper Secrets Manager (B)\n\nGood for: Companies already on Keeper's business vault that want per-device machine identities with client-side decryption and an official MCP server.\n\nAhead on:\n- Maintenance \u0026 community, 92 against 80\n\nAlso in its favour:\n- Runs on your own machine\n\nWatch for: Secrets Manager is priced by quote. The add-ons page shows Custom Pricing and Request a Quote\n\n\n## Score by category\n\n| Category | Weight | Azure Key Vault | Keeper Secrets Manager | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 87 | 76 | Azure Key Vault +11 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 85 | 71 | Azure Key Vault +14 |\n| Agent ergonomics | 13% (16.2 this run) | 75 | 63 | Azure Key Vault +12 |\n| Security \u0026 auth | 14% (17.5 this run) | 86 | 86 | even |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 20 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 80 | 92 | Keeper Secrets Manager +12 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 77 | 78 | Keeper Secrets Manager +1 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **74.7 · BB** | **69.4 · B** | |\n\n## Facts side by side\n\n| Fact | Azure Key Vault | Keeper Secrets Manager |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Microsoft Corporation | Keeper Security, Inc. |\n| Hosted endpoint | `https://\u003cvault-name\u003e.vault.azure.net` | no (local only) |\n| Transports | HTTP | HTTP, stdio |\n| Auth | OAuth | API key |\n| Pricing | Pay per use | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under Microsoft's Product Terms. The Azure SDK client libraries are MIT | Proprietary service under Keeper's SaaS Terms of Use. The SDKs, CLI, MCP server and agent kit on GitHub are MIT |\n| Tools exposed | none | 19 |\n| Read-only variant documented | no | yes |\n| llms.txt | no | yes |\n| Last release | 2026-10-02 | 2026-10-06 |\n| Terms last updated | no date given | no date given |\n| Privacy policy last updated | 2026-09-01 | no date given |\n| Customer content may train models | yes | not found in the text |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | not found in the text | yes |\n| Popularity | 2.6M npm/wk, 9.5M PyPI/wk | 117 stars, 52k npm/wk, 45k PyPI/wk |\n\n## Verdicts\n\n**Azure Key Vault.** Access runs on Microsoft Entra ID tokens and Azure roles that can be scoped to one secret, with soft delete, a 99.99 per cent SLA and a public OpenAPI contract. Secret rotation needs an Event Grid trigger and a function the owner writes, audit logging is off until enabled, and an Azure subscription needs a person and a payment card.\n\n**Keeper Secrets Manager.** Each client device signs requests with its own key, is locked to an IP address by default and can be revoked alone, and secrets decrypt only on the client. The add-on has no public price, no request limits were found in the reviewed documentation, and a person must create the application and device in the vault.\n\n## Before you call either\n\n### Azure Key Vault\n\n1. Request a token for the resource https://vault.azure.net and send it as a Bearer header. Every call must carry `api-version`, such as 2025-07-01, because there is no default\n2. Ask for the Key Vault Secrets User role on the vault or the single secret. Key Vault Reader returns metadata only, not values\n3. Cache secret values in memory. A vault allows 4,000 reads and 300 secret creations per 10 seconds, and a subscription five times that\n4. On 429 wait 1, 2, 4, 8 then 16 seconds. Throttled requests do not count against the limit\n5. Don't retry Set Secret blindly. Each successful call creates a new version of the secret\n\n### Keeper Secrets Manager\n\n1. Ask the vault owner for a new device on an application that holds only the folders the task needs. Use the Base64 configuration, not the first one-time token\n2. Run commands under `ksm exec` so secrets arrive as environment variables and stay out of the model's context\n3. Expect HTTP 403 with `{\"error\":\"throttled\"}` under load. The Python SDK retries five times from 11 seconds, so allow for long waits\n4. A device is locked to the IP address it first connects from unless it was created with `--unlock-ip`. Check this before running from a dynamic address\n5. Leave `--auto-approve` off on the MCP server. It removes confirmation for deletes and for unmasking values\n\n## Questions\n\n### Which is better for AI agents, Azure Key Vault or Keeper Secrets Manager?\n\nAzure Key Vault scores 74.7 (BB) on agent readiness against Keeper Secrets Manager's 69.4 (B), and leads in 3 of 7 scored categories. Keeper Secrets Manager leads on maintenance \u0026 community.\n\n### Do Azure Key Vault and Keeper Secrets Manager need an API key?\n\nAzure Key Vault uses an OAuth sign-in. Keeper Secrets Manager needs an API key.\n\n### Can an agent call Azure Key Vault and Keeper Secrets Manager without installing anything?\n\nAzure Key Vault has a hosted endpoint at https://\u003cvault-name\u003e.vault.azure.net. Keeper Secrets Manager runs on your own machine, with no hosted endpoint listed.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/azure-key-vault-vs-keeper-secrets-manager.json, and with the fewest tokens: https://www.anchorterminal.com/compare/azure-key-vault-vs-keeper-secrets-manager.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"azure-key-vault\", \"b\": \"keeper-secrets-manager\"}`. From a terminal: `anchor compare azure-key-vault keeper-secrets-manager`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/azure-key-vault.json and https://www.anchorterminal.com/api/v1/tools/keeper-secrets-manager.json\n\n## Other comparisons with Azure Key Vault or Keeper Secrets Manager\n\n- [1Password service accounts, SDKs and Environments MCP vs Azure Key Vault](https://www.anchorterminal.com/compare/1password-vs-azure-key-vault.md)\n- [1Password service accounts, SDKs and Environments MCP vs Keeper Secrets Manager](https://www.anchorterminal.com/compare/1password-vs-keeper-secrets-manager.md)\n- [Akeyless (SecretlessAI and MCP server) vs Azure Key Vault](https://www.anchorterminal.com/compare/akeyless-vs-azure-key-vault.md)\n- [Akeyless (SecretlessAI and MCP server) vs Keeper Secrets Manager](https://www.anchorterminal.com/compare/akeyless-vs-keeper-secrets-manager.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 Keeper Secrets Manager](https://www.anchorterminal.com/compare/aws-secrets-manager-vs-keeper-secrets-manager.md)\n- [Azure Key Vault vs Bitwarden Secrets Manager](https://www.anchorterminal.com/compare/azure-key-vault-vs-bitwarden-secrets-manager.md)\n- [Azure Key Vault vs Doppler](https://www.anchorterminal.com/compare/azure-key-vault-vs-doppler.md)\n- [Azure Key Vault vs Google Cloud Secret Manager](https://www.anchorterminal.com/compare/azure-key-vault-vs-google-secret-manager.md)\n- [Azure Key Vault vs HashiCorp Vault + Vault MCP Server](https://www.anchorterminal.com/compare/azure-key-vault-vs-hashicorp-vault.md)\n- [Azure Key Vault vs Infisical](https://www.anchorterminal.com/compare/azure-key-vault-vs-infisical.md)\n- [Azure Key Vault vs Phase](https://www.anchorterminal.com/compare/azure-key-vault-vs-phase.md)\n- [Azure Key Vault vs Pulumi ESC](https://www.anchorterminal.com/compare/azure-key-vault-vs-pulumi-esc.md)\n- [Bitwarden Secrets Manager vs Keeper Secrets Manager](https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-keeper-secrets-manager.md)\n- [Doppler vs Keeper Secrets Manager](https://www.anchorterminal.com/compare/doppler-vs-keeper-secrets-manager.md)\n- [Google Cloud Secret Manager vs Keeper Secrets Manager](https://www.anchorterminal.com/compare/google-secret-manager-vs-keeper-secrets-manager.md)\n- [HashiCorp Vault + Vault MCP Server vs Keeper Secrets Manager](https://www.anchorterminal.com/compare/hashicorp-vault-vs-keeper-secrets-manager.md)\n- [Infisical vs Keeper Secrets Manager](https://www.anchorterminal.com/compare/infisical-vs-keeper-secrets-manager.md)\n- [Keeper Secrets Manager vs Phase](https://www.anchorterminal.com/compare/keeper-secrets-manager-vs-phase.md)\n- [Keeper Secrets Manager vs Pulumi ESC](https://www.anchorterminal.com/compare/keeper-secrets-manager-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": "Azure Key Vault vs Keeper Secrets Manager", "url": "" } ], "description": "Azure Key Vault scores 74.7 (BB) on agent readiness against Keeper Secrets Manager's 69.4 (B), and leads in 3 of 7 scored categories. Keeper Secrets Manager leads on maintenance \u0026 community. Both do secrets store. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Azure Key Vault BB 74.7", "Keeper Secrets Manager B 69.4", "scores" ], "h1": "Azure Key Vault vs Keeper Secrets Manager", "image": "https://www.anchorterminal.com/assets/og/compare-azure-key-vault-vs-keeper-secrets-manager.png", "path": "/compare/azure-key-vault-vs-keeper-secrets-manager", "published": "2026-10-01", "section": "tools", "title": "Azure Key Vault vs Keeper Secrets Manager for AI agents", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/azure-key-vault-vs-keeper-secrets-manager" }, "tokens": { "markdown": 2600, "slim": 730 }, "version": 1 }