 OK, we're going to change it up a little bit. We're going to bring another user on stage. So I'd like to introduce Doug Coleman. Doug is from Charles Schwab. He's the managing director of Cloud Platforms, Engineering and Operations. I always have to read the titles to make sure I get them right. So manager director of Cloud Strategy and all the things related to Cloud Strategy. Doug, come on on stage. We'd love to spend some time with you. Hey, so you've got fans on the front row, is that? All made three or four, not too many. So you'll work for them, right? All right, no big head here. Well, Doug, thank you for coming. We've heard a lot about the evolution of the project, the evolution of the platform. We've also, from Eric, we got a sense of what American Airlines has done and what they want to see as we evolve. What I was hoping for today is if you could maybe take us through a little bit of the Schwab story around adoption, and then we could kind of tease interesting parts of that out as we go. Yeah, definitely. No, thanks for having me. We've got a pretty good story of Schwab. So Schwab, for those who don't know, so we've been in business nearly 50 years. Over 12 main active brokerage accounts in our clients and trust us with 3 and 1 half trillion of their assets, right? So everything that we do is to steward that forward, right? So it's built into our DNA, Chuck started it, and really with a focus on innovation, and that's really where Cloud Foundry comes in, right? So it's really helping to empower our digital initiatives. We've got some of the most critical operations in Schwab running on the platform. Great. So it's a good story, and thanks for letting me share it. It is, it is. So when we spoke before the event, you were particularly proud of some of the automation work that you put into this platform, sort of enhancing that developer experience to kind of fit your workflow. Can you share some of that? Yeah, yeah, so our group was really formed in 17 and is really meant to be close to the developers, close to the people who are actually consuming the platform. I'm a longtime developer. Many people on the team are longtime developers. And really everything that we put in place is to put those guardrails in. So we encourage innovation from the developers, but while following our guardrails. So everything in the back end of the platform, infrastructure is code. So developers can come in, they can set up orgs, they can set up spaces, bind security groups, and that all goes as infrastructure is code. So we have it, it's following those good practices and guardrails, and it really speeds adoption up through the pipeline. So we do that from the back end, and the front end we enforce complete automation of everything going to the platform. We don't want people come in doing CF pushes into production. We want them running their pipelines, so static code, dynamic code. So we're trying to follow the mantra that everything goes in through automation. Yeah, and of course, being financial services compliance really matters. So I'm assuming there's quite a bit of thought that you've put into getting the aspects of compliance that have always existed sort of baked into that automation cycle. Yeah, yeah, so one of the guiding principles at Schwab is really formed around trust is everything, earned in a lifetime and lost in an instant. And it's so true in our technology world, right? If you don't follow those good practices, you can lose everything. So we have strong partnerships with our pivotal partners, strong partnerships with our application and architecture teams. So we come in and we build, so our team, we write engineering practices, we write working code for teams to consume. So when all these follow the guidelines, that makes sure that we're always audit-worthy. We can go back and have traceability through the entire stack and through the entire deployment lifecycle. Yeah, it really can be automated, right? We don't actually, we can let developers kind of be freed up to innovate. So one of the things that, thematically, that we hear from different end users, different customers of the distributions is there's sort of a spectrum of adoption cycles that happen. On one hand, you sometimes have kind of a top-down mandate and everybody must use this platform. On the other hand, you have a very organic, very kind of grassroots and bottom-up. Maybe you can kind of place yourself on the spectrum if that's okay and talk a little bit about how the adoption within the developer community in your company is going. Yeah, it was a very purpose-built initiative to stand up for our organization and really to foster bringing this out to the developer community. So last year alone, so we saw over 300% increase in applications running in production and a much higher increase in non-prod usage as well. So and nearly all of that adoption was from teams finding it easy, convenient, inaccessible to go onto the platform. So we've got a lot of digital initiatives going on like many other companies, right? But really a smaller subset of the digital initiatives are going initially. It's really organic adoption. Well, that's really good to hear. I mean, that seems to be thematically one of the most successful patterns, right? If you demonstrate the value that you can just push code, you know, and all of those compliance things are kind of, they melt away, they're still there, but they melt away from the developer's concerns. So while I wanna switch things, that sounds like a lot of success. I'm gonna put you on the spot here, but I'm interested, are there challenges that you ran into that obviously you've gotten over that you'd be willing to share? I would love to say there are no challenges, but you know. We'd know your line. Everybody here would start heckling, right? No, tons of challenges. I mean, over 50 years, you build up a lot of different ways of doing things, right? So everything that my team was focused on was really efficiency, self-service. So we stood up a lot of tooling around the platform. And really what it was is to bring in these different parts of Schwab that are different compliance systems. We integrate logging out of the box. We integrate our APM tools out of the box. So when people come into the platform, they get that, but there is a lot of blood, sweat, and tears that went into that. And it was really talking to the different teams about working differently, following an API-first strategy, right? You know, many places in the company, there weren't APIs that we could leverage to say, hey, we wanna go in dynamically create network routes and this and that, right? But it's like our network team, they kicked it, they stood up an API, and we've got that automation going in. But there's a ton of challenges, right, that we still get to overcome. Yeah, I appreciate that. So now it's your turn, and I'd like you to put this community on the spot. What are the things that they can do better for you? You've got other users, right? Are there things that maybe is a larger community of end users that you could do together? You have the contributors and the project leads that help build the code. So what can this group here do to help Schwab? Yeah, you know it's, personally and in the team, particularly excited around some of the stuff coming from Istio and sidecars and being able to build in that service mesh. Allowing it a developer to be able to specify their load balancing and then possibly doing it between a Kubernetes cluster and their paths, right? I mean, this is really cool stuff, right? Really a lot of potential. So I think it's really around that sort of stuff. Bringing more visibility to the platform from, how am I running? How are we doing? There's quite a bit that we build around it, to look at overall the health of applications and this and that. Availability is core for us. So anything that comes into from an availability perspective that helps to keep the platform visible and transparent that we or the developers don't have to worry about, you know, it's a big boom. That's great. That's great. Well, thank you so much for coming. I always appreciate the opportunity to hear the end user stories. In particular, if you can speak to this community, tell us what we can do to help you better. So thank you so much. It also sounds like a great success at Schwab so far. And as a customer, I appreciate it. In particular, thoughtfulness about compliance. So thanks again. Thanks again. Appreciate it. All right.