Alternatives
Products that do what Latchkey does
Credential layer for local AI agents
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9LO
Latch is an open-source proxy that sits between AI agents and the tools they use. It intercepts all tool calls and applies security policies in real-time: Safe operations pass through instantly. Risky operations require human approval via dashboard or Telegram. Dangerous operations are blocked completely I built Latch to address the growing security risks of AI agents accessing critical systems. There have been 1,800+ exposed agent gateways discovered in the wild and recent security audits showing multiple vulnerabilities in agent frameworks, so this was motivated by the clear urgent need…
Feb 2026 · latchagent.com
- 10
- 11
Connect Claude Code to your internal systems w/o credentials
Mar 2026
- 12
- 13KD
Every AI agent that does something useful - opening a PR, posting in Slack, updating a ticket - needs to call an API on behalf of a user. That means OAuth. Authorization flows, token storage, refresh logic, per-user credential isolation. Today, most teams solve this with a long-lived API key in an .env file, shared across every user and every session. As everyone in an organization becomes a software engineer - whether they know it or not - you can't expect each of them to roll their own OAuth. Secure credential handling needs to be baked into the infrastructure. The core issue: agents are a…
Mar 2026 · kontext.dev
- 14CS
AI agents are starting to get real access like GitHub tokens, cloud credentials, customer data, deploy permissions. Not coincidentally, the rate of major cybersecurity incidents is rising rapidly. See for yourself: https://epoch.ai/data/cve?view=graph https://genai.owasp.org/resource/state-of-agentic-ai-securit... My friend and I, both AI researchers, are working on fixing this through an open-source project we've just started called Clay Seal. We've started with a simple version of Identity: an open-source way to issue short-lived, verifiable…
Jul 2026 · github.com
- 15AS
MachineAuth is a self-hosted OAuth 2.0 server for authenticating AI agents and machines. What is an AI agent in this context? A software bot (like OpenCLAW, Claude Code, etc.) that makes API calls to access protected resources. Instead of sharing long-lived API keys, your agents can authenticate using OAuth 2.0 Client Credentials and receive short-lived JWT tokens. Why? No more sharing API keys Short-lived tokens (configurable) Easy credential rotation Industry-standard security
Feb 2026 · github.com
- 16IM
May 2026 · github.com
- 17MA
Show HN: SEKSBot – AI agents that can't see your secrets SEKSBot is a fork of OpenClaw where agents have zero access to API keys, tokens, or credentials — ever. The core insight is borrowed from SQL prepared statements: separate the instructions from the sensitive data. Agents write requests using named secret references. A broker intercepts and injects the real credentials at execution time. The agent never sees them. How it works: seksh (our nushell fork) has secure built-in commands (seksh-http, seksh-git) that route through the broker. Agents can make authenticated API calls and git…
Feb 2026 · seksbot.com
- 18TT
Hi everyone, nice to meet you and I am a newcomer of HN. I have made a binary tool Aih that could communicate with Bard, ChatGPT, Claude, and Llama(HuggingChat) from the terminal. https://github.com/Databingo/aih Since CAPTCHA challenges and bots detecting have become increasingly difficult, I've changed my strategy from hacking the APIs to simulating a real browser's action. The tool first takes the logged-in cookies of Google, ChatGPT, Claude, and HuggingChat accounts from the real Chrome browser, then it opens an invisible instance of Chromium for communication, then…
2023 · github.com
- 19OS
Hi HN, Matvey, Ildar, Joey, and Dominik here. If you're building LLM agents that use tools, you're probably worried about prompt injection attacks that can hijack those tools. We were too, and found that solutions like prompt-based filtering or secondary "guard" LLMs can be unreliable. Our thesis is that agent security should be handled at the network level between the agent and the LLM, just like a traditional web application firewall. So we built Archestra Platform: an open-source gateway that acts as a secure proxy for your AI agents. It's designed to be a deterministic firewall against…
Oct 2025 · archestra.ai
- 20
- 21
- 22
- 23GC
Hello HN, we're Andrew and Stephen from Keyboard (https://www.keyboard.dev/). After building AI tools for the past year, we recently made a YouTube video on building MCP servers and realized MCP is a total game-changer. It essentially lets AI do anything by connecting to your apps. But the deeper we dove, the clearer it became that security and privacy were complete afterthoughts. Coming from backgrounds at Okta and Stripe, this made us pretty uncomfortable. We kept seeing the same pattern: every app needs its own MCP server, each storing sensitive tokens, with minimal…
2025 · github.com
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →