This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
Agnos LLM gateway
Contain LiteLLM, Bifrost, Portkey.. behind one control plane
Agnos is an OpenAI-compatible control plane that wraps the LLM gateway you already run. Keys stay in your encrypted vault (the gateway gets one per request and stores none); you get budgets, guardrails, routing, cost attribution and audit, and you can swap or combine gateways (litellm, bifrost, portkey etc) with a config change. MIT, self-hosted. Live demo, https://agnos-llm-gateway.site https://github.com/siva010928/agnos-proxy-oss
We open-sourced Agnos Proxy: a control plane that contains the LLM gateway you already run.
Most gateways fuse two jobs - translating your request to each provider, and governing it (keys, budgets, guardrails, cost, audit). Fuse them and your provider keys live inside the code parsing untrusted input, and switching gateways means a rewrite.
Agnos separates them. It contains LiteLLM, Bifrost, Portkey, or a built-in engine as swappable adapters behind one OpenAI-compatible endpoint:
Change one line, keep your SDK.
Route each provider to the gateway that serves it best, or swap one at runtime. Keys stay Fernet-encrypted in your vault, injected per request. The gateway stores nothing. Budgets that stop spend before it happens, PII/secret guardrails, cost attribution and audit, the same across every gateway. Self-hosted, MIT, about 1 ms overhead.
Feedback and "which gateway should we contain next" welcome.
About Agnos LLM gateway on Product Hunt
“Contain LiteLLM, Bifrost, Portkey.. behind one control plane”
Agnos LLM gateway was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #139 on the daily leaderboard. Agnos is an OpenAI-compatible control plane that wraps the LLM gateway you already run. Keys stay in your encrypted vault (the gateway gets one per request and stores none); you get budgets, guardrails, routing, cost attribution and audit, and you can swap or combine gateways (litellm, bifrost, portkey etc) with a config change. MIT, self-hosted. Live demo, https://agnos-llm-gateway.site https://github.com/siva010928/agnos-proxy-oss
On the analytics side, Agnos LLM gateway competes within API, Analytics, Software Engineering and GitHub — topics that collectively have 356.5k followers on Product Hunt. The dashboard above tracks how Agnos LLM gateway performed against the three products that launched closest to it on the same day.
Who hunted Agnos LLM gateway?
Agnos LLM gateway was hunted by Sivaprakash Kumar. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of Agnos LLM gateway including community comment highlights and product details, visit the product overview.
We open-sourced Agnos Proxy: a control plane that contains the LLM gateway you already run.
Most gateways fuse two jobs - translating your request to each provider, and governing it (keys, budgets, guardrails, cost, audit). Fuse them and your provider keys live inside the code parsing untrusted input, and switching gateways means a rewrite.
Agnos separates them. It contains LiteLLM, Bifrost, Portkey, or a built-in engine as swappable adapters behind one OpenAI-compatible endpoint:
Change one line, keep your SDK.
Route each provider to the gateway that serves it best, or swap one at runtime.
Keys stay Fernet-encrypted in your vault, injected per request. The gateway stores nothing.
Budgets that stop spend before it happens, PII/secret guardrails, cost attribution and audit, the same across every gateway.
Self-hosted, MIT, about 1 ms overhead.
Live playground: agnos-llm-gateway.site
Repo: github.com/siva010928/agnos-proxy-oss
Feedback and "which gateway should we contain next" welcome.