nowfound

Alternatives

Products that do what Fullmakt does

Scoped, revocable credentials for AI agents — fully audited

  1. 1
    Cred97

    OAuth credential delegation for AI agents

    Apr 2026

  2. 2

    Give AI agents access to real-time data across 200+ apps

    May 2026

  3. 3

    Give AI access to 6754+ APIs with zero credentials exposed

    Feb 2026

  4. 4
    Latchkey122

    Credential layer for local AI agents

    Mar 2026

  5. 5

    Money movement for AI agents

    Jul 2026

  6. 6
    OpenBox171

    See, verify, and govern every agent action.

    Apr 2026

  7. 7
    0xAudit110

    The security layer for AI agents to scan, fix verify via MCP

    Feb 2026

  8. 8
    Loomal92

    Identity infrastructure for AI agents

    Apr 2026

  9. 9

    One identity layer for your customers, APIs, and agents

    Jul 2026

  10. 10

    Drop-in MCP Security Developers Love and CISOs Trust

    Mar 2026

  11. 11
    Toolport130

    Every tool, one port. One MCP setup for all your AI agents

    29d ago · toolport.app

  12. 12
    DCP104

    Give your AI agents encrypted permission and keys

    May 2026

  13. 13
    CtrlAI104

    Transparent proxy that secures AI agents with guardrails

    Mar 2026

  14. 14AS

    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

  15. 15KD

    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

  16. 16LO

    Hi HN, Martin, Nils, and Jannes here. We are building Legit, an open source version control and collaboration layer for AI agents and AI native applications. You can find the repo here https://github.com/Legit-Control/monorepo and the website here https://legitcontrol.com Over the last years, we worked on multiple developer tools and AI driven products. As soon as we started letting agents modify real files and business critical data, one problem kept showing up. We could not reliably answer what changed, why it changed, or how to safely undo it. Today, most AI…

    Jan 2026

  17. 17LO

    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

  18. 18MA

    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

  19. 19CM

    Here's something I realized: the most AI-native knowledge base isn't a SaaS product with an API. It's a folder of markdown files on your disk. Obsidian stores everything as plain .md files. That means Claude Code (or any AI tool) can grep, read, write, and traverse your entire knowledge base with zero setup. No API keys. No OAuth. No middleware. Just local file I/O. The only missing piece was sync. I wanted my vault on iPhone (iCloud), on Mac (local), and on GitHub (backup + version history) — without paying $4/mo for Obsidian Sync. cc-md is ~400 lines of bash. iCloud handles Apple…

    Feb 2026 · github.com

  20. 20AL

    AGENTS.lock keeps AI agent skills, instructions, and MCP servers in sync across Claude, Codex, Gemini, and Copilot CLIs using a single TOML lockfile as the source of truth. Instead of manually copying skills and configs between tools, you declare everything once in AGENTS.lock and run `al sync`. GitHub: https://github.com/luml-ai/AGENTS.lock

    Jan 2026 · github.com

  21. 21VA

    Hi all, Gorkem here. I started VerifyWise [1] to make AI governance less painful. Today, we’re launching our open-source platform to help teams take control of their AI compliance process. VerifyWise helps organizations navigate AI governance by providing audit readiness, risk registers, model fairness checks, and compliance documentation. Those are all built into a single platform you can self-host. We’ve been quietly building VerifyWise for a while, and we’re now at a place where it’s ready for more teams to try. Since we started, we've: - Released our core platform on GitHub:…

    2025 · verifywise.ai

  22. 22CS

    We've been building with AI tools and noticed there wasn't a good way to manage MCP servers across a team or see what's actually flowing to LLM providers. Who's running what? Which tools are approved? What data is going where or whats shared on AI websites? So we built CyberCage (). What it does: MCP Management — Auto or manual discovery of MCP servers, with approval workflows. Manage allowed MCP servers org-wide (down to individual tools). Secure MCP catalog (integrates with GitHub's MCP Catalog). Operations — Manage allowed AI applications org-wide. Full audit logs (Splunk integration…

    Dec 2025 · cybercage.io

  23. 23OS

    We’re building an open-source tool that makes it easy to expose secure, LLM-optimized APIs on top of your structured data—without manually designing endpoints or worrying about compliance. AI agents and LLM-powered applications need structured access to data, but traditional APIs and databases weren’t built with AI workloads in mind. Our tool automatically generates APIs that: - Filter out PII & sensitive data to comply with GDPR, CPRA, SOC 2, and other regulations. - Provide traceability & auditing, so AI apps aren’t black boxes, and security teams stay in control. - Optimize for AI…

    2025 · github.com

  24. 24

    Give AI agents your company data. Only what they can see.

    3d ago · warehousd.com

Ranked by how close each launch is in meaning, then by votes. Refine with a description →