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
Olyx
One integration. Every AI request governed and traced.
Most teams hardcode a provider SDK, ship fast, and immediately lose visibility into what ran, what it actually cost, or whether sensitive data leaked. Olyx sits in the request path — one base URL change. Policy enforcement, PII redaction, cost-aware model routing, and a tamper-proof audit trail on every request. No stack rewrite. Provider credentials stay in your environment. Built for engineering teams past the prototype.
Olyx started as an internal tool inside an AI infrastructure platform I was building. I was routing between a frontier model for complex data extrapolation and a private model for routine tasks—but I had no real-time way to verify if a routing change was actually saving money, or if it had quietly started leaking PII to an unapproved endpoint.
Cost tracking was a bolted-on afterthought. Auditing production meant manually stitching together scattered provider and application logs. I spent more time maintaining proxy infrastructure than building actual product features.
So I scrapped the multi-language library approach — maintaining the same logic across Ruby, Python, and TypeScript codebases is a nightmare. We went CLI-first instead. Your stack points at one endpoint. The language it's written in stops mattering.
Policy enforcement and PII masking happen before the call reaches the provider. Every routing decision is recorded from request one — tamper-proof and exportable to meet EU AI Act record-keeping requirements.
Early access is open — link in the post. Happy to answer anything on the routing engine, architecture, or what you're running into in your own stack.
About Olyx on Product Hunt
“One integration. Every AI request governed and traced.”
Olyx was submitted on Product Hunt and earned 7 upvotes and 1 comments, placing #62 on the daily leaderboard. Most teams hardcode a provider SDK, ship fast, and immediately lose visibility into what ran, what it actually cost, or whether sensitive data leaked. Olyx sits in the request path — one base URL change. Policy enforcement, PII redaction, cost-aware model routing, and a tamper-proof audit trail on every request. No stack rewrite. Provider credentials stay in your environment. Built for engineering teams past the prototype.
On the analytics side, Olyx competes within API, Developer Tools and Artificial Intelligence — topics that collectively have 1.1M followers on Product Hunt. The dashboard above tracks how Olyx performed against the three products that launched closest to it on the same day.
Who hunted Olyx?
Olyx was hunted by Moses Njoroge. 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 Olyx including community comment highlights and product details, visit the product overview.
Moses Njoroge
Olyx started as an internal tool inside an AI infrastructure platform I was building. I was routing between a frontier model for complex data extrapolation and a private model for routine tasks—but I had no real-time way to verify if a routing change was actually saving money, or if it had quietly started leaking PII to an unapproved endpoint.
Cost tracking was a bolted-on afterthought. Auditing production meant manually stitching together scattered provider and application logs. I spent more time maintaining proxy infrastructure than building actual product features.
So I scrapped the multi-language library approach — maintaining the same logic across Ruby, Python, and TypeScript codebases is a nightmare. We went CLI-first instead. Your stack points at one endpoint. The language it's written in stops mattering.
Policy enforcement and PII masking happen before the call reaches the provider. Every routing decision is recorded from request one — tamper-proof and exportable to meet EU AI Act record-keeping requirements.
Early access is open — link in the post. Happy to answer anything on the routing engine, architecture, or what you're running into in your own stack.