nowfound

AI · alternatives · 2026

24 alternatives to I built an open source computer-use SDK enabling agents to authenticate

over this weekend myself and two of my friends took part in a hackathon and built this side-project. we have been diving into computer-use recently and developed an sdk to make it easy to implement for devs like us. one feature we were missing though, was the agent being able to log into services. anthropic understandably blocks this capability with their guardrails, and you wouldn't want your credentials to end up in any model context anyways. so we added a keychain service to the vm that the agent is using. it was built using the pass cli (https://www.passwordstore.org/).…

This open-source SDK enables developers to build AI agents capable of computer automation with secure authentication. Created during a hackathon, it solves the problem of agents needing to log into services by adding a… Below are 24 products that do a similar job, ranked by how close each is in meaning and then by launch-day votes. Prices are shown for the 1 we have checked on their own sites, 1 of them free or with a free tier.

  1. 1

    Hi HN — I’m a heavy OpenClaw user and, like many others, I’ve been thinking about how to give these new “unleashed” agents secure access to my accounts. Agents need API access to be useful. But API keys are long-lived secrets. And agents are not secure environments. So I built something for myself that quickly turned into a product: keychains.dev. The idea is simple: agents never see raw credentials. With Keychains.dev: • Agents make API calls via a drop-in replacement for curl or JavaScript’s fetch() • They use template variable names instead of embedding credentials • The request is…

    Feb 2026 · keychains.dev · its alternatives →

  2. 2
    Latchkey▲122

    Hi HN, At Imbue, we’ve been following the rapid developments in the agent landscape and noticed that the way agents interact with third-party services on users’ behalf often leaves a lot to be desired. Integrations are ad hoc, complicated, context-heavy, and either unfriendly to non-technical users or tied to a lock-in of some sort. We‘re experimenting with a command-line tool, Latchkey, that could be used by local agents targeted at non-technical users while avoiding remote intermediaries. As far as we know, this is the only existing approach at the intersection of these two goals. Core…

    Mar 2026 · github.com · its alternatives →

  3. 3
    AgentAuth▲462

    Connect your AI Agents with your Accounts

    2024 · its alternatives →

  4. 4
    DCP▲104

    Give your AI agents encrypted permission and keys

    May 2026 · dcpagent.com · its alternatives →

  5. 5
    Buda▲197

    Run a full AI agent team in the cloud — no hardware, no setup. Persistent memory, browser automation, parallel agents. The OpenClaw alternative built for teams. Start free.

    May 2026 · buda.im · its alternatives →

  6. 6

    OpenAgents - The collaboration OS for AI agents. Contribute to openagents-org/openagents development by creating an account on GitHub.

    Apr 2026 · open-agents.dev · its alternatives →

  7. 7

    We built the Kontext CLI because AI coding agents need access to GitHub, Stripe, databases, and dozens of other services — and right now most teams handle this by copy-pasting long-lived API keys into .env files, or the actual chat interface, whilst hoping for the best. The problem isn't just secret sprawl. It's that there's no lineage of access. You don't know which developer launched which agent, what it accessed, or whether it should have been allowed to. The moment you hand raw credentials to a process, you've lost the ability to enforce policy, audit access, or rotate without pain. The…

    Apr 2026 · github.com · its alternatives →

  8. 8
    Cred▲97

    OAuth credential delegation for AI agents

    Apr 2026 · cred.ninja · its alternatives →

  9. 9

    Hi HN, I’m the creator of Cordum. I’ve been working in DevOps and infrastructure for years (currently in the fintech/security space), and as I started playing with AI agents, I noticed a scary pattern. Most "safety" mechanisms rely on system prompts ("Please don't do X") or flimsy Python logic inside the agent itself. If we treat agents as autonomous employees, giving them root access and hoping they listen to instructions felt insane to me. I wanted a way to enforce hard constraints that the LLM cannot override, no matter how "jailbroken" it gets. So I built Cordum. It’s an open-source…

    Jan 2026 · github.com · its alternatives →

  10. 10

    Build & scale AI \ agents as microservices with IAM

    Dec 2025 · agentfield.ai · its alternatives →

  11. 11

    Hey HN, A few months ago, I tried to automate some of my work with the popular AI agent OpenClaw, and then I quickly realized how difficult it is to get it to work with APIs and third-party services securely, which is essential for a lot of work-related tasks. Then I realized OpenClaw is more of a personal assistant and it was not designed to get actual work done as a coworker. So I started to build Valmis, an alternative to OpenClaw that works with more than 100 apps and services, with security being the priority. Valmis addresses the security issue by designing a proxy system: dockerized…

    Jul 2026 · github.com · its alternatives →

  12. 12

    GitHub: https://github.com/ClioAI/kw-sdk Most AI agent frameworks target code. Write code, run tests, fix errors, repeat. That works because code has a natural verification signal. It works or it doesn't. This SDK treats knowledge work like an engineering problem: Task → Brief → Rubric (hidden from executor) → Work → Verify → Fail? → Retry → Pass → Submit The orchestrator coordinates subagents, web search, code execution, and file I/O. then checks its own work against criteria it can't game (the rubric is generated in a separate call and the executor never sees it…

    Feb 2026 · github.com · its alternatives →

  13. 13

    🧑‍🚀 Authentication and authorization infrastructure for SaaS and AI apps, built on OIDC and OAuth 2.1 with multi-tenancy, SSO, and RBAC. - Release v1.0.0-beta.9 · logto-io/logto

    2022 · github.com · its alternatives →

  14. 14

    Hi HN, I built Agent Passport, an open-source identity verification layer for AI agents. Think "Sign in with Google, but for Agents." The problem: AI agents are everywhere now (OpenClaw has 180K+ GitHub stars, Moltbook had 2.3M agent accounts), but there's no standard way for agents to prove their identity. Malicious agents can impersonate others, and skill/plugin marketplaces have no auth layer. Cisco's security team already found data exfiltration in third-party agent skills. Agent Passport solves this with: - Ed25519 challenge-response authentication (private keys never leave the…

    Feb 2026 · agent-passport-red.vercel.app · its alternatives →

  15. 15

    We build runtime security for AI agents. The playground started as an internal tool that we used to test our own guardrails. But we kept finding the same types of vulnerabilities because we think about attacks a certain way. At some point you need people who don't think like you. So we open-sourced it. Each challenge is a live agent with real tools and a published system prompt. Whenever a challenge is over, the full winning conversation transcript and guardrail logs get documented publicly. Building the general-purpose agent itself was probably the most fun part. Getting it to reliably use…

    Mar 2026 · github.com · its alternatives →

  16. 16

    A clean, modular SDK for building AI agents with OpenHands V1. - OpenHands/software-agent-sdk

    Dec 2025 · openhands.dev · its alternatives →

  17. 17IS

    Hey HN! For that last 8 months I've been trying to make agents that can hack web applications to find vulnerabilities in them - An AI Security Tester. The system has 29 agents in total, a custom LLM Orchestration framework which works on the task-subtask architecture (old-school but works amazingly for my use case, and is pretty reliable) with custom agent calling mechanism. No Auo-Gen, Langchain and Crew AI - Everything custom built for pentesting. Each test runs in an isolated Kali linux environment (on AWS Fargate), where the agents have full access to the environment to undertake any…

    2025 · its alternatives →

  18. 18KD

    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 · its alternatives →

  19. 19YA

    After adding "Human" as a LLM provider to OpenCode a few months ago as a joke, it turns-out that acting as a LLM is quite painful. But it was surprisingly useful for understanding real agent harnesses dev. So I thought I wouldn't leave anyone out! I made a small oss game - You Are An Agent - youareanagent.app - to share in the (useful?) frustration It's a bit ridiculous. To tell you about some entirely necessary features, we've got: - A full WASM arch-linux vm that runs in your browser for the agent coding level - A bad desktop simulation with a beautiful excel simulation for our computer…

    Feb 2026 · youareanagent.app · its alternatives →

  20. 20

    I’ve been experimenting with AI agents lately, and one problem kept coming up: they either get a raw API key with full access or nothing at all. That’s risky, especially if you’re testing agents that can make arbitrary calls. So I hacked together a tiny package called Kage Keys - https://github.com/kagehq/keys It lets you wrap agent actions with scoped, short-lived tokens instead of handing over your real API keys. Example: ```js import { withAgentKey, getLogs } from "@kagehq/keys"; async function main() { await withAgentKey("github:repos.read", async () => {…

    2025 · github.com · its alternatives →

  21. 21

    TL;DR: we built a framework-agnostic agent runtime that uses gVisor for isolation and runs on k8s. It’s open-source under AGPLv3 Recently we’ve been working on a customer support “AI assistant” - essentially an interactive knowledge base/L1 support but with an option to touch resources that belong to a customer it’s talking to. We found existing tools to be lacking in these aspects: 1. Fully intercepted i/o. We wanted to trace out LLM calls as well as any other networking calls attempted by the harness so that guardrails and audit trails apply to all current and future systems…

    Jul 2026 · github.com · its alternatives →

  22. 22

    We wanted to build a development environment that can make you a better agentic engineer, not a tool that makes money when you waste tokens. A tool where you can swap models between turns, edit the context, and see every agent action. To do it, we had to build our own harness. Free to use. We don't sell inference, so bring your own key. The sore spot is Claude subscriptions. We can't support them because of Anthropic's terms. The app runs on your machine, and your data never touches our servers. We've been building Voidleap Code using Voidleap Code since January. We didn't rush to launch,…

    Aug 2026 · voidleap.com · its alternatives →

  23. 23

    Hi HN. I'm the founder of Phoenix Labs (ex TikTok, Applied AI) and we're open sourcing our internal tooling today which is like a toolchain / meta-harness for CLI agents useful for really scaling eng and creative work. We are a very small team who's building a very ambitious product so we had to find ways to squeeze every ounce of efficiency that we could get our hands on. Harness strengths of different models (Claude, GPTs) and CLI-harnesses (Claude Code, Codex), safe/robust browser integration to speed up UX/QA testing, teams cli to speed up security reviews and parallelize…

    May 2026 · agents-cli.sh · its alternatives →

  24. 24IM

    Hey HN, I’m Chris, a solo dev in Melbourne AU. For the past month I've been spending my after work hours building AgentVisa. I'm both excited (and admittedly nervous) to be sharing it with you all today. I've been spending a lot of time thinking about the future of AI agents and the more I experimented, the more I realized I was building on a fragile foundation. How do we build trust into these systems? How do we know what our agents are doing, and who gave them permission? My long-term vision is to give developers an "Agent Atlas" - a clear map of their agentic workforce, showing where…

    2025 · agentvisa.dev · its alternatives →

Also compare

Ranked by how close each launch is in meaning, then by votes. Prices were read from each product’s own site when checked and can change. Refine with your own description →