HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
maximhq
bifrost
Go2025–2026
maximhq / bifrost

bifrost

Open-source, high-performance AI gateway that works as your LLM gateway, MCP gateway and agent gateway. One OpenAI-compatible API for 10,000+ models, with failover, load balancing, semantic caching, virtual keys, budgets and MCP Code Mode. Works with any SDK or agent and adds under 200µs of overhead at 5k RPS.

12Distinct people
24Mentions
0Explicit recommenders
9.5KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Open-source, high-performance AI gateway that works as your LLM gateway, MCP gateway and agent gateway. One OpenAI-compatible API for 10,000+ models, with failover, load balancing, semantic caching, virtual keys, budgets and MCP Code Mode. Works with any SDK or agent and adds under 200µs of overhead at 5k RPS.

GitHub

Where it is used

No documented product use was verified in the last source check.

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 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM 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 month24 dated mentions

Observed mentions: 2025-08-07 05:06:18 UTC to 2026-10-13 07:02:41 UTC.

02462025-08-01 00:00:00 UTC to 2025-09-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 commentsAug 20252025-09-01 00:00:00 UTC to 2025-10-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2025-10-01 00:00:00 UTC to 2025-11-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-11-01 00:00:00 UTC to 2025-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 3 mentions; 3 submissions, 0 comments2026-01-01 00:00:00 UTC to 2026-02-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2026-02-01 00:00:00 UTC to 2026-03-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2026-03-01 00:00:00 UTC to 2026-04-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 commentsMar 20262026-04-01 00:00:00 UTC to 2026-05-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-05-01 00:00:00 UTC to 2026-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-01 00:00:00 UTC to 2026-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-01 00:00:00 UTC to 2026-08-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2026-08-01 00:00:00 UTC to 2026-09-01 00:00:00 UTC (exclusive): 7 mentions; 6 submissions, 1 comments2026-09-01 00:00:00 UTC to 2026-10-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2026-10-01 00:00:00 UTC to 2026-11-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 commentsOct 2026

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
Aug 20252025-08-01 00:00:00 UTC2025-09-01 00:00:00 UTC312
Sep 20252025-09-01 00:00:00 UTC2025-10-01 00:00:00 UTC110
Oct 20252025-10-01 00:00:00 UTC2025-11-01 00:00:00 UTC101
Nov 20252025-11-01 00:00:00 UTC2025-12-01 00:00:00 UTC000
Dec 20252025-12-01 00:00:00 UTC2026-01-01 00:00:00 UTC330
Jan 20262026-01-01 00:00:00 UTC2026-02-01 00:00:00 UTC110
Feb 20262026-02-01 00:00:00 UTC2026-03-01 00:00:00 UTC110
Mar 20262026-03-01 00:00:00 UTC2026-04-01 00:00:00 UTC211
Apr 20262026-04-01 00:00:00 UTC2026-05-01 00:00:00 UTC101
May 20262026-05-01 00:00:00 UTC2026-06-01 00:00:00 UTC000
Jun 20262026-06-01 00:00:00 UTC2026-07-01 00:00:00 UTC000
Jul 20262026-07-01 00:00:00 UTC2026-08-01 00:00:00 UTC110
Aug 20262026-08-01 00:00:00 UTC2026-09-01 00:00:00 UTC761
Sep 20262026-09-01 00:00:00 UTC2026-10-01 00:00:00 UTC110
Oct 20262026-10-01 00:00:00 UTC2026-11-01 00:00:00 UTC211

What Hacker News says

24 sources
Swapnoneel·Aug 7, 2026Submission

Show HN: A model router should also provide a MCP gateway

So, I was recently exploring different options for model routing based on task complexity, and realized that it’s absolutely essential that the model router provides an unified MCP gateway as well. Because it’s as painful as connecting your separate providers to a service. For example, you are using OpenCode and Hermes, and as provider, you have got Groq, OpenRouter and Anthropic, and also a couple of MCPs. So, the hassle comes from connecting all your MCPs and LLM providers to both OpenCode and Hermes separately. Now, you can do it for two, but what if you also use OpenClaw, jcode, or Muse Code? It becomes a nightmare of executing busy chores. So, a LLM and MCP gateway like Bifrost becomes necessary, which is both free and open-source. Out of all the solutions I tried like Truefoundry or LiteLLM, Bifrost sounded the best one to me. Pleas
Read the rest
e share your feedbacks and opinion regarding this in the comments.
2 points · Open discussion
Swapnoneel·Aug 3, 2026Submission

Show HN: Changed how I use agent harnesses

I’ve been using OpenCode for quite a while now, and I’m in love with it. The subscription cost of Claude Code or Codex doesn’t make much sense to me, so I prefer the free tier of OpenCode Zen! But for planning and drafting I do need capable models, which I grab from Zenmux or similar providers, and those are heavily rate-limited. I’d get most of the way through a task and hit a limit, which meant stopping, opening the config, swapping the provider, restarting, and picking the task back up from wherever it died. Three or four times per complex task. Losing the quota was annoying. Losing my place in the task was worse. What I settled on was putting a gateway in front of everything and pointing OpenCode at that instead of at any single provider. One base URL in the OpenCode config, and the routing happens behind it. When one provider 429s, t
Read the rest
he request goes to the next one with headroom. I tried LiteLLM first. It works, and if your stack is already Python it’s probably the more obvious pick. But, I recently found out about Bifrost, and switched from LiteLLM. What made it fit my setup is that it’s a single Go binary with a local SQLite config store, so there’s no separate database service to run alongside it. I’ve got 9 providers configured with fallbacks between them, which is the part that actually fixed the interruptions. Sharing in case it helps anyone with the same problem. Took me a while to land on this.
3 points · Open discussion

Showing the 15 most recent of 24 sources. Enable JavaScript to search and browse every indexed mention.

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.