How robust is the custom routing mechanism in LiteLLM? I know it has user and IP/regional. The conditional routing offered by PKGateway seems to be more robust than these and by the looks of it, pretty easy to adjust for any use case as it hooks into metadata labels. Hooking this into running user/ps logging >> meta opens a whole world of OS takeover bliss with simplicity. This is an off the cuff comparison & what went through my mind when quick browsing the Gateway GHio. Please let me know if LiteLLM has this covered with the same flexibility. Again I say... "How robust is the custom routing mechanism in LiteLLM?" because my comment is more of a potential lead than an affirmative statement.
i watch your videos often. in a lot of your videos there are notification sounds. that is distracting as you never know if that was on your own computer. as a friendly feedback: i'd recommend disabling them. anyways, great content!
Interesting demo!
Glad you think so!
btw what's the diff to litellm(gateway) ?
How robust is the custom routing mechanism in LiteLLM? I know it has user and IP/regional. The conditional routing offered by PKGateway seems to be more robust than these and by the looks of it, pretty easy to adjust for any use case as it hooks into metadata labels. Hooking this into running user/ps logging >> meta opens a whole world of OS takeover bliss with simplicity. This is an off the cuff comparison & what went through my mind when quick browsing the Gateway GHio. Please let me know if LiteLLM has this covered with the same flexibility. Again I say... "How robust is the custom routing mechanism in LiteLLM?" because my comment is more of a potential lead than an affirmative statement.
i watch your videos often. in a lot of your videos there are notification sounds. that is distracting as you never know if that was on your own computer. as a friendly feedback: i'd recommend disabling them. anyways, great content!
Thanks for the tip!