Superstar watch along I'm gonna ask for that when I go into the grocery store. Hey, you guys got any pot up up by it But up up by out you can't do that to people anymore They just look at you side you order food sometimes and you just change it a little bit and people go If you're seeing this on YouTube just like the other parts if you haven't seen the two parts Please go watch those parts Reasons if you'd like to see full on cut versions, but you can ever the patreon Check that out and at the end of this part We will talk about the movie and review it She's gonna say don't I look fantastic don't I smell fantastic Well, I give them bathed for 18 years. Oh my the power. Hmm. Well, well, well, well, he's swinging Oh He'll have no fury like a woman's score Whatever will he do? Whatever will he do?  Better don't come in my way. We are dead people. Black cats. Tell everyone. My son is dead. We can do anything. Whoa! How many times do I have to break it? So good luck! Dang! Were those dummies? They had to be right. Oh my! Gyao physics head. Physics mean nothing, yeah. Gyao physics head! Whoa! Wow! Good grief! That's pretty sweet how they do that.  Yeah, good luck. Oh yes!  Just tear it all apart. These jumps! Wow! Good lord! You could see the ram that shot them up into the air following them, yeah. He's got a bazooka now. My word! It's gone off the rails, broken loose! Yes! This is what you have to do to get that superstar. That was amazing. Oh yes, that's typically what happens when you go straight out of the car. You just automatically shoot straight into the air. Makes a lot of sense. I love these ramp shots. Where is she with her machine gun? She's coming, don't worry. What exactly is that sound anyway? Yeah, here she comes. Get him!   She won't be able to resist. Yeah! She won't be able to resist. Someone needs to put Joe Biden's face over Rajnikov. Use it for his campaign. Ow! Round of the tailbone. I think he wants you. Yeah! Prediction. I think she's gonna fall down the well. Yeah, I was having the exact same thought. That's where she ends. She ends in the well. No! Yeah! What's gonna happen? She's going to be chased by that bull, because she's wearing red. And she's gonna fall in the well. And no one's gonna save her. Have you? No one can. He bends the bullets. They hear it come!  Oh no. Stop the bull.  You gave me nothing but good. Yeah. Not wrong. I don't believe her. I don't believe her one minute. Exactly. No, you're not. My rage will keep me alive. I don't want you to live without me. I don't want you to live without me. Oh! I think so. Loved her. Great. Yeah, I'll remember her character for a long, long time. Yeah, that was a lot. And her name is... Which one is she? That one, right? Yeah. Yes. Yeah. Ramya Krishnan. Ramya Krishnan. At least you did correctly get her in Bahubali. Bahubali. She's super relaxed. We've seen her in a few things. Which must have been another added level. You know, there's so much about it. Having her in it. Having grown up. Watching Donald Sinema and seeing her in this. Getting to see her in Bahubali. You know, when we saw Bahubali, we didn't know who she was. We didn't know who Prabhas was. We didn't know anybody. So, it adds so much more depth to see her. If I watch Bahubali again, I'll enjoy it so much more just because she's in it. Yeah. Yeah, she was great. And Rajna Khan's Rajna Khan. Yeah, that was a lot of fun. So much fun. Very 90s. We've seen a lot of 90s Hindi films. Right. Not that this was full on Kieran Johar. Not at all. It was for a hot minute. When we got to the 18 years later thing with the daughter. But it had that 90s flair almost that we have not seen too much outside of Hindi cinema. Right. But it had some of those elements in it. It did. Of the drama, the melodrama, the close ups, the obsession with like constant. Yeah. It was fun though. Very entertaining. I enjoy the, this is the first time we've seen superstar classic. Yeah. Back in the day, we've only ever seen, we've seen like old school classics of him, but it wasn't him as superstar. It wasn't him as the actor Rajna Khan before he became the persona that is superstar. Yeah. And for all of you who've grown up watching him, how fun it must be to see, you know, his movies now where he's just continuing to be who he's always been. Yeah. It's got to be just great. Yeah. And this was a lot of fun. Great recommendation. I know he's a lot of like classic references. And it's one of the reasons I wanted to get it because I know this is like one of the big classics of back in the day for him of becoming superstar. And so like any newer stuff will probably have references to like this one or a couple others. Well, clearly that's one of the ones on the shirt. Yeah, right there. Yeah. Most of what I think is another one. I think maybe it's that one. I forget. That's so good. So entertaining. He's a lot of fun.  I loved every second she was on screen. Yeah, she was a lot of fun to watch. Her whole arc of being like this annoying, self obsessed person and then turning into like this like villain of like, if I can have you, no one is. Yes. I know who I want in Drani to dress up in cosplay. Oh, yeah. Yeah. She got to dress up like her. And I'll be a Rajnikanth, but I'm giving in. I'm just, I'm just straight up giving in.  Your highness. I didn't know that our nonbar actually did the music for this. At least I did. I forgot. Yeah, I had forgotten that too. I think it should have been clear when that one song in particular that we've heard several times. Yeah. It's been around obviously very long time, but yeah, it was a lot of fun. It was it was a really good time. KS. Why do I know that name? KS Ravi. Yeah, we've seen that name a lot. Have we seen any of his films or do I just know him from like when we look up his, is he an actor as well? Is that why? Apparently so. Writer, director, producer. 76 things he's done as an actor. Trying to see if there's something that we've seen of his as a director outside of this now. But I thought it was a lot of fun. It was a lot of like elements of keeping you engaged and the scale of the film a couple of times. I didn't mention it, but the scale of the film was huge. Sometimes they had a montage sequence where he was doing the construction and the mining and the people were eating. And I thought that's a lot of production for just a quick montage sequence. So I don't know if it was storyboarded that way or thought of beforehand. Another superstar from before this one. He also directed. I think he's on the shirt somewhere. I don't know which one though. Same director. It's another superstar classic. I've heard a lot about a few years before this. Is she in it? Same director. I'm going to ask all the time. Bummer. Mina, who we've seen before is I think the lead in it. But maybe that's another one you guys can tell us if it's worth a watch. We've seen that a few times. I don't know if it's in Tamil cinema or just Indian cinema in general. There's no action at all. Right.  Off the rails. Which was a lot of fun. These things that run straight into a tree, they would just stop. They go 50 feet up. I love it. It's absolutely hilarious. It's not as big, but it reminds me of the same joy I had watching that graveyard fight at the end of Dawn. Very similar. Very similar to that. It was just the style. It was like we want to give you some over the top action. Over the top action. To pie physics. Which is a lot of fun. The songs were great. I thought a lot of the stunt work. In terms of the stunt work of people falling in particular. Yeah. Like they took some hard hits. Hard hits. Hitting cars before they hit the ground. Some really good stuff. And good plot twists. I thought it was going to end a certain way. I did not foresee her turning the gun on herself. Yeah. Like what she did to the kid. Right. I thought she was going to do something different. A lot of good twists. I like that she remained the villain the entire time. Me too. It wasn't like a change of heart. No, that would have sucked. When she started saying what she was saying, I thought, no, this can't be. She's too committed to jumping his bones. Yeah, a lot of great. Or not letting anybody else. She must have had so much fun portraying this character. Yeah, 1999. I bet it's a pretty iconic performance for her. Gotta be. In her career. Maybe she has a ton, obviously. We're still newbies to her. But she was a lot of fun. I thought his love interest was cute and did a good job. Well cast. Obviously she, the villain, had a lot more meaty stuff to do in this. Yeah. One of the lesser scenes when I thought it was a pretty iconic, when she was intimidating with her foot on her face. I was like, damn. Yeah. They were so many moments like that. I was just, yeah, okay. Handcuff me. Take me away. Just do it. Just take me. That's what made her so great was that she wasn't repulsive. She wasn't this, there wasn't this sense of, ew, he would never do that. It was the sense of, yeah. She's tough to resist, man. You've got good staying power. I feel like you could, you could do a sequel to this, like Raj Khanta and his current age and then bring her back and like she's reincarnated into somebody else's. Somebody do that. That would be so great. I was hoping like they would go a little further with her in the room for 18 years.  She's totally. She's totally gone. Her nails are this long. 1999. I would do it. I would do it to look at Raj's. I just wanted to be like, maybe she probably said that. Wouldn't I have been defecating on myself?  A little different movie in the 1990. I get it. I get it. But I just wanted her to keep going farther because I enjoyed it. That was fun. Thanks for that. I hope you enjoyed it. Enjoyed the watch along because we did as well. Let us know what the next Tamil film should be. Let us know what the next Raj Dekant and all of them. Ramya. Ramya film should be. Next watch along should be and if you saw us on YouTube, you saw a very cut up version. If you'd like to see full on cut versions you can have it on Patreon. I'll put a link in the description below in the pinned comment so you can go check that out. And on to the next watch along.


Epigenetics is an old system and has been regulating our genes for millions of years. Healthy bodies need many types of functioning cells like brain cells, skin cells, and white blood cells. But did you know that different cells contain the same DNA? Difference between cells in your liver versus your brain is not the DNA per se, but that the different parts of the DNA are turned on or off. These different parts of DNA are called genes. Epigenetics controls when each of over 20,000 genes is turned on and off in every one of our 100 trillion cells. When the gene is not needed, the regulator turns it off, keeping the gene from making its product. Epigenetics directs how we grow in the womb and through life. If this system is altered, genes can be turned on or off in the wrong cells or at the wrong time. Recently, humans have created thousands of new chemicals. Scientists know that some of these chemicals can change our epigenetics, altering how our genes are regulated. Some of these chemicals are in air pollution from cars and trucks. Some in pesticide formulations. And one chemical called BPA is in canned foods, linings, and in some plastic bottles and some store receipts. So how do these chemicals affect epigenetics? When pesticides are sprayed on fruits and vegetable crops to kill pests, their residues may remain for us to ingest. Farm workers, their families, or people living close to farms, can be exposed to pesticides by ingesting and inhaling these chemicals. People who use pesticides on their lawns and gardens can also get exposed by touching them and inhaling these chemicals. When pesticides travel through our bodies, some can alter the epigenetic system. The same is true for ingestion of excessive amounts of BPA or inhalation of certain air pollutants. The chemicals can remove gene regulators, allowing genes that are off to turn on. This can lead to too many genes being on at the same time or the wrong genes being on at the wrong time. The more the system is affected, the greater our chance for illness. Chemicals in the environment can upset gene regulation in both adults and children. Support healthy bodies by helping to reduce air pollution. Find out about legislation on environmental pollution and chemical policy to be an informed voter. And avoid BPA and foods with high pesticide residues, particularly if you're pregnant. A clean environment supports health for this generation and the next.


Welcome, everyone, to today's Santa Rosa City Council meeting. Madam City Clerk, can we get a roll call? Let the record show that all councilmembers are present. Great. Now, item two on the agenda is going to be the administration of oath of office and presentation of certificate of appointment to newly appointed councilmember Richard Dowd. Madam City Clerk will be administering the oath. Welcome, Mr. Dowd. Please repeat after me. I, Richard Dowd, do solemnly swear that I will support and defend the Constitution of the United States and the Constitution of the State of California against all enemies, foreign and domestic, that I will bear true faith and allegiance to the Constitution of the United States and the Constitution of the State of California that I take this obligation freely without any mental reservation or purpose of evasion and that I will well and faithfully discharge the duties upon which I am about to enter. This is subscribed and sworn to this before me on this 14th day of January, 2020, in the city of Santa Rosa, California. Thank you, Mr. Dowd. Welcome aboard. Thank you. Mr. Dowd, before you make any comments, did we have any cards on this item? So, definitely we'd do the one public comment, then I'd invite you to make some comments. And Mr. City Manager, is this a live mic down here? Is this one operational? We have one card on this item, Mr. Dwayne DeWitt. Your preference. Feelings mutual, Dwayne. For taking on this sometimes thankless task, it's a wonderful thing that you volunteered your time, and I wanted to commend him for all of his time that he spent on the board of public utilities. He met me through my coming there and getting a chance to perhaps talk about positive things that could occur that that board had within its purview. He has seemed to be a fair and good man. I hope he stays that way in this position on into the future. Good luck to you in the new year, sir. Thank you. Thank you. Mr. Dowd, would you like to make any comments? Thank you very much, Mayor and other members of the council. It's a great pleasure for me to sit here with you and look for ways to improve our fine city. I also want to say that I'm really was quite proud, even though it was overwhelming to fill in the application to get the appointment, but I was very proud that this community had 19 different people who wanted to help out. And when you add up the council and all the boards and commissions that this city has, I think we have a strong leadership help and pull the wagon in our community and it makes me proud to be a resident here. I do want to take a moment to say I have friends and family here, my wife and sister-in-law and one of my sons, good friends, the Zoom alts and good friend, Ananda Sweet from the chamber and a fellow colleague at the Board of Public Utilities, Lisa Baddon Fort. I just want to say that I spent 25 years on the BPU. There were a lot of stressful times and stressful decisions that had to be made, but together the BPU and the City Council, I think, accomplished a lot and it makes me proud to have that heritage. Thank you very much. Thank you for your willingness to participate. Look forward to seeing your contributions. Any other council members would like to make any comments on this item? Seeing none, we then are going to recess this open session and we'll reconvene in closed session at 2 o'clock in the Mayor's Conference Room.


Hello everyone, welcome to theCUBE's presentation of the AWS Startup Showcase, Martek Emerging Cloud Scale, customer experience. This is season two, episode three of the ongoing series covering the exciting startups from the AWS ecosystem, talking about the data analytics, all the news and all the hot stories. I'm John Furrier, your host of theCUBE. And today we're excited to be joined by Rachel Opsler, VP of product at heap, heap.io. Here to talk about from what to why the future of digital insights, great to see you. Thanks for joining us today. Thanks for having me, John. Thanks for having me back. Well, we had a great conversation prior to the event here, a lot going on. You guys had acquired Aurek in an acquisition. You kind of teased that out last time. Talk about this, the news here and why is it important?  Yeah, so heap is a digital insights platform. So as you mentioned, it's all about analytics. And so heap really excels at helping you understand what your users and customers are doing in your digital application at scale. So when it comes to Aurek, what we really saw was a broken workflow. Maybe I would even call it a broken market where a lot of customers had an analytics tool like heap. So using heap on one hand to figure out what is happening at scale with their users. But on the other hand, they were also using like a session replay tool separately to look at individual sessions and see exactly what was happening. And no one was very effective at using these tools together. They didn't connect at all. And so as a result, neither one of them could really be fully leveraged. And so with this acquisition, we're able to put these two tools together so that users can both understand the what at scale and then really see the why immediately together in one place. You know, I love that word why because there's always that famous motivational video on the internet. You got to know your why. You know, it's very a motivational thing. But now you're getting more practicality. What and why is the lens you want, right? So I totally see that. And again, you tease that out in our last interview we did. But I want to understand what's under the covers under the acquisition. What was the big thesis behind it? Why the joint forces? What does this all mean? Why is this so important to understand this new what and why and the acquisition specifically? Yeah, so let me give you example of a couple of use cases that's really helpful for understanding this. So imagine that you are a product manager or maybe a growth marketer, but you're someone who owns a digital experience. And what you're trying to do, of course, is make that digital experience amazing for your users so that they get value. And that may mean that they're using it more. It may mean that new features are easily discoverable, that you can upsell things on your own. There's all sorts of different things that that may mean. But it's all about making it easy to use, discoverable, understandable, and as self-service as possible too. And so most of these digital builders, so we call them digital builders sometimes, they are trying to figure out when the application is not working the way that it should be working, where people are getting stuck, where they're not getting the value and figure how to fix that. And so one really great use case is I just want to understand in mass, like let's say you have a flow, where are people dropping off, right? So I see that I have a four step funnel and between the step three and four people are dropping off. Heap is great for getting very detailed on exactly what action they're taking where they're dropping off. But then the second you find what that action is, quantitatively, you want to watch it. You want to see what they did exactly before it, you want to see what they did after it, you want to understand why they're getting stuck, what they're confused at, are they mousing over two things? Like you kind of want to watch their session. And so what this acquisition allows us to do is to put those things together seamlessly. You find the point in friction, you watch a bunch of examples, very easily. In the past, this would take you at least hours if you could do it at all. And then another use case is the other direction. So there's the kind of, I think of it as the max to the min, and then there's the other direction as well, like you have the, or maybe it's the macro to micro, you have the micro to macro, which is you have one user that had a problem and maybe they send in a support ticket.  Did this happen to a lot of users? And this is really worth fixing because all these customers are having the same problem. That's the micro to macro flow that you can do as well. Yeah, and that's like the quantitative, qualitative of the what and the why. I totally see the value there and I like the way you explain that. Good call out. The question I have for you is a lot of people have these tools. I got someone who does that. I got someone over here that does the quantitative. I don't need to have one company do it, or do I? So the question I have for you, what does having a single partner or vendor providing both the quantitative and the qualitative nails mean for your customers? So it's all because now it's immediate. So today with the two tools being separate, you may find something quantitatively, but then to find the sessions that you want to watch that are relevant to that quantitative data point, it's very difficult at least it takes hours to do so. And a lot of times people just give up and they don't bother. The other way is also true. You can watch sessions. You can watch as many sessions as you want. You can spend hours doing it. You may never find anything of interest, right? So it just ends up being something that users don't do. And actually we've interviewed a lot of customers. They have a lot of guilt about this. A lot of product managers feel like they should be spending all this time, but they just don't have the time to spend. And so it not only brings them together, but it brings them together with immediacy. So you can immediately find the issue, find exactly where it is and watch it. And this is a big deal because if you think about, I guess like today's economic conditions, you don't have a lot of money to waste. You don't have a lot of time to waste. You have to be very impactful with what you're doing and with your spending of development resources. Yeah, and totally. And I think one of the things that's immediacy is key because it allows you to connect dots faster. And we have the aha moments all the time. If you miss that, the consequences can be quantified in a bad product experience and lost customers. So you totally see that. Zooming out now, I want to get your thoughts on this because we're going down this road of essentially every company is digital now, right? So digitization, digital transformation. What do you want to call it? Data is digital. This video is an experience. It's also data as well. You're talking, we're going to share this and people are going to experience that. So every website that's kind of old school is now becoming essentially a digital native application or e-commerce platform. All the things that were once preserved for the big guys, the hyperscalers in the categories, the big budgets now are coming down to every company. Every company is a digital company. What challenges do they have to transition from, I got a website, I got a marketing team. Now I've got to look like a world-class product, e-commerce, multifaceted application with developers, with change, with agility. Well, so I think that last thing you said is a really important part of it, the agility. So these products, when you're going from just a website to a product, they're a lot more complex, right? And so maybe I can give an example. We have a customer, it's an insurance company. So they have this online workflow. And if you can imagine signing up for insurance online, it's a pretty long, complicated workflow.  And so it's a good experience, but it's still fraught with opportunities of people getting stuck and never coming back. And so one of the things that HEP allowed this customer to do was figure out something that wasn't working in the workflow. And so if you think about traditional analytics tools, typically what you're doing is you're writing tracking code and you're saying, hey, I'm gonna track this funnel, this process. And so maybe it has five different forms or pages that you have to go through. And so what you're doing when you track it is you say, did you submit the first one? Did you submit the second one? Did you submit the third one? So you know where they're falling off. Where they're falling off, but you don't know why. You don't know which thing got them stuck because each one of these pages has multiple inputs and it has maybe multiple steps that you need to do. And so you're completely blind to exactly what's happening. Well, it turned out because HEP collects all this data that on one of these pages where users were dropping off, it was because they were clicking on a fact. There was a link to a fact. And because it's a big company, the fact took them to a completely different application, didn't know how to get back from there and they just lost people. And imagine if you were doing this with traditional means today, right? You don't have any visibility into what's happening on that page.  You might think about, what do I do to fix this? How do I make this flow work better?  One of your ideas could be, let's break it into multiple pages. Maybe there's too much stuff on this page. One of your ideas may have been, let's try a fact. They're getting stuck, let's give them some more help. That would be a very bad idea, right? Because that was actually the reason why they were leaving and never coming back. So the point I'm making is that if you don't know exactly where people are getting stuck and you can't see exactly what is happening, then you're gonna make a lot of very bad decisions. You're gonna waste a lot of resources trying things that make no sense. It is hard enough as a digital builder and all the product managers and growth marketers and marketers out there can attest to this. It's hard enough when you know exactly what the problem is to figure out a good solution, right? That's still hard. But if you don't know the problem, it's impossible. Okay, so let's just level up. The bumper sticker now for the challenges are what? Decision making, what's the, stack ranked the top three challenges from that? So it's being agile, right? So being very fast because you're competing with a lot of companies right now. It's about making really good decisions and driving impact, right? So you have to have all the data that you need. You have to have the specific information about what's going on.  So now you got the acquisition of Orca and Orric and you have this visibility and the customers that are building, investing, you mentioned. Okay, as they invest, whether it's the digital product or new technology and R&D, what feedback have you guys seen from these investments, from these customers? What results have come out of it? Could you share any specific answers to the problems and challenges you outlined?  You know what I'm saying? So it's like, where can you, where are these challenges addressed? And what are some of the results? Yeah, so what we've seen with our customers is that when they are applying this data and doing this analysis on, say workflows or goals that they're trying to accomplish, they've been able to move the needle quite a bit.  When they know exactly where they're failing, it is much easier to make an investment and move the needle. Awesome. Well, let's move on to the next big topic, which I love is about data science and data engineering.  And I want to ask you specifically how he uniquely is positioned to help companies succeed where in the old big tech world, they're tightening the ropes on secure cookies, privacy, data sharing. At the same time, there's been an explosion in cloud scale, data opportunities. And new technologies. So it seems like a new level of capability is going to replace the old cookies, privacy, data sharing, which seem to be constricting or going away. How do you, what's your reaction to that? Can you share how heat fits into this next generation and the current situation going on with the cookies and privacy stuff? Yep. So it is really important in this world to be collecting data compliantly, right? And so what that means is you don't want to be reliant on third party cookies. You want to be reliant on just first party information. You want to make sure that you don't collect any PII. Heap is built to do that from the ground up. We by default will not collect information like what do people put into forms, right? Because that's a obvious source of PII. The other thing is that there's just so much data. So you kind of alluded to this with this idea of data science. So first of all, you're collecting data compliantly. You're making sure that you have all the data of what your user actions are doing compliantly. But then it's so much data that it, like how do you know where to start, right? You want to know, you want to get to that specific point that users are dropping off, but there's so many different options out there. And so that's where heap is applying data science to automatically find those points of friction and automatically surface them to users so that you don't have to guess and check and constantly guess at what the problem is, but you can see it in the product surface right for you. You know, Rachel, that's a great point. I want to call that out because I think a lot of companies don't underestimate what you said earlier. Capturing in compliance way means you're opting in to say not to get the data to unwind it later, figure it out. You're capturing it in a compliant way which actually reduces the risk and operational technical debt you might have to deploy to get it fixed on compliance. Okay, that's one thing. I love that. I want to make sure people understand that value. That's a huge value, especially for people that don't have huge teams and diverse platforms or other data sources. The other thing you mentioned is owning their own data and that first party data is a strategic advantage mainly around personalization and targeted customer interaction. So the question is with the new data, I own the data, you got to capture it with compliance. How do you do personalization and targeted customer interactions at the same time while being compliant? It just seems like compliance is restrictive and kind of forecloses value, but open means you get a personalization and targeted interactions. How do you guys connect the dots there by being compliant but yet being valuable on the personalization and targeted? Well, it all depends on how the customer is managing their information, but imagine that you have a logged in user. Well, you know who the logged in user is, right? And so all we really need is an ID. We don't need to know any of the user information. We just need an ID. And then we can serve up the information about like what have they done? If they've done these three actions, maybe that means that this particular offer would be entrusted to them. And so that information is available within Heap for our customers to use it as they want to with their users. So you're saying you can enable companies to own their data, be compliant, and then manage it end to end from a privacy standpoint? Yes. That's got to be a top seller right there. Well, it's not just a top seller, it's a necessity. It's a must have. I mean, think about it.  What do they face? What's the alternative? You don't get the heap going immediately. What's the alternative? I'm going through logs. I got to have to get a request to forget my data. All these things are all going on, right? What's the consequence of not doing this? Well, there's a couple of consequences. So one is, and I kind of alluded to it earlier, that you're blind to what your users are doing, which means that you're making investments that may not make sense, right? So you can decide to add all the cool features in the world, but if the customers don't perceive them as being valuable or don't find them or don't understand them, it doesn't serve your business. And so this is one of the rule number one of being a product manager is you're trying to balance what your customers need with what is also good for your business, and both of those have to be in place. So that's basically where you are, is that you'll be making investments that just won't be hitting the mark and you won't be moving the needle, and as I mentioned, it's more important now in this economic climate than ever to make sure that the investments you're making are targeted and impactful. Yeah, and I think the other thing to point out is it's a big backlash against the whole Facebook, you're the product, you're getting used, the user's being used for product, but you guys have a way to make that happen in a way that's safe for the user. Yes, safe and compliant. So we're all about making sure that we certainly don't get our customers into trouble and we recommend that they follow all compliance rules because the last thing you want to be is on the wrong side of a compliance officer. Well, there's also the user satisfaction problem and the fines. So a lot going on there, great product. I got to ask you real quick before we kind of wrap up here, what's the reaction been to the acquisition of quantitative, qualitative? What's been the vibe? What are some, what are people saying about it? We've got a lot of interest. So I mentioned earlier that this is really a broken workflow in the market. And when users see the two products working together, they just love it because they have not been able to leverage them being separate before. And so it just makes it so much easier for these digital builders to figure out what do I invest in because they know exactly where people are having trouble. So it's been really great. We've had a lot of reach-outs already asking us how they can use it, try it, not quite available yet. So it's going to be available later this summer. But great response so far. Awesome. Well, I love the opportunity. I love the conversation. I have to ask you now, looking forward, what does the future look like for companies taking advantage of your platform and tool? What can they expect in terms of R&D, investments, area of moves you're making? You're the head of product, you get the keys to the kingdom. What's the future look like? What's coming next? Yeah, so other than pulling the call and the quant together, you actually hinted at it earlier when you're asking me about data science, but continuing to automate as much of the analysis as we can. So first of all, analysis, analytics, it should be easy for everyone. So we're continuing to invest in making it easy, but part of making it easy is, like we can automate analysis. We can see that your website has a login page on it and build a funnel for you automatically. So that's some of the stuff that we're working on is how do we both automate getting up to speed and getting that initial analysis done easily without any work? And then also, how do we automate more complex analyses? So you have typically, a lot of companies have a data science team and they end up doing a lot of analysis. It's a little bit more complex. I'm not saying data science teams will go away. They will be around forever. There's tons of very complex analysis that they're probably not even getting time to do. We're gonna start chipping away at that so we can help product managers do more and more of that self-service and then free up the data science team to do even more interesting things. I really like how you use the word product managers, product builders, digital builders, because while I got you, I want to get your thought on this because it's a real industry shift. You're talking about it directly here about websites going to e-commerce, CMOs, a C-suite, they generally observe that websites are old technology, but not going away because the next level abstraction builds on top of it. What's the new capabilities? Because for the CMOs and the C-suites and the product folks out there, they're not building web pages, they're building applications. What is it about this new world that's different from the old web architecture? How would you talk to a CMO or a leader and when they ask what's this new opportunity to take my website? Because maybe it's not enough traffic, people are consuming out in the organic. What's this new expectation and what does a new product manager environment look like if it's not the web, so to speak? Well, there's a couple of things. So one is, and you alluded to it a bit, like the websites are also getting more complex and you need to start thinking of your website as a product. Now, it may not be the product that you sell, but it is, well, for e-commerce, it's a place that you get access to the product. For B2B SaaS, it is the window to the product, it's a place where you can learn about the product and you need to think about not just like what pieces of content are being used, but you need to understand the user flow through the application. So that's how it's a lot more like a product. Rachel, thanks so much for coming on theCUBE here for this presentation. Final word, put a plug in for the company. What are you guys up to? What are you looking for? Take a minute to explain kind of that. What's going on? How do people contact you with a great value proposition? Put a plug in for the company. Yeah, well, if you want to up-level your product experience or website experience, you want to be able to drive impact quickly, try Heap. You can go to heap.io, you can try it for free. We have a free trial, we have a free product even. And yeah, and then if you have any questions you want to talk to a live person, you can do that too at sales at heap.io. Rachel, thanks so much. Customer scale, experiences with the cloud. Obviously, this is the season two, episode three of the ongoing series. I'm John Furrier, your host. Thanks for watching.


From around the globe, it's theCUBE with coverage of KubeCon and CloudNativeCon Europe 2021 virtual. Brought to you by Red Hat, the CloudNative Computing Foundation and ecosystem partners. All right, welcome back to theCUBE's coverage of KubeCon and CloudNativeCon 2021 virtual. I'm John Furrier, host of theCUBE. He was a great guest. I'm excited to talk to his company that he was part of, founding CTO, was bought by Red Hat, Ali Ghoshan, senior director of global software engineering at Red Hat, formerly the CTO of StackRocks. Ali, thanks for coming on, appreciate it. Thanks for joining us. Yeah, thanks for having me. Excited to be here. So big acquisition in January. We covered it on SiliconANGLE. You guys, security company, venture backed, Amplify, Sequoia and on and on. Big part of Red Hat's story in their security as developers want to shift left, as they say, and as more and more modern applications are being developed. So congratulations. Real quick, just quick highlight of what you guys do as a company and inside Red Hat. Sure. So the company's premise was built around how do you bring security to the entire application lifecycle? So StackRocks focuses on sort of three big areas that we talk about. One is how do you secure the supply chain? The second part of it is how do you secure infrastructure and posture management? And then the third part is now how do you protect the workload that run on top of that infrastructure? So this is the part that aligned really well with Red Hat, which is, Red Hat wanted to take a lot of what we do around infrastructure, posture management, configuration management and developer tools integrated into a lot of the things they do. And obviously the workload protection part was a very seamless part of integrating us into the open shift part because we were built around code native constructs.  Yeah. You guys got a great story. Obviously, cloud native applications are rocking and rolling. You guys were in early serverless merges, Kubernetes and then security in what I call the real time developer workflow. Ones that are building really fast pushing code. Now it's called day two operations. So cloud native day two operations kind of encapsulates this new environment. You guys were right in the sweet spot of that. So this became quite the big deal. Red Hat saw an opportunity to bring you in. What was the motivation when you guys did the deal? Was it like, wow, this is a good fit? How did you react? What was the vibe at Stack Rocks when this was all going down? Yeah. So I think there's really three areas you look for anytime a company comes up and sort of starts knocking on your door. One is really, is the team going to be the right fit? You know, is the culture going to be the right environment for the people for us? That was the big part of what we were taking into consideration. We found Red Hat's general culture, how they approach people and sort of the overall approach to the community was very much aligned with what we were trying to do. The second part of it was really the product fit. So we had from, you know, very early on started to focus purely on the Kubernetes components and doing everything we could. We called sort of our product approach built in versus bolted on. And this is sort of a philosophy that Red Hat had adopted for a long time. And it's a part of a lot of their developer tools, part of their shift left story as well as part of OpenShift. And then the third part of it was really the larger strategy of how do you go to market? So we were hitting that point where we were in triple digit customers and we were thinking about scalability and how do we scale the company? And that was the part that also fit really well, which was obviously Red Hat more and more hearing from their customers about the importance and the criticality of security. So that last part happened to be one part we ended up spending a lot of time on and ended up being sort of three out of three matches that made this acquisition happen. Well, congratulations, always great to see startups in the right position, good hustle, great product, great market, you guys did a great job. Congratulations.  This is huge news, obviously you now work for an Open Source company, I'm sure that was probably a part of it. Take us through the news. This is the top story here for this segment. Take us through Open Source, take us through the news. Yeah, so traditionally, Stackerox was a proprietary tool. We do have open source tooling, but the entire platform in itself was a proprietary tool. This has been a number of discussions that we've had with the Red Hat team from the very beginning. And it sort of aligns around a couple of core philosophies. One is obviously Red Hat at its core being an open source company and being very much plugged into the community and working with users and developers and engineers to be able to sort of get feedback and build better products. But I think the other part of it is that, I think a lot of us from a historic standpoint have viewed security to be a proprietary thing because we've always viewed these sort of magic algorithms or black boxes or some magic under the hood that really moved the needle. And that happens not to be the case anymore. Also because Stackerox's philosophy was really built around Kubernetes and built in, we feel like one of the really great messages around why to open source a security product is to build that trust with the community. Being able to expose here's how the product works, here's how it integrates, here are the actions it takes, here's the ramifications or repercussions of some of the decisions you may make in the product. Those all I feel make for very good stories of how you build connection, trust and communication with the community and actually get feedback on it. And obviously at its core, the company being very much focused on Kubernetes developer tools, service mesh, these are all open source toolings obviously. So for us it was very important to sort of talk to talk and walk to walk. And this is sort of an easy decision at the end of the day for us to take the platform open source. And we're excited about it because I think most people still want a product I supported commercial product. So while it's great to have some of the tip of the spear customers look at it and adopt the open source and be able to drive it themselves, we're still hearing from a lot of the customers that what they do want is really that support and that continuous management maintenance and improvement around the product. So we're actually pretty excited. We think it's only going to increase our velocity and momentum into that community. Well, I have some questions on how it's going to work, but I do want to get your comment because I think this is a pretty big deal. You know, I had a conversation about 10 years ago with Doug Cutting who was the founder of Hadoop. And he was telling me a story about a company he worked for, he did all this coding, they went under and the IP was gone, the software was gone. And it was a story to highlight that proprietary software sometimes could never see the light of day and it doesn't continue. Here, you guys are going to continue the story, continue the code. How does that feel? What's your expectations? How's that going to work? I'm assuming that's what you're going to open it up, which means that anyone can download the code. Is that right? Take us through, how to first of all, do you agree with that? This is going to stay alive and how's it going to work? Yeah, I mean, I think as a founder, one of the most fulfilling things to have is something you build that becomes sustainable and stands the test of time. And I think especially in today's world, open sourcing a tool that is in demand and only in a market that's growing is really a great way to do that, especially if you have a sort of an established user base and a customer base. And then to sort of back that on top of, thousands of customers and users that come with Red Hat in itself, gives us a lot of confidence that that's going to continue and only grow further. So the decision wasn't a difficult one. You know, although transparently, I feel like even if we had pushed back, I think Red Hat was pretty determined about open sourcing again anyway. But it's to say that we actually were in agreement to be able to go down that path. I do think that there's a lot of details to be worked out because obviously there's sort of a lot of the nuances in how you build product and manage it and maintain it. And then how do you introduce community feedback and community collaboration as part of open source projects is another big part of it. I think the part we're really excited about is that it's very important to have really good community engagement, maintenance and response. And for us, even though we actually discussed this particular strategy during Stackbox, one of the hindering aspects of it was really the resources required to be able to manage and maintain such a massive open source project. So having Red Hat behind us and having a lot of this experience was very relevant. I think as a startup to start proprietary and suddenly open it and try to change your entire business model, go to market strategy, commercialization, change the entire culture of the company can sometimes create a lot of headwind. And as a startup, like sort of, I feel like every year just trying not to die until you create that escape velocity. So those were, I think, some of the risk items that Red Hat was able to remove for us and as a result made the decision that much easier. Yeah, and you got the mothership with Red Hat, they've done this before, they've been doing it for generations. You guys, you know, the startup, things are going crazy. It's like whitewater rafting. So everything's happening so fast. And now you got the community behind you because you're going to have the CNC. If you get KubeCon, I mean, it's a pretty great community. The support is amazing. I think the only thing the engineers might want to worry about is go back into the code base and clean things up a bit. That's why I'm trying to see the code. They're like, wait a minute, their names are on it. So it's always a fun time. In all seriousness, no, this is a big, big story on the DevSecOps.  We've been covering that for all of the life of the queue for the 11 years now and the greatness of DevOps. But now DevSecOps is critical and Kubernetes native security is what people are looking at. When you look at that trend only continuing, what's your focus? What do you see now that you're in Red Hat as the CTO, former CTO of StackRocks and now part of Red Hat, it's going to get bigger and stronger Kubernetes native and shifting left and or DevSecOps. What's your focus? Yeah. So I would say our focus is really around two big buckets. One is Kubernetes native sort of a different way to think about it as we think about our roadmap planning and go-to-market strategy is it's mutually exclusive with being infrastructure native. That's how we think about it. As a startup, we really have to focus on an area and Kubernetes was a great place for us to focus on because it was becoming the dominant orchestration engine. Now that we have the resources and the power of Red Hat behind us, the way we're thinking about this is infrastructure native. So thinking about cloud native infrastructure where you're using composable, reusable constructs and objects, how do you build potential offerings or features or security components that don't rely on third-party tools or components anymore? How do you leverage the existing infrastructure itself to be able to conduct some of these traditional use cases? And one example we use for this particular scenario is networking. Networking the way firewalling and segmentation was typically done was people would tweak IP tables or they would install, for example, a proxy or a container that would terminate NTLS or become inline and it would create all sorts of sort of operational and risk overhead for users and for customers. And one of the things we're really proud of as sort of the company that pioneered this notion of cloud native security is if you just leverage network policies in Kubernetes you don't have to be in line. You don't have to have additional privileges. You don't have to create additional risk or operational overhead for users. So we're taking those sort of core philosophies and extending them the same way we did to Kubernetes all the way through service mesh. So we're doing the same sorts of things through Istio being able to do a lot of the things people that are traditionally doing through, for example, proxies through layer six and seven, we want to do through Istio. And then the same way, for example, we introduced a product called KubeLinter which was an open source tool which would basically look at YAML on Helm charts and give you best practices responses. And it's something you point, for example, to your Git repository. We want to take those sort of principles enabling developers giving them feedback allowing them not to break their existing workflows and leveraging components in existing infrastructure to be able to sort of push security into cloud native and really the two pillars we look at are ensuring we can get users and customers up and running as quickly as possible and reduce as much as possible operational overhead for them over time. So we feel these two are really at the core of open sourcing and building into the infrastructure which has sort of given us momentum over the last six years and we feel pretty confident with Red Hat's help we can even expand that further. Yeah, I mean, you bring up a good point and certainly as you get more scale with Red Hat and on the customer base, you know, not only in dealing with the threat detection around containers and cloud native applications, you got to kind of build into the life cycle and you got to figure out, okay, it's not just Kubernetes anymore, it's something else. And you got advanced cluster security with Red Hat, they got OpenShift cloud platform, you're going to have managed services. So this means that you're going to have scale, right? So how do you view that? Because now you're going to have, you guys at the center of the advanced cluster security paradigm for Red Hat, that's a big deal for them. And they got a lot of R&D and a lot of, I wouldn't say R&D, emerging technologies developing around that. We covered that in depth. So when you start to get into advanced cluster, it's just, it's compliance too. It's not just threat detection, you got insights, telemetry, data acquisition. So you have to kind of be part of that now. How do you guys feel about that? Are you up for the task? What's your story? Yeah, I hope so. It's early days, but we feel pretty confident about it. We have a very good team. So as part of the advanced cluster security, we work also very closely with the advanced cluster management team in Red Hat because it's not just about security, it's about how do you operationalize it, how do you manage it, maintain it into your point, sort of run it long-term at scale. The compliance part of it is a very important part. I still feel like that's in its infancy and these are a lot of conversations we're having internally at Red Hat, which is, we all feel that compliance is going to sort of more from, the standard benchmarks you have from CIS or particular compliance requirements, like the power of PCI or NIST, into how do you create more flexible and composable policies through a unified language that allows you to be able to create more custom or more useful things specific to your business. So this is actually an area where we're doing a lot of collaboration with the advanced cluster management team, which is that how do you sort of bring to light a really easy way for customers to be able to describe and sort of abstract policies and then at the same time be able to actually implement and enforce them. So we think that's really the next key point of what we have to accomplish to be able to sort of not only gain scale, but to be able to take this notion of not only detection and response, but be able to actually build in what we call declarative security into your infrastructure. And what that means is to be able to really dictate how you want your applications, your services, your infrastructure to be configured and run and then anything that is sort of conflicting with that is auto responded to. And I think that's really the larger vision that with Red Hat would find it accomplished. And that's a nice posture to have. You build it in, get it built in, you have the declarative models, then you kind of go from there and then let the automation kick in. You got insights coming in from Red Hat. So all these things are kind of evolving. It's still early days and I think it's a nice move by Red Hat. So congratulations. Final question for you is as you prepare to go the next generation, KubeCon is also seeing a lot more end user participation. People, you know, cloud native is going mainstream. When I say mainstream, I'm seeing beyond the hyperscales and the early adopters, Kubernetes and other infrastructure control planes are coming in. You start to see the platforms emerge. Nobody wants another security tool, right? They want platforms that enable applications and or tools. As it gets more complicated, what's going to be the easy button and security cloud native? What's the approach? What's your vision on what's next? Yeah, so, you know, I don't know if there is an easy button in security. And I think part of it is that there's just such a fragmentation in use cases and sort of designs and infrastructure that that doesn't exist, especially if you're dealing with such a complex stack. And not only just a complex stack, but potentially use cases that not only span runtime, but they deal with your deployment and your development lifecycle. So the way we think about it is more sort of this notion that has been around for a long time, which is the shared responsibility model. Security is not security's job anymore, especially because security teams probably cannot really keep up with the learning curve. Like they have to understand containers. Then they have to understand Kubernetes and Istio and Envoy and cloud platforms and APIs.  So the way we think about it is if you deal with security in a declarative fashion, and if you can state things in a way where how infrastructure is ran is properly configured. So it's more about safety than security. Then what you can do is push a lot of these best practices back as part of your Git process. Involve developers, engineers, the right product security team that are responsible for day-to-day managing and maintaining these. And the example we think about is like CVEs. There are plenty of, for example, vulnerability tools, but the CVEs are still an unsolved problem because, you know, where are they? What is the impact? Are they actually running? Are they being exploited in the wild? All these things have different ramifications as you span it across the lifecycle. So for us, it's about understanding context, understanding assets, ensuring how the infrastructure has to handle that asset and then ensuring that the route for that response is sent to the right team so they can address it properly. And I think that's really our larger vision is how can you automate this entire lifecycle? So the information is routed to the right teams, the right teams are appending it to the application. And in the future, our goal is not to just pardon the workload or the compute environment, but use this information to actually pardon application themselves so that creates that additional agility and scalability. Yeah, it's in the lifecycle of that build-in, right? In the beginning, more productivity, more security, and then letting everything take over on the automation side. All the congratulations on the acquisition to end with the Red Hat buyout. That was great for them and for you guys. Take a minute, quickly, this final, final question for the folks watching here. The big news is your open sourcing Stack Rocks. So that's a big news here at KubeCon. Obviously, what can people do to get involved? Would you share a quick commercial for what people can do to get involved? What are you guys looking for? Take a pledge to the community. Yeah, I mean, what we're looking for is more involvement and direct feedback from our community, from our users, from our customers. So there's a number, obviously, the Stack Rocks platform itself being open sourced. We have other open-source tools like the KubeLinter. What we're looking for is feedback from users as to what are the pain points that they're trying to solve for? And then give us feedback as to how we're not addressing those or how can we better design our systems? I mean, this is the sort of feedback we're looking for and naturally, with more resources, we can be a lot faster in response. So send us feedback, good or bad. We would love to hear from our users and our customers and get a better sense of what they're looking for. Innovation out in the open, love it. Got to love open source going next gen. I like all Sean senior director of global software engineering a new title at Red Hat, former CTO founder of Stack Rocks which spread out acquired in January, 2021. Thanks for coming on, congratulations. Thanks for having me. Okay, so it keeps coverage of KubeCon, CloudNativeCon 2021. I'm John Furrier, your host. Thanks for watching.