>>The Cube Presents UI Path Forward five. Brought to you by UI Path. >>Welcome back to the Cube's Coverage of Forward five UI Path Customer event. This is the fourth forward that we've been at. We started in Miami, had some great events. It's all about the customer stories. Dave Valante with Dave Nicholson, Flow Yees here. She's the director of engineering and development at dsu and Kate Hall is to her right. And Kate is the director of Automation Solutions at dsu. Ladies, welcome to the Cube. Thanks so much. Thanks >>You to >>Be here. Tell us about dsu. You guys are huge company, but but give us the focus. >>Yeah, absolutely. Dentsu, it's one of the largest advertising networks out there. One of the largest in the world with over 66,000 employees and we're operating in a hundred plus countries. We're really proud to serve 95% of the Fortune 100 companies. Household names like Microsoft Factor and Gamble. If you seen the Super Bowls ads last year, Larry, Larry Davids ads for the crypto brand. That's a hilarious one for anyone who haven't seen it. So we're just really proud to be here and we really respect the creatives of our company. >>That was the best commercial, the Super Bowl by far. For sure. I, I said at the top of saying that Dave and I were talking UI pass, a cool company. You guys kinda look like cool people. You got cool jobs. Tell, tell us about your respective roles. What do you guys do? Yeah, >>Absolutely, absolutely. Well, I'm the director of engineering and automation, so what I really do is to implement the automation operating model and connecting developers across five continents together, making sure that we're delivering and deploying automation projects up to our best standards setting by the operating model. So it's a really, really great job. And when we get to see all these brilliant minds across the world >>And, And Kate, what's your role? Yeah, >>And the Automation Solutions vertical that I head up, the focus is really on converting business requirements into technical designs for flows, developers to deliver. So making sure that we are managing our pipeline, sourcing the right ideas, prioritizing them according to the business businesses objectives and making sure that we route them to the right place. So is it, does it need to be an automation first? Do we need to optimize the process? Does this make sense for citizen developers or do we need to bring in the professional resources on flow's >>Team? So you're bilingual, you speak, you're like the translator, you speak geek and wall, right? Is that fair? Okay. So take me back to the, let's, let's do a little mini case study here. How did you guys get started? I'm always interested, was this a top down? Is, is is top down required to be successful? Cuz it does feel like you can have bottom up bottoms up with rpa, but, but how did you guys get started? What was the journey like? >>Yeah, we started back in 2017, very traditional top down approach. So we delivered a couple POCs working directly with UiPath. You know, going back those five years, delivered those really highly scalable top down solutions that drove hundreds of thousands of hours of ROI for the business. However, as people kind of began to embrace automation and they learned that this is something that they could, that could help them, it's not something that they should be afraid of to take away their jobs. You know, DSU is a young company with a lot of young, young creatives. They wanna make their lives better. So we were absolutely inundated with all of these use cases of, hey I, I need a bot to do this. I need a bot to do that i's gonna save me, you know, 10 hours a week. It's gonna save my team a hundred hours a month, et cetera, et cetera. All of these smaller use cases that were gonna be hugely impactful for the individuals, their teams, even in entire department, but didn't have that scalable ROI for us to put professional development resources against it. So starting in 2020 we really introduced the citizen development program to put the power into those people's hands so that they could create their own solutions. And that was really just a snowball effect to tackle it from the bottom up as well as the top down. >>So a lot of young people, Dave, they not not threatened by robots that racing it. So >>They've grown up with the technology, they know that they can order an Uber from their phone, right? Why am I, you know, sitting here at MITs typing data from Excel into a program that might be older than some of our youngest employees. >>Yeah. Now, now the way you described it, correct me if I'm wrong, the way you described it, it sounds like there's sort of a gating function though. You're not just putting these tools in the hands of people sitting, especially creatives who are there to create. You're not saying, Oh you want things automated, here are the tools. Go ahead. Automated. We'll we, for those of you who want to learn how to use the tools, we'll have you automate that there. Did I hear that right? You're, you're sort of making decisions about what things will be developed even by citizen developers. >>Let me, Do you wanna talk to them about governance? Yeah, absolutely. >>Yeah, so I think we started out with assistant development program, obviously the huge success, right? Last year we're also here at the Cubes. We're very happy to be back again. But I think a lot, a lot had changed and we've grown a lot since last year. One, I have the joy being a part of this team. And then the other thing is that we really expanded and implemented an automation operating model that I mentioned briefly just earlier. So what that enabled us to do is to unite developers from five continents together organically and we're now able to tap into their talent at a global scale. So we are really using this operating model to grow our automation practice in a scalable and also controlled manner. Okay. What I mean by that is that these developer originally were sitting in 18 plus markets, right? There's not much communication collaboration between them. >>And then we went in and bridged them together. What happened is that originally they were only delivering projects and use cases within their region and sometimes these use cases could be very, very much, you know, small scale and not really maximizing their talent. What we are now able to do is tap into a global automation pipeline. So we connecting these highly skilled people to the pipeline elsewhere, the use cases elsewhere that might not be within their regions because one of our focus, a lot of change I mentioned, right? One thing that will never change with our team, it's used automation to elevate people's potential. Now it's really a win-win situation cuz we are connecting the use cases from different pipelines. So the business is happy cuz we are delivering these high scalable solutions. We also utilizing these developers and they're happy because their skills are being maximized and then at the same time growing our automation program. So then that way the citizen development program so that the lower complexities projects are being delivered at a local level and we are able to innovate at a local level. >>I, I have so many questions flow based on what you just said. It's blowing my mind >>Here. It's a whole cycle. >>So let me start with how do you, you know, one of the, one of the concerns I had initially with RPA, cuz just you're talking about some very narrow use cases and your goal is to expand that to realize the potential of each individual, right? But early days I saw a lot of what I call paving the cow path, taking a process that was not a great process and then automating it, right? And that was limiting the potential. So how do you guys prioritize which processes to focus on and maybe which processes should be rethought, >>Right? Exactly. A lot of time when we do automation, right, we talk about innovations and all that stuff, but innovation doesn't happen with the same people sitting in the same room doing the same thing. So what we are doing now, able to connect all these people, different developers from different groups, we really bring the diversity together. That's diversity D diverse diversity in the mindset, diversity in the skill. So what are we really able to do and we see how we tackle this problem is to, and that's a problem for a lot of business out there is the short-termism. So there's something, what we do is that we take two approaches. One, before we, you know, for example, when we used to receive a use case, right? Maybe it's for the China market involving a specific tool and we just go right into development and start coding and all that good stuff, which is great. >>But what we do with this automation framework, which we think it's a really great service for any company out there that want to grow and mature their automation practice, it's to take a step back, think about, okay, so the China market would be beneficial from this automation. Can we also look at the Philippine market? Can we also look at the Thailand market? Because we also know that they have similar processes and similar auto tools that they use. So we are really able to make our automation in a more meaningful way by scaling a project just beyond one market. Now it's impacting the entire region and benefiting people in the entire region. That is what we say, you know, putting automation for good and then that's what we talked about at dsu, Teaming without limits. And that's a, so >>By taking, we wanna make sure that we're really like taking a step back, connecting all of the dots, building the one thing the right way, the first time. Exactly. And what's really integral into being able to have that transparency, that visibility is that now we're all working on the same platform. So you know, Brian spoke to you last year about our migration into automation cloud, having everything that single pipeline in the cloud. Anybody at DSU can often join the automation community and get access to automation hub, see what's out there, submit their own ideas, use the launchpad to go and take training. Yeah. And get started on their own automation journey as a citizen developer and you know, see the different paths that are available to them from that one central space. >>So by taking us a breath, stepping back, pausing just a bit, the business impact at the tail end is much, much higher. Now you start in 2017 really before you UI path made it's big enterprise play, it acquired process gold, you know, cloud elements now most recently referenced some others. How much of what you guys are, are, are doing is platform versus kind of the initial sort of robot installation? Yeah, >>I mean platforms power people and that's what we're here to do as the global automation team. Whether it's powering the citizen developers, the professional developers, anybody who's interacting with our automations at dsu, we wanna make sure that we're connecting the docs for them on a platform basis so that developers can develop and they don't need to develop those simple use cases that could be done by a citizen developer. You know, they're super smart technical people, they wanna do the cool shit with the new stuff. They wanna branch into, you know, using AI center and doing document understanding. That's, you know, the nature of human curiosity. Citizen developers, they're thrilled that we're making an investment to upscale them, to give them a new capability so that they can automate their own work. And they don't, they, they're the process experts. They don't need to spend a month talking to us when they could spend that time taking the training, learning how to create something themselves. >>How, how much sort of use case runway when you guys step back and look at your business, do you see a limit to the use cases? I mean where are you, if you had on a spectrum of, you know, maturity, how much more opportunity is there for DSU to automate? >>There's so much I think the, you feel >>Like it's limitless? >>No, I absolutely feel like it's limitless because there one thing, it's, there's the use cases and I think it's all about connecting the talent and making sure that something we do really, you know, making sure that we deliver these use cases, invest the time in our people so we make sure our professional developers part of our team spending 10 to 20% of the time to do learning and development because only limitless if our people are getting the latest and the greatest technology and we want to invest the time and we see this as an investment in the people making sure that we deliver the promise of putting people first. And the second thing, it's also investment in our company's growth. And that's a long term goal. And overcoming just focusing on things our short term. So that is something we really focus to do. And not only the use cases we are doing what we are doing as an operating model for automation. That is also something that we really value because then this is a kind of a playbook and a success model for many companies out there to grow their automation practice. So that's another angle that we are also focusing >>On. Well that, that's a relief because you guys are both seem really cool and, and I'm sitting here thinking they don't realize they're working themselves out of a job once they get everything automated, what are they gonna do? Right? But, but so, so it sounds like it's a never ending process, but because you guys are, are such a large global organization, it seems like you might have a luxury of being able to benchmark automations from one region and then benchmark them against other regions that aren't using that automation to be able to see very, very quickly not only realize ROI really quickly from the region where it's been implemented, but to be able to compare it to almost a control. Is that, is that part of your process? Yeah, >>Absolutely. Because we are such a global brand and with the automation, automation operating model, what we are able to do, not only focusing on the talent and the people, but also focusing on the infrastructure. So for example, right, maybe there's a first use case developing in Argentina and they have never done these automation before. And when they go to their security team and asking for an Okta bypass service account and the security team Argentina, like we never heard of automation, we don't know what UiPath is, why would I give you a service account for good reason, right? They're doing their job right. But what we able to do with automation model, it's to establish trust between the developers and the security team. So now we have a set up standing infrastructure that we are ready to go whenever an automation's ready to deploy and we're able to get the set up standing infrastructure because we have the governance to make sure the quality would delivered and making sure anything that we deployed, automation that we deploy are developed and governed by the best practice. So that's how we able to kind of get this automation expand globally in a very control and scalable manner because the people that we have build a relationship with. What are >>The governors to how fast you can adopt? Is it just expertise or bandwidth of that expertise or what's the bottleneck? >>Yeah, >>If >>You wanna talk more about, >>So in terms of the pipeline, we really wanna make sure that we are taking that step back and instead of just going, let's develop, develop, develop, here are the requirements like get started and go, we've prove the value of automation at Densu. We wanna make sure we are taking that step back and observing the pipeline. And it's, it's up to us to work with the business to really establish their priorities and the priorities. It's a, it's a big global organization. There might be different priorities in APAC than there are in EM for a good reason. APAC may not be adopted on the same, you know, e r P system for example. So they might have those smaller scale ROI use cases, but that's where we wanna work with them to identify, you know, maybe this is a legitimate need, the ROI is not there, let's upscale some citizen developers so that they can start, you know, working for themselves and get those results faster for those simpler use cases. >>Does, does the funding come from the line of business or IT or a combination? I mean there are obviously budget constraints are very concerned about the macro and the recession. You guys have some global brands, you know, as, as things ebb and flow in the economy, you're competing with other budgets. But where are the budgets coming from inside of dsu? Is it the business, is it the tech >>Group? Yeah, we really consider our automation group is the cause of doing business because we are here connecting people with bridging people together and really elevating. And the reason why we structure it that way, it's people, we do automation at dsu not to reduce head count, not to, you know, not, not just those matrix number that we measure, but really it's to giving time back to the people, giving time back to our business. So then that way they can focus on their wellbeing and that way they can focus on the work-life balance, right? So that's what we say. We are forced for good and by using automation for good as one really great example. So I think because of this agenda and because DSU do prioritize people, you know, so that's why we're getting the funding, we're getting the budget and we are seeing as a cause of doing business. So then we can get these time back using innovation to make people more fulfilling and applying automation in meaningful ways. >>Kate and Flo, congratulations. Your energy is palpable and really great success, wonderful story. Really appreciate you sharing. Thank you so >>Much for having us today. >>You're very welcome. All keep it right there. Dave Nicholson and Dave Ante. We're live from UI path forward at five from Las Vegas. We're in the Venetian Consent Convention Center. Will be right back, right for the short break.

>>Welcome back to Los Angeles, Lisa Martin and Dave Nicholson here on day three of the cubes, coverage of coop con and cloud native con north America, 21, Dave, we've had a lot of great conversations. The last three days it's been jam packed. Yes, it has been. And yes, it has been fantastic. And it's been live. Did we mention that it's inline live in Los Angeles and we're very pleased to welcome one of our alumni back to the program. David Stephanie is here. The CEO of Trulio David. Welcome back. It's good to see you. >>Thanks for having me. It's good to be here. Isn't it great to be in person? Oh man. It's been a reunion. >>It hasn't been a reunion and they have Ubered been talking about these great little, have you seen these wristbands that they have? I actually asked >>For two, cause I'm a big hugger, so >>Excellent. So, so here we are day three of coupon. That's actually probably day five, our third day of coverage. I'm losing track to it's Friday. I know that, that I can tell you, you guys announced two dot five a couple of weeks ago. Tell us what's in that. What's exciting. Before we crack open Twilio, uh, choy. >>Sure, sure. Well, it's been exciting to be here. Look, the theme right of resiliency realize has been it's right up our wheelhouse, right? To signal that more people are getting into production type of environments. More people require data protection for cloud native applications, right? And, uh, there's two dot five releases. It is as an answer to what we're seeing in the market. It really is centered predominantly around, uh, ransomware protection. And uh, you know, for us, when we look at this, I I've done a lot of work in, in cybersecurity, my career. And we took a hard look about a year ago around this area. How do we do this? How do we participate? How do we protect and help people recover? Because recovery that's part of the security conversation. You can talk about all the other things, but recovery is just as important. And we look at, uh, everything from a zero trust architecture that we provide now to adhering, to NIST standards and framework that's everything from immutability. Uh, so you can't touch the backups now, right? Uh, th that's fine to encryption, right? We'll encrypt from the application all the way to that, to the storage repository. And we'll leverage Keem in that system. So it's kind of like Bitcoin, right? You need a key to get your coin. You as an end-user only have your key to your data alone. And that's it. So all these things become more and more important as we adopt more cloud native technology. And >>As the threat landscape changes dramatically. >>Oh yeah. I got to tell you right. Every time we, you, you publish an application into another cloud, it's a new vector, right? So now I'm living in a multi-cloud world where multiple applications in my data now lives, right? So people are trying to attack backups through, uh, consoles and the ministry of consoles to the actual back of themselves. So new vectors, new problems need new solutions. >>And you mentioned, you mentioned something, you, you, you asked the question, how do we participate? And we are here at KU con uh, w uh, cloud native foundation. So what about, what's your connection to the open source community and efforts there? How do you participate in that? >>Yeah, so it's a really great question because, you know, uh, we are a closed source solution that focuses all of our efforts on the open source community and protecting cloud native applications. Our roots have been protecting cloud native applications since 2013, 2014, and with a lot of very large logos. And, um, you know, through time there are open source projects that do emerge, you know, in this community. And for example, Valero is an open source data protection platform, um, for all of its goodness, as a, as a community-based project, they're also deficiencies, right? So Valero in itself is, uh, focuses only on label based applications. It doesn't really scale. It doesn't have a UI it's really CLI driven, which is good for some people and it's free. But you know, if you need to really talk about an enterprise grade platform, this is where we pick up, you know, we, in our last release, we gave you the ability to capture your Valero based backups. And now you want to be an adult with an enterprise caliber, you know, backup solution and continue to protect your environment and have compliance and governance needs all satisfied. That's where, that's where we really stand out. >>Well, when you're talking to customers in any industry, what are the things that you talk about in terms of relief, categorizing the key differentiators that really make Trulia stand out above the competition? >>Yeah. Cause there, there a bunch of, they're a bunch of great competitors out there. There's no doubt about it. A lot of the legacy folks that you do see perhaps on those show floor, they do tuck in Valero and under the, under the covers, they can check a box or you can set aside some customer needs some of the pure play people that, that we do see out there, great solutions too. But really where we shine is, you know, we are the most flexible agnostic solution that there is in this market. And we've had people like red hat and Susa and verandas, digital ocean and HPS morale. And the list goes on, certify, say, Trulio is the solution of choice. And now no matter where you are in this journey or who you're using, we have your back. So there's a lot of flexibility. There we are complete storage agnostic. >>We are cloud agnostic in going back to how you want to build our architecture application. People are in various phases in their, in their journey. A lot of times, many moons ago, you may have started with just a label based application. Then you have another department that has a new technique and they want to use helm, or you may be adopting open shift and you're using operators to us. It doesn't matter. You have peace of mind. So whether you have, you have to protect multiple departments or you as an end user, as one single tenant are using various techniques, we'll discover or protect and we can move forward. >>So if you looked at, if you look at it from a workload basis, um, and you look at your customers are the workloads that you're protecting. What's, what's the mix of what you think of as legacy virtualized things versus containerized things. And then, and then, and then the other kind of follow on to that is, um, are you seeing a lot of modernization and migration or are you seeing people leave the legacy things alone and then develop net new in sort of separate silos? >>Yeah. So that's a great question. And I, to tell you the answer varies, that's, that's the honest answer, right? You end up having, you may have a group or a CIO that says, look, your CTO says, we're moving to this new architecture. The water's great, bring your applications in. And so either it's, we're going to lift and shift an application and then start to break it apart over time and develop microservices, or we're gonna start net new. And it really does run, run the gambit. And so, you know, as we look at, for some of those people, they have peace of mind that they can bring their two on applications in and we can recover. And for some people that say, look, I'm going to start brand new, and these are gonna be stateless applications. Um, we've seen this story before, right? Our, our, uh, uh, I joke around, it's kinda like the movie Groundhog's day. >>Uh, you know, we, we started many moons ago within the OpenStack world and we started with stateless to stateful. Always, always, always finds a way, but for the stateless people, um, when you start thinking about security, I've had conversations with CSOs around the world who say, I'm going to publish a stainless application. What I'm concerned about things like drift, you know, what's happening in runtime may be completely different than what I intended. So now we give you the ability to capture that runtime state compare. The two things identify what's changed. If you don't like what you see, and you can take that point in time recovery into a sandbox and forensically take it apart. You know, one of our superpowers, if you will, is the, our point in time, backups are all in an open format. Everyone else has proprietary Schemos. So the benefit of an open format is you have the ability to leverage a lot of third party tooling. So take a point in time, run scanners across it. And it, God forbid Trulio goes away. You still have access and you can recreate a point in time. So when you start thinking about compliance, heavy environments, think about telcos, right? Or financial institutions. They have to keep things for 15 years, right? Technologies change, architectures change. You can't have that lock-in >>So we continue to thrive. And on that front, one of the marketing terms that we hear a lot, and I want to get your opinion on this as a feature proofing, how do you, what does, what does it mean to you and Trillium and how do you enable that for organizations, like you said, for the FSI is I have to keep data for 15 years and other industries that have to keep it for maybe even longer. >>I mean, right. The future proof, uh, you know, terminology, that's part of our mantra actually, when I talked about, you know, a superpower being as agnostic and flexible as can be right, as long as you adhere to standards, right? The standards that are out here, we have that agnostic play. And then again, not just capturing an applications, metadata data, but that open format, right? Giving you that open capability to unpack something. So you're not, there is no, there is no vendor lock-in with us at all. So all these things play a part into, into future-proofing yourself. And because we live and breathe cloud native applications, you know, it's not just Kubernetes right? Over the course of time, there'll be other things, right. You're going to see mixed workloads too. They're gonna be VM based in the cloud and container based in the cloud and server lists as well. But you, as long as you have that framework to continuously build off of it, that's, that's where we go. You know, uh, it shouldn't matter where your application lives, right? At the end of the day, we will protect the application and its data. It can live anywhere. So conversations around multi-cloud change, we start to think and talk across cloud, right? The ability to move your application, your data, wherever it, wherever it needs to be to. >>Well, you talked about recoverability and that is the whole point of backing up video. You have to be able to recover something that we've seen in the last 18, 19 months. Anyone can backup >>Data. >>That's right. That's right. If you can't recover it, or if you can't recover it in time. Yeah. We're talking like going on a business potential and we've seen the massive changes in the security landscape in the last 18, 19 months ransomware. I was looking at some, some cybersecurity data that showed that just in the first half of this calendar year, January one to June 30, 20, 21, ransomware was up nearly 11 X DDoS attacks are up. We've got this remote workforce. That's going to probably persist for a while. So the ability to recover data from not if we get hit by ransomware, but when we get hit by ransomware is >>When you're, you're absolutely right. And, and, and to your plate anyway. So anyone can back up anything. When you look at it, it's at its highest form. We talk about point time where you orchestration, right. Backup is a use case. Dr. Is a use case, right? How do you, reorchestrate something that's complex, right? The containers, these applications in the cloud native space, there are morphous, they're living things, right? The metadata is different from one day to the next, the data itself is different from when one day the net to the next. So that's, what's so great about Trillium. It's such an elegant solution. It allows your, reorchestrate a point in time when and where you need it. So yes. You have to be able to recover. Yes. It's not a matter of if, but when. Right. And that's why recovery is part of that security conversation. Um, you know, I I've seen insurance companies, right? They want to provide insurance for ransomware. Well, you're gonna have enough attacks where they don't want to provide that insurance anymore. It costs too much. The investment that you make with, with Trulio will save you so much more money down the road. Right. Uh, who's our product manager actually gave a talk about that yesterday and the economics were really interesting. >>Hmm. So how has the recovery methodology who participates in that changed over time? As, as we, you know, as we are in this world of developer operators who take on greater responsibility for infrastructure things. Yeah. Who's, who's responsible for backup and recovery today and how, how has that changed >>Everyone? Everyone's responsible. So, you know, we rewind however many years, right? And it used predominantly CIS admin that was in charge of backup administrator, but a ticket in your backup administrator, right. Cloud native space and application lifecycle management is a team sport. Security is a team sport. It's a holistic approach. Right? So when you think about the, the team that you put out on the field, whether your DevOps, your SRE dev sec ops it ops, you're all going to have a need for point in time, we orchestration for various things and the term may not be backup. Right? It's something else. And maybe for test dev purposes, maybe for forensic purposes, maybe for Dr. Right. So I say it's a team sport and security as a holistic thing that everyone has to get on board with >>The three orchestration is exactly the right way to talk about absolute these processes. It's not just recovery, you're rebuilding >>Yeah. A complex environment. It's always changing. >>That's one of the guarantees. It's always going to be changing >>That much. >>Can you give us a, leave us with a customer example that you think really articulates the value of what Trulio delivers? >>Yeah. So it's interesting. I won't say who the customer is, but I'll tell you it's in the defense agency, it's a defense agency. Uh, they have developers all over the place. Uh, they need self-service capabilities for the tenants to mind their own backups. So you don't need to contact someone, right. They can build, they have one >>Dashboard, single pane of glass or truth to manage all their Corinthians applications. And it gives them that infrastructure to progress whether your dev ops or not your it ops, uh, this, this group has rolled it out across the nation and they're using in their work with very sensitive environments. So now we have they're back. And what are some of the big business outcomes that they're achieving already? >>The big business outcomes? Well, so operational efficiencies are definitely first and foremost, right? Empowering the end user with more tools, right? Because we've seen this shift left and people talking about dev ops, right. So how do I empower them to do more? So I see that operational efficiency, the recoverability aspect, God forbid, something goes wrong. How do you, how do you do that in the cost of that? Um, and then also, um, being native to the environment, the Trillium solution is built for Kubernetes. It is built on go. It is a Qubit stateless Kubernetes application. So you have to have seamless integration into these environments. And then going back to what I was saying before, knowing peace of mind, the credibility aspect, that it is blessed by, you know, red hat and suicide Mirandas and all these other, other folks in the field, um, that you can guarantee it's going to work >>Well, that helps to give your customers the confidence that there, and that confidence might sound trivial. It's not, especially when we're talking about security, it's not at all that, that's a, that's a big business outcome for you guys. When a customer says, I'm confident I have the right solution, we're going to be able to recover when things happen, we try, we fully trust in the solution that we're, >>And we'll bring more into production faster that helps everyone out here too. Right? It feels good. You have that credibility. You have that assurance that I can move faster and I can move into different clouds faster. And that's, we're gonna continue to put, we're gonna continue to push the envelope there. You know, coming a, as we look into, you know, going forward, we're going to come out with other capabilities. That's going to continue to differentiate ourselves from, from folks. Uh, we'll, we'll talk about in time, the ability to propagate data across multiple clouds simultaneously. So making RTOs look at the split seconds and minutes. And so I hope that we can have that conversation next time we were together, because it's really exciting. >>Any, any CTA that you want to give to the audience, any, any, uh, like upcoming or recent webinars that you think they would be really benefit from? >>I guess one thing I put out there is that, um, I understand that people need to continuously learn. There is a skillset hole in, in this market. We can, we understand that, you know, and people look to us as not just a vendor, but a partner. And a lot of the questions that we do get are how do I do this? Or how do I do that? Engage us, ask us to consume our product is really, really easy. You can download from the website or go to an, you know, red hats operator hub, or go to the marketplace over at Susa, and let's begin to begin and we're here to help. And so reach out, right? We want everyone to be successful. >>Awesome. trillium.io. David, thank you for joining us. This has been an exciting conversation. Good >>To see you all. >>Likewise. Good to see you in person take care. We look forward to the next time we see you when unpacking what other great things are going on on Trulia. We appreciate your >>Time. Thank you so much. Good to be here >>For David's fie and David Nicholson, the two Davids I'm going to sandwich. I'm Lisa Martin, you we're coming to you live from Los Angeles. This is Q con cloud native con north America, 2021. Stick around our next guest joins us momentarily.