OneCLI – Vault for AI Agents in Rust

We built OneCLI because AI agents are being given raw API keys. And it's going about as well as you'd expect. We figured the answer isn't "don't give agents access," it's "give them access without giving them secrets."OneCLI is an open-source gateway that sits between your AI agents and the services they call. You store your real credentials once in OneCLI's encrypted vault, and give your agents placeholder keys. When an agent makes an HTTP call through the proxy, OneCLI matches the request by host/path, verifies the agent should have access, swaps the placeholder for the real credential, and forwards the request. The agent never touches the actual secret. It just uses CLI or MCP tools as normal.Try it in one line: docker run --pull always -p 10254:10254 -p 10255:10255 -v onecli-data:/app/data ghcr.io/onecli/onecliThe proxy is written in Rust, the dashboard is Next.js, and secrets are AES-256-GCM encrypted at rest. Everything runs in a single Docker container with an embedded Postgres (PGlite), no external dependencies. Works with any agent framework (OpenClaw, NanoClaw, IronClaw, or anything that can set an HTTPS_PROXY).We started with what felt most urgent: agents shouldn't be holding raw credentials. The next layer is access policies and audit, defining what each agent can call, logging everything, and requiring human approval before sensitive actions go through.It's Apache-2.0 licensed. We'd love feedback on the approach, and we're especially curious how people are handling agent auth today.GitHub: https://github.com/onecli/onecli Site: https://onecli.sh

Hacker NewsToolAISource
0Sign in to voteCopy link

FL score

62

out of 100

Verdict

VALIDATE

high confidence

Competition

12

competitors found, emerging market, funded players

Trend

No signal yet

A Rust-based open-source vault and proxy for AI agents to securely manage API keys, addressing a critical pain point in a crowded, well-funded market.

The pain

AI agents are being given raw API keys, leading to severe security vulnerabilities like prompt injection, data breaches, and lack of audit trails. Traditional secrets managers are insufficient as they leave credentials in agent memory.

The gap

While traditional secrets managers fail, the market is crowded with funded enterprise solutions (Oasis Security, Akeyless, CyberArk, 1Password) and similar open-source proxies (Runloop Agent Gateway). OneCLI's gap is in offering a self-contained, Rust-based, open-source proxy solution specifically for AI agent secrets, but it lacks a clear unique unserved audience with evidence.

Build angle

Develop OneCLI as an open-source gateway in Rust that securely proxies AI agent requests, swapping placeholder keys for real credentials. Focus on ease of deployment (single Docker container) and robust security, then explore commercial offerings (e.g., enterprise features, managed service).

Strengths

  • Addresses a critical and urgent security problem for AI agents.
  • The proxy-based solution directly tackles the vulnerability of secrets in agent memory (prompt injection).
  • Already built and open-source MVP, demonstrating technical feasibility.
  • High market growth potential due to increasing AI agent adoption.
  • Self-contained, minimal dependencies, and built in Rust for performance/security.

Risks

  • Highly crowded market with multiple well-funded competitors offering enterprise-grade solutions.
  • Lack of a clear, proven monetization model for the open-source project.
  • Competition from similar open-source proxy tools (e.g., Runloop Agent Gateway).
  • Enterprise clients may prefer commercially backed and supported security solutions over an open-source project.
  • The effort required for ongoing development, maintenance, and competitive feature parity might be too high for a solo builder.

Next steps

  1. **Define and validate a specific monetization strategy**: Explore enterprise features, managed service, or support contracts for OneCLI.
  2. **Identify a hyper-niche paying audience**: Instead of broadly targeting 'AI agents,' focus on 'AI agents for X industry' or 'AI agents for Y specific task' where the security pain is exceptionally high and existing solutions are clearly failing/overpriced.
  3. **Gather explicit feedback on willingness to pay**: Conduct interviews with MLOps engineers, security leads, and AI developers in target companies to understand their budget and preferred solution types (commercial vs. open-source for security infrastructure).
  4. **Analyze competitor pricing and features**: Deep dive into how existing funded players differentiate and price, to find a precise commercial gap OneCLI can fill.

Questions about this idea?

FlyBot reads the scoring and gives you a second opinion on “OneCLI – Vault for AI Agents in Rust”.

Open FlyBot