Foreign, can you describe what challenges you have in your organization? So Ori is an open source company building out a planet scale, Network infrastructure, so we're building a 15 to 20 region, Global Network, where Cloud, neutral, kubernetes, neutral or kubernetes native, and of course we use the Ori open source tools and as we develop this network, one of our challenges is figuring out pricing and basically, we charge our customers not on the number of IDs or monthly average users, but we do that on the basis of traffic.

So we need a sophisticated professional grade solution to really manage our traffic and meter it, especially. Why did you pick so so? As we started looking, we wanted to replace our nginx Ingress controller with a kubernetes native Ingress or API Gateway solution in order to implement the requirements we have towards rate limiting and controlling all the traffic flow of course, Ori as a software company and an open source organization consider doing it ourselves and using the open source route due to the teams.

You know huge interest in the whole networking and security stack, and we also, you know, wrote a number of MVPs with projects such as Ambassador traffic, Citrix and Contour before really choosing glue, Edge Sr as our solution, so our challenges are large and also the scope of the project is also large and we looked for a partner that could live up to those challenges. I think it was generally hands down. You know the best support for our requirements for rate limiting across multiple clusters, and you know in general, we like the architecture of glue.

We like the product, maturity level. We like the easiness configuration and the whole management plane. We, like the support for dynamic rate, limiting configuration, that's very important for us. Frankly, we like the sales team, I, know that's unusual to say we like the attitude. The customer experience we got in the very beginning was a factor. You know we were given access to very good quality field. Engineers I think that compared to some of the other companies was a major factor that we had.

You know this direct contact that allowed us to make a complete MVP and do that on our end and with solar very quickly. With that kind of access to solo Engineers, we were able to develop the Prototype very quickly and discuss any topic related to glue and Envoy, and of course that was extremely important for us. We didn't have you know all the experience we needed, I think in the beginning and then no surprise.

You know pre-sales turned into customer support and even after signing the contract, we um we got improved quality of support, how's the experience with solo. So far the conversations um I had with the solo team, with Edith with Chris. Of course, these are extremely impressive individuals, but also just great cheerleaders for the product and can go very deep into the technology and very impressive and sort of similar to how worried believes software companies should tick, and so we look forward to building on those relationships. I think we're.

You know really happy that we're able to implement our requirements pretty quickly or is up and running as a as a Global Network. So we did this more or less. On the fly, so it was important for our team. We had no down time. You know. Support offered by solo was extremely valuable and it really allowed us to progress quickly, not only in the development, but also in the whole deployment. We've had great support for the global rate, limiting requirements that we have.

We I believe that that's a real differentiator in how glue and and solo put that together as an example, we have support rate limits per host. We can go to different tenants or or endpoints or paths, and those are also shared between clusters. So that gives us a lot of flexibility. It simplifies the way we set up our sort of proxy infrastructure because it doesn't require us to do that in multiple places. So that's also very good.

The rate limiting support for persistence is very important for us, as we scale clusters and deploy kubernetes in a larger ways. They're points that make it extremely beneficial to work with, with solo, and especially with blue in this particular type of network deployment, so I think that's a good summary of our experience.

Foreign.