GitHub Repository

A lightweight, DSL-driven LLM gateway for routing, patching provider quirks, and normalizing APIs across channels

25 starsGo

Open-next-router (ONR) – An Nginx-inspired, config-driven LLM router

Name: Open-next-router (ONR) – An Nginx-inspired, config-driven LLM router
Availability: InStock
Author: song2025

by song2025·Feb 24, 2026·1 point·0 comments

Visit Project View on HN

AI Analysis

●MidBold Bet

Nginx-style config for LLM routing. Early-stage, needs demos and actual deployment stories.

Strengths

•Config-driven approach avoids hardcoded boilerplate; atomic reload philosophy borrowed from proven Nginx patterns
•DSL abstraction could meaningfully reduce code in multi-provider orchestration
•Go + performant gateway stack is right choice for this infrastructure layer

Weaknesses

•README lacks any working example, demo, or proof-of-concept output; 'Nginx for LLMs' is aspirational language without substance
•LLM routing is crowded (LiteLLM, Helicone, Unify); no stated differentiation beyond 'open and config-driven'
•Only 7 GitHub stars and minimal commit history; unclear if this is active or exploratory

Post Description

Despite the name, OpenRouter's core isn't truly open. I’m building open-next-router (ONR) to change that.

Inspired by Nginx’s atomic configuration philosophy, ONR allows developers to integrate and switch between various LLM channels through simple config files rather than writing boilerplate code. The goal is to move away from "hard-coded integrations" and toward a modular, high-performance routing layer.

I'm aiming to build the "Nginx for the LLM era." It’s still in the early stages, and I’d love to get feedback from the community or collaborate with anyone interested in the future of open LLM infrastructure.