Alternatives
Products that do what RunAgent; Multi-Framework Agent Deployment and Rust,Go,JS SDKs(+others) does
RunAgent eliminates the complexity of AI agent deployment across different frameworks and languages. Today's developers face deployment nightmares with fragmented frameworks (LlamaIndex, LangChain, LangGraph, CrewAI, Letta, Agno, etc.) each requiring different deployment processes, creating unnecessary friction. The Solution: Like MCP (Model Context Protocol), RunAgent provides a standardized approach to agent deployment. Developers simply provide a config file and their agent code - RunAgent handles the rest with REST API and WebSocket (Streaming and non streaming). Our open-source platform…
- 1NO
Hello HN! The day has finally come to stop adding features and start sharing what I've been building the last 5-6 months. It's a bit of CrewAI, OpenDevon, LangFuse/Cloud all in one, providing devs who prefer TypeScript an integrated framework thats provides a lot out of the box to start experimenting and building agents with. It started after peeking at the LangChain docs a few times and never liking the example code. I began experimenting with automating a simple Jira request from the engineering team to add an index to one of our Google Spanner databases (for context I'm the…
2024 · github.com
- 2
- 3
- 4
- 5IB
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
- 6
- 7AM
Hi HN, Excited to share Agno, a framework and runtime for multi-agent systems. Think of it as FastAPI for AI Agents. At its core is the AgentOS, a high-performance server/runtime that helps you run and manage AI agents, multi-agent teams, and step-based agentic workflows — all inside your own cloud, with full privacy and no external data sharing. What makes it different • Fast & lightweight — Agents instantiate in ~3μs and use ~6.6 KiB of memory on average (tested on M4 MacBook Pro). • Runtime architecture — Async, stateless, horizontally scalable runtime built on FastAPI. • Integrated…
Oct 2025 · agno.link
- 8AA
Hey HN! We've just open-sourced Agent, our framework for running computer-use workflows across multiple apps in isolated macOS/Linux sandboxes. After launching Computer a few weeks ago, we realized many of you wanted to run complex workflows that span multiple applications. Agent builds on Computer to make this possible. It works with local Ollama models (if you're privacy-minded) or cloud providers like OpenAI, Anthropic, and others. Why we built this: We kept hitting the same problems when building multi-app AI agents - they'd break in unpredictable ways, work inconsistently across…
2025 · github.com
- 9
Open-source 2D IDE for managing AI agents in native CLIs, terminal, gits, beads issues, and files across multiple projects and machines. Self-host on a single machine via localhost OR host on a cluster via Tailscale OR connect to app.49agents.com (coming soon) - alpbahadur/49-IDE
5d ago · github.com
- 10RA
Hi HN folks, I have been building AI agents for quite some time now. The shift has gone from LLM + Tools → LLM Workflows → Agent + Tools + Memory, and now we are finally seeing true agency emerge: agents as systems composed of tools, command-line access, fine-grained system capabilities, and memory. This way of building agents is powerful, and I believe it is here to stay. But the real question is: are the systems powering these agents ready for that future? I do not think so. Using Docker for a single agent is not going to scale well, because agents need to be lightweight and fast. LLMs…
Mar 2026 · github.com
- 11AC
Built an AI code reviewer using Letta (Python) that I can call natively from Rust applications. The interesting part: real-time streaming works perfectly across the language boundary with zero hassle using RunAgent. The agent runs in Python with persistent memory, leverages the best in house agentic memory management with Letta (Pythonic AI agent framework), and my rust code just uses it (kinda) natively, though Letta has no Rust bindings. And, streaming works like magic. No FFI, no complex bridges - just native async/streaming that feels like calling any Rust librar, but without…
2025 · medium.com
- 12NC
There's been some interesting work lately with BrowserAI (runs LLMs in the browser using WebGPU) enabling local, private AI processing. Now, the team has released BrowserAgent - a no-code tool built on top of it. BrowserAgent lets you create custom AI workflows using a drag-and-drop interface, all within your browser. This means personalized web summarizers, research assistants, or content generators can all run locally with no cloud costs and full data privacy. Check it out here - https://browseragent.dev Key features include: - No-Code Workflow Builder: Design custom AI agents…
2025 · browseragent.dev
- 13RL
Hi HN — I’m building an interoperability layer for AI agents that lets local and remote agents run inside the same network and coordinate with each other. Here is a demo: https://youtu.be/2_1U-Jr8wf4 • OpenClaw runs locally on-device • it connects to remote agents through Hybro Hub • both participate in the same workflow execution The goal is to make agent-to-agent coordination work across environments (local machines, cloud agents, MCP servers, etc). Right now most agent systems operate inside isolated runtimes. Hybro is an attempt to make them composable across boundaries.…
Apr 2026 · github.com
- 14RA
Hey HN, I built SuperHQ, an app that lets you run coding agents in local sandboxes (powered by Shuru). No custom UI wrapping the agents, they run as CLI/TUI like they were designed to. It just provides you the tools most of us (okay, maybe just me?) needed for running multiple coding agents in parallel without worrying about breaking your system or work environment. Each agent runs in its own microVM. You mount your projects in, writes go to a tmpfs overlay so your host is never touched, and you get a unified diff view to accept or discard changes. API keys never enter the sandbox, they…
Apr 2026 · superhq.ai
- 15
- 16UA
Recently several AI labs have published experiments where they tried to get AI coding agents to complete large software projects. - Cursor attempted to make a browser from scratch: https://cursor.com/blog/scaling-agents - Anthropic attempted to make a C Compiler: https://www.anthropic.com/engineering/building-c-compiler A few weeks ago I posted xmloxide, an agent-made Rust replacement for libxml2 made by pointing Claude code at the libxml2 test suite: https://news.ycombinator.com/item?id=47201816 curl is arguably the most widely deployed…
Mar 2026 · github.com
- 17AA
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
- 18UA
Three months ago, we started developing an open source agent framework. We previously tried existing frameworks in our enterprise product but faced challenges in certain areas. Problems we experienced: * We risked our stateless architecture when we wanted to add an agented feature to our existing system. Current frameworks lack server-client architecture, requiring significant effort to maintain statelessness when adding an agent framework to your application. * Scaling problem - needed to write Docker configurations as existing frameworks lack official Docker support. Each agent in my…
2025 · github.com
- 19
- 20AA
Hey HN! I am super excited (and slightly nervous) to introduce AgentServe! AgentServe is a framework to make hosting scalable AI agents as easy as possible. With 4 lines of code AS wraps your agent (any framework) in a FastAPI and connects it to a Task Queue (celery or redis). Why Should You Care? Standardized Communication Pattern: AgentServe proposes that all agents should communicate with each other and the outside world with “Tasks” that can be submitted in a sync or async way. This simple API wil enable Framework Agnostic: No favorites. OpenAI, LangChain, LlamaIndex, CrewAI are all…
2024 · github.com
- 21LT
Running multiple coding agents could make user losing track of what they were doing. Once subagents start spawning other subagents, basic questions get hard to answer: what is running right now, what tool did it just call, did the child agent actually do what the parent asked. Lazyagent is a terminal TUI that collects events from Claude Code, Codex, and OpenCode and shows them in one place. It groups sessions from different runtimes by working directory, so Claude and Codex runs on the same repo appear under the same project. From there you can: - Filter events by type: tool calls, user…
Apr 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
Jul 2026 · github.com
- 24AF
I’ve been working on a temporal database for agents that combines graphs, tables, and compute. While building it, I ended up needing an agent framework that could handle both simple tool-use tasks and more graph-based execution, so I pulled that out into a separate project, Agent Forge. Agent Forge uses a two-tier execution model: * a heuristic router decides whether a request is simple or complex * simple requests go through a lightweight agent loop with a single system prompt and tool-calling loop * more complex requests can use memory retrieval, reflection constraints, tree search, and…
Mar 2026 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →