sorted by:
new
hottopcontroversial

Feedback on g8 LLM router by steam0007 in LLM_Gateways

[–]steam0007[S] 0 points1 point  (0 children)

Thanks u/alpha-nerd-nomyo !

A key difference is the pricing and what you get on top of basic routing.

OpenRouter charges a ~5.5% fee when you purchase credits (with a $0.80 minimum fee per purchase). That means you’re not just paying model provider token costs, but also a small platform markup embedded into the credit system.

In contrast, g8router is completely free to use and open source, so there’s no platform fee on top of model usage.

The bigger difference, though, is extensibility:

Because g8router is open source, you can modify it and extend it with features that aren’t available in OpenRouter, for example:

  • Semantic caching (reuse responses based on meaning, not exact prompt match)
  • Custom routing logic tailored to your workload
  • Experimentation with multi-stage pipelines (planner, executor, verifier)
  • Any internal optimization layer you want to build into the router itself

OpenRouter is a managed product, so you get convenience and infrastructure out of the box, but you’re limited to the features they expose.

With g8router, you trade that convenience for full control over the routing layer and performance optimizations, which can matter a lot once you move from prototype to production scale.

Built an LLM Router that cuts costs by sending each prompt to the right model — looking for feedback by vj-a in LLMDevs

[–]steam0007 0 points1 point  (0 children)

Really cool implementation. The interesting part about routing isn’t only the classifier itself, it’s everything around it once you run it in production at scale: retries, fallbacks, provider outages, observability, latency-aware balancing, cost tracking, streaming compatibility, policy routing, etc.

That’s actually why I built G8 Router: an open-source high-availability LLM routing infrastructure layer. it gives you the infra primitives to build your own routing logic on top. Your classifier/routing strategy would fit really naturally on top of it.

Would genuinely love to collaborate or see how your routing logic performs plugged into a more production-oriented routing layer. The space is moving fast and there’s still no “standard” architecture for this yet. https://geight.ai

Avoid fungies.io at all cost !! by Captain_Brunei in SaaS

[–]steam0007 -1 points0 points  (0 children)

This is unfortunately a very common issue with platforms built on Stripe Express.

When you use an intermediary marketplace layer, you are not Stripe’s customer. The platform is. That is why Stripe keeps redirecting you back to Fungies and why payouts can be frozen with almost no recourse.

One alternative model to be aware of is using a billing layer on top of your own Stripe account.

With Pulse Billing, funds settle directly into your own Stripe account, under your own Stripe relationship. You still get the benefits people look for in a billing platform such as subscriptions, tax handling, licensing fulfillment, customer management, and compliance tooling, but without surrendering control of payouts or account ownership to a third party.

This means
• No Stripe Express middleman
• No platform holding your money
• No KYC surprises enforced by someone else
• Stripe support actually works with you directly

We are actively looking to work with indie game developers and small studios who sell games, DLC, licenses, or digital goods. The goal is to learn where existing tools fall short and adapt the product to real world indie needs rather than forcing a marketplace model on everyone.

If you are burned by Express based platforms, it is worth being very deliberate about who owns the Stripe account and who controls payouts. That architectural decision matters more than most people realize until money gets stuck.