 So, hi everyone, my name is Edith Levine, I'm the founder and CEO of SolarIO. Solar is a company focusing on application networking, which means that we're doing everything we need in order to make your application in all the connectivity, security, and observability that it's made. We have, we're running some of the biggest STO deployment in the world, including a hundred of customer all over the world. We have recently raised another $135 million in a billion dollar valuation. We make us a unicorn. More important than this, we are really, really strongly participating in the STO community. So, some of the people who are working in Solar is people like Christian Posta, who wrote the last STO in action book. Olin San and Araj, who are two of the TLC member from the five who exist in the ecosystem of STO. But, Solar is all about that, which means that everyone working in Solar is focusing on service mesh. So, what are we doing? So, we basically have a platform, it's called GLU. And in that platform, we have two building blocks. The first one is GLU Getway, and the other one is GLU Mesh. So, it's kind of like deep-dying to what it is this. So, GLU Getway is very simple, right? We basically took the STO Getway and worked for the last five years with our customers to build the best API Getway that exists in the market. Basically, it's very simple. We had a developer portal, external, all with plugability, rate limiting, transformation, everything you need in order to, including federation, including to make your Getway, the default Getway of STO, working as a full-blown API Getway. But we have from our customers that they are very excited about GraphQL. So, we kind of like push the limit a little bit more. What we have for them is that basically the application team, they're interesting in GraphQL and they're coming to them and ask them to basically forward all the traffic to this GraphQL server. And in the GraphQL server, the application team is basically needed to do quite a lot of stuff in order to make it happen. They need to create a schema and resolvers. They need to build it. They need to make sure that security apply, and so on and so on. There is quite a lot of burden here. And also, everything right now is with extra hope. So, we kind of look with thinking, what can we do in order to actually save that for a customer? What we did was basically do GraphQL and build it into Envoy. So, basically right now, we teach Envoy how to be a GraphQL server. So now, the only thing that they need to give us is basically a schema and a resolver. There is a lot of build-in, but you can also write your own Wasm resolver. And then everything else is declarative. You basically can, Envoy just will get a request of GraphQL and know how to do this, including even stitching. So, it's pretty unique. So, that's what is Getway. Pretty simple concept. In GlowMesh, we basically, our STO distro. So, if you think about it, you guys all probably know our STO is working, but if you only have one cluster with STO, we're already doing quite a lot for you to make sure that you are successful. We first of all, AppStream first, right? We are working a lot with the community. If there is anything that we need to put AppStream, we are putting it AppStream. Besides that, we have a special build, like feats and arms and anything else you need. We're giving you N minus four if you, because at least our customer are not upgrading every three months. And we make sure that if there is any CVE, we basically put forward them to all of that. Besides that, we're taking over your life cycles of STO management if you're interested in this. And we also put a lot of functionality that our customer asked, like cert rotation and brought all the functionality of external and rate limiting to the east-west as well. Okay, so that's great, but no one running one cluster. So now the question is, what do you sue? Our customer is running between five cluster to 100 clusters. We even have the biggest customers who's basically running on 60 data center with thousands of instance of STO all over the world. So the question is, what are you going to do? Come to each of your STO and kind of like configure it? No, you need to build something. So we kind of like build it for you. That's the management plan. That, giving us the ability to basically discuss, get all the life cycles of your STO, push configuration in a very secure real architecture and make sure that all your infrastructure is working really well. Because we have a picture of all the clusters, we can do also route bans locality and basically make sure that if the user is not available on the same cluster, it will fell over to the cluster next, to the data center next and so on. That plus the get way and the developer portal give you everything you need in order to basically run your application. Inclusion there is one more feature that is extremely important, which is kind of like come to the basic of what we doing service mesh. Why are we excited about service mesh? Why are we excited about Kubernetes altogether? I mean, there is one aim to it and that aim is basically to run your infrastructure and care part of it and delegate it to your application room team. That's basically all the reason that we're doing the thing that we're doing. So that's exactly why we basically create the concept of workspace that is giving you exactly that ability. This is the admin view, right? So basically now as an admin, I can see my cluster and the standard and my STO and everything that I need and also the workspace. But if I'm the application owner, I don't need to know anything about that. I'm only going to view the C, my view on my workspace with observability to my workspace and the ability to basically also import and export policy and destination. Okay, so that's what we have. This is what the glue platform is, but I really excited today to introduce another piece to the puzzle and that's basically the glue network. So what is the glue network? From today, basically glue will drive CNI and Kubernetes network policy. Think about it in that demo, which I cannot show you because I don't have enough time. We basically have two cluster. On those cluster, you have STO in one of them, you have Celium in the other one, you basically have a colleague. You have both of them registered to the management plane. And basically in order to create defense in depth, when you're telling me that one service cannot talk to the other one, we are going to translate it to a STO configuration but we're also going to actually translate it to Celium or to CaliGo in that case. So think about what we're just doing. We basically take the leverage of the orchestration and the multi-cluster and the multi-tenancy and the workspace and bring it this power to Celium and to CaliGo and to other CNI that you are interested in. So that's great, but we actually personally, we're really hot about EBPF. In the last conference, me and you will talk about how you can actually supercharge your service mesh and leveraging technology like EBPF. We basically talk in STOCon about the same concept about sideless, basically, with EBPF versus sidecar in service mesh. We wrote a blog that explaining this and even internally after working for two years with EBPF was extremely important to us to give the community the tooling that we built, Bumblebee, which is basically a docker for EBPF that allowing you to run it, to build it, to run it, to deploy it and share. So because we are so excited about EBPF, it's really important to us that our platform will have better included but swappable. So we will drive any CNI that you want, but we also going to ship your Celium. And we're going to do exactly what we're doing with STO, but right now with Celium. So basically, we will glue them together, we'll make sure that they work seamlessly together and we'll make it extremely, extremely easy for you, the customer. So again, it's better included by swappable. You don't have to use Celium, but if you do, we'll give you support and make sure that we are patching it. So basically, we'll do exactly what we're doing with STO, right? If you're interested in it, it's coming for free with our product, right? If you're not interested in our product, which is totally fine, we will give you support, enterprise support on Celium. We are very into education. And therefore, we have a big platform of workshop and certificate program for STO and Envoy. Now we added recently EBPF and now Celium as well. And Lee and Rosano is in the TLC member of STO, is going to do a hood and going to talk about the people who are working on it for years behind the scene. So whether we're giving you, we're giving you a platform, right? That has three building blocks. Glue Gateway, GlueMesh and Glue Network. You can decide at which one you want to choose. Each of them is a standalone product, but you can miss the match and basically make it seamlessly working together. So we are solo. If you are interested in working with STO, Envoy, EBPF or Celium, we are hiring and we would love to have you on board. Thank you so much.