>>Hello and welcome back to the live coverage of the Cube here. Live in Detroit, Michigan for Cub Con, our seventh year covering all seven years. The cube has been here. M John Fur, host of the Cube, co-founder of the Cube. I'm here with Lisa Mart, my co-host, and our new host, Savannah Peterson. Great to see you guys. We're wrapping up day one of three days of coverage, and our guest analyst is Sario Wall, who's the cube analyst who's gonna give us his report. He's been out all day, ear to the ground in the sessions, peeking in, sneaking in, crashing him, getting all the data. Great to see you, Sarvi. Lisa Savannah, let's wrap this puppy up. >>I am so excited to be here. My first coupon with the cube and being here with you and Lisa has just been a treat. I can't wait to hear what you have to say in on the report side. And I mean, I have just been reflecting, it was last year's coupon that brought me to you, so I feel so lucky. So much can change in a year, folks. You never know where you're be. Wherever you're sitting today, you could be living your dreams in just a few >>Months. Lisa, so much has changed. I mean, just look at the past this year. Events we're back in person. Yeah. Yep. This is a big team here. They're still wearing masks, although we can take 'em off with a cube. But mask requirement. Tech has changed. Conversations are upleveling, skill gaps still there. So much has changed. >>So much has changed. There's so much evolution and so much innovation that we've also seen. You know, we started out the keynote this morning, standing room. Only thousands of people are here. Even though there's a mass requirement, the community that is CNCF Co Con is stronger than I, stronger than I saw it last year. This is only my second co con. But the collaboration, what they've done, their devotion to the maintainers, their devotion to really finding mentors for mentees was really a strong message this morning. And we heard a >>Lot of that today. And it's going beyond Kubernetes, even though it's called co con. I also call it cloud native con, which I think we'll probably end up being the name because at the end of day, the cloud native scaling, you're starting to see the pressure points. You're start to see where things are breaking, where automation's coming in, breaking in a good way. And we're gonna break it all down Again. So much going on again, I've overs gonna be in charge. Digital is transformation. If you take it to its conclusion, then you will see that the developers are running the business. It isn't a department, it's not serving the business, it is the business. If that's the case, everything has to change. And we're, we're happy to have Sarib here with us Cube analysts on the badge. I saw that with the press pass. Well, >>Thank you. Thanks for getting me that badge. So I'm here with you guys and >>Well, you got a rapport. Let's get into it. You, I >>Know. Let's hear what you gotta say. I'm excited. >>Yeah. Went around, actually attend some sessions and, and with the analysts were sitting in, in the media slash press, and I spoke to some people at their booth and the, there are a few, few patterns, you know, which are, some are the exaggeration of existing patterns or some are kind of new patterns emerging. So things are getting complex in open source. The lawn more projects, right. They have, the CNCF has graduated some projects even after graduation, they're, they're exploring, right? Kubernetes is one of those projects which has graduated. And on that front, just a side note, the new projects where, which are entering the cncf, they're the, we, we gotta see that process and the three stages and all that stuff. I tweeted all day long, if you wanna know what it is, you can look at my tweets. But when I will look, actually write right on that actually after, after the show ends, what, what I saw there, these new projects need to be curated properly. >>I think they need to be weed. There's a lot of noise in these projects. There's a lot of overlap. So the, the work is cut out for CNCF folks, by the way. They're sort of managerial committee or whatever you call that. The, the people who are leading it, they're try, I think they're doing their best and they're doing a good job of that. And another thing actually, I really liked in the morning's keynote was that lot of women on the stage and minorities represented. I loved it, to be honest with you. So believe me, I'm a minority even though I'm Indian, but from India, I'm a minority. So people who have Punjab either know that I'm a minority, so I, I understand their pain and how hard it is to, to break through the ceiling and all that. So I love that part as well. Yeah, the >>Activity is clear. Yeah. From day one. It's in the, it's in the dna. I mean, they'll reject anything that the opposite >>Representation too. I mean, it's not just that everyone's invited, it's they're celebrated and that's a very big difference. Yeah. It's, you see conferences offer discounts for women for tickets or minorities, but you don't necessarily see them put them running where their mouth is actually recruit the right women to be on stage. Right. Something you know a little bit about John >>Diversity brings better outcomes, better product perspectives. The product is better with all the perspectives involved. Percent, it might go a little slower, maybe a little debates, but it's all good. I mean, it's, to me, the better product comes when everyone's in. >>I hope you didn't just imply that women would make society. So >>I think John men, like slower means a slower, >>More diversity, more debate, >>The worst. Bringing the diversity into picture >>Wine. That's, that's how good groups, which is, which is >>Great. I mean, yeah, yeah, >>Yeah, yeah. I, I take that mulligan back and say, hey, you knows >>That's >>Just, it's gonna go so much faster and better and cheaper, but that not diversity. Absolutely. >>Yes. Well, you make better products faster because you have a variety >>Of perspectives. The bigger the group, there's more debate. More debate is key. But the key to success is aligning and committing. Absolutely. Once you have that, and that's what open sources has been about for. Oh God, yeah. Generations >>Has been a huge theme in the >>Show generations. All right, so, so, >>So you have to add another, like another important, so observation if you will, is that the security is, is paramount right. Requirement, especially for open source. There was a stat which was presented in the morning that 60% of the projects in under CNCF have more vulnerabilities today than they had last year. So that was, That's shocking actually. It's a big jump. It's a big jump. Like big jump means jump, jump means like it can be from from 40 to 60 or or 50 or 60. But still that percentage is high. What, what that means is that lot more people are contributing. It's very sort of di carmic or ironic that we say like, Oh this project has 10,000 contributors. Is that a good thing? Right. We do. Do we know the quality of that, where they're coming from? Are there any back doors being, you know, open there? How stringent is the process of rolling those things, which are being checked in, into production? You know, who is doing that? I've >>Wondered about that. Yeah. The quantity, quality, efficacy game. Yes. And what a balance that must be for someone like CNCF putting in the structure to try and >>That's >>Hard. Curate and regulate and, and you know, provide some bumpers on the bowling lane, so to speak, of, of all of these projects. Yeah. >>Yeah. We thought if anybody thought that the innovation coming from, or the number of services coming from AWS or Google Cloud or likes of them is overwhelming, look at open source, it's even more >>Overwhelming. What's your take on the supply chain discussion? More code more happening. What are you hearing there? >>The supply chain from the software? Yeah. >>Supply chain software, supply chain security pays. Are people talking about that? What are you >>Seeing? Yeah, actually people are talking about that. The creation, the curation, not creation. Curation of suppliers of software I think is best done in the cloud. Marketplaces Ive call biased or what, you know, but curation of open source is hard. It's hard to know which project to pick. It's hard to know which project will pan out. Many of the good projects don't see the day light of the day, but some decent ones like it becomes >>A marketing problem. Exactly. The more you have out there. Exactly. The more you gotta get above the noise. Exactly. And the noise echo that. And you got, you got GitHub stars, you got contributors, you have vanity metrics now coming in to this that are influencing what's real. But sometimes the best project could have smaller groups. >>Yeah, exactly. And another controversial thing a little bit I will say that is that there's a economics of the practitioner, right? I usually talk about that and economics of the, the enterprise, right? So practitioners in our world, in software world especially right in systems world, practitioners are changing jobs every two to three years. And number of developers doubles every three years. That's the stat I've seen from Uncle Bob. He's authority on that software side of things. Wow. So that means there's a lot more new entrance that means a lot of churn. So who is watching out for the enterprise enterprises economics, You know, like are we creating stable enterprises? How stable are our operations? On a side note to that, most of us see the software as like one band, which is not true. When we talk about all these roles and personas, somebody's writing software for, for core layer, which is the infrastructure part. Somebody's writing business applications, somebody's writing, you know, systems of bracket, some somebody's writing systems of differentiation. We talk about those things. We need to distinguish between those and have principle based technology consumption, which I usually write about in our Oh, >>So bottom line in Europe about it, in your opinion. Yeah. What's the top story here at coupon? >>Top story is >>Headline. Yeah, >>The, the headline. Okay. The open source cannot be ignored. That's a headline. >>And what should people be paying attention to if there's a trend coming out? See any kind of trends coming out or any kind of signal, What, what do you see that people should pay attention to here? The put top >>Two, three things. The signal is that, that if you are a big shop, like you'd need to assess your like capacity to absorb open source. You need to be certain size to absorb the open source. If you are below that threshold, I mean we can talk about that at some other time. Like what is that threshold? I will suggest you to go with the managed services from somebody, whoever is providing those managed services around open source. So manage es, right? So from, take it from aws, Google Cloud or Azure or IBM or anybody, right? So use open source as managed offering rather than doing it yourself. Because doing it yourself is a lot more heavy lifting. >>I I, >>There's so many thoughts coming, right? >>Mind it's, >>So I gotta ask you, what's your rapport? You have some swag, What's the swag look >>Like to you? I do. Just as serious of a report as you do on the to floor, but I do, so you know, I come from a marketing background and as I, I know that Lisa does as well. And one of the things that I think about that we touched on in this is, is you know, canceling the noise or standing out from the noise and, and on a show floor, that's actually a huge challenge for these startups, especially when you're up against a rancher or companies or a Cisco with a very large budget. And let's say you've only got a couple grand for an activation here. Like most of my clients, that's how I ended up in the CU County ecosystem, was here with the A client before. So there actually was a booth over there and I, they didn't quite catch me enough, but they had noise canceling headphones. >>So if you just wanted to take a minute on the show floor and just not hear anything, which I thought was a little bit clever, but gonna take you through some of my favorite swag from today and to all the vendors, you know, this is why you should really put some thought into your swag. You never know when you're gonna end up on the cube. So since most swag is injection molded plastic that's gonna end up in the landfill, I really appreciate that garden has given all of us a potable plant. And even the packaging is plantable, which is very exciting. So most sustainable swag goes to garden. Well done >>Rep replicated, I believe is their name. They do a really good job every year. They had some very funny pins that say a word that, I'm not gonna say live on television, but they have created, they brought two things for us, yet it's replicated little etch sketch for your inner child, which is very nice. And given that we are in Detroit, we are in Motor City, we are in the home of Ford. We had Ford on the show. I love that they have done the custom K eight s key chains in the blue oval logo. Like >>Fords right behind us by the way, and are on you >>Interviewed, we had 'em on earlier GitLab taking it one level more personal and actually giving out digital portraits today. Nice. Cool. Which is quite fun. Get lap house multiple booths here. They actually IPOed while they were on the show floor at CubeCon 2021, which is fun to see that whole gang again. And then last but not least, really embracing the ship wheel logo of a Kubernetes is the robusta accrue that is giving out bucket hats. And if you check out my Twitter at sabba Savvy, you can see me holding the ship wheel that they're letting everyone pose with. So we are all in on Kubernetes. That cove gone 2022, that's for sure. Yeah. >>And this is something, day one guys, we've got three. >>I wanna get one of those >>Hats. We we need to, we need a group photo >>By the end of Friday we will have a beverage and hats on to sign off. That's, that's my word. If I can convince John, >>Don, what's your takeaway? You guys did a great kind of kickoff about last week or so about what you were excited about, what your thoughts were going to be. We're only on day one, There's been thousands of people here, we've had great conversations with contributors, the community. What's your take on day one? What's your, what's your tagline? >>Well, Savannah and I had at we up, we, we were talking about what we might see and I think we, we were right. I think we had it right. There's gonna be a lot more people than there were last year. Okay, check. That's definitely true. We're in >>Person, which >>Is refreshing. I was very surprised about the mask mandate that kind of caught me up guard. I was major. Yeah. Cause I've been comfortable without the mask. I'm not a mask person, but I had to wear it and I was like, ah, mask. But I understand I support that. But whatever. It's >>Corporate travel policy. So you know, that's what it is. >>And then, you know, they, I thought that they did an okay job with the gates, but they wasn't slow like last time. But on the content side, definitely Kubernetes security, top line headline, Kubernetes at scale security, that's, that's to me the bumper sticker top things to pay attention to the supply chain and the role of docker and the web assembly was a surprise. You're starting to see containers ecosystem coming back to, I won't say tension growth in the functionality of containers cuz they have to solve the security problem in the container images. Okay, you got scanning technology so it's a little bit in the weeds, but there's a huge movement going on to fix that problem to scale it so it's not a problem area contain. And then Dr sent a great job with productivity interviews. Scott Johnston over a hundred million in revenue so far. That's my number. They have not publicly said that. That's what I'm reporting from sources extremely well financially. And they, and they love their business model. They make productivity for developers. That's a scoop. That's new >>Information. That's a nice scoop we just dropped there on the co casually. >>You're watching that. Pay attention to that. But that, that's proof. But guess what, Red Hat's got developers too. Yes. Other people have to, So developers gonna go where it's the best. Yeah. Developers are voting with their code, they're voting with their feet. You will see the winners with the developers and that's what we've talked about. >>Well and the companies are catering to the developers. Savannah and I had a great conversation with Ford. Yeah. You saw, you showed their fantastic swag was an E for Ev right behind us. They were talking about the, all the cultural changes that they've really focused on to cater towards the developers. The developers becoming the influencers as you say. But to see a company that is as, as historied as Ford Motor Company and what they're doing to attract and retain developer talent was impressive. And honestly that surprised me. Yeah. >>And their head of deb relations has been working for, for, for 29 years. Which I mean first of all, most companies on the show floor haven't been around for 29 years. Right. But what I love is when you put community first, you get employees to stick around. And I think community is one of the biggest themes here at Cuco. >>Great. My, my favorite story that surprised me and was cool was the Red Hat Lockheed Martin interview where they had edge deployments with micro edge, >>Micro shift, >>Micro >>Shift, new projects under, there's, there are three new projects under, >>Under that was so, so cool because it was an edge story in deployment for the military where lives are on the line, they actually had it working. That is a real world example of Kubernetes and tech orchestrating to deploy the industrial edge. And I think that's proof in my mind that Kubernetes and this ecosystem is gonna move faster through this next wave of growth. Because once things start clicking, you get hybrid on premise to super cloud and edge. That was, that was my favorite cause it was real. That was real >>Story that it can make is literally life and death on the battlefield. Yeah, that was amazing. With what they're doing and what >>They're talking check out the Lockheed Martin Red Hat edge story on Silicon Angle and then a press release all pillar. >>Yeah. Another actually it's impressive, which we knew this which is happening, but I didn't know that it was happening at this scale is the finops. The finops is, I saw your is a discipline which most companies are adopting bigger companies, which are spending like hundreds of millions dollars in cloud average. Si a team size of finops for finops is seven people. And average number of tools is I think 3.5 or around 3.7 or something like that. Average number of tools they use to control the cost. So finops is a very generic term for years. It's not financial operations, it's the financial operations for the cloud cost, you know, containing the cloud costs. So that's a finops that is a very emerging sort of discipline >>To keep an eye on. And well, not only is that important, I talked to, well one of the principles over there, it's growing and they have real big players in that foundation. Their, their events are highly attended. It's super important. It's just, it's the cost side of cloud. And, and of course, you know, everyone wants to know what's going on. No one wants to leave there. Their Amazon on Yeah, you wanna leave the lights on the cloud, as we always say, you never know what the bill's gonna look like. >>The cloud is gonna reach $3 billion in next few years. So we might as well control the cost there. Yeah, >>It was, it was funny to get the reaction I found, I don't know if I was, how I react, I dunno how I felt. But we, we did introduce Super Cloud to a couple of guests and a, there were a couple reactions, a couple drawn. There was a couple, right. There was a couple, couple reactions. And what I love about the super cloud is that some people are like, oh, cringing. And some people are like, yeah, go. So it's a, it's a solid debate. It is solid. I saw more in the segments that I did with you together. People leaning in. Yeah. Super fun. We had a couple sum up, we had a couple, we had a couple cringes, I'll say their names, but I'll go back and make sure I, >>I think people >>Get 'em later. I think people, >>I think people cringe on the, on the term not on the idea. Yeah. You know, so the whole idea is that we are building top of the cloud >>And then so I mean you're gonna like this, I did successfully introduce here on the cube, a new term called architectural list. He did? That's right. Okay. And I wanna thank Charles Fitzgerald for that cuz he called super cloud architectural list. And that's exactly the point of super cloud. If you have a great coding environment, you shouldn't have to do an architecture to do. You should code and let the architecture of the Super cloud make it happen. And of course Brian Gracely, who will be on tomorrow at his cloud cast said Super Cloud enables super services. Super Cloud enables what Super services, super service. The microservices underneath the covers have to be different. High performing, automated. So again, the debate and Susan, the goal is to keep it open. And that's our, that's our goal. But we had a lot of fun with that. It was fun to poke the bear a little bit. So >>What is interesting to see just how people respond to it too, with you throwing it out there so consistently, >>You wanna poke the bear, get a conversation going, you know, let let it go. We'll see, it's been positive so far. >>There, there I had a discussion outside somebody who is from Ford but not attending this conference and they have been there for a while. I, I just some moment hit like me, like I said, people, okay, technologists are horizontal, the codes are horizontal. They will go from four to GM to Chrysler to Bank of America to, you know, GE whatever, you know, like cross vertical within vertical different vendors. So, but the culture of a company is local, right? Right. Ford has been building cars for forever. They sort of democratize it. They commercialize it, right? But they have some intense culture. It's hard to change those cultures. And how do we bring in the new thinking? What is, what approach that should be? Is it a sandbox approach for like putting new sensors on the car? They have to compete with te likes our Tesla, right? Yeah. But they cannot, if they are afraid of deluding their existing market or they're afraid of failure there, right? So it's very >>Tricky. Great stuff. Sorry. Great to have you on as our cube analyst breaking down the stories. We'll document that, that we'll roll out a post on it. Lisa Savannah, let's wrap up the show for day one. We got day two and three. We'll start with you. What's your summary? Quick bumper sticker. What's today's show all about? >>I'm a community first gal and this entire experience is about community and it's really nice to see the community come together, celebrate that, share ideas, and to have our community together on stage. >>Yeah. To me, to me it was all real. It's happening. Kubernetes cloud native at scale, it's happening, it's real. And we see proof points and we're gonna have faster time to value. It's gonna accelerate faster from here. >>The proof points, the impact is real. And we saw that in some amazing stories. And this is just a one of the cubes >>Coverage. Ib final word on this segment was well >>Said Lisa. Yeah, I, I think I, I would repeat what I said. I got eight, nine years back at a rack space conference. Open source is amazing for one biggest reason. It gives the ability to the developing nations to be at somewhat at par where the dev develop nations and, and those people to lift up their masses through the automation. Cuz when automation happens, the corruption goes down and the economy blossoms. And I think it's great and, and we need to do more in it, but we have to be careful about the supply chains around the software so that, so our systems are secure and they are robust. Yeah, >>That's it. Okay. To me for SAR B and my two great co-host, Lisa Martin, Savannah Peterson. I'm John Furry. You're watching the Cube Day one in, in the Books. We'll see you tomorrow, day two Cuban Cloud Native live in Detroit. Thanks for watching.

>>Okay, welcome back. Everyone's Cube's coverage here in Las Vegas for Amazon re Mars machine learning, automation, robotics, and space out. John fir host of the queue. Got a great set of guests here talking about AI, Jason Montgomery CTO and co-founder man and Ryans CEO, founder guys. Thanks for coming on. We're just chatting, lost my train of thought. Cuz we were chatting about something else, your history with DataRobot and, and your backgrounds entrepreneurs. Welcome to the queue. Thanks >>Tur. Thanks for having >>Us. So first, before we get into the conversation, tell me about the company. You guys have a history together, multiple startups, multiple exits. What are you guys working on? Obviously AI is hot here as part of the show. M is Mars machine learning, which we all know is the basis for AI. What's the story. >>Yeah, really. We're we're here for two of the letters and Mars. We're here for the machine learning and the automation part. So at the high level, man is a no code AI application development platform. And basically anybody could log in and start making AI applications. It could be anything from just texting it with the Twilio integration to tell you that you're doing great or that you need to exercise more to integrating with zenes to get support tickets classified. >>So Jason, we were talking too about before he came on camera about the cloud and how you can spin up resources. The data world is coming together and I, and I like to see two flash points. The, I call it the 2010 big data era that began and then failed Hadoop crashed and burned. Yeah. Then out of the, out of the woodwork came data robots and the data stacks and the snowflakes >>Data break snowflake. >>And now you have that world coming back at scale. So we're now seeing a huge era of, I need to stand up infrastructure and platform to do all this heavy lifting. I don't have time to do. Right. That sounds like what you guys are doing. Is that kind of the case? >>That's absolutely correct. Yeah. Typically you would have to hire a whole team. It would take you months to sort of get the infrastructure automation in place, the dev ops DevOps pipelines together. And to do the automation to spin up, spin down, scale up scale down requires a lot of special expertise with, you know, Kubernetes. Yeah. And a lot of the other data pipelines and a lot of the AWS technologies. So we automate a lot of that. So >>If, if DevOps did what they did, infrastructure has code. Yeah. Data has code. This is kind of like that. It's not data ops per se. Is there a category? How do you see this? Cuz it's you could say data ops, but that's also it's DevOps dev. It's a lot going on. Oh yeah. It's not just seeing AI ops, right? There's a lot more, what, what would you call this? >>It's a good question. I don't know if we've quite come up with the name. I know >>It's not data ops. It's not >>Like we call it AI process automation >>SSPA instead of RPA, >>What RPA promised to be. Yes, >>Exactly. But what's the challenge. The number one problem is it's I would say not, not so much all on ever on undifferent heavy lifting. It's a lot of heavy lifting that for sure. Yes. What's involved. What's the consequences of not going this way. If I want to do it myself, can you take me through the, the pros and cons of what the scale scope, the scale of without you guys? >>Yeah. Historically you needed to curate all your data, bring it together and have some sort of data lake or something like that. And then you had to do really a lot of feature engineering and a lot of other sort of data science on the back end and automate the whole thing and deploy it and get it out there. It's a, it's a pretty rigorous and, and challenging problem that, you know, we there's a lot of automation platforms for, but they typically focus on data scientists with these large language models we're using they're pre-trained. So you've sort of taken out that whole first step of all that data collection to start out and you can basically start prototyping almost instantly because they've already got like 6 billion parameters, 10 billion parameters in them. They understand the human language really well. And a lot of other problems. I dunno if you have anything you wanna add to that, Ryan, but >>Yeah, I think the other part is we deal with a lot of organizations that don't have big it teams. Yeah. And it would be impossible quite frankly, for them to ever do something like deploy text, track as an example. Yeah. They're just not gonna do it, but now they can come to us. They know the problem they want solved. They know that they have all these invoices as an example and they wanna run it through a text track. And now with us they can just drag and drop and say, yeah, we want tech extract. Then we wanted to go through this. This is what we >>Want. Expertise is a huge problem. And the fact that it's changing too, right? Yeah. Put that out there. You guys say, you know, cybersecurity challenges. We guys do have a background on that. So you know, all the cutting edge. So this just seems to be this it, I hate to say transformation. Cause I not the word I'm looking for, I'd say stuck in the mud kind of scenario where they can't, they have to get bigger, faster. Yeah. And the scale is bigger and they don't have the people to do it. So you're seeing the rise of managed service. You mentioned Kubernetes, right? I know this young 21 year old kid, he's got a great business. He runs a managed service. Yep. Just for Kubernetes. Why? Because no, one's there to stand up the clusters. >>Yeah. >>It's a big gap. >>So this, you have these sets of services coming in now, where, where do you guys fit into that conversation? If I'm the customer? My problem is what, what is my, what is my problem that I need you guys for? What does it look like to describe my problem? >>Typically you actually, you, you kind of know that your employees are spending a lot of time, a lot of hours. So I'll just give you a real example. We have a customer that they were spending 60 hours a week just reviewing these accounts, payable, invoices, 60 hours a week on that. And they knew there had to be a better way. So manual review manual, like when we got their data, they were showing us these invoices and they had to have their people circle the total on the invoice, highlight the customer name, the >>Person who quit the next day. Right? >>No like they, they, Hey, you know, they had four people doing this, I think. And the point is, is they come to us and we say, well, you know, AI can, can just basically using something like text track can just do this. And then we can enrich those outputs from text track with the AI. So that's where the transformers come in. And when we showed them that and got them up and running in about 30 minutes, they were mind blown. Yeah. And now this is a company that doesn't have a big it department. So the >>Kind, and they had the ability to quantify the problem >>They knew. And, and in this case it was actually a business user. It was not a technical >>In is our she consequence technical it's hours. She consequences that's wasted. Manual, labor wasted. >>Exactly. Yeah. And, and to their point, it was look, we have way more high, valuable tasks that our people could be doing yeah. Than doing this AP thing. It takes 60 hours. And I think that's really important to remember about AI. What're I don't think it's gonna automate away people's jobs. Yeah. What it's going to do is it's going to free us up to focus on what really matters and focus on the high value stuff. And that's what people should >>Be doing. I know it's a cliche. I'm gonna say it again. Cause I keep saying, cause I keep saying for people to listen, the bank teller argument always was the big thing. Oh yeah. They're gonna get killed by the ATM machine. No, they're opening up more branches. That's right. That's right. So it's like, come on. People let's get, get over that. So I, I definitely agree with that. Then the question, next question is what's your secret sauce? I'm the customer I'm gonna like that value proposition. You make something go away. It's a pain relief. Then there's the growth side. Okay. You can solve from problems. Now I want this, the, the vitamin you got aspirin. And I want the vitamin. What's the growth angle for you guys with your customers. What's the big learnings. Once they get the beach head with problem solving. >>I think it, it, it it's the big one is let's say that we start with the account payable thing because it's so our platform's so approachable. They go in and then they start tinkering with the initial, we'll call it a template. So they might say, Hey, you know what, actually, in this edge case, I'm gonna play with this. And not only do I want it to go to our accounting system, but if it's this edge case, I want it to email me. So they'll just drag and drop an email block into our canvas. And now they're making it >>Their own. There is the no code, low code's situation. They're essentially building a notification engine under the covers. They have no idea what they're doing. That's >>Right. They get the, they just know that, Hey, you know what? When, when like the amount's over $10,000, I want an email. They know that's what they want. They don't, they don't know that's the notification engine. Of >>Course that's value email. Exactly. I get what I wanted. All right. So tell me about the secret sauce. What's under the covers. What's the big, big, big scale, valuable, valuable, secret sauce. >>I would say part of it. And, and honestly, the reason that we're able to do this now is transformer architecture. When the transformer papers came out and then of course the attention is all you need paper, those kind of unlocked it and made this all possible. Beyond that. I think the other secret sauce we've been doing this a long time. >>So we kind of, we know we're in the paid points. We went to those band points. Cause we weren't data scientists or ML people. >>Yeah. >>Yeah. You, you walked the snow and no shoes on in the winter. That's right. These kids now got boots on. They're all happy. You've installed machines. You've loaded OSS on, on top of rack switches. Yeah. I mean, it's unbelievable how awesome it's right now to be a developer and now a business user's doing the low code. Yep. If you have the system architecture set up, so back to the data engineering side, you guys had the experience got you here. This is a big discussion right now. We're having in, in, on the cube and many conversations like the server market, you had that go away through Amazon and Google was one of the first, obviously the board, but the idea that servers could be everywhere. So the SRE role came out the site reliability engineer, right. Which was one guy or gal and zillions of servers. Now you're seeing the same kind of role with data engineering. And then there's not a lot of people that fit the requirement of being a data engineer. It's like, yeah, it's very unique. Cause you're dealing with a system architecture, not data science. So start to see the role of this, this, this new persona, because they're taking on all the manual challenges of doing that. You guys are kind of replaced that I think. Well, do you agree with it about the data engineer? First of all? >>I think, yeah. Well and it's different cuz there's the older data engineer and then there's sort of the newer cloud aware one who knows how to use all the cloud technologies. And so when you're trying, we've tried to hire some of those and it's like, okay, you're really familiar with old database technology, but can you orchestrate that in a serverless environment with a lot of AWS technology for instance. And it's, and that's hard though. They don't, they don't, there's not a lot of people who know that space, >>So there's no real curriculum out there. That's gonna teach you how to handle, you know, ETL. And also like I got I'm on stream data from this source. Right. I'm using sequel I'm I got put all together. >>Yeah. So it's yeah, it's a lot of just not >>Data science. It's >>Figure that out. So its a large language models too. We don't have to worry about some of the data there too. It's it's already, you know, codified in the model. And then as we collect data, as people use our platform, they can then curate data. They want to annotate or enrich the model with so that it works better as it goes. So we're kind of curating, collecting the data as it's used. So as it evolves, it just gets better. >>Well, you guys obviously have a lot of experience together and congratulations on the venture. Thank you. What's going on here at re Mars. Why are you here? What's the pitch. What's the story. Where's your, you got two letters. You got the, you got the M for the machine learning and AI and you got the, a for automation. What's the ecosystem here for you? What are you doing? >>Well, I mean, I think you, you kind of said it right. We're here because the machine learning and the automation part, >>But >>More, more widely than that. I mean we work very, very closely with Amazon on a number of front things like text track, transcribe Alexa, basically all these AWS services are just integrations within our system. So you might want to hook up your AI to an Alexa so that you could say, Hey Alexa, tell me updates about my LinkedIn feed. I don't know, whatever, whatever your hearts content >>Is. Well what about this cube transcription? >>Yeah, exactly. A hundred percent. >>Yeah. We could do that. You know, feed all this in there and then we could do summarization of everything >>Here, >>Q and a extraction >>And say, Hey, these guys are >>Technicals. Yeah, >>There you go. No, they mentioned Kubernetes. We didn't say serverless chef puppet. Those are words straight, you know, and no linguistics matters right into that's a service that no one's ever gonna build. >>Well, and actually on that point, really interesting. We work with some healthcare companies and when you're basically, when people call in and they call into the insurance, they have a question about their, what like is this gonna be covered? And what they want to key in on are things like I just went to my doctor and got a cancer diagnosis. So the, the, the relevant thing here is they just got this diagnosis. And why is that important? Well, because if you just got a diagnosis, they want to start a certain triage to make you successful with your treatments. Because obviously there's an >>Incentive to do time. That time series matters and, and data exactly. And machine learning reacts to it. But also it could be fed back old data. It used to be time series to store it. Yeah. But now you could reuse it to see how to make the machine learning better. Are you guys doing anything, anything around that, how to make that machine learning smarter, look doing look backs or maybe not the right word, but because you have data, I might as well look back at it's happened. >>So part of, part of our platform and part of what we do is as people use these applications, to your point, there's lots of data that's getting generated, but we capture all that. And that becomes now a labeled data set within our platform. And you can take that label data set and do something called fine tuning, which just makes the underlying model more and more yours. It's proprietary. The more you do it. And it's more accurate. Usually the more you do it. >>So yeah, we keep all that. I wanna ask your reaction on this is a good point. The competitive advantage in the intellectual property is gonna be the workflows. And so the data is the IP. If this refinement happens, that becomes intellectual property. Yeah. That's kind of not software. It's the data modeling. It's the data itself is worth something. Are you guys seeing that? >>Yeah. And actually how we position the company is man team is a control plane and you retain ownership of the data plane. So it is your intellectual property. Yeah. It's in your system, it's in your AWS environment. >>That's not what everyone else is doing. Everyone wants to be the control plane and the data plan. We >>Don't wanna own your data. We don't, it's a compliance and security nightmare. Yeah. >>Let's be, Real's the question. What do you optimize for? Great. And I think that's a fair, a fair bet. Given the fact that clients want to be more agile with their data anyway, and the more restrictions you put on them, why would that this only gets you in trouble? Yeah. I could see that being a and plus lock. In's gonna be a huge factor. Yeah. I think this is coming fast and no one's talking about it in the press, but everyone's like run to silos, be a silo and that's not how data works. No. So the question is how do you create siloing of data for say domain specific applications while maintaining a horizontally scalable data plan or control plan that seems to be kind of disconnected everyone to lock in their data. What do you guys think about that? This industry transition we're in now because it seems people are reverting back to fourth grade, right. And to, you know, back to silos. >>Yeah. I think, well, I think the companies probably want their silo of data, their IP. And so as they refine their models and, and we give them the ability to deploy it in their own stage maker and their own VPC, they, they retain and own it. They can actually get rid of us and they still have that model. Now they may have to build, you know, a lot of pipelines and other technology to support it. But well, >>Your lock in is usability. Exactly. And value. Yeah. Value proposition is the lock in bingo. That's not counterintuitive. Exactly. Yeah. You say, Hey, more value. How do I wanna get rid of it? Valuable. I'll pay for it. Right. As long as you have multiple value, step up. And that's what cloud does. I mean, think that's the thing about cloud. That's gonna make all this work. In my opinion, the value enablement is much higher. Yeah. So good business model. Anything else here at the show that you observed that you like, that you think people would be interested in? What's the most important story coming out of the, the holistic, if you zoom up and look at re Mars, what's, what's coming out of the vibe. >>You know, one thing that I think about a lot is we're, you know, we have Artis here, humanity hopefully soon gonna be going to Mars. And I think that's really, really exciting. And I also think when we go to Mars, we're probably not gonna send a bunch of software engineers up there. >>Right. So like robots will do break fix now. So, you know, we're good. It's gone. So services are gonna be easy. >>Yeah. But I, oh, >>I left that device back at earth. I just think that's not gonna be good. Just >>Replicated it in one. I think there's like an eight >>Minute, the first monopoly on next day delivery in space. >>They'll just have a spaceship that sends out drones to Barss. Yeah. But I think that when we start going back to the moon and we go to Mars, people are gonna think, Hey, I need this application now to solve this problem that I didn't anticipate having. And in science fiction, we kind of saw this with like how, right? Like you had this AI on this computer or this, on this spaceship that could do all this stuff. We need that. And I haven't seen that here yet. >>No, it's not >>Here yet. And >>It's right now I think getting the hardware right first. Yep. But we did a lot of reporting on this with the D O D and the tactile edge, you know, military applications. It's a fundamental, I won't say it's a tech, religious argument. Like, do you believe in agile realtime data or do you believe in democratizing multi-vendor, you know, capability? I think, I think the interesting needs to sort itself out because sometimes multi vendor multi-cloud might not work for an application that needs this database or this application at the edge. >>Right. >>You know, so if you're in space, the back haul, it matters. >>It really does. Yeah. >>Yeah. Not a good time to go back and get that highly available data. You mean highly, is it highly available or there's two terms highly available, which means real time and available. Yeah. Available means it's on a dis, right? >>Yeah. >>So that's a big challenge. Well guys, thanks for coming on. Plug for the company. What are you guys up to? How much funding do you have? How old are you staff hiring? What's some of the details. >>We're about 45 people right now. We are a globally distributed team. So we hire every like from every country, pretty much we are fully remote. So if you're looking for that, hit us up, definitely always look for engineers, looking for more data scientists. We're very, very well funded as well. And yeah. So >>You guys headquarters out, you guys headquartered. >>So a lot of us live in Columbus, Ohio that's technically HQ, but like I said, we we're in pretty much every continent except in Antarctica. So >>You're for all virtual. >>Yeah. A hundred percent virtual, a hundred percent. >>Got it. Well, congratulations and love to hear that Datadog story at another time >>Or DataBot >>Yeah. I mean data, DataBot sorry. Let's get, get all confused >>Data dog data company. >>Well, thanks for coming on and congratulations for your success and thanks for sharing. Yeah. >>Thanks for having us for having >>Pleasure to be here. It's a cube here at rebars. I'm John furier host. Thanks for watching more coming back after this short break.

>>Yeah, yeah. Welcome back to the third session in our building, A vibrant data ecosystem track. This session is unleash the power of your cloud data warehouse. So what comes after you've moved your data to the cloud in this session will explore White Enterprise Analytics is finally ready for the cloud, and we'll discuss how you can consume Enterprise Analytics in the very same way he would cloud services. We'll also explore where analytics meets cloud and see firsthand how thought spot is open for everyone. Let's get going. I'm happy to say we'll be hearing from two folks from thought spot today, Michael said Cassie, VP of strategic partnerships, and Vika Valentina, senior product marketing manager. And I'm very excited to welcome from our partner at AWS Gal Bar MIA, product engineering manager with Red Shift. We'll also be sharing a live demo of thought spot for BTC Marketing Analytics directly on Red Shift data. Gal, please kick us off. >>Thank you, Military. And thanks. The talks about team and everyone attending today for joining us. When we talk about data driven organizations, we hear that 85% of businesses want to be data driven. However, on Lee. 37% have been successful in We ask ourselves, Why is that and believe it or not, Ah, lot of customers tell us that they struggled with live in defining what being data driven it even means, and in particular aligning that definition between the business and the technology stakeholders. Let's talk a little bit. Let's look at our own definition. A data driven organization is an organization that harnesses data is an asset. The drive sustained innovation and create actionable insights. The super charge, the experience of their customers so they demand more. Let's focus on a few things here. One is data is an asset. Data is very much like a product needs to evolve sustained innovation. It's not just innovation innovation, it's sustained. We need to continuously innovate when it comes to data actionable insights. It's not just interesting insights these air actionable that the business can take and act upon, and obviously the actual experience we. Whether whether the customers are internal or external, we want them to request Mawr insights and as such, drive mawr innovation, and we call this the for the flywheel. We use the flywheel metaphor here where we created that data set. Okay, Our first product. Any focused on a specific use case? We build an initial NDP around that we provided with that with our customers, internal or external. They provide feedback, the request, more features. They want mawr insights that enables us to learn bringing more data and reach that actual data. And again we create MAWR insights. And as the flywheel spins faster, we improve on operational efficiencies, supporting greater data richness, and we reduce the cost of experimentation and legacy environments were never built for this kind of agility. In many cases, customers have struggled to keep momentum in their fleet, flywheel in particular around operational efficiency and experimentation. This is where Richie fits in and helps customer make the transition to a true data driven organization. Red Shift is the most widely used data warehouse with tens of thousands of customers. It allows you to analyze all your data. It is the only cloud data warehouse that sits, allows you to analyze data that sits in your data lake on Amazon, a street with no loading duplication or CTL required. It is also allows you to scale with the business with its hybrid architectures it also accelerates performance. It's a shared storage that provides the ability to scale toe unlimited concurrency. While the UN instant storage provides low late and say access to data it also provides three. Key asks that customers consistently tell us that matter the most when it comes to cost. One is usage based pricing Instead of license based pricing. Great value as you scale your data warehouse using, for example, reserved instances they can save up to 75% compared to on the mind demand prices. And as your data grows, infrequently accessed data can be stored. Cost effectively in S three encouraged through Amazon spectrum, and the third aspect is predictable. Month to month spend with no hitting charges and surprises. Unlike and unlike other cloud data warehouses, where you need premium versions for additional enterprise capabilities. Wretched spicing include building security compression and data transfer. >>Great Thanks. Scout um, eso. As you can see, everybody wins with the cloud data warehouses. Um, there's this evolution of movement of users and data and organizations to get value with these cloud data warehouses. And the key is the data has to be accessible by the users, and this data and the ability to make business decisions on the data. It ranges from users on the front line all the way up to the boardroom. So while we've seen this evolution to the Cloud Data Warehouse, as you can see from the statistic from Forrester, we're still struggling with how much of that data actually gets used for analytics. And so what is holding us back? One of the main reasons is old technology really trying to work with today's modern cloud data warehouses? They weren't built for it. So you run into issues of trying to do data replication, getting the data out of the cloud data warehouse. You can do analysis and then maintaining these middle layers of data so that you can access it quickly and get the answers you need. Another issue that's holding us back is this idea that you have to have your data in perfect shape with the perfect pipeline based on the exact dashboard unique. Um, this isn't true. Now, with Cloud data warehouse and the speed of important business data getting into those cloud data warehouses, you need a solution that allows you to access it right away without having everything to be perfect from the start, and I think this is a great opportunity for GAL and I have a little further discussion on what we're seeing in the marketplace. Um, one of the primary ones is like, What are the limiting factors, your Siegel of legacy technologies in the market when it comes to this cloud transformation we're talking about >>here? It's a great question, Michael and the variety of aspect when it comes to legacy, the other warehouses that are slowing down innovation for companies and businesses. I'll focus on 21 is performance right? We want faster insights. Companies want the ability to analyze MAWR data faster. And when it comes to on prem or legacy data warehouses, that's hard to achieve because the second aspect comes into display, which is the lack of flexibility, right. If you want to increase your capacity of your warehouse, you need to ensure request someone needs to go and bring an actual machine and install it and expand your data warehouse. When it comes to the cloud, it's literally a click of a button, which allows you to increase the capacity of your data warehouse and enable your internal and external users to perform analytics at scale and much faster. >>It falls right into the explanation you provided there, right as the speed of the data warehouses and the data gets faster and faster as it scales, older solutions aren't built toe leverage that, um, you know, they're either they're having to make technical, you know, technical cuts there, either looking at smaller amounts of data so that they can get to the data quicker. Um, or it's taking longer to get to the data when the data warehouse is ready, when it could just be live career to get the answers you need. And that's definitely an issue that we're seeing in the marketplace. I think the other one that you're looking at is things like governance, lineage, regulatory requirements. How is the cloud you know, making it easier? >>That's That's again an area where I think the cloud shines. Because AWS AWS scale allows significantly more investment in securing security policies and compliance, it allows customers. So, for example, Amazon redshift comes by default with suck 1 to 3 p. C. I. Aiso fared rampant HIPPA compliance, all of them out of the box and at our scale. We have the capacity to implement those by default for all of our customers and allow them to focus. Their very expensive, valuable ICTY resource is on actual applications that differentiate their business and transform the customer experience. >>That's a great point, gal. So we've talked about the, you know, limiting factors. Technology wise, we've mentioned things like governance. But what about the cultural aspect? Right? So what do you see? What do you see in team struggling in meeting? You know, their cloud data warehouse strategy today. >>And and that's true. One of the biggest challenges for large large organizations when they moved to the cloud is not about the technology. It's about people, process and culture, and we see differences between organizations that talk about moving to the cloud and ones that actually do it. And first of all, you wanna have senior leadership, drive and be aligned and committed to making the move to the cloud. But it's not just that you want. We see organizations sometimes Carol get paralyzed. If they can't figure out how to move each and every last work clothes, there's no need to boil the ocean, so we often work with organizations to find that iterative motion that relative process off identifying the use cases are date identifying workloads in migrating them one at a time and and through that allowed organization to grow its knowledge from a cloud perspective as well as adopt its tooling and learn about the new capabilities. >>And from an analytics perspective, we see the same right. You don't need a pixel perfect dashboard every single time to get value from your data. You don't need to wait until the data warehouse is perfect or the pipeline to the data warehouse is perfect. With today's technology, you should be able to look at the data in your cloud data warehouse immediately and get value from it. And that's the you know, that's that change that we're pushing and starting to see today. Thanks. God, that was That was really interesting. Um, you know, as we look through that, you know, this transformation we're seeing in analytics, um, isn't really that old? 20 years ago, data warehouses were primarily on Prem and the applications the B I tools used for analytics around them were on premise well, and so you saw things like applications like Salesforce. That live in the cloud. You start having to pull data from the cloud on Prem in order to do analytics with it. Um, you know, then we saw the shift about 10 years ago in the explosion of Cloud Data Warehouse Because of their scale, cost reduced, reduce shin reduction and speed. You know, we're seeing cloud data. Warehouses like Amazon Red Shift really take place, take hold of the marketplace and are the predominant ways of storing data moving forward. What we haven't seen is the B I tools catch up. And so when you have this new cloud data warehouse technology, you really need tools that were custom built for it to take advantage of it, to be able to query the cloud data warehouse directly and get results very quickly without having to worry about creating, you know, a middle layer of data or pipelines in order to manage it. And, you know, one company captures that really Well, um, chick fil A. I'm sure everybody has heard of is one of the largest food chains in America. And, you know, they made a huge investment in red shift and one of the purposes of that investment is they wanted to get access to the data mawr quickly, and they really wanted to give their business users, um, the ability to do some ad hoc analysis on the data that they were capturing. They found that with their older tools, the problems that they were finding was that all the data when they're trying to do this analysis was staying at the analyst level. So somebody needed to create a dashboard in order to share that data with a user. And if the user's requirements changed, the analysts were starting to become burdened with requests for changes and the time it took to reflect those changes. So they wanted to move to fought spot with embrace to connect to Red Shift so they could start giving business users that capability. Query the database right away. And with this, um, they were able to find, you know, very common things in in the supply chain analysis around the ability to figure out what store should get, what product that was selling better. The other part was they didn't have to wait for the data to get settled into some sort of repository or second level database. They were able to query it quickly. And then with that, they're able to make changes right in the red shift database that were then reflected to customers and the business users right away. So what they found from this is by adopting thought spot, they were actually able to arm business users with the ability to make decisions very quickly. And they cleared up the backlog that they were having and the delay with their analysts. And they're also putting their analysts toe work on different projects where they could get better value from. So when you look at the way we work with a cloud data warehouse, um, you have to think of thoughts about embrace as the tool that access that layer. The perfect analytic partner for the Cloud Data Warehouse. We will do the live query for the business user. You don't need to know how to script and sequel, um Thio access, you know, red shift. You can type the question that you want the answer to and thought spot will take care of that query. We will do the indexing so that the results come back faster for you and we will also do the analysis on. This is one of the things I wanted to cover, which is our spot i. Q. This is new for our ability to use this with embrace and our partners at Red Shift is now. We can give you the ability to do auto analysis to look at things like leading indicators, trends and anomalies. So to put this in perspective amount imagine somebody was doing forecasting for you know Q three in the western region. And they looked at how their stores were doing. And they saw that, you know, one store was performing well, Spot like, you might be able to look at that analysis and see if there's a leading product that is underperforming based on perhaps the last few quarters of data. And bring that up to the business user for analysis right away. They don't need to have to figure that out. And, um, you know, slice and dice to find that issue on their own. And then finally, all the work you do in data management and governance in your cloud data warehouse gets reflected in the results in embrace right away. So I've done a lot of talking about embrace, and I could do more, but I think it would be far better toe. Have Vika actually show you how the product works, Vika. >>Thanks, Michael. We learned a lot today about the power of leveraging your red shift data and thought spot. But now let me show you how it works. The coronavirus pandemic has presented extraordinary challenges for many businesses, and some industries have fared better than others. One industry that seems to weather the storm pretty well actually is streaming media. So companies like Netflix and who Lou. And in this demo, we're going to be looking at data from B to C marketing efforts. First streaming media company in 2020 lately, we've been running campaigns for comedy, drama, kids and family and reality content. Each of our campaigns last four weeks, and they're staggered on a weekly basis. Therefore, we always have four campaigns running, and we can focus on one campaign launch per >>week, >>and today we'll be digging into how our campaigns are performing. We'll be looking at things like impressions, conversions and users demographic data. So let's go ahead and look at that data. We'll see what we can learn from what's happened this year so far, and how we can apply those learnings to future decision making. As you can already see on the thoughts about homepage, I've created a few pin boards that I use for reporting purposes. The homepage also includes what others on my team and I have been looking at most recently. Now, before we dive into a search, will first take a look at how to make a direct connection to the customer database and red shift to save time. I've already pre built the connection Red Shift, but I'll show you how easy it is to make that connection in just three steps. So first we give the connection name and we select our connection type and was on red Shift. Then we enter our red shift credentials, and finally, we select the tables that we want to use Great now ready to start searching. So let's start in this data to get a better idea of how our marketing efforts have been affected either positively or negatively by this really challenging situation. When we think of ad based online marketing campaigns, we think of impressions, clicks and conversions. Let's >>look at those >>on a daily basis for our purposes. So all this data is available to us in Thought spot, and we can easily you search to create a nice line chart like this that shows US trends over the last few months and based on experience. We understand that we're going to have more clicks than impressions and more impressions and conversions. If we started the chart for a minute, we could see that while impressions appear to be pretty steady over the course of the year, clicks and especially conversions both get a nice boost in mid to late March, right around the time that pandemic related policies were being implemented. So right off the bat, we found something interesting, and we can come back to this now. There are few metrics that we're gonna focus on as we analyze our marketing data. Our overall goal is obviously to drive conversions, meaning that we bring new users into our streaming service. And in order to get a visitor to sign up in the first place, we need them to get into our sign up page. A compelling campaign is going to generate clicks, so if someone is interested in our ad, they're more likely to click on it, so we'll search for Click through Rape 5% and we'll look this up by campaign name. Now even compare all the campaigns that we've launched this year to see which have been most effective and bring visitors star site. And I mentioned earlier that we have four different types of campaign content, each one aligned with one of our most popular genres. So by adding campaign content, yeah, >>and I >>just want to see the top 10. I could limit my church. Just these top 10 campaigns automatically sorted by click through rate and assigned a color for each category so we could see right away that comedy and drama each of three of the top 10 campaigns by click through rate reality is, too, including the top spot and kids and family makes one appearance as well. Without spot. We know that any non technical user can ask a question and get an answer. They can explore the answer and ask another question. When you get an answer that you want to share, keep an eye on moving forward, you pin the answer to pin board. So the BBC Marketing Campaign Statistics PIN board gives us a solid overview of our campaign related activities and metrics throughout 2020. The visuals here keep us up to date on click through rate and cost per click, but also another really important metrics that conversions or cost proposition. Now it's important to our business that we evaluate the effectiveness of our spending. Let's do another search. We're going to look at how many new customers were getting so conversions and the price cost per acquisition that we're spending to get each of these by the campaign contact category. So >>this is a >>really telling chart. We can basically see how much each new users costing us, based on the content that they see prior to signing up to the service. Drama and reality users are actually relatively expensive compared to those who joined based on comedy and kids and family content that they saw. And if all the genres kids and family is actually giving us the best bang for our marketing >>buck. >>And that's good news because the genres providing the best value are also providing the most customers. We mentioned earlier that we actually saw a sizable uptick in conversions as stay at home policies were implemented across much of the country. So we're gonna remove cost per acquisition, and we're gonna take a daily look how our campaign content has trended over the years so far. Eso By doing this now, we can see a comparison of the different genres daily. Some campaigns have been more successful than others. Obviously, for example, kids and family contact has always fared pretty well Azaz comedy. But as we moved into the stay at home area of the line chart, we really saw these two genres begin to separate from the rest. And even here in June, as some states started to reopen, we're seeing that they're still trending up, and we're also seeing reality start to catch up around that time. And while the first pin board that we looked at included all sorts of campaign metrics, this is another PIN board that we've created so solely to focus on conversions. So not only can we see which campaigns drug significant conversions, we could also dig into the demographics of new users, like which campaigns and what content brought users from different parts of the country or from different age groups. And all this is just a quick search away without spot search directly on a red shift. Data Mhm. All right, Thank you. And back to you, Michael. >>Great. Thanks, Vika. That was excellent. Um, so as you can see, you can very quickly go from zero to search with thought Spot, um, connected to any cloud data warehouse. And I think it's important to understand that we mentioned it before. Not everything has to be perfect. In your doubt, in your cloud data warehouse, um, you can use thought spot as your initial for your initial tool. It's for investigatory purposes, A Z you can see here with star, Gento, imax and anthem. And a lot of these cases we were looking at billions of rows of data within minutes. And as you as your data warehouse maturity grows, you can start to add more and more thoughts about users to leverage the data and get better analysis from it. So we hope that you've enjoyed what you see today and take the step to either do one of two things. We have a free trial of thoughts about cloud. If you go to the website that you see below and register, we can get you access the thought spots so you can start searching today. Another option, by contacting our team, is to do a zero to search workshop where 90 minutes will work with you to connect your data source and start to build some insights and exactly what you're trying to find for your business. Um thanks, everybody. I would especially like to thank golf from AWS for joining us on this today. We appreciate your participation, and I hope everybody enjoyed what they saw. I think we have a few questions now. >>Thank you, Vika, Gal and Michael. It's always exciting to see a live demo. I know that I'm one of those comedy numbers. We have just a few minutes left, but I would love to ask a couple of last questions Before we go. Michael will give you the first question. Do I need to have all of my data cleaned and ready in my cloud data warehouse before I begin with thought spot? >>That's a great question, Mallory. No, you don't. You can really start using thought spot for search right away and start getting analysis and start understanding the data through the automatic search analysis and the way that we query the data and we've seen customers do that. Chick fil a example that we talked about earlier is where they were able to use thoughts bought to notice an anomaly in the Cloud Data Warehouse linking between product and store. They were able to fix that very quickly. Then that gets reflected across all of the users because our product queries the Cloud Data Warehouse directly so you can get started right away without it having to be perfect. And >>that's awesome. And gal will leave a fun one for you. What can we look forward to from Amazon Red Shift next year? >>That's a great question. And you know, the team has been innovating extremely fast. We released more than 200 features in the last year and a half, and we continue innovating. Um, one thing that stands out is aqua, which is a innovative new technology. Um, in fact, lovely stands for Advanced Square Accelerator, and it allows customers to achieve performance that up to 10 times faster, uh, than what they've seen really outstanding and and the way we've achieved that is through a shift in paradigm in the actual technological implementation section. Uh, aqua is a new distributed and hardware accelerated processing layer, which effectively allows us to push down operations analytics operations like compression, encryption, filtering and aggregations to the storage there layer and allow the aqua nodes that are built with custom. AWS designed analytics processors to perform these operations faster than traditional soup use. And we no longer need to bring, you know, scan the data and bring it all the way to the computational notes were able to apply these these predicates filtering and encourage encryption and compression and aggregations at the storage level. And likewise is going to be available for every are a three, um, customer out of the box with no changes to come. So I apologize for being getting out a little bit, but this is really exciting. >>No, that's why we invited you. Call. Thank you on. Thank you. Also to Michael and Vika. That was excellent. We really appreciate it. For all of you tuning in at home. The final session of this track is coming up shortly. You aren't gonna want to miss it. We're gonna end strong, come back and hear directly from our customer a T mobile on how T Mobile is building a data driven organization with thought spot in which >>pro, It's >>up next, see you then.