 Yes, so good morning, everyone. It's a pleasure to welcome you all back to BackstageCon. I am Balaji Sivasuramanian. I lead the products management for the developer tools at Red Hat. We're excited to be a leading contributor and a big supporter of BackstageCon project. Today, I wanted to share some of our contributions to help increase backstage adoption in enterprises. So we've been working with a lot of adopters and listening to their feedback around specific challenges they face as they try to increase adoption. We have many efforts going on to address these challenges, but today I will just focus on three areas for this talk. One is our enterprise security, other is plugins for enterprises, and then the enterprise orchestration. If you, in case you don't know already, Red Hat maintains all the plugins and all the work they're doing here in open source. So nothing is behind firewall there. Everything is in open source. For most enterprises, Backstage defaults are rules maintenance for model may not work, as it requires sort of rebuilding backstage for RBAC rule changes. Not exactly a scalable way to, a scalable process for the enterprises. So I would like to introduce the RBAC plugin that is available free of charge. You can configure the RBAC policy through a simple backstage UI. You can define roles, associate users or groups to the roles, and then define permissions for those roles. The plugin is leveraging the backstage permissions framework so that any, so any plugin using that framework, including the scaffolder or the catalog, can use this plugin to specify RBAC policies. In the next release, we also plan to support conditional policies as well, and that'll be pretty exciting. And this is available for download today. Next, what I'm going to talk about is software supply chain risks. It's one of the biggest challenges in facing development teams. Well, the notion to shift left in security practices is well understood. It is often difficult for developers to implement that in reality. So luckily, we can leverage the backstage software template to embed the best practices to lower the supply chain attacks. So we're going to set up templates and the plugins enhancements to address these issues. The templates that you can use, you can get in the URL that is shown there, already integrates with the typical steps to ensure software security, including software test bomb generation, signing, provenance, attestation, image scanning, and policy enforcement through the enterprise contract. So this is basically taking the ability for developers to be able to quickly get to deliver software in a secure fashion without them to go figure it out. So you have enhanced the Tecton and Quay plugins. You can see some of these UIs there. But you also integrate with more tools in the next few months. Another favorite topic of mine is the need for plugin validation for the project. Today, there are a number of challenges in the plugin and then the plugin ecosystem. These challenges make it harder for the enterprises to adopt, but also, importantly, risk turning off users' broken plugins as the plugins may not work when you go between one version to the other version. At Red Hat, we went ahead and validated 50-plus plugins so far. I know there are 150 plugins, and maybe there are more hidden plugins that's not there. So we would like to understand what plugins you're using. I showed the previous presenter talk about a few plugins that they're using, but there are a lot of plugins out there. So we want to really get your full survey. So this survey, if you click on it, scan it, for example. And we'll share the results back to the community. It will help us to figure out which plugins people really are using, and we want to make sure we validate them. We want to also automate the whole process. So we're going to try to build the automated tools so that every release the plugin works, and we'll share with the community. And also, building on the validated plugins is obviously that we have to also worry about how to discover these plugins within the back stage, within the product itself. With the upcoming plugin catalogs, Admin can see the installed plugins and install them. Either they can look at the installed plugins or install new plugins from the community or validated plugins. They can also disable, enable, or install, maintain, et cetera, all through it. Obviously, you need a dynamic plugin framework we talked about earlier to be able to do it live from the catalog, but it is definitely something we are working on. The other use case that we hear quite often in enterprise, the need for sophisticated orchestration of workflows. While the users love the self-service capabilities of a software template, you go there, you have a happy path to go through a workflow, and you want to get something done, great. But that's not always the life works, right? There's a lot of processing involved that requires human intervention, such as onboarding, or maybe you need approvals. So we created a new plugin for this purpose called the Orchestrator plugin that is available for you to download. It improves, obviously, upon the software templates that you already have, but it also performs long-running tasks. It will do conditional branching and parallel execution, handle failures better. It will do hierarchical workflows. The other big feature is the event-driven where the workflow can stop and wait for something else to happen before it moves on. So in the animation, you can see that we're able to handle errors in the workflow, as well as open up G.R.Ticket, wait for the G.R.Ticket to close before they continue with the process. So initial feedback has been great with the customers. We would love to get your feedback as well. The next plugin I want to talk about is sort of the new front-end notification plugin that leverages the backstage notification system that I talked to you earlier. This allows you to notify users. The plugins can notify the users directly on the backstage UI. Obviously, it works with the orchestrator plugin I talked to in the previous slide in that it can notify the backstage users if there's any events that are happening. For example, the developer, in the previous case, was getting notified of the G.R.Ticket being created. We are waiting on the G.R.Ticket, so the workflow is basically stopped, but that's the process. That's the process they have in the company, but at least the developer is kept abreast of what's going on. You can also download this today and try it out. A quick plug-in to our commercial product. We have a commercial offering in a fully supported backstage, 24x7 supported. It's an on-prem offering. You can deploy it to any Kubernetes. We launched it in December of last year and already has good traction. Please stop by our booth if you have any questions. With that, that's my talk, and thank you for joining me today and enjoy the rest of the conference. Happy to take any calls.