Alternatives
Products that do what AxonFlow, governing LLM and agent workflows does
Hi HN, we’re building AxonFlow for teams running LLMs or agents in real production systems. Once agent workflows move past demos, failures are rarely model issues. They tend to show up as execution problems during real runs. Short 2-minute technical demo showing execution control and auditability in practice: https://youtu.be/FNgnESo9RtI AxonFlow is a self-hosted, source-available (BSL 1.1) control plane that sits inline in the execution path and governs LLM calls, tool calls, retries, approvals, and policy enforcement step by step. It does not replace your orchestrator and…
- 1CO
Hi HN! I’m excited to share ControlFlow, our new open-source framework for building agentic workflows. ControlFlow is built around a core opinion that LLMs perform really well on small, well-defined tasks and run off the rails otherwise. I know that may seem obvious, but the key insight is that if you compose enough of these small tasks into a structured workflow, you can recover the kind of complex behaviors we associate with autonomous AIs, without sacrificing control or observability at each step. It ends up feeling a lot like writing a traditional software workflow. With ControlFlow you:…
2024 · github.com
- 2AR
So, it feels like this should exist. But I couldn't find it. So I tried to build it. Agentflow lets you run complex LLM workflows from a simple JSON file. This can be as little as a list of tasks. Tasks can include variables, so you can reuse workflows for different outputs by providing different variable values. They can also include custom functions, so you can go beyond text generation to do anything you want to write a function for. Someone might say: "Why not just use ChatGPT?" Among other reasons, I'd say that you can't template a workflow with ChatGPT, trigger it with different…
2023 · github.com
- 3AO
Hi HN, we are Nick and Ben, creators of Axilla - an open source TypeScript framework to develop LLM applications. It’s in the early stages but you can use it today: we’ve already published 2 modules and have more coming soon. Ben and I met while working at Cruise on the ML platform for self-driving cars. We spent many years there and learned the hard way that shipping AI is not quite the same as shipping regular code. There are many parts of the ML lifecycle, e.g., mining, processing, and labeling data and training, evaluating, and deploying models. Although none of them are rocket science,…
2023 · github.com
- 4
- 5WU
Hey HN – Gregor & Magnus here again. A few months ago, we launched Browser Use (https://news.ycombinator.com/item?id=43173378), which let LLMs perform tasks in the browser using natural language prompts. It was great for one-off tasks like booking flights or finding products—but we soon realized enterprises have somewhat different needs: They typically have one workflow with dynamic variables (e.g., filling out a form and downloading a PDF) that they want to reliably run a million times without breaking. Pure LLM agents were slow, expensive, and unpredictable for these…
2025 · github.com
- 6WW
I spent a few hours last weekend testing whether AI can replace code by executing directly. Built a contact manager where every HTTP request goes to an LLM with three tools: database (SQLite), webResponse (HTML/JSON/JS), and updateMemory (feedback). No routes, no controllers, no business logic. The AI designs schemas on first request, generates UIs from paths alone, and evolves based on natural language feedback. It works—forms submit, data persists, APIs return JSON—but it's catastrophically slow (30-60s per request), absurdly expensive ($0.05/request), and has zero UI…
Nov 2025 · github.com
- 72C
Single-agent LLMs suck at long-running complex tasks. We’ve open-sourced a multi-agent orchestrator that we’ve been using to handle long-running LLM tasks. We found that single LLM agents tend to stall, loop, or generate non-compiling code, so we built a harness for agents to coordinate over shared context while work is in progress. How it works: 1. Orchestrator agent that manages task decomposition 2. Sub-agents for parallel work 3. Subscriptions to task state and progress 4. Real-time sharing of intermediate discoveries between agents We tested this on a Putnam-level math problem, but the…
Feb 2026 · github.com
- 8
- 9FA
I think graph is a wrong abstraction for building AI agents. Just look at how incredibly hard it is to make routing using LangGraph - conditional edges are a mess. I built Laminar Flow to solve a common frustration with traditional workflow engines - the rigid need to predefine all node connections. Instead of static DAGs, Flow uses a dynamic task queue system that lets workflows evolve at runtime. Flow is built on 3 core principles: * Concurrent Execution - Tasks run in parallel automatically * Dynamic Scheduling - Tasks can schedule new tasks at runtime * Smart Dependencies - Tasks can…
2024 · github.com
- 10
- 11
- 12PE
Hey HN — I’m Adil from Katanemo (with Salman, Shuguang, and Meiyu) We previously shared an early version of this project as ArchGW. Based on customer feedback, the scope expanded from “LLM routing and model access” into something broader: delivery infrastructure for agentic applications. We renamed it to Plano and reworked the architecture accordingly. The problem On-the-ground AI practitioners will tell you that calling an LLM is not the hard part. The really hard part is delivering agentic applications to production quickly and reliably, then iterating without rewriting system code every…
Jan 2026 · github.com
- 13
- 14ZD
Hey HN! We just released a new library for building LLM-powered applications: @axflow/models. It is part of a larger suite of libraries we're developing for TypeScript developers working with generative AI. This library provides the simplest APIs for 1) invoking the most popular LLM and embedding models (openai, anthropic, cohere, huggingface, etc.) 2) streaming LLM responses to clients, including augmenting the streams with additional arbitrary data and 3) building client-side applications with React hooks. @axflow/models has zero dependencies and is built using only the…
2023 · docs.axflow.dev
- 15IB
The HN community may find the context of the prompts, organized by each turn in each session, the most useful. See the website/docs/prompts.md and session-X.md files. I also started exploring some workflows for the LLM to execute, organized in the website/docs/tasks/ folder. I found it pretty handy to have the LLM document our work as we went and simply embedded the static site into the executable, along with all the music and logic. The whole project took me about a day for the backend. The C++ controller itself took only a few turns. I enjoyed focusing on my son's…
2025 · github.com
- 16AO
I have spent a long time working in an XP/TDD style, so when AI coding tools became useful enough for real work, I adopted them quickly. The first bottleneck I hit was not code generation, it was verification: AI could write code and tests quickly, but I was still the person reviewing implementations, clicking through flows, checking logs, inspecting database state, and deciding whether the result was actually correct. That pushed me to move validation further left. Before implementation, AI had to produce test plans. After implementation, it had to execute those plans too: drive the…
Mar 2026
- 17KR
I've spent the past few years building 50+ AI agents in prod (some reached 1M+ sessions/day), and the hardest part was never building them — it was figuring out why they fail. AI agents don't crash. They just quietly give wrong answers. You end up scrolling through traces one by one, trying to find a pattern across hundreds of sessions. Kelet automates that investigation. Here's how it works: 1. You connect your traces and signals (user feedback, edits, clicks, sentiment, LLM-as-a-judge, etc.) 2. Kelet processes those signals and extracts facts about each session 3. It forms hypotheses…
Apr 2026 · kelet.ai
- 18CA
I built this because I was tired of creating pull requests in 20 repositories just to change a single line of workflow job version. With Infra as AI, just mention the change. Agents work on all repos in parallel, read the docs, make a bunch of PRs and fill in the description. You can see the demo of the actual dashboard in the landing. Let me know your thoughts :) It means a lot to me!
Sep 2025 · infrastructureas.ai
- 19GA
It all started with a conversation among friends about limitations in current multi-agent orchestration frameworks. We faced issues like limited control over agent memory and state, complicated persistence, scaling problems, and lack of type safety in Python-based tools. These challenges inspired us to try something different. The result was GraphFlow, a Rust-based lean framework for orchestrating multi-agent workflows that's simple, scalable, and robust. Its key features include: Graph-based orchestration: Easily define workflows using nodes and edges. Lean Execution Engine: A minimal and…
2025 · github.com
- 20BA
Hey, Lorenzo here, Started to work on this side-project for a week or so, I’m curious what y’all think! Coflow connects AI to your current platforms and automates any repetitive/manual task without coding. How it works: - Specify the trigger/input the AI should expect - Tell the AI what to do - Specify where to send/store the output - Deploy and let it run Would love your feedback :) Early access: https://www.joincoflow.com/
2023 · joincoflow.com
- 21
- 22
Install the CLI and run your first AX experiment
30d ago · docs.514.ax
- 23
- 24HA
Hi HN, I am Umer. I recently built an experimental framework called HyperFlow to explore the idea of self-improving AI agents. Usually, when an agent fails a task, we developers step in to manually tweak the prompt or adjust the code logic. I wanted to see if an agent could automate its own improvement loop. Built on LangChain and LangGraph, HyperFlow uses two agents: - A TaskAgent that solves the domain problem. - A MetaAgent that acts as the improver. The MetaAgent looks at the TaskAgent's evaluation logs, rewrites the underlying Python code, tools, and prompt files, and then tests the new…
Apr 2026
Ranked by how close each launch is in meaning, then by votes. Refine with a description →