AI · alternatives · 2026
24 alternatives to Concierge - Framework for Building Agentic Web Interfaces
Hey HN, We’re building Concierge, An open source framework that allows you to build Agentic Applications, letting LLMs navigate, interact, and transact with your service It's a declarative framework which makes it easy for you to create Microservices for AI agents. You can expose your existing web offerings to LLMs. To support navigation you can use several abstractions like Stages, Tasks, Workflows and more. These specify the rules and guiding principles of how an Agent interacts with the service. It's especially useful when you want to expose complex business logic with thousands of APIs,…
Concierge is an open-source framework for building applications that allow large language models to navigate, interact with, and conduct transactions on web services. It uses a declarative approach with abstractions… 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
Arch▲314Hey 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…
2024 · github.com · its alternatives →
- 2
InsForge▲622We built InsForge because we wanted to use pure prompts to build a production-grade app faster. In practice, AI isn’t reliable enough when generating code or configuring backend pieces like schema, RLS, auth, or functions. Postgres MCP and Supabase MCP are a good starting point, but they felt more like API wrappers for agents than something designed to guide AI safely through backend tasks. So we built our own MCP server on top of Postgres and added a set of context-engineering tools to make prompt-driven workflows more predictable. It gradually turned into a Postgres-based BaaS. Key…
Mar 2026 · insforge.dev · its alternatives →
- 3
AgentSky▲430Any harness, any LLM — cloud-hosted agents on demand.
Aug 2026 · agentsky.dev · its alternatives →
- 4
- 5
Many teams connecting LLMs to external tools eventually encounter the same architectural issue: as more tools and agents are added, the integration pattern becomes an N×M mesh of direct connections. Each agent implements its own auth, retries, rate limiting, and logging; each tool needs credentials distributed to multiple places and observability becomes fragmented. We built LLM gateway with this goal to provide a single place to manage authentication, authorization, routing, and observability for MCP servers, with a path toward a more general agent-gateway architecture in the future. The…
Dec 2025 · truefoundry.com · its alternatives →
- 6
Hey HN, We’ve been building browser agents for a while. In production, we kept converging on the same pattern: deterministic scripts for the happy path, agents only for edge cases. So we built Demonstrate Mode. The idea is simple: You perform your workflow once in a remote browser. Notte records the interactions and generates deterministic automation code. How it works: - Record clicks, inputs, navigations in a cloud browser - Compile them into deterministic code (no LLM at runtime) - Run and deploy on managed browser infrastructure Closest analog is Playwright codegen but: - Infrastructure…
2025 · notte.cc · its alternatives →
- 7
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 · its alternatives →
- 8
The open source LLM router that connects your AI agents and harnesses to any provider in seconds. Subscriptions, pay-per-token, local models, and custom providers.
2024 · manifest.build · its alternatives →
- 9
Build AI agents that respond with UI instead of text
Feb 2026 · thesys.dev · its alternatives →
- 10
LLM Gatewayfree tier▲296I built an OpenAI-compatible LLM gateway that routes requests to OpenAI, Anthropic, Ollama, vLLM, llama-server, SGLang... anything that speaks /v1/chat/completions. Single Go binary, one YAML config file, no infrastructure. It does the things you'd expect from this kind of gateway... semantic routing via a three-layer cascade (keyword heuristics, embedding similarity, LLM classifier) that picks the best model when clients omit the model field, weighted round-robin load balancing across local inference servers with health checks and failover. The part I think is most…
2025 · llmgateway.io · its alternatives →
- 11
I shipped a wiki layer for AI agents that uses markdown + git as the source of truth, with a bleve (BM25) + SQLite index on top. No vector or graph db yet. It runs locally in ~/.wuphf/wiki/ and you can git clone it out if you want to take your knowledge with you. The shape is the one Karpathy has been circling for a while: an LLM-native knowledge substrate that agents both read from and write into, so context compounds across sessions rather than getting re-pasted every morning. Most implementations of that idea land on Postgres, pgvector, Neo4j, Kafka, and a dashboard. I…
Apr 2026 · github.com · its alternatives →
- 12
Hey HN! Wanted to show our open source agent harness called Gambit. If you’re not familiar, agent harnesses are sort of like an operating system for an agent... they handle tool calling, planning, context window management, and don’t require as much developer orchestration. Normally you might see an agent orchestration framework pipeline like: compute -> compute -> compute -> LLM -> compute -> compute -> LLM we invert this so with an agent harness, it’s more like: LLM -> LLM -> LLM -> compute -> LLM -> LLM -> compute -> LLM Essentially you describe each agent in either a self contained…
Jan 2026 · github.com · its alternatives →
- 13
Hey HN, I made Browser-Use, an open-source tool that lets (all Langchain supported) LLMs execute tasks directly in the browser just with function calling. It allows you to build agents that interact with web elements using natural language prompts. We created a layer that simplifies website interaction for LLMs by extracting xPaths and interactive elements like buttons and input fields (and other fancy things). This enables you to design custom web automation and scraping functions without manual inspection through DevTools. Hasn't this been done a lot of times? Good question, as a general…
2024 · github.com · its alternatives →
- 14
Hey HN, we’re building an open specification that lets agents discover and invoke APIs with natural language, built on the OpenAPI standard. agents.json clearly defines the contract between LLMs and API as a standard that's open, observable, and replicable. Here’s a walkthrough of how it works: https://youtu.be/kby2Wdt2Dtk?si=59xGCDy48Zzwr7ND. There’s 2 parts to this: 1. An agents.json file describes how to link API calls together into outcome-based tools for LLMs. This file sits alongside an OpenAPI file. 2. The agents.json SDK loads agents.json files as tools for an LLM that…
2025 · github.com · its alternatives →
- 15
Hey HN, I've been working on an open-source framework for creating AI agents that evolve, communicate, and collaborate to solve complex tasks. The Evolving Agents Framework allows agents to: Reuse, evolve, or create new agents dynamically based on semantic similarity Communicate and delegate tasks to other specialized agents Continuously improve by learning from past executions Define workflows in YAML, making it easy to orchestrate agent interactions Search for relevant tools and agents using OpenAI embeddings Support multiple AI frameworks (BeeAI, etc.) Current Status & Roadmap This is…
2025 · github.com · its alternatives →
- 16
Open Agents▲161OpenAgents - 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 →
- 17
Hey HN, We've been building a multi-model API for LLMs called OpenRouter since we launched the Window AI extension in April this year [0]. The events of the last week make it clear the LLM landscape is unpredictable, so LLM aggregators are picking up interest. Unlike others, we're making a router on top of a public, explorable dataset. We recently built a way to rank and visualize this data, including the token counts we see going to and from different models, both open-sourced (like Llama, Mistral, finetunes, and variants) and closed-sourced (OpenAI, Anthropic). The API supports - 50+…
Apr 2026 · openrouter.ai · its alternatives →
- 18
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 · its alternatives →
- 19
Hey HN! A few months ago we shared mcp-agent (https://github.com/lastmile-ai/mcp-agent) [1][2], a lightweight framework that implements every agent pattern from Anthropic’s Building Effective Agents blog [3] and handles MCP server/client management seamlessly. Our core bet is that connecting LLMs to tools, resources, and external systems will soon be MCP-native by default. Today we're launching a significant update: Agents as MCP servers. Currently "agentic" behavior exists only on the MCP client side – clients like Claude or Cursor use MCP servers to solve tasks.…
2025 · github.com · its alternatives →
- 20
Hi all, I wanted to reshare this after some time. I've been working on evolving my service framework into an agent harness. As all of this AI tooling has evolved its become clear to me that agents, services and workflows are part of a core system of operations which would benefit from a single framework. Previously Go Micro only enabled service development. But now it includes Agents and Workflows. What does that mean? Well firstly services which are registered in a central registry automatically become tools for agents. The service endpoints individually become callable tools via MCP.…
2019 · go.micro.mu · its alternatives →
- 21OS
2023 · sugarcaneai.dev · its alternatives →
- 22
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 · its alternatives →
- 23
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 · its alternatives →
- 24
Hey HN, I spent my xmas break building an agent framework called mcp-agent [1](https://github.com/lastmile-ai/mcp-agent) for Model Context Protocol [2]. It makes it easy to build AI apps with MCP servers, and implements every pattern from the popular Building Effective Agents blog [3] as well as OpenAI’s Swarm [4]. I’m sharing it early to get community feedback on where to take it from here, and to ask for contributions. For those who aren’t familiar with MCP, I think of it as a standardized interface to let AI communicate with software via tool calls, resources and…
2025 · github.com · 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 →