Alternatives
Products that do what Agentpanel – Universal LLM API Written in Rust does
Agentpanel is an observability platform for optimizing the control flow, performance, token usage, and correctness of LLM/AI agents! Built-in @rustlang, the first release of Agent Panel currently features an AI gateway that provides seamless access to 100+ LLMs across 20+ platforms, including OpenAI GPT-4o, Gemini 1.5 Pro latest, AnthropicAI Claude 3.5, MistralAI, Cohere, Groq,Perplexity AI, and more.
- 1

- 2

- 3

Get 10x speed for building automations. AI copilot is here
2025
- 4

- 5

- 6

- 7

- 8

- 9
- 10
- 11

- 12

- 13WI
At Laminar (https://github.com/lmnr-ai/lmnr) we're building open source AI observability platform in Rust. We obsess over instrumentation DX for our Python and TS SDKs and in this new blog we outline how we made the most seamless way of instrumenting recently released claude agent sdk
Dec 2025 · laminar.sh
- 14CM
Hey HN, I've been building AutoAgents, an AI agent framework in Rust. Today I'm sharing a feature I haven't seen done well elsewhere: composable middleware layers for LLM inference pipelines. The problem Every agent framework lets you swap LLM providers. Almost none of them give you a structured way to enforce safety, caching, or data sanitization in the inference path itself. You end up with guardrails as application-level if-statements, caching bolted on as a separate service, and PII handling as a "we'll add it later" TODO that never ships. This gets worse with local models. Cloud APIs…
Mar 2026 · github.com
- 15AI
The goal of Agentic is to create a set of standard AI functions / tools which are optimized for both normal TS-usage as well as LLM-based apps. It's designed to work with all of the major TS AI SDKs (LangChain, LlamaIndex, Vercel AI SDK, OpenAI SDK, Firebase Genkit, etc) via adaptors. Would love feedback from the HN community :)
2024 · github.com
- 16IB
Link: https://docs.trysoma.ai/ For the past ~9 months I’ve been building Soma, an open-source AI agent & workflow runtime written in Rust, with a TypeScript SDK (Python coming soon). It’s not a framework; it’s meant to sit underneath whatever agent/tooling code you already write (Vercel AI SDK, LangChain, custom code, etc.). It provides features around your framework + a better DX for building agents. I’ve tried to take a Next.JS model: open-source, good DX, self-deployable. I originally set out to build a vertical back-office/operations product for SMEs. I needed a…
Dec 2025 · docs.trysoma.ai
- 17OS
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
- 18IB
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
- 19IS
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
- 20AA
Mar 2026 · github.com
- 21AA
I’ve been experimenting with infrastructure for multi-agent systems. I built a small project called AgentLog. The core idea is very simple, topics are just append-only JSONL files. Agents publish events over HTTP and subscribe to streams using SSE. The system is intentionally single-node and minimal for now. Future ideas I’m exploring: - replayable agent workflows - tracing reasoning across agents - visualizing event timelines - distributed/federated agent logs Curious if others building agent systems have run into similar needs.
Mar 2026 · github.com
- 22AA
We’ve published a set of open-source reference implementations on how to build production-grade Agentic AI applications on AWS. What’s in the repo: • Agentic RAG, memory, and planning workflows with LangGraph & CrewAI • Strands-based flows with observability using OTEL & Arize • Evaluation with LLM-as-judge and cost/performance regressions • Built with Bedrock, S3, Step Functions, and more GitHub: https://github.com/aws-samples/sample-agentic-frameworks-on-... Would love your thoughts — feedback, issues, and stars welcome!
2025 · github.com
- 23AR
If you're interested in exploring what LLM-based agent systems these days actually do to solve certain benchmarks such as SWEBench or WebArena, we created a small leaderboard with our team, that allows to view a lot of public and OSS agent results including all the runtime traces (the step-by-step reasoning behind the scenes). Looking at traces is actually quite interesting, as they reveal a lot about the inner working and shortcomings of current agent system, e.g. see https://explorer.invariantlabs.ai/u/invariant/webarena--SteP... for an example trace.
2024 · explorer.invariantlabs.ai
- 24

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