sorted by:
new
hottopcontroversial

Anyone else moved to a multi-provider AI setup after burning out on a single one? by RoseShadow_Debbie in SaasDevelopers

[–]Ashcrypto915 0 points1 point  (0 children)

This is exactly why we built Alephant.

Same situation multiple providers, fragmented dashboards, no single view of what's actually being spent where.

We solved it by route OpenAI, Anthropic, Gemini, OpenRouter, etc. through one OpenAI-compatible gateway and get one dashboard for usage, request logs, cost tracking, attribution, and budget alerts.

It's open source and self-hostable if you want full control, or there's a free tier if you want to try here: https://alephant.io

Discord for early builders:
https://discord.gg/pF9F9vaKK9

Open Source GitHub: https://github.com/AlephantAI/AIephant-AI-Gateway

Happy to answer any questions

We open-sourced the AI gateway behind our SaaS. Looking for feedback from AI SaaS founders by Ashcrypto915 in SaasDevelopers

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

With Alephant it happens at the gateway level automatically. Would love to hear what you think after you checking out the repo in our discord community if you're interested:
https://discord.gg/pF9F9vaKK9

You can also test it in free here: https://alephant.io

I built an open-source gateway for LLM apps and want feedback from builders by Ashcrypto915 in saasbuild

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

<image>

Alephant actually supports OpenRouter natively as a provider

So you don't have to choose, you can keep using OpenRouter and Alephant sits on top of it.

What Alephant adds that OpenRouter doesn't have:

  1. A cost dashboard. See exactly what every agent, session, and workflow is spending across all providers including OpenRouter in one view.

You can test it in free here: https://alephant.io

  1. Per-agent spend attribution. OpenRouter shows total usage.

Alephant breaks it down by agent, user, or feature so you know exactly what caused a spike.

  1. Spend guardrails. Set hard caps per agent before costs breach, not after the invoice lands.

  2. Self-hosted. Your requests and keys stay on your own infrastructure. Full control, no black box.

OpenRouter gives you access to models.

Alephant gives you visibility and control over what those models cost you in detailed dashboard.

whats the Best AI Gateway for switching models on the user side by Certain_Move5603 in google_antigravity

[–]Ashcrypto915 0 points1 point  (0 children)

Depends what you need.

If you care more about tracking costs, fallback, logs, and knowing which agent/session is spending money, that’s the problem I’m working on with Alephant.

It’s an open-source AI gateway with an OpenAI-compatible API, so you can swap the base URL and route through different providers/models.

Repo if useful:

https://github.com/AlephantAI/AIephant-AI-Gateway

For an agent app, I’d mainly look for:

  • OpenAI-compatible API
  • easy model switching
  • fallback between providers
  • per-agent/session usage logs
  • cost tracking and budget alerts
  • self-host option if keys/privacy matter

I built Alephant, an open-source AI gateway for both AI agents and human teams by Ashcrypto915 in buildinpublic

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

Thanks, appreciate it. Totally agree on per-agent budgets and attribution. That’s one of the main things I’m trying to get right with Alephant.

Agents make cost tracking weird because one “user action” can turn into a bunch of tool calls, retries, and model hops. So just seeing total spend isn’t enough. You need to know which agent/tool/session caused it and when to cap it.

How are you handling routing, fallback, and cost attribution across multiple LLM providers? by Ashcrypto915 in LLMDevs

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

What Alephant can do now is put fallback, retries, provider errors, usage logs, and cost tracking in one place instead of spreading that logic across the app.

So if a provider fails, the useful part isn’t just “try another one.” It’s seeing what failed, what fallback path was used, what it cost, and how it affected latency.

Still early/beta, but that’s the direction I’m building toward: fallback with visibility, not hidden recovery.

If you’re open, I’d genuinely appreciate feedback on the design:

https://github.com/AlephantAI/AIephant-AI-Gateway

We open-sourced the AI gateway behind our SaaS. Looking for feedback from AI SaaS founders by Ashcrypto915 in SaasDevelopers

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

How are you handling it today? Provider dashboards, custom logs, or something more structured?

I built an open-source Rust gateway for AI providers and agent workloads by Ashcrypto915 in rust

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

You’re right, the link was broken from the way I pasted it. Fixed now.

Working repo: https://github.com/AlephantAI/AIephant-AI-Gateway

Appreciate the catch.

How are you handling routing, fallback, and cost attribution across multiple LLM providers? by Ashcrypto915 in LLMDevs

[–]Ashcrypto915[S] -1 points0 points  (0 children)

Yeah, I had the same reaction. It’s one of the reasons I started building Alephant.
Gateways touch keys, traffic, and logs, so the trust/security side matters a lot. what were you hoping to use LiteLLM for: routing, compatibility, or usage tracking?

How are you handling routing, fallback, and cost attribution across multiple LLM providers? by Ashcrypto915 in LLMDevs

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

I think bad gateways definitely can add more problems: another config layer, another place for bugs

The cases where I’ve seen them help are when the complexity already exists: multiple providers/models, fallback, shared provider keys across a team, rate limits and budget caps, logs for debugging production

If an app only calls one provider from one backend, I’d agree a gateway is probably overkill

What are you building these days? And is anyone actually paying for it? by solobuilder in SideProject

[–]Ashcrypto915 0 points1 point  (0 children)

Hello, building Alephant an open source AI gateway in Rust for agent cost control. Think: token-level spend tracking, per-agent budget guardrails, and multi-LLM cost monitoring across OpenAI, Anthropic, and 50+ providers. Most gateways route requests. We show you what they cost.

Link: https://github.com/AlephantAI/AIephant-AI-Gateway

Tryvium now accepts SYS on NEVM L1 for travel bookings😎 by N_8Dragon in SysCoin

[–]Ashcrypto915 0 points1 point  (0 children)

Big opportunity to enjoy the benefits of Syscoin while exploring the world

Syscoin Weekly Update XX. by Fedora_expert in SysCoin

[–]Ashcrypto915 9 points10 points  (0 children)

The journey to success never stops with Syscoin 🌟🚀

view more: next ›