 Okay, hi guys. Thank you so much for joining us. So you know where you are. We'll talk real quick. This is a speech-provided speech story about that. We are solo. We are an application networking company very aligned to the networking and the ceiling vision that Thomas has. So it's actually working very nicely. We believe is that the future of the networking is the piece of an open source project that we each choosing to make a big haul. We work with a lot of customers for the during the last years and we kind of like notice a pattern and that pattern, we're calling it cake. And what did we see is that the vision is that those project that we all know, right, Scylium for CNI, MBN slash STL for service mesh, Kubernetes for the orchestration platform Envoy proxy for the layer seven and Spiffy for identity, is basically the layers and the piece that we need to do the future of the networking. Now, it's very simple which each of those layers are actually come together and responsible to. We started with Kubernetes which is basically the orchestration. Then Scylium was doing layer three, layer four connectivity. What's going on? Then a workload entity with Spiffy Inspire, East West connectivity policy with MBN and STL and last and not least, basically the ingress and egress API get way with Envoy. So now is that true, right? Why, how did we came with that conclusion? So honestly, you know, usually we, our community is basically following a lot of the hyperscalar. So let's see what they think about that. And what we say is that Google is actually aligned to that vision 100%. They are using Scylium 100%. This is what you basically know, data plan, V2 using it for the CNI. They are using STL intensively. As you know, they are the founder of it as well as going to a really soon MBN. That's where we're working with. Kubernetes, you know guys, that that's what they're using. Envoy proxy with traffic director as well as Spiffy and Spire. If you're looking at Microsoft pretty much aligned, the only thing is that they do not have get way that is Envoy based yet. We'll see if they will come. But they are very aggressive going on to the service mesh. I think that was their announcement. I expected another announcement this conference. Okay, so what about Microsoft? Microsoft is always the strange. Amazon, that's what I said. Oh, I meant Amazon. It's a very, very different cloud. They usually follow up, right? They really need to get a conviction for the community that that's the direction. This is why eventually they launch EKS. But if you're looking at the rest, they're basically, if you're looking at the rest, you know, they don't really have the right solution or they're not following the community. They all will have to say that they're really aggressive on us on the NBN and STO. So, you know, that's the way they're basically leveraging by partner. And then Red Hat, again, same thing. I mean, in the nutshell, it's they supporting the same stat. And honestly, way more customers. So now let's talk real quick on STO. Really just in line in case you don't know what it is. It was launched with Google IBM and Lyft in 2017. It's a really, really diverse community. And I think this is the key. A lot of companies contributing to it. It's very diverse community. But forget about that community. I can tell you as a customer, we have over 200 customers that we are using, that using STO in production. And we're helping them from everywhere. So most likely you are using it as well. As you know, it's part of the CNCF now. So it's announced and it's graduated recently. So it's a well, you know, robust project. And we even have a new splash here, Lizzie. I don't know if you saw it. Izzy, the dolphin. I don't know if you see. It's pretty cool. So that's awesome. The other thing is that, as I said, we're talking about MPN. You heard it, serverless, maybe. It's server-side less service mesh. But what you don't know is that we're working very aggressively for it. I will argue for over three years. And finally, we can announce it as a beta disk conference. So I'm really, really excited about that. You should try that. I know the perception of STO was before. You should try that. Because it will simplify your user experience. It will take drastically your cost and it's improved the performance. And you can read some of those resources. I will recommend you to go and listen to that talk. This is Christian Post on my calling and this is a talk about a service mesh and it's comparing very nicely. Scyllium service mesh and STO in a very objective way. Okay, Scyllium and MPN. So I don't know if many of you know this, but two years ago, we actually announced that announcement here, like in Kupkon. We basically announced that we're really excited about Scyllium. We predicted that that would be the future. Great job, ISOvelin and Scyllium team. And we wanted to join that. So we announced it two years ago and we did quite a lot in the community in order to try to be a partner. For some reason, we shadowed but we are working and aggressively contributing and working as part of the community. As we said on the first talk, it's very important to us to bring the layers together. This is why we're contributing right now. We're contributing, verify that MPN is going to work seamlessly with CNI, specifically Scyllium because we're selling it. So it's really, really nicely working together. We also announcing our support for Scyllium, a glue networking for Scyllium. So look, we're working with a lot of open source customers. We saw where they're shooting themselves off the foot. We created an insight engine that helping them not to do that. So this is just example of how it looks, what is giving over the open source but that's the provider guys and so on. So if you are interesting, we would love to work with you as we're working with a lot of other customers. But all of this need to be wrapped somehow. So networking will happen, right? I'm pretty sure. And the vision is to make it easy to use and as MPN as it can be, right? But in the nutshell, eventually you're using all of this in order to implement that on your organization. And the question, how should we best do that? And as you know, we are big friends of open source and therefore we are very, very excited about backstage and really, really excited about the project who is actually right now, at least we see it in our customer. I can tell you all of our customers are not accepting. Looking at that exactly project. How can we take project like Cilium together with MPN and make it so easy and so adoptable in your organization? I think this is the answer. I think that I'm very excited about what we can do there. We have our own distro for solo, working with all those customers. If you're interesting, please reach out. And I think that's all I have. Thank you for my time.