 All right, we're going to get started. Thank you all for being here today. My name is Jesse Suin. I'm a co-founder and CTO of Acuity, and one of the original creators of the Argo project. So we're here at ArgoCon, and you might expect me to be singing the praises of Argo CD and GitOps. But actually, today I'll be spending a little time kind of explaining some of the challenges with GitOps and some of the things that Argo CD isn't great at and why we feel that more tooling needs to be developed to improve that developer experience. A little bit about Acuity. We are a team founded by Argo creators, leads, maintainers of the Argo project. And we help companies implement GitOps with Argo. Acuity offers an easy to manage platform for running a more scalable and secure version of Argo CD. And we also offer solutions and support for the Argo project. So if you think about what GitOps is, it's really more of a philosophy than and not really a solution. Basically, GitOps is just adding additional rules and constraints on how you should be deploying changes to your environments. But it really doesn't provide any guidance on the practices or processes to go about achieving that. So at the end of the day, GitOps just made things harder for everyone. Because a lot of this stuff that we were previously doing before GitOps in our CI pipeline no longer worked after GitOps. And when we built Argo CD, we built it as a tool to help practice GitOps. But it was never enough. It's great at deploying changes from a Git repository to a single environment. But there's a lot of things that it doesn't do. First, it has no understanding of multiple environments or a concept of a pipeline to orchestrate changes across environments. It doesn't even help you write changes to Git because it expects some other tool to do that ahead of time. And finally, once it does sync an app, it doesn't do any verification of that update after the fact, such as running any form of tests or analysis. So over the years, a number of small features and Argo ProjLab projects have cropped up to deal with these limitations. And I call these a spot solutions because each of these tools or these features only solve one piece of the puzzle. And none of these consider the bigger picture or the overall developer experience. And with all these approaches, it just feels like we're kind of trying to brute force Argo CD into something it was really never designed to do. So we set out to kind of build a tool that approaches the challenges of GitOps in CD holistically. We wanted the solution to provide a flexible pipeline to define how changes are promoted between different environments. We wanted an intuitive UI that gives a better understanding about what was or needs to be or about to be promoted. We wanted to hide the GitOps nuances to developers who frankly don't really care about GitOps. And we wanted to provide guardrails ensuring that promotions are happening within defined processes. So Cargo is an open source project that we recently announced to fill in these gaps. And it's a multi-stage GitOps application orchestration tool for promoting changes through multiple environments. And our biggest goal of Cargo is to provide a better, more intuitive layer on top of your GitOps tooling. We want to enable application developers to safely promote their apps through multiple environments. For normal day-to-day operations, we envision app developers to be visiting the Cargo UI more often than the Argo CD UI because to promote their changes day to day. They still go to Argo CD when there's a problem, you see logs, events, but in the happy path, Cargo would be used more often to deploy things. So with Cargo, you'll get better visibility into your promotion process. You're seeing all your environments at a glance, understanding what's running, where, and what's safe to deploy. You'll be able to see history of what was deployed along with links back to your source code repo and commit history. And we built it with the GitOps use case in mind. And one of the unique features about our Cargo is its ability to promote configuration, not just images. And in other words, you're able to promote manifest changes like environment variables from stage to stage. Cargo makes Git writebacks and rollbacks really easy with one click. And finally, you can start practicing progressive delivery by qualifying your artifacts before they're allowed to deploy to other stages. So if you're interested in Cargo, check out our GitHub. And we also have a Discord server where you can ask questions, chat with other users, and also where we host office hours. So the biggest thing you can do is just give us feedback, try it out, and yeah, start the Git repo. Thank you.