Envoy is legendary in (dev)ops circles, but I don't understand what it lends to the AI space. I feel like building a separate backend service that runs behind envoy would make more sense but that's just me.
Show HN: Arch – an intelligent prompt gateway built on Envoy
11–20 of 20 posts
Re: Show HN: Arch – an intelligent prompt gateway built on Envoy
#12Tetrate and Bloomberg want to contribute their code to Envoy to create "Envoy AI Gateway", similarly to how there is an "Envoy Gateway" spec. Do you see this as being complementary or competitive with your work? https://tetrate.io/press/tetrate-and-bloomberg-collaborate-o...
Based on the press release, its kinda hard to tell exactly how different/alike we will be, but Arch will always be "designed-first" for prompts and LLM application workloads without exposing all Envoy related features. And Envoy is "designed-first" for micro-services application workloads. So there will be some overlap but our design principles will deviate over time I feel. But we are very open to collaborating with the community here...
Re: Show HN: Arch – an intelligent prompt gateway built on Envoy
#13Hi, I'm curious how preventing jailbreaks protects the user ? > Prompt guardrails to prevent jailbreak attempts and ensure safe user interactions [...]
Re: Show HN: Arch – an intelligent prompt gateway built on Envoy
#14Re: Show HN: Arch – an intelligent prompt gateway built on Envoy
#15That's quite an overloaded name... Good luck with SEO for "how do i run arch on linux?" :p
Re: Show HN: Arch – an intelligent prompt gateway built on Envoy
#16Lately, I have seen few gateways around LLM. Namely, openrouter, portkey.ai, etc. My key question is, who would be the ideal customer who would need a proxy or a gateway like this? Why couldn't it be an extension or plugin of existing LBs, proxies etc.
Sidenote: Arch is def interesting!
A typical user we've seen at Portkey is a mid or a large size eng org where a central "Gen AI team" has now come up. This Gen AI team builds services that the rest of the company uses to build whatever AI features or products they want.
To build such a service, they need traditional API Gateway features like rate limiting, access rules, and also AI-specific features like universal API to multiple LLM providers, universal routing, central guardrails, AI-native observability + central dashboard for other stakeholders, and more.
It can absolutely be a plugin on top of existing Gateways.. like we've explored putting Portkey on Kong, but the need for a dedicated AI Gateway still remains, that can do all of these things I described in an easier way.
Probably, solutions like Langchain/Llamaindex etc. also fit in somewhere here, but a dedicated service for "ops" related issues for LLM APIs is something that we're seeing orgs adopt as a good practice.
Re: Show HN: Arch – an intelligent prompt gateway built on Envoy
#17We picked it for the second-chance pool (https://news.ycombinator.com/item?id=26998308) when it was already several days old, and by the time the thread got going, it basically got evicted from cache. This is a manual workaround to correct that. Sorry all!
I've moved the comments from the other thread hither, which is why most of them are hours older than the current submission is.
Re: Show HN: Arch – an intelligent prompt gateway built on Envoy
#18Re: Show HN: Arch – an intelligent prompt gateway built on Envoy
#19Since its an envoy filter it was trivial to setup in Istio Ingress. Good stuff.
Re: Show HN: Arch – an intelligent prompt gateway built on Envoy
#20Since its an envoy filter it was trivial to setup in Istio Ingress. Good stuff.