HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
ulab-uiuc
LLMRouter
Python2025–2026
ulab-uiuc / LLMRouter

LLMRouter

LLMRouter: An Open-Source Library for LLM Routing

2Distinct people
6Mentions
0Explicit recommenders
3.1KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

LLMRouter: An Open-Source Library for LLM Routing

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 7:27:27 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by 3-hour interval6 dated mentions

Observed mentions: 2025-12-30 10:11:32 UTC to 2026-01-01 08:59:32 UTC.

0122025-12-30 09:00:00 UTC to 2025-12-30 12:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 commentsDec 30, 09:002025-12-30 12:00:00 UTC to 2025-12-30 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-30 15:00:00 UTC to 2025-12-30 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-30 18:00:00 UTC to 2025-12-30 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-30 21:00:00 UTC to 2025-12-31 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-31 00:00:00 UTC to 2025-12-31 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-31 03:00:00 UTC to 2025-12-31 06:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2025-12-31 06:00:00 UTC to 2025-12-31 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsDec 31, 06:002025-12-31 09:00:00 UTC to 2025-12-31 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-31 12:00:00 UTC to 2025-12-31 15:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2025-12-31 15:00:00 UTC to 2025-12-31 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-31 18:00:00 UTC to 2025-12-31 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-31 21:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 00:00:00 UTC to 2026-01-01 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 03:00:00 UTC to 2026-01-01 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 06:00:00 UTC to 2026-01-01 09:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsJan 1, 06:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Dec 30, 09:002025-12-30 09:00:00 UTC2025-12-30 12:00:00 UTC211
Dec 30, 12:002025-12-30 12:00:00 UTC2025-12-30 15:00:00 UTC000
Dec 30, 15:002025-12-30 15:00:00 UTC2025-12-30 18:00:00 UTC000
Dec 30, 18:002025-12-30 18:00:00 UTC2025-12-30 21:00:00 UTC000
Dec 30, 21:002025-12-30 21:00:00 UTC2025-12-31 00:00:00 UTC000
Dec 31, 00:002025-12-31 00:00:00 UTC2025-12-31 03:00:00 UTC000
Dec 31, 03:002025-12-31 03:00:00 UTC2025-12-31 06:00:00 UTC211
Dec 31, 06:002025-12-31 06:00:00 UTC2025-12-31 09:00:00 UTC000
Dec 31, 09:002025-12-31 09:00:00 UTC2025-12-31 12:00:00 UTC000
Dec 31, 12:002025-12-31 12:00:00 UTC2025-12-31 15:00:00 UTC110
Dec 31, 15:002025-12-31 15:00:00 UTC2025-12-31 18:00:00 UTC000
Dec 31, 18:002025-12-31 18:00:00 UTC2025-12-31 21:00:00 UTC000
Dec 31, 21:002025-12-31 21:00:00 UTC2026-01-01 00:00:00 UTC000
Jan 1, 00:002026-01-01 00:00:00 UTC2026-01-01 03:00:00 UTC000
Jan 1, 03:002026-01-01 03:00:00 UTC2026-01-01 06:00:00 UTC000
Jan 1, 06:002026-01-01 06:00:00 UTC2026-01-01 09:00:00 UTC110

What Hacker News says

2 sources
OP here. I'm a CS PhD student at UIUC working on User Modeling and Applied ML. We built LLMRouter because we noticed a gap in the current LLM stack: everyone knows we shouldn't route every query to GPT-4/o1 (it's slow and expensive), but building a reliable router that handles context, reasoning, and user history is surprisingly hard. Most existing solutions are either simple regex/keyword matching or closed-source APIs. We wanted to build a standard, open-source library that unifies the SOTA. What LLMRouter actually does: It provides a unified interface to 16+ routing strategies, ranging from lightweight ML to heavy reasoning agents: Single-Round: Classification-based (KNN, SVM, BERT) and Embedding-based methods. Multi-Round & Agentic: Routers that "think" before assigning models (CoT reasoning) or break down tasks step-by-step. Personal
Read the rest
ized Routing: This is a key focus of our research. The router learns from user interaction history to fit individual preferences (e.g., some users prefer concise answers from faster models, others need detailed reasoning). The Pipeline: We didn't just ship the model weights. The library includes: Data Generation: A pipeline to generate synthetic routing data for your specific domain. Benchmarks: 11 datasets to evaluate router performance. Deployment: A CLI and Gradio UI to visualize routing decisions in real-time. In our experiments, we typically see 30–50% cost reduction while maintaining response quality by correctly identifying easy vs. hard queries. The code is open source (MIT/Apache): https://github.com/ulab-uiuc/LLMRouter Happy to answer any questions about the implementation details or the specific RL/Ranking algorithms we used!
In Show HN: LLMRouter – Stop using GPT-4/o1 for everything (16 routing strategies)

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.