>> Live from Las Vegas; it's the Cube. Covering the AWS Accenture Executive Summit. Brought to you by Accenture. >> Welcome back everyone to the Cube's live coverage of the AWS executive summit here at the Venetian in Las Vegas Nevada. I'm your host Rebecca Knight. We have two guests for this segment. We have Hitoshi Ienaka the CEO of ARISE Analytics and Takuya Kudo the Chief Sciences Officer at ARISE. Thank you both so much for coming on the program. >> Thank you. >> So I want to start by having you tell our viewers a little bit more about ARISE analytics. >> Well ARISE analytics is a joint venture between KDDI and Accenture. Well last, well last year we established a company yeah. That's family. >> Right and that's you know kind of we provide like tying the capabilities and the KDDI is kind of number two mobile network operator in Japan, has 50 million subscribers, massive data. So that's there a lot of room to cook but they don't have enough capability to support that. So that's why we kind of married together. >> And it helps companies leverage a wealth of knowledge resources and data between firms to bring about digital transformation. >> Right. >> That's what you're doing. So talk a little bit about what you've seen so far. >> Well so we have two assets, KDDI has, well big data and well Accenture has, well a lot of analytic skills. So using this well these assets, we built our integrated analytics platform hosted on a eda-brais. And what our first challenge was to deduce, channel out to the other operators and were which caused a challenge risk to well more than 40 million subscribers and by digging into that data and using machine learning origin and our data includes (mumbles) and life style service usage. And well, we optimize customer channels and contact timing and well to target customers efficiently. And well we well we tried art of well, other event well art of >> (mumbles) >> Yeah yeah. >> Yeah (mumbles) marketing. >> Okay. >> Yeah and we can get a good result and well it was not only due to our activities but only last year, only KDDI well could increase the market share among three network operators in Japan. That is our our achievements yeah. >> That's very impressive! So can you talk a little bit about the initial pilot in particular what you saw. Taku, do want to? >> Right so like as he mentioned like we have two work stream gigantic work stream. One is for consumer facing right. So customer chai and the you know out of on three marketing's or like recommendation engines based upon this stream data because we have massive like this is a consumption data too. Not just about like you know one handset data. In another work stream is a B2B, a business domain which is sounds like not related to mobile network operators but they have massive network to sell to B2B customer. So we utilize those gigantic data, combine those maybe I can mention but data but combine those data creating new service model. So that's quite a new IOT initiatives for B2B layers and consumer initiatives you know to support ongoing current business. >> And you're using this in a variety of sectors in particular I wanted you to ask you about one that you're doing with Toyota and a taxi service. >> Right so (mumbles) so yeah that that one is like five years like example because a, unless otherwise, I don't think that new business model to compete with Uber never happened right? So KDDI provide like Maura Handu said like location data over like you indigenous subscribers creating some, you know demand side riders for (mumbles) right? Over there, on top of that Toyota's transact log, which is technically like kinematics data provide like supply side which is cause, right? Focusing model and taxi also provide like meters, where customer riders get in and get off and combine those three completely different cable and data sets. >> But also with things like weather and those kinds of other >> Exactly yeah. >> outside. >> Open data too. And combine those data sets. We in, we provide, Accenture provides like talents and creating completely new forecasting model it's called AI taxi dispatch model. So now if you go to Tokyo, majority of taxi has our algorithm like Arizona takes in, you know KDDI and Accenture provide it. >> So that's very cool! Can you talk a little bit about what you've learned, about, in terms of when the weather is like this, taxis happen this >> Yeah, so it's of course weather has massive impact over, like if it's mornings specifically lane, it boosts like demands and also events. We have also events data. Maybe I don't know concerts, some famous singer, celebrities came and it's you know boost like riders demands. So that's actually significant impact of our demand focused model. Rather than using pushing like Uber, you strike you know app, mobile app. we actually treated as (mumbles) like taxi actually go because taxi driver and I can see where is a hot spot to pick up riders. And that's what we try to do. So based up on those, you know people don't even have like maybe like my father's age right, that don't have a smartphone they can get the benefit universality right. So that's the base concepts to provide Universal model to those you know without these >> So even people lacking technology >> Right exactly. >> Can still reap the benefits of this kind of approach. >> (mumbles) is universality so that's also our business strategy. Yeah. >> So you're also using this approach in a manufacturing environment. >> Yeah that's right. We are also working with some manufacturing factory. On the factory field were experienced workers can detect machine breakdown before they occur. But well how can that not be passed on to less experienced employees? So we created a live predictive maintenance which alerts companies ahead of time to pre potential breakdowns. Sensors (mumbles) about things like vibrations, temperature and electrical current. The collected data is analyzed by the AI system. So in this way the prediction of machine (mumbles) can be performed by almost anyone. Well it used to be others by only experienced employees before, yeah. >> So it not only helps the company know when a machine is going to fail, it also empowers the employee to fix it him or herself. >> Right it's a preventive way and so it's up and running over the ad-abreis. We use kinesis in late shift you know, learn the functions and over EC2. So that's completely free stock over ad-abreis capability too. >> So what you're describing sounds like it requires a lot of collaboration, a lot of deep relationship building between not only Accenture and KDDI but also the clients that you're working with. Can you describe how you all work together? >> Right. So maybe I'm going to provide that information. So like of course like KDDI's employee has specific domain knowledge and we provide like you know like data science capabilities and also like maybe through the interview right, found workers or like taxi, they have specific domain knowledge So combine those collaboration. It's called two in the box and we collaboratively paired each employees and you know supply the knowledge each other so that's it. Just one is not enough but as a team integrated over database and created a very strong team and that's a you know we try to cherish and that's culture. And the two boost the data science, data driven companies decision-making process. >> So i think our viewers are pretty amazed and impressed with what's going on. But in this era of 5G and IOT, what's next, what are you working at? It's a relatively new partnership. What are what are some of the most exciting things in the pipeline? >> So the (laughs) the very strategic so we strategizing right now in terms of 5G in IOT. But definitely one of the pieces could be like deep learning right? And also about your realities which nobody has done before. So that's where we try to collaborate with other sectors, industries, to create a new. And to do so we need a massive like computation power like GPU servers and we have to rely on the ad-abreis because otherwise we cannot achieve those goals and specifically 5G maybe changing in the game. Maybe like you know low latency and you know wireless connectivity, you know we don't need connections so maybe the factory lining assembly lines. You know completely change the way crispy like edge computing no more. Maybe like for computing, right, in between like Saba and edge because of the 5G. I don't know but we are strategizing now in a very exciting moment. We are doing right now. >> Indeed it is. >> Yeah. >> Well Hitoshi, Taku, thank you so much for coming on the Cube. This was a lot of fun. >> Thank you very much. I'm Rebecca Knight. Stay tuned for more of the Cube's live coverage of the AWS Executive Summit coming up just after this. (Uptempo music)

>> Announcer: Live from San Diego, California, it's theCUBE. Covering KubeCon and CloudNativeCon. Brought to you by Red Hat, the Cloud Native Computing Foundation and its ecosystem partners. >> Welcome back, I'm Stu Miniman and my Co-host is John Troyer. And you're watching theCUBE here in day two of our coverage of KubeCon and CloudNativeCon. And joining me is Tobi Knaup who is the co-founder and CTO of D2iQ. See what I did there, Tobi? >> That's right, I love it. >> Alright. So Tobi, first of all, KubeCon, of course D2iQ, last year when we were here it was Mesosphere, so give us a little bit, you've been to lots of customer meetings, 12,000 people in attendance, tell us a little bit about the energy and how your team's finding the show so far. >> Yeah, obviously biggest KubeCon so far and it's just amazing how far this community has come, how it's grown. How many projects are part of it now, how many vendors here, too. You know two expo halls with different booths and you know, I think it just shows how important this community, this ecosystem is. When customers come to us and say they want to work with Kubernetes the community's why they're really doing it. >> Yeah, it is a great community, great vibe for people that aren't already in it. It's easy to get started, but one of the big themes we're hearing here is simplicity, how to make it easier to get going and once they get going, what happens after day one? That's some of the rebranded pieces. So for our audience, explain a little bit, why the rebrand focus of the company, Day 2 operations, absolutely something that I hear a lot of discussion on and why is your team specifically well positioned for that environment. >> No absolutely, so the rebrand we did because obviously our old company named Mesosphere has Mesos in it. That's the open source product we started with. But we've been doing a lot more than that actually for many years, right? We help customers run Apache Kafka and Spark and Cassandra. We've been doing a lot with Kubernetes also for some time now and even more so now. So having one particular technology in the company name was holding us back, right. People just put us in that box but we're doing so much more. So that was the reason for the rebrand and so, we wanted a name that doesn't have a particular technology in it and so we're looking for what is really expressed, what we do, what we help our customers with? And we've always been focused on Day 2 operations, so everything that happens after the initial install. How do you monitor things properly, upgrade them and so on? So that's why we loved that Day 2 concept. And then the IQ really stands for a couple of things. First of all we try to put a lot of automation into our products, so make those products smart to help our customers. But more importantly too, when we look at the ecosystem as a whole, where are most customers at, where are most companies at. Well, they're still early in their cloud-native journey and they need to get up to speed, they need to get smart about cloud-native and about Day 2 operations and so that's the IQ piece. We want to help our customers become smart about this space, get educated and then learn to do cloud-native. >> So Tobi, one of the things that fascinates me about the Kubernetes ecosystem is that people bring stuff to the table. Kubernetes is here, that's evolving. Other companies, entities, projects are coming to the table with other open source concepts and solving problems that they have in the field. At D2iQ, when you were Mesosphere, you have years of experience dealing with production issues, scaling management, all these sort of really, really fascinating cloud-native problems, so you bring a lot of experience to the table. So one of the projects that you are now working on and working with your customers and partners and the bigger ecosystem on is a way of approaching operators. The concept of bringing this kind of lifecycle automation to applications and helping with all these Day 2 problems. Can you talk a little about so KUDO is the name of the framework, I guess. Can you talk a little bit about that and how you're bringing that here to sit at the table and what some people's experiences with that are and what they are using it for? >> Absolutely, yeah, so these data services, these stapler workloads like Kafka, Cassandra and Spark, that's been in our DNA for a very long time. In fact, a little known fact, Apache Spark was originally a demo application for Apache Mesos. That's how it started originally. Obviously, it took off. So, we've been doing that since even before we were a company. And we've been helping our customers on top of Mesos with running these complex data stacks and there's some equivalent of operators on top of Mesos called frameworks. So we've been building these frameworks and we realized it's a little too hard to build these things. We typically had to write thousands of lines of code, 10, 20,000 sometimes and it took too long. So what we actually did on Mesos many years ago is we extracted the common patterns from those frameworks and built it into a library and made it so you can actually build a framework with just configuration, with just YAML, so it's a language that allows you to essentially sequence your operations into phases and steps. kind of like you would write a run book that a human operator takes and then goes through, right? So when we looked at the Kubernetes Operator space, we saw some of those same challenges that we had faced years ago. Building a Kubernetes Operator requires to write a lot of code. Not every company has Go programmers, people that are skilled enough in Kubernetes that they can write an operator. And more importantly too, once you write those 10,000 lines of code or more, you also have to maintain it. You have to keep up with API changes and so, a lot of folks we talked to at KubeCon last year and to customers, said it's just too hard to build operators. The other side of that too, is folks said it's a little too hard to use those operators too because very common use cases, you build a data pipeline. That means you'll be using multiple different operators, say Kafka, Cassandra and Spark. So if those all have different APIs, that's pretty hard to manage. So we wanted to simplify that. We wanted to create an alternative way for building operators that doesn't require you to learn Go, doesn't require you to write code, it works with just this orchestration language that KUDO offers and then for the KUDO users, the API is the same across these different operators. It has a plugin for Kube Cuddle, so you can interface with all the different operators through that. So yeah, simplicity and a great developer experience are the keys here. >> Tobi, I was wondering maybe you bring us inside the personas you target with this type of solution. As we've seen the maturation of this space, first couple of years I came, it felt very infrastructure heavy. The last year or two, there's more of the AppDev discussion there. They don't always speak the same languages. Looks like you've got some tooling here to help simplify that environment and make it easier because of course your application developers don't want to worry about that stuff. That's the promise of things like serverless, or just we're going to take care of that and stats and whatnot, so where specifically do you target and what are you hearing from customers as to how they're sorting through these organizational changes? >> Yeah, so I think ultimately, everybody kind of wants a platform as a service in some way, right? If you're building an app for your business, you don't want to think about, how do I provision this database, how to do that? And obviously, I can go to a public cloud and I can use all those public cloud services but what a lot of folks are doing now is they're running on various different types of infrastructure. They're running on multiple public clouds. They're running on the Edge. We work with a lot of customers that have a need to deploy these data services, these operators in Edge locations, on the manufacturing floor in a factory, for instance. Or on a cruise ship, that's one company we're working with. So, how do you bring this API-driven deployment of these services to all these different types of locations? And so that's what we try to achieve with KUDO for the data services and then with our other products too, like Kommander, which is a multi-cluster control plane. It's about when organizations have all these different clusters. And very typically they get into the dozens or even hundreds of clusters fast. How do you then manage that? How do you apply configuration consistently across these clusters? Manage your secrets and RBAC rules and things like that? So those are all the Day 2 things that we try to help customers with. There's a little bit of a tension there sometimes, right? Because the great thing about Kubernetes is it's great for developers. It has a nice API, people love the API. People are very quick to adopt it, right? They try it out on their laptop, they setup their first cluster. That typically goes very fast and they very quickly have their first app running. So it happens organically, right? But every large organization also has a need to put the right governance in place, right? How I keep those clusters secure? How do I meet my regulatory requirements? How do I make sure I can upgrade those clusters fast, if I need to fix a security issue and so on? So there's that tension between the governance, the central IT and what the developers want to do. We try to strike a balance there with our products to give developers the agility that cloud-native promises but at the same time, give the IT folks the right controls so they can meet their requirements. >> Tobi, here at the show this year, obviously bigger and a lot more folks at different parts of their cloud-native journey. Again, with the experience you all have, as you talk to folks this year, obviously people are clearly in production. You talk about some of the governance issues, is there anything you can say about either what you think is going to make for a successful partnership with you and a successful customer? What qualities do you need to have by the time you're growing up in production and then also as they're making choices here, what should the end users be looking at? >> Right, so one of the things we realized over the years is actually cloud-native is a journey. Every organization is somewhere else on that journey. And you said partnership, I think that's the key word here. We want to partner with our customers because we realize that this stuff is complicated, right? And it's actually for us as a company, our journey has been kind of interesting because we started at this large scale spot, right? Before we were even a company, we were running these clusters with tens of thousands of notes. These large online services at Twitter and other companies, that's where we started and that's where our first product kind of landed. It's at that large scale is what we're known for but most organizations out there are much earlier in their journey to cloud-native. As so, what we realized is that we really need to partner with folks to even at the very first steps, where they're just getting educated about this space, right? What are containers? How are they different from VMs? What is this cluster management thing, right? How does this all fit together? So we try to hold our customers' hands, catch them where they are. Besides all of the software that we're building, we also offer trainings for example. And so we just try to have the conversation with the customer. Figure out what their needs are, whether that's training, whether that's services or different products. And the different products that come together in our Kubernetes product line, they're really designed to meet the customer at these different stages. There's Konway, that's our Kubernetes distribution, get your first project up and running. Then once you get a little bit more sophisticated, you probably want to do CI/CD. So we have an upcoming product for that, it's called Dispatch. Pretty excited about it. The data services with KUDO. Folks typically add that next and then very quickly you have these dozens of hundreds of clusters. Now, you need Kommander, right? So we try to fit that all together. Meet the customer where they are and I think education is a big piece of that. >> All right, Tobi, we want to give you the final word. You talked about some of the things coming out here, so just give us your viewpoint of the ecosystem broader as to what next things need to be done to help even further the journey that we're all on? >> Yeah, I think in terms of next things, there's a lot of interest around operators. Well, operators as the implementation but really what's happening is, people are running more and more different workloads on top of Kubernetes, right? And I think that's where a lot of the work is going to happen over the next year. There's some discussions in the CNCF now even. What is an operator? How do we define that? Is it something fairly broad? Is it something fairly specific? But Kubernetes is definitely the factor standard for doing cloud-native and people are putting it in a lot of different environments. They're putting it in Edge locations. So I think we need to figure out how do you have a sane sort of development workflow for these types of deployments? How do you define an application that might actually run on multiple different clusters? So I think there's going to be a lot of talk. Operators obviously, but also on the developers side, in a layer above Kubernetes, right? How can I just define my application in a way where I say maybe just run this thing at a highly available way on two different cloud providers, instead of saying specifically it needs to go here, it needs to go there? Or deploy this thing in a follow the sun model or whatever that is. So I think that's where a lot of the conversations are going to happen, is that level above. >> All right well Tobi, appreciate the updates. Congratulations on the progress and definitely look forward to catching more from you and D2iQ team in the near future. >> Thank you very much for having me. >> All right, for John Troyer, I'm Stu Miniman, lots more to come. Thanks for watching theCUBE. (light music)

>>from San Francisco. It's the queue every day to thank you. Brought to you by day to like you. Hey, >>welcome back already, Jeffrey. Here with the Cube were a day to IQ's headquarters in downtown San Francisco. They used to be metal sphere, which is what you might know them as. And they've rebranded earlier this year. And they're really talking about helping Enterprises in their journey to cloud native. And we're really excited to have really one of the product guys he's been here and seeing this journey and how through with the customers and helping the company transforming his Chandler hosing tonight. He's the s VP of engineering and product. Chandler, great to see you. Thanks. So, first off, give everyone kind of a background on on the day to like you. I think a lot of people knew mesosphere. You guys around making noise? What kind of changed in the marketplace to to do a rebranding? >>Sure. Yeah, we've been obviously, Mason's here in the past and may so so I think a lot of people watching the cube knows No, no one knows about Mace ose as as we were going along our journey as a company. We noticed that a lot of people are also asking for carbonates. Eso We've actually been working with kubernetes since I don't know 16 4017 something that for a while now and as Maur Maur as communities ecosystem starting involving mature more. We also want to jump in and take advantage of that. And we started building some products that were specific to kubernetes and eso. We thought, Look, you know, it's a little bit confusing for people May, SOS and Kubernetes and at times those two technologies were seen almost as competitive, even though we didn't always see it that way. The market saw it that way, so we said, Look, this is going too confusing for customers being called Mesa Sphere. Let's let's rebrand around Maur what we really do. And we felt like what we do is not just focus around one specific technology. We felt like we helped customers with more than that more than just may so support more than just community support, Andi said. Look, let's let's get us a name that shows what we actually do for customers, and that's really helping them take their workloads and put them on on Not just, you know, um, a source platform, but actually take their workloads, bring them into production and enterprise way. That's really ready for day two. And that's that's why we called it data. >>And let's unpack the day to, cause I think some people are really familiar with the concept of day two. And for some people, they probably never heard it. But it's a pretty interesting concept, and I think it packs a lot of meaning in it. A number of letters. I think you >>can kind of just think about it if you were writing software, right? I mean, Day zero is okay. We're gonna design it. We're gonna start playing with some ideas. We're gonna pull into different technologies. We're gonna do a POC. We're gonna build our skateboards. So to say, that's kind of your day. Zero. What do we want? Okay, we're gonna build a Data Analytics pipeline. We want spark. We're going to store data. Cassandra, we're gonna use cough. Go to pass it around. We're gonna run our containers on top of communities. That's just kind of your day. Zero idea. You get it working, you slap it on a cluster. Things are good right? Day one might be okay. Let's actually do a beta put in production in some kind of way. You start getting customers using it. But now, in Day two, after all that's done, you're like, Wait a second. Things were going wrong. Where's our monitoring? We didn't set that up. Where's our logging? Oh, I don't know. Like, >>who do we >>call this? Our container Run time, we think has above. Who do we call like? Oh, I don't know What support contract that we cut, Right? So that's the things that we want to help customers with. We want to help them in the whole journey, getting to Day two. But once they're there, we want them to be ready for day two, right? And that's what we do. >>I love it because one of my favorite quotes I've used it 1000 times. I'll do 2001 right? Is that open source is free like a puppy. Exactly for you. When you leave you guys, you're not writing a check necessarily to the to the shelter, But there's a whole lot of other check. You got a right and take care of. And I think that's such a key piece. Thio Enterprise, right. They need somebody to call when that thing breaks. >>Yeah. I mean, I haven't come from enterprise company. I was actually a customer basis Fear before I joined. Yeah, that's exactly why we're customers that we wanted. Not only that, insurance policy, but someone that partner with us as we start figuring this out, you know? I mean, just picking. You know what container run time do I want to use with communities? That one decision could take months if you're not familiar with it. And you you put a couple of your best architects on it. Go research container. You go research, cryo go research doctor. Tell me what's what's the best one we should use with kubernetes. Whereas if you're going, if you have a partnership with a company like day two, you can say, Look, I trust these. You know this company, they they're they're experts of this and they see a lot of this. Let's go with their recommendation. It's >>okay. So you got you got your white board. You've got a whole bunch of open source things going on, right? And you've got a whole bunch of initiatives and the pressure's coming down from from on high to get going, you've got containers, Asian and Cloud native and hybrid Cloud all the stuff. And then you've got some port CEO on his team trying to figure it out. You guys have a whole plethora of service is around some of these products. So as you try it and then you got the journey right and you don't start from from a standing start. You gotta go. You gotta go. So how do you map out the combination of how people progress through their journey? What are the different types of systems that they want to put in place and into, prioritize and have some type of a logical successful implementation and roll out of these things from day zero day 132? No, it's >>a great question. I think that's actually how we formed our product. Strategy is we've been doing this for a while now and we've we've gone. We've gone on this journey with really big advanced customers like ride sharing companies and large telcos customers like that. We've also gone on this journey with smaller, less sophisticated customers like, you know, industrial customers from the Midwest. Right? And those are two very, very different customers. But what's similar is they're both going on the same journey we feel like, but they're just at different places. So we wanted to build products, find the customer where they're at in their journey, and the way we see it really is just at the very beginning. It's just training, right? So we have, ah, bunch of support. We're sorry. Service is around training. Help you understand? Not just kubernetes, but the whole cloud native ecosystem. So what is all this stuff? How does it work? How does it fit together? How do I just deploy simple app to right? That's the beginning of it. We also have some products in that area as well, to help people scale their training across the whole whole organization. So that's really exciting for us once once, once that customer has their training down there like Okay, look, get I need a cluster now, like I need a destroyer of sorts and criminals itself is great, but it needs a lot of pieces to actually get it ready for prime time. And that's where we build a product called Convoy Say Okay, here is your enterprise great. Ready to go kubernetes destro right out of the box. And that product is really it's what you could use to just fiddle around with communities. It's also what you put into production right on the game. That's that's been scale tested, security tests and mixed workload tested. It's everything. So that's that's kind of our communities. Destro. So you've gotten your training. You have your destro and now you're like, OK, I actually wanna want to run some applesauce. >>Let me hold there. Is it Is it open corps? Or, you know, there's a lot of conversation in the way the boys actually >>the way we built convoy. It's a great question. The way we build convoys said, Okay, we don't We want to pick the best of breed from each of these. Have you seen the cloud native ecosystem kind of like >>by charter, high charter, whatever it is, where they have all the logos and all the different spiral thing. So it's crazy. Got thousands of logos, right? And >>we said, Look, we're gonna navigate this for you. What's the best container run time to pick. And it's It's almost as if we were gonna build this for ourselves using all open source technology. So convoys completely opens. Okay, um, there's some special sauce that we put in on how to bring these things together. Install it. But all the actual components itself is open source. Okay, so that's so if you're a customer, you're like, OK, I want open source. I don't want to be tied to any specific vendor. I want to run on Lee open. So >>yeah, I was just thinking in terms of you know, how Duke is a reference right. And you had, you know, the Horton worst cloud there and map our strategies, which were radically different in the way they actually packaged told a dupe under the covers. Yeah, >>you can think of it similar. How Cloudera per ship, Possibly where they had cdh. And they brought in a lot of open source. But they also had a lot of proprietary components to see th and what we've tried to get away from it is tying someone in tow. Us. I know that sounds counterintuitive from a business perspective, but we don't want customers to feel like if I go with D to like you. I always have to go with me to like you. I have to drink the Kool Aid, and I'm never gonna be able to get off. >>Kind of not. Doesn't really go with the open source. Exactly this stuff. It's not >>right for our customers, right? A lot of our customers want that optionality, and they don't want to feel locked in. And so when we built convoy, he said, Look, you know, if we were to start our own company, not not an infrastructure coming that we are right now, but just a software company build any kind of ab How would we approach it? And that was one of the problems we saw for We don't wanna feel like we're tied into any. >>Right. Okay, so you got to get the training, you got the products. What's >>next? What's next is if you think about the journey, you're like, OK, a lot. What we've found and this may or may not be totally true is one of the first things people like to run on committees is actually they're builds. So see, I see. And we said, How can we help with this. We looked around the market and there's a lot of great see, I see products out there right now. There's get lab, which is great partner of ours. It's a great product. There's there's your older products. Like Jenkins. There's a bunch of sass products, Travis. See all these things. But what we we wanted to do if we were customers of our own products is something that was native to Kubernetes. And so we started looking at projects like tectonic and proud. Some of these projects, right? And we said, How can we do the same thing we did with convoy where we bring these projects together and make it easy for someone to adopt these kubernetes native. See, I see tools. And we did some stuff there that we think is pretty innovative as well. And that's what that's the product we call dispatch. >>Okay. What do you got? More than just products. You've got profession service. That's right. So now >>you need help setting all this up. How do you actually bring your legacy applications to this new platform? How do you get your legacy builds onto these new build systems That that's where our service is coming the plate and kind of steer you through this whole journey. Lastly, what we next in the journey, though? Those service's compliment Really? Well, with with the kind of the rest of the product suite, right? And we didn't just stop with C i c. He said, what is the next type of work that we want to run here? Okay, so there we looked at things like red hat operators. Right? And we said, Look, red hats doing really cool thing here with this operator framework, how can we simplify it? We learn we've done a lot of this before with D. C. O s, where we built what we called the DCS sdk to help people bring advanced complex workloads onto that platform. And we saw a lot of similarities with operators to our d c West sdk. We said, How can we bring some of our understanding and knowledge to that world? And we built this open source product called kudo. Okay, people are free to go check that out. And that's how we bring more advanced workload. So if you think about the journey back to the journey again, you got some training you have your have your cluster, you put your builds on it. Now you want to run some advance work logs? That's where Kudo comes. >>Okay? And then finally, at the end of the trail is 1 800 I need help. Well, almost into the trail. We're not there yet. There was one thing they're still moving with one more step right on >>the very last one. Actually, we said, Okay, what's next in this journey? And that's running multiple clusters of the same. Okay, so that's kind of the scale. That's the end of the journey from for us, for our proxy as it stands right now. And that's where you build a product called Commander. And that's really helping us launch and manage multiple >>companies clusters at the same time. >>So it's so great that you have the perspective of a customer and you bring that directly in two. You know what you want because you just have gone through this this journey. But I'm just curious, you know, if you put your old hat on, you know, kind of c i o your customer. You know, you just talked about the cake chart with Lord knows how many logos? How do you help people even just begin to think about about the choices and about the crazy rapid change in what? That I mean? Kubernetes wasn't a thing four years ago to help them stay on top of it to help them, you know, both kind of have a night to the vision, you know, make sure you're delivering today on not just get completely distracted by every bright, shiny object that happens to come along. Yeah, no, >>I think it's really challenging for the buyers. You know, I think there's a, especially as the industry continues to make sure there's a new concept that gets thrown at all times. Service Manager. You know, some new, cool way to do monitoring or logging right? And you almost feel like a dinosaur. If you're not right on top of these things to go to a conference in, are you using? You know, you know B P f. Yet what is that? You didn't feel right? Exactly. I think I think most importantly, what customers want is the ability what, the ability to move their technology and their platforms as their business has the need. If the need isn't there for the business, and the technology is running well. There shouldn't be a reason to move to a new platform. Our new set of technologies, in fact, with dese us with Mason charities. To us, we have a lot of happy customers that are gonna be moving crib. Amazing if they wanted to anytime soon. Do you see What's that? Something's that criminal is currently doesn't do. It may never do because the community is just not focused on it that DCS is solving. And those customers just want to see that will continue to support them in the journey that they're on with their their business. And I think that's what's most important is just really understanding our customer's understanding their business, understand where they wanna go. What are their goals, So to say, for their technology platforms and and making sure you were always one step ahead >>of them, that's a >>good place to be one step ahead of demand. All right, well, thanks for for taking a few minutes and sharing the story. Appreciate it. Okay. Thank you. All right. Thanks. Chandler. I'm Jeff. You're watching >>the Cube. Where? Day two. I >>Q in downtown San Francisco. Thanks for watching. We'll see you next time