 Hey everyone, I'm Jake Laverne, head of product at Docker and I'm excited to be here with you all at WASM Day. And as a member, a proud member of CNCF with a seat on the technical oversight committee that Justin Cormack or CTO holds, Docker gets a chance to see a lot of exciting projects coming through. So a lot of the WASM projects coming through are in sandbox status. Justin and team get to work with the maintainers of these projects and especially through our collaborative efforts on the container D project, we get to learn a lot about what's coming along. So projects like Fermion and Spin and many others, WASM Edge and WASM time. And it's a really exciting time to be on a journey together to help each other build great software and make the most of secure and reusable components. This is what Kelsey was talking about, being on a journey together as a community because there is a big burden to maintaining what we are creating here. And I think we all want to share in that burden. Back in 2019, Docker saw the promise of WebAssembly on the server. And that's why we were experimenting with WASM and WASI even back then. And there was a famous tweet actually that Solomon Hikes, our founder, put out back in March of 2019 that said something like, if WASM and WASI had existed in 2008, we wouldn't have needed to create Docker. That's how important it is. And all hyperbole aside, we believe even more so today that WASM is an incredibly important technology on the server side. That's why we're using our learnings from containers to help the WebAssembly community and more importantly to help millions of developers discover WASM. That's really what we're trying to do is help create that bridge. In software, we build things in the context of what came before so that we can benefit from past learnings and so that we can smooth adoption for the masses of developers. We don't want everybody to have to approach WASM from a Greenfield application perspective because there are already hundreds of millions of non-Greenfield applications out there already written in Java, in Go, in Python, in Rust. We want to let developers use the tools that they're comfortable with and that they know and love. And Solomon even followed up on the next day to his tweet and talked about a tight coexistence between containers and WASM modules and the entire ecosystem actually. And this coexistence is what we've been working towards together with the community. You should be able to run a WASM module side by side with a SQL database and a cloud message queue, all accessible from your desktop or from a Kubernetes cluster. So later on today, Ivan Padrasas in the office of our CTO is giving a lightning talk, everything you wanted to know to adopt WASM now where you can hear more about how to actually get started and run WASM with the tools that you already know and love. A big key to this vision is bringing the industry together across a variety of components and run times. And in this, we share a mission with the Byte Code Alliance, which was formed to shepherd exactly this type of cross industry ecosystem and collaboration. Byte Code Alliance mission includes the statement that the problem we're attempting to solve is fundamentally a cross industry problem. Our intent is to bring groups together to solve problems for everyone. This is the Byte Code Alliance's intent. This is also Docker's intent. As a community, we've learned a lot about what made Docker successful, the types of workflows and developer experiences that it takes to make containerized development possible, not just for a few, but for all developers. Developers like build, share, and run that work seamlessly between environments from your laptop all the way through to production environments were indispensable for the widespread adoption of containers. And we believe that some of these learnings about developer workflows and developer experience can help bring WASM to the most inclusively large set of developers possible. And to do this, we should show all developers the possibilities that WASM opens up. In terms of performance and overhead, in terms of isolation, in terms of platform agnosticism, all the things that build on top of what we've already gotten place, we need to show them concrete mechanisms for incorporating these into existing work and existing applications. We need to build a bridge for developers. And so to that end, we've been working with more teams and projects to make sure that Docker can support as many WASM run times as possible. As of late March, this now includes spin, slight, WASM time, and WASM edge, all critical projects within the ecosystem. And in addition, run WASI is a multi-company effort to make it easier to write container D shims for WASM workloads. Last December, the run WASI project was donated and moved to the CNCF container D GitHub organization. And with a lot of work from people at Microsoft and Second State and Docker and others, we now have enough features in run WASI to run WASM containers with Docker or in a Kubernetes cluster. There's still a lot of work to do, but there are enough features for people to start testing. So I'd encourage people to play around with the WASM integration in Docker to play around with run WASI to run containers inside Kubernetes. You can do this all using Docker desktop. And if you'd like to chat with the run WASI maintainers, be sure to join in on the CNCF's run WASI channel. With that, I hope you enjoy WASM day. I hope you enjoy the entire conference. Please find me or Justin or others from Docker around the conference all day today and this week. Thank you very much.