(upbeat music) >> Welcome back to theCUBE's coverage of Women in Data Science 2023 live from Stanford University. This is Lisa Martin. My co-host is Tracy Yuan. We're excited to be having great conversations all day but you know, 'cause you've been watching. We've been interviewing some very inspiring women and some men as well, talking about all of the amazing applications of data science. You're not going to want to miss this next conversation. Our guest is Gabriela de Queiroz, Principal Cloud Advocate Manager of Microsoft. Welcome, Gabriela. We're excited to have you. >> Thank you very much. I'm so excited to be talking to you. >> Yeah, you're on theCUBE. >> Yeah, finally. (Lisa laughing) Like a dream come true. (laughs) >> I know and we love that. We're so thrilled to have you. So you have a ton of experience in the data space. I was doing some research on you. You've worked in software, financial advertisement, health. Talk to us a little bit about you. What's your background in? >> So I was trained in statistics. So I'm a statistician and then I worked in epidemiology. I worked with air pollution and public health. So I was a researcher before moving into the industry. So as I was talking today, the weekly paths, it's exactly who I am. I went back and forth and back and forth and stopped and tried something else until I figured out that I want to do data science and that I want to do different things because with data science we can... The beauty of data science is that you can move across domains. So I worked in healthcare, financial, and then different technology companies. >> Well the nice thing, one of the exciting things that data science, that I geek out about and Tracy knows 'cause we've been talking about this all day, it's just all the different, to your point, diverse, pun intended, applications of data science. You know, this morning we were talking about, we had the VP of data science from Meta as a keynote. She came to theCUBE talking and really kind of explaining from a content perspective, from a monetization perspective, and of course so many people in the world are users of Facebook. It makes it tangible. But we also heard today conversations about the applications of data science in police violence, in climate change. We're in California, we're expecting a massive rainstorm and we don't know what to do when it rains or snows. But climate change is real. Everyone's talking about it, and there's data science at its foundation. That's one of the things that I love. But you also have a lot of experience building diverse teams. Talk a little bit about that. You've created some very sophisticated data science solutions. Talk about your recommendation to others to build diverse teams. What's in it for them? And maybe share some data science project or two that you really found inspirational. >> Yeah, absolutely. So I do love building teams. Every time I'm given the task of building teams, I feel the luckiest person in the world because you have the option to pick like different backgrounds and all the diverse set of like people that you can find. I don't think it's easy, like people say, yeah, it's very hard. You have to be intentional. You have to go from the very first part when you are writing the job description through the interview process. So you have to be very intentional in every step. And you have to think through when you are doing that. And I love, like my last team, we had like 10 people and we were so diverse. Like just talking about languages. We had like 15 languages inside a team. So how beautiful it is. Like all different backgrounds, like myself as a statistician, but we had people from engineering background, biology, languages, and so on. So it's, yeah, like every time thinking about building a team, if you wanted your team to be diverse, you need to be intentional. >> I'm so glad you brought up that intention point because that is the fundamental requirement really is to build it with intention. >> Exactly, and I love to hear like how there's different languages. So like I'm assuming, or like different backgrounds, I'm assuming everybody just zig zags their way into the team and now you're all women in data science and I think that's so precious. >> Exactly. And not only woman, right. >> Tracy: Not only woman, you're right. >> The team was diverse not only in terms of like gender, but like background, ethnicity, and spoken languages, and language that they use to program and backgrounds. Like as I mentioned, not everybody did the statistics in school or computer science. And it was like one of my best teams was when we had this combination also like things that I'm good at the other person is not as good and we have this knowledge sharing all the time. Every day I would feel like I'm learning something. In a small talk or if I was reviewing something, there was always something new because of like the richness of the diverse set of people that were in your team. >> Well what you've done is so impressive, because not only have you been intentional with it, but you sound like the hallmark of a great leader of someone who hires and builds teams to fill gaps. They don't have to know less than I do for me to be the leader. They have to have different skills, different areas of expertise. That is really, honestly Gabriela, that's the hallmark of a great leader. And that's not easy to come by. So tell me, who were some of your mentors and sponsors along the way that maybe influenced you in that direction? Or is that just who you are? >> That's a great question. And I joke that I want to be the role model that I never had, right. So growing up, I didn't have anyone that I could see other than my mom probably or my sister. But there was no one that I could see, I want to become that person one day. And once I was tracing my path, I started to see people looking at me and like, you inspire me so much, and I'm like, oh wow, this is amazing and I want to do do this over and over and over again. So I want to be that person to inspire others. And no matter, like I'll be like a VP, CEO, whoever, you know, I want to be, I want to keep inspiring people because that's so valuable. >> Lisa: Oh, that's huge. >> And I feel like when we grow professionally and then go to the next level, we sometimes we lose that, you know, thing that's essential. And I think also like, it's part of who I am as I was building and all my experiences as I was going through, I became what I mentioned is unique person that I think we all are unique somehow. >> You're a rockstar. Isn't she a rockstar? >> You dropping quotes out. >> I'm loving this. I'm like, I've inspired Gabriela. (Gabriela laughing) >> Oh my God. But yeah, 'cause we were asking our other guests about the same question, like, who are your role models? And then we're talking about how like it's very important for women to see that there is a representation, that there is someone they look up to and they want to be. And so that like, it motivates them to stay in this field and to start in this field to begin with. So yeah, I think like you are definitely filling a void and for all these women who dream to be in data science. And I think that's just amazing. >> And you're a founder too. In 2012, you founded R Ladies. Talk a little bit about that. This is present in more than 200 cities in 55 plus countries. Talk about R Ladies and maybe the catalyst to launch it. >> Yes, so you always start, so I'm from Brazil, I always talk about this because it's such, again, I grew up over there. So I was there my whole life and then I moved to here, Silicon Valley. And when I moved to San Francisco, like the doors opened. So many things happening in the city. That was back in 2012. Data science was exploding. And I found out something about Meetup.com, it's a website that you can join and go in all these events. And I was going to this event and I joke that it was kind of like going to the Disneyland, where you don't know if I should go that direction or the other direction. >> Yeah, yeah. >> And I was like, should I go and learn about data visualization? Should I go and learn about SQL or should I go and learn about Hadoop, right? So I would go every day to those meetups. And I was a student back then, so you know, the budget was very restricted as a student. So we don't have much to spend. And then they would serve dinner and you would learn for free. And then I got to a point where I was like, hey, they are doing all of this as a volunteer. Like they are running this meetup and events for free. And I felt like it's a cycle. I need to do something, right. I'm taking all this in. I'm having this huge opportunity to be here. I want to give back. So that's what how everything started. I was like, no, I have to think about something. I need to think about something that I can give back. And I was using R back then and I'm like how about I do something with R. I love R, I'm so passionate about R, what about if I create a community around R but not a regular community, because by going to this events, I felt that as a Latina and as a woman, I was always in the corner and I was not being able to participate and to, you know, be myself and to network and ask questions. I would be in the corner. So I said to myself, what about if I do something where everybody feel included, where everybody can participate, can share, can ask questions without judgment? So that's how R ladies all came together. >> That's awesome. >> Talk about intentions, like you have to, you had that go in mind, but yeah, I wanted to dive a little bit into R. So could you please talk more about where did the passion for R come from, and like how did the special connection between you and R the language, like born, how did that come from? >> It was not a love at first sight. >> No. >> Not at all. Not at all. Because that was back in Brazil. So all the documentation were in English, all the tutorials, only two. We had like very few tutorials. It was not like nowadays that we have so many tutorials and courses. There were like two tutorials, other documentation in English. So it's was hard for me like as someone that didn't know much English to go through the language and then to learn to program was not easy task. But then as I was going through the language and learning and reading books and finding the people behind the language, I don't know how I felt in love. And then when I came to to San Francisco, I saw some of like the main contributors who are speaking in person and I'm like, wow, they are like humans. I don't know, it was like, I have no idea why I had this love. But I think the the people and then the community was the thing that kept me with the R language. >> Yeah, the community factors is so important. And it's so, at WIDS it's so palpable. I mean I literally walk in the door, every WIDS I've done, I think I've been doing them for theCUBE since 2017. theCUBE has been here since the beginning in 2015 with our co-founders. But you walk in, you get this sense of belonging. And this sense of I can do anything, why not? Why not me? Look at her up there, and now look at you speaking in the technical talk today on theCUBE. So inspiring. One of the things that I always think is you can't be what you can't see. We need to be able to see more people that look like you and sound like you and like me and like you as well. And WIDS gives us that opportunity, which is fantastic, but it's also helping to move the needle, really. And I was looking at some of the Anitab.org stats just yesterday about 2022. And they're showing, you know, the percentage of females in technical roles has been hovering around 25% for a while. It's a little higher now. I think it's 27.6 according to any to Anitab. We're seeing more women hired in roles. But what are the challenges, and I would love to get your advice on this, for those that might be in this situation is attrition, women who are leaving roles. What would your advice be to a woman who might be trying to navigate family and work and career ladder to stay in that role and keep pushing forward? >> I'll go back to the community. If you don't have a community around you, it's so hard to navigate. >> That's a great point. >> You are lonely. There is no one that you can bounce ideas off, that you can share what you are feeling or like that you can learn as well. So sometimes you feel like you are the only person that is going through that problem or like, you maybe have a family or you are planning to have a family and you have to make a decision. But you've never seen anyone going through this. So when you have a community, you see people like you, right. So that's where we were saying about having different people and people like you so they can share as well. And you feel like, oh yeah, so they went through this, they succeed. I can also go through this and succeed. So I think the attrition problem is still big problem. And I'm sure will be worse now with everything that is happening in Tech with layoffs. >> Yes and the great resignation. >> Yeah. >> We are going back, you know, a few steps, like a lot of like advancements that we did. I feel like we are going back unfortunately, but I always tell this, make sure that you have a community. Make sure that you have a mentor. Make sure that you have someone or some people, not only one mentor, different mentors, that can support you through this trajectory. Because it's not easy. But there are a lot of us out there. >> There really are. And that's a great point. I love everything about the community. It's all about that network effect and feeling like you belong- >> That's all WIDS is about. >> Yeah. >> Yes. Absolutely. >> Like coming over here, it's like seeing the old friends again. It's like I'm so glad that I'm coming because I'm all my old friends that I only see like maybe once a year. >> Tracy: Reunion. >> Yeah, exactly. And I feel like that our tank get, you know- >> Lisa: Replenished. >> Exactly. For the rest of the year. >> Yes. >> Oh, that's precious. >> I love that. >> I agree with that. I think one of the things that when I say, you know, you can't see, I think, well, how many females in technology would I be able to recognize? And of course you can be female technology working in the healthcare sector or working in finance or manufacturing, but, you know, we need to be able to have more that we can see and identify. And one of the things that I recently found out, I was telling Tracy this earlier that I geeked out about was finding out that the CTO of Open AI, ChatGPT, is a female. I'm like, (gasps) why aren't we talking about this more? She was profiled on Fast Company. I've seen a few pieces on her, Mira Murati. But we're hearing so much about ChatJTP being... ChatGPT, I always get that wrong, about being like, likening it to the launch of the iPhone, which revolutionized mobile and connectivity. And here we have a female in the technical role. Let's put her on a pedestal because that is hugely inspiring. >> Exactly, like let's bring everybody to the front. >> Yes. >> Right. >> And let's have them talk to us because like, you didn't know. I didn't know probably about this, right. You didn't know. Like, we don't know about this. It's kind of like we are hidden. We need to give them the spotlight. Every woman to give the spotlight, so they can keep aspiring the new generation. >> Or Susan Wojcicki who ran, how long does she run YouTube? All the YouTube influencers that probably have no idea who are influential for whatever they're doing on YouTube in different social platforms that don't realize, do you realize there was a female behind the helm that for a long time that turned it into what it is today? That's outstanding. Why aren't we talking about this more? >> How about Megan Smith, was the first CTO on the Obama administration. >> That's right. I knew it had to do with Obama. Couldn't remember. Yes. Let's let's find more pedestals. But organizations like WIDS, your involvement as a speaker, showing more people you can be this because you can see it, >> Yeah, exactly. is the right direction that will help hopefully bring us back to some of the pre-pandemic levels, and keep moving forward because there's so much potential with data science that can impact everyone's lives. I always think, you know, we have this expectation that we have our mobile phone and we can get whatever we want wherever we are in the world and whatever time of day it is. And that's all data driven. The regular average person that's not in tech thinks about data as a, well I'm paying for it. What's all these data charges? But it's powering the world. It's powering those experiences that we all want as consumers or in our business lives or we expect to be able to do a transaction, whether it's something in a CRM system or an Uber transaction like that, and have the app respond, maybe even know me a little bit better than I know myself. And that's all data. So I think we're just at the precipice of the massive impact that data science will make in our lives. And luckily we have leaders like you who can help navigate us along this path. >> Thank you. >> What advice for, last question for you is advice for those in the audience who might be nervous or maybe lack a little bit of confidence to go I really like data science, or I really like engineering, but I don't see a lot of me out there. What would you say to them? >> Especially for people who are from like a non-linear track where like going onto that track. >> Yeah, I would say keep going. Keep going. I don't think it's easy. It's not easy. But keep going because the more you go the more, again, you advance and there are opportunities out there. Sometimes it takes a little bit, but just keep going. Keep going and following your dreams, that you get there, right. So again, data science, such a broad field that doesn't require you to come from a specific background. And I think the beauty of data science exactly is this is like the combination, the most successful data science teams are the teams that have all these different backgrounds. So if you think that we as data scientists, we started programming when we were nine, that's not true, right. You can be 30, 40, shifting careers, starting to program right now. It doesn't matter. Like you get there no matter how old you are. And no matter what's your background. >> There's no limit. >> There was no limits. >> I love that, Gabriela, >> Thank so much. for inspiring. I know you inspired me. I'm pretty sure you probably inspired Tracy with your story. And sometimes like what you just said, you have to be your own mentor and that's okay. Because eventually you're going to turn into a mentor for many, many others and sounds like you're already paving that path and we so appreciate it. You are now officially a CUBE alumni. >> Yes. Thank you. >> Yay. We've loved having you. Thank you so much for your time. >> Thank you. Thank you. >> For our guest and for Tracy's Yuan, this is Lisa Martin. We are live at WIDS 23, the eighth annual Women in Data Science Conference at Stanford. Stick around. Our next guest joins us in just a few minutes. (upbeat music)

>> Narrator: theCUBE's live coverage is made possible by funding from Dell Technologies. Creating technologies that drive human progress. (upbeat music) >> Hey, welcome back to the Fira in Barcelona. My name is Dave Vellante. I'm here with David Nicholson, day four of MWC '23. Show's winding down a little bit, but it's still pretty packed here. Lot of innovation, planes, trains, automobiles, and we're talking 5G all week, private networks, connected breweries. It's super exciting. Really happy to have Warren Jackson here as the Edge Gateway Product Technologist at Dell Technologies, and Scott Waller, the CTO of the 5G Open Innovation Lab. Folks, welcome to theCUBE. >> Good to be here. >> Really interesting stories that we're going to talk about. Let's start, Scott, with you, what is the Open Innovation Lab? >> So it was hatched three years ago. Ideated about a bunch of guys from Microsoft who ran startup ventures program, started the developers program over at Microsoft, if you're familiar with MSDN. And they came three years ago and said, how does CSPs working with someone like T-Mobile who's in our backyard, I'm from Seattle. How do they monetize the edge? You need a developer ecosystem of applications and use cases. That's always been the thing. The carriers are building the networks, but where's the ecosystem of startups? So we built a startup ecosystem that is sponsored by partners, Dell being one sponsor, Intel, Microsoft, VMware, Aspirant, you name it. The enterprise folks who are also in the connectivity business. And with that, we're not like a Y Combinator or a Techstars where it's investment first and it's all about funding. It's all about getting introductions from a startup who might have a VR or AI type of application or observability for 5G slicing, and bring that in front of the Microsoft's of the world, or the Intel's and the Dell's of the world that they might not have the capabilities to do it because they're still a small little startup with an MVP. So we really incubate. We're the connectors and build a network. We've had 101 startups over the last three years. They've raised over a billion dollars. And it's really valuable to our partners like T-Mobile and Dell, et cetera, where we're bringing in folks like Expedo and GenXComm and Firecell. Start up private companies that are around here they were cohorts from our program in the past. >> That's awesome because I've often, I mean, I've seen Dell get into this business and I'm like, wow, they've done a really good job of finding these guys. I wonder what the pipeline is. >> We're trying to create the pipeline for the entire industry, whether it's 5G on the edge for the CSPs, or it's for private enterprise networks. >> Warren, what's this cool little thing you got here? >> Yeah, so this is very unique in the Dell portfolio. So when people think of Dell, they think of servers laptops, et cetera. But what this does is it's designed to be deployed at the edge in harsh environments and it allows customers to do analytics, data collection at the edge. And what's unique about it is it's got an extended temperature range. There's no fan in this and there's lots of ports on it for data ingestion. So this is a smaller box Edge Gateway 3200. This is the product that we're using in the brewery. And then we have a bigger brother of this, the Edge Gateway 5200. So the value of it, you can scale depending on what your edge compute requirements are at the edge. >> So tell us about the brewery story. And you covered it, I know you were in the Dell booth, but it's basically an analog brewery. They're taking measurements and temperatures and then writing it down and then entering it in and somebody from your company saw it and said, "We can help you with this problem." Explain the story. >> Yeah, so Scott and I did a walkthrough of the brewery back in November timeframe. >> It's in Framingham, Mass. >> Framingham, Mass, correct. And basically, we talked to him, and we said, what keeps you guys up at night? What's a problem that we can solve? Very simple, a kind of a lower budget, didn't have a lot money to spend on it, but what problem can we solve that will realize great benefit for you? So we looked at their fermentation process, which was completely analog. Somebody was walking around with a clipboard looking at analog gauges. And what we did is we digitized that process. So what this did for them rather than being completely reactive, and by the time they realized there was something going wrong with the fermentation process, it's too late. A batch of scrap. This allowed them to be proactive. So anytime, anywhere on the tablet or a phone, they can see if that fermentation process is going out of range and do something about it before the batch gets scrapped. >> Okay. Amazing. And Scott, you got a picture of this workflow here? >> Yeah, actually this is the final product. >> Explain that. >> As Warren mentioned, the data is actually residing in the industrial side of the network So we wanted to keep the IT/OT separation, which is critical on the factory floor. And so all the data is brought in from the sensors via digital connection once it's converted and into the edge gateway. Then there's a snapshot of it using Telit deviceWISE, their dashboarding application, that is decoding all the digital readings, putting them in a nice dashboard. And then when we gave them, we realized another problem was they're using cheap little Chromebooks that they spill beer on once a week and throw them out. That's why they bought the cheap ones 'cause they go through them so fast. So we got a Dell Latitude Rugged notebook. This is a brand new tablet, but they have the dashboarding software. So no matter if they're out there on the floor, but because the data resides there on the factory they have access to be able to change the parameters. This one's in the maturation cycle. This one's in the crashing cycle where they're bringing the temperature back down, stopping the fermentation process, getting it ready to go to the canning side of the house. >> And they're doing all that from this dashboard. >> They're doing all from the dashboard. They also have a giant screen that we put up there that in the floor instead of walking a hundred yards back behind a whole bunch of machinery equipment from a safety perspective, now they just look up on the screen and go, "Oh, that's red. That's out of range." They're actually doing a bunch of cleaning and a bunch of other things right now, too. So this is real time from Boston. >> Dave: Oh okay. >> Scott: This is actually real time from Boston. >> I'm no hop master, but I'm looking at these things flashing at me and I'm thinking something's wrong with my beer. >> We literally just lit this up last week. So we're still tweaking a few things, but they're also learning around. This is a new capability they never had. Oh, we have the ability to alert and monitor at different processes with different batches, different brews, different yeast types. Then now they're also training and learning. And we're going to turn that into eventually a product that other breweries might be able to use. >> So back to the kind of nuts and bolts of the system. The device that you have here has essentially wifi antennas on the back. >> Warren: Correct. >> Pull that up again if you would, please. >> Now I've seen this, just so people are clear, there are also paddle 5G antennas that go on the other side. >> Correct. >> That's sort of the connection from the 5G network that then gets transmogrified, technical term guys, into wifi so the devices that are physically connected to the brew vats, don't know what they're called. >> Fermentation tanks. >> Fermentation tanks, thank you. Those are wifi. That's a wifi signal that's going into this. Is that correct? >> Scott: No. >> No, it's not. >> It's a hard wire. >> Okay, okay. >> But, you're right. This particular gateway. >> It could be wifi if it's hard wire. >> It could be, yes. Could be any technology really. >> This particular gateway is not outfitted with 5G, but something that was very important in this application was to isolate the IT network, which is on wifi and physically connected from the OT network, which is the 5G connection. So we're sending the data directly from the gateway up to the cloud. The two partners that we worked with on this project were ifm, big sensor manufacturer that actually did the wired sensors into an industrial network called IO-Link. So they're physically wired into the gateway and then in the gateway we have a solution from our partner Telit that has deviceWISE software that actually takes the data in, runs the analytics on it, the logic, and then visualizes that data locally on those panels and also up to their cloud, which is what we're looking at. So they can look at it locally, they're in the plant and then up in the cloud on a phone or a tablet, whatever, when they're at home. >> We're talking about a small business here. I don't know how many employees they have, but it's not thousands. And I love that you're talking about an IT network and an OT network. And so they wanted, it is very common when we talk about industrial internet of things use cases, but we're talking about a tiny business here. >> Warren: Correct. >> They wanted to separate those networks because of cost, because of contention. Explain why. >> Yeah, just because, I mean, they're running their ERP system, their payroll, all of their kind of the way they run their business on their IT network and you don't want to have the same traffic out on the factory floor on that network, so it was pretty important. And the other thing is we really, one of the things that we didn't want to do in this project is interrupt their production process at all. So we installed this entire system in two days. They didn't have to shut down, they didn't have to stop. We didn't have to interrupt their process at all. It was like we were invisible there and we spun the thing up and within two days, very simple, easy, but tremendous value for their business. >> Talk about new markets here. I mean, it's like any company that's analog that needs to go digital. It's like 99% of the companies on the planet. What are you guys seeing out there in terms of the types of examples beyond breweries? >> Yeah, I could talk to that. So I spent a lot of time over the last couple years running my own little IoT company and a lot of it being in agriculture. So like in Washington state, 70% of the world's hops is actually grown in Washington state. It's my hometown. But in the Ag producing regions, there's lack of connectivity. So there's interest in private networks because the carriers aren't necessarily deploying it. But because we have the vast amount of hops there's a lot of IPAs, a lot of hoppy IPAs that come out of Seattle. And with that, there's a ton of craft breweries that are about the same size, some are a little larger. Anheuser-Busch and InBev and Heineken they've got great IoT platforms. They've done it. They're mass scale, they have to digitize. But the smaller shops, they don't, when we talk about IT/OT separation, they're not aware of that. They think it's just, I get local broadband and I get wifi and one hotspot inside my facility and it works. So a little bit of it was the education. I have got years in IT/OT security in my background so that education and we come forward with a solution that actually does that for them. And now they're aware of it. So now when they're asking questions of other vendors that are trying to sell them some type of solution, they're inherently aware of what should be done so they're not vulnerable to ransomware attacks, et cetera. So it's known as the Purdue Model. >> Well, what should they do? >> We came in and keep it completely separated and educated them because in the end too we'll build a design guide and a starter kit out of this that other brewers can use. Because I've toured dozens of breweries in Washington, the exact same scenario, analog gauges, analog process, very manual. And in the end, when you ask the brewer, what do they want out of this? It keeps them up at night because if the temperature goes out of range, because the chiller fails, >> They ruined. >> That's $30,000 lost in beer. That's a lot to a small business. However, it's also once they start digitizing the data and to Warren's point, it's read-only. We're not changing any of the process. We augmented on top of their existing systems. We didn't change their process. But now they have the ability to look at the data and see batch to batch consistency. Quality doesn't always mean best, it means consistency from batch to batch. Every beer from exhibit A from yesterday to two months from now of the same style of beer should be the same taste, flavor, boldness, et cetera. This is giving them the insights on it. >> It's like St. Louis Buds, when we were kids. We would buy the St. Louis Buds 'cause they tasted better than the Merrimack Buds. And then Budweiser made them all the same. >> Must be an East coast thing. >> It's an old guy thing, Dave. You weren't born yet. >> I was in high school. Yeah, I was in high school. >> We like the hops. >> We weren't 21. Do me a favor, clarify OT versus IT. It's something we talk about all the time, but not everyone's familiar with that separation. Define OT for me. >> It's really the factory floor. You got IT systems that are ERP systems, billing, you're getting your emails, stuff like that. Where the ransomware usually gets infected in. The OT side is the industrial control network. >> David: What's the 'O' stand for? >> Operation. >> David: Operation? >> Yeah, the operations side. >> 'Cause some people will think objects 'cause we think internet of things. >> The industrial operations, think of it that way. >> But in a sense those are things that are connected. >> And you think of that as they are the safety systems as well. So a machine, if someone doesn't push the stop button, you'd think if there's a lot of traffic on that network, it isn't guaranteed that that stop button actually stops that blade from coming down, someone's going to lose their arm. So it's very tied to safety, reliability, low latency. It is crafted in design that it never touches the internet inherently without having to go through a security gateway which is what we did. >> You mentioned the large companies like InBev, et cetera. You're saying they're already there. Are they not part of your target market? Or are there ways that you can help them? Is this really more of a small to mid-size company? >> For this particular solution, I think so, yeah. Because the cost to entry is low. I mean, you talk about InBev, they have millions of dollars of budgets to spend on OT. So they're completely automated from top to bottom. But these little craft brewers, which they're everywhere in the US. Vermont, Washington state, they're completely manual. A lot of these guys just started in their garage. And they just scaled up and they got a cult kind of following around their beers. One thing that we found here this week, when you talk around edge and 5G and beer, those things get people excited. In our booth we're serving beer, and all these kind of topics, it brings people together. >> And it lets the little guy compete more effectively with the big giants. >> Correct. >> And how do you do more with less as the little guy is kind of the big thing and to Warren's point, we have folks come up and say, "Great, this is for beer, but what about wine? What about the fermentation process of wine?" Same materials in the end. A vessel of some sort, maybe it's stainless steel. The clamps are the same, the sensors are the same. The parameters like temperature are key in any type of fermentation. We had someone talking about olive oil and using that. It's the same sanitary beverage style equipment. We grabbed sensors that were off the shelf and then we integrated them in and used the set of platforms that we could. How do we rapidly enable these guys at the lowest possible cost with stuff that's at the shelf. And there's four different companies in the solution. >> We were having a conversation with T-Mobile a little earlier and she mentioned the idea of this sounding scary. And this is a great example of showing that in fact, at a relatively small scale, this technology makes a lot of sense. So from that perspective, of course you can implement private 5G networks at an industrial scale with tens of millions of dollars of investment. But what about all of the other things below? And that seems to be a perfect example. >> Yeah, correct. And it's one of the things with the gateway and having flexibility the way Dell did a great job of putting really good modems in it. It had a wide spectrum range of what bands they support. So being able to say, at a larger facility, I mean, if Heineken wants to deploy something like this, oh, heck yeah, they probably could do it. And they might have a private 5G network, but let's say T-Mobile offers a private offering on their public via a slice. It's easy to connect that radio to it. You just change the sims. >> Is that how the CSPs fit here? How are they monetized? >> Yeah, correct. So one of our partners is T-Mobile and so we're working with them. We've got other telco partners that are coming on board in our lab. And so we'll do the same thing. We're going to take this back and put it in the lab and offer it up as others because the baseline building blocks or Lego blocks per se can be used in a bunch of different industries. It's really that starter point of giving folks the idea of what's possible. >> So small manufacturing, agriculture you mentioned, any other sort of use cases we should tune into? >> I think it's environmental monitoring, all of that stuff, I see it in IoT deployments all over the world. Just the simple starter kits 'cause a farmer doesn't want to get sold a solution, a platform, where he's got to hire a bunch of coders and partner with the big carriers. He just wants something that works. >> Another use case that we see a lot, a high cost in a lot of these places is the cost of energy. And a lot of companies don't know what they're spending on electricity. So a very simple energy monitoring system like that, it's a really good ROI. I'm going to spend five or $10,000 on a system like this, but I'm going to save $20,000 over a year 'cause I'm able to see, have visibility into that data. That's a lot of what this story's about, just giving visibility into the process. >> It's very cool, and like you said, it gets people excited. Is it a big market? How do you size it? Is it a big TAM? >> Yeah, so one thing that Dell brings to the table in this space is people are buying their laptops, their servers and whatnot from Dell and companies are comfortable in doing business with Dell because of our model direct to customer and whatnot. So our ability to bring a device like this to the OT space and have them have that same user experience they have with laptops and our client products in a ruggedized solution like this and bring a lot of partners to the table makes it easy for our customers to implement this across all kinds of industries. >> So we're talking to billions, tens of billions. Do we know how big this market is? What's the TAM? I mean, come on, you work for Dell. You have to do a TAM analysis. >> Yes, no, yeah. I mean, it really is in the billions. The market is huge for this one. I think we just tapped into it. We're kind of focused in on the brewery piece of it and the liquor piece of it, but the possibilities are endless. >> Yeah, that's tip of the spear. Guys, great story. >> It's scalable. I think the biggest thing, just my final feedback is working and partnering with Dell is we got something as small as this edge gateway that I can run a Packet Core on and run a 5G standalone node and then have one of the small little 5G radios out there. And I've got these deployed in a farm. Give the farmer an idea of what's possible, give him a unit on his tractor, and now he can do something that, we're providing connectivity he had never had before. But as we scale up, we've got the big brother to this. When we scale up from that, we got the telco size units that we can put. So it's very scalable. It's just a great suite of offerings. >> Yeah, outstanding. Guys, thanks for sharing the story. Great to have you on theCUBE. >> Good to be with you today. >> Stop by for beer later. >> You know it. All right, Dave Vellante for Dave Nicholson and the entire CUBE team, we're here live at the Fira in Barcelona MWC '23 day four. Keep it right there. (upbeat music)

>> Narrator: theCUBE's live coverage is made possible by funding from Dell Technologies. Creating technologies that drive human progress. (upbeat music) >> Welcome back to Barcelona, Spain, everyone. It's theCUBE live at MWC '23, day three of four days of CUBE coverage. It's like a cannon of CUBE content coming right at you. I'm Lisa Martin with Dave Nicholson. We've got Dell and VMware here. Going to be talking about the ecosystem partnerships and what they're doing to further organizations in the telco industry. Please welcome Jared Woodrey, Director of Partner Engineering Open Telecom Ecosystem Lab, OTEL. Odded Solomon is here as well, Director of Product Management, VMware Service Provider and Edge Business Unit at VMware. Guys, great to have you on the program. >> Thank you for having me. >> Welcome to theCUBE. So Jared, first question for you. Talk about OTEL. I know there's a big announcement this week, but give the audience context and understanding of what OTEL is and how it works. >> Sure. So the Open Telecom Ecosystem Lab is physically located at Round Rock, Texas, it's the heart and soul of it. But this week we also just announced opening up the Cork, Ireland extension of OTEL. The reason for our existence is to to try and make it as easy as possible for both partners and customers to come together and to re-aggregate this disaggregated ecosystem. So that comes with a number of automation tools and basically just giving a known good testing environment so that tests that happen in our lab are as close to real world as they possibly can be and make it as transparent and open as possible for both partners like VMware as well as customers. >> Odded, talk about what you're doing with Dell and OTEL and give us a customer example of maybe one that you're working with or even even mentioning it by a high level descriptor if you have to. >> Yeah. So we provide a telco cloud platform, which is essentially a vertical in VMware. The telco cloud platform is serving network function vendors, such as Ericsson, Nokia, Mavenir, and so on. What we do with Dell as part of this partnership is essentially complementing the platform with some additional functionality that is not coming out of the box. We used to have a data protection in the past, but this is no longer our main business focus. So we do provide APIs that we can expose and work together with Dell PPDM solution so customer can benefit from this and leverage the partnership and have overall solution that is not coming out of the box from VMware. >> I'm curious, from a VMware perspective. VMware is associated often with the V in VMware, virtualization, and we've seen a transition over time between sort of flavors of virtualization and what is the mix currently today in the telecom space between environments that are leveraging what we would think of as more traditional virtualization with full blown Linux, Windows operating systems in a VM versus the world of containerized microservices? What does that mix look like today? Where do you see it going? >> Yeah, so the VMware telco cloud platform exists for about eight years. And the V started around that time. You might heard about open stack in addition to VMware. So this has definitely helped the network equipment providers with virtualizing their network functions. Those are typically VNF, virtualized network functions, inside the VMs. Essentially we have 4G applications, so core applications, EPC, we have IMS. Those are typically, I would say maybe 80 or 90% of the ecosystem right now. 5G is associated with cloud native network functions. So 5G is getting started now, getting deployed. There is an exponential growth on the core side. Now, when we expand towards the edge of the network we see more potential growth. This is 5G ran, we see the vRAN, we see the open RAN, we see early POCs, we see field trials that are starting. We obviously has production customer now. You just spoke to one. So this is really starting, cloud native is really starting I would say about 10 to 20% of the network functions these days are cloud native. >> Jared, question for you. You mentioned data protection, a huge topic there obviously from a security perspective. Data protection used to be the responsibility of the CSPs. You guys are changing that. Can you talk a little bit about how you're doing that and what Dell's play there is? >> Yeah, so PowerProtect Data Management is a product, but it's produced by Dell. So what this does is it enables data protection over virtual cloud as well as the physical infrastructure of specifically in this case of a telecoms ecosystem. So what this does is enables an ability to rapidly redeploy and back up existing configurations all the way up to the TCP and TCA that pulls the basis of our work here with VMware. >> So you've offloaded that responsibility from the CSPs. You freed them from that. >> So the work that we did, honestly was to make sure that we have a very clear and concise and accurate procedures for how to conduct this as well. And to put this through a realistic and real world as if it was in a telecoms own production network, what did that would actually look like, and what it would take to bring it back up as well. So our responsibility is to make sure that when we when we provide these products to the customers that not only do they work exactly as their intended to, but there is also documentation to help support them and to enable them to have their exact specifications met by as well. >> Got it. So talk about a little bit about OTEL expansion into Cork. What you guys are doing together to enable CSPs here in EMEA? >> Yeah, so the reason why we opened up a facility in Cork Island was to give, for an EMEA audience, for an EMEA CSPs and ability to look and feel and touch some of the products that we're working on. It also just facilitates and ease especially for European-based partners to have a chance to very easily come to a lab environment. The difference though, honestly, is the between Round Rock, Texas and Cork Island is that it's virtually an extension of the same thing. Like the physical locations can make it easier to provide access and obviously to showcase the products that we've developed with partners. But the reality is that it's more than just the physical location. It's more about the ability and ease by which customers and partners can access the labs. >> So we should be expecting a lot of Tito's vodka to be consumed in Cork at some point. Might change the national beverage. >> We do need to have some international exchange. >> Yeah, no, that's good to know. Odded, on the VMware side of things. There's a large group of folks who have VMware skillsets. >> Odded: Correct. >> The telecom industry is moving into this world of the kind of agility that those folks are familiar with. How do people come out of the traditional VMware virtualization world and move into that world of cloud native applications and serve the telecom space? What would your recommendation be? If you were speaking at a VMUG, a VMware Users Group meeting with all of your telecom background, what would you share with them that's critical to understand about how telecom is different, or how telecom's spot in its evolution might be different than the traditional IT space? >> So we're talking about the people with the knowledge and the background of. >> Yeah, I'm a V expert, let's say. And I'm looking into the future and I hear that there are 80,000 people in Barcelona at this event, and I hear that Dell is building optimized infrastructure specifically for telecom, and that VMware is involved. And I'm an expert in VMware and I want to be involved. What do I need to do? I know it's a little bit outside of the box question, but especially against the backdrop of economic headwinds globally, there are a lot of people facing transitions. What are your thoughts there? >> So, first of all, we understand the telco requirements, we understand the telco needs, and we make sure that what we learn from the customers, what we learn from the partners is being built into the VMware products. And simplicity is number one thing that is important for us. We want the customer experience, we want the user experience to be the same as they know even though we are transitioning into cloud native networks that require more frequent upgrades and they have more complexity to be honest. And what we do in our vertical inside VMware we are focusing on automation, telco cloud automation, telco cloud service assurance. Think of it as a wrapper around the SDDC stack that we have from VMware that really simplifies the operations for the telcos because it's really a challenge about skillset. You need to be a DevOps, SRE in order to operate these networks. And things are becoming really complex. We simplify it for them with the same VMware experience. We have a very good ability to do that. We sell products in VMware. Unlike our competition that is mostly selling professional services and support, we try to focus more on the products and delivering the value. Of course, we have services offering because telcos requires some customizations, but we do focus on automation simplicity throughout our staff. >> So just follow up. So in other words the investment in education in this VMware ecosystem absolutely can be extended and applied into the telecom world. I think it's an important thing. >> I was going to add to that. Our engagement in OTEL was also something that we created a solutions brief whether we released from Mobile World Congress this week. But in conjunction with that, we also have a white paper coming out that has a much more expansive explanation and documentation of what it was that we accomplished in the work that we've done together. And that's not something that is going to be a one-off thing. This is something that will stay evergreen that we'll continue to expand both the testing scope as well as the documentation for what this solution looks like and how it can be used as well as documentation on for the V experts for how they can then leverage and realize the the potential for what we're creating together. >> Jared, does Dell look at OTEL as having the potential to facilitate the continued evolution of the actual telco industry? And if so, how? >> Well, I mean, it would be a horrible answer if I were to say no to that. >> Right. >> I think, I honestly believe that one of the most difficult things about this idea of having desired ecosystem is not just trying to put it back together, but then also how to give yourself choice. So each time that you build one of those solution sets like that exists as an island out of all the other possibilities that comes with it. And OTEL seeks to not just be able to facilitate building that first solution set. Like that's what solutions engineering can do. And that's generally done relatively protected and internally. The Open Telecom Ecosystem seeks to build that then to also provide the ability to very easily change specific components of that whether that's a hardware component, a NIC, whether a security pass just came out or a change in either TCP or TCA or we talked a little bit about for this specific engagement that it was done on TCP 2.5. >> Odded: Correct. >> Obviously there's already a 2.7 and 3.0 is coming out. It's not like we're going to sit around and write our coattails of what 2.7 has happened. So this isn't intended to be a one and done thing. So when we talk about trying to make that easier and simpler and de-risk all of the risk that comes from trying to put all these things together, it's not just the the one single solution that you built in the lab. It's what's the next one? And how do I optimize this? And I have specific requirements as a CSP, how can I take something you built that doesn't quite match it, but how do I make that adjustment? So that's what we see to do and make it as easy and as painless as possible. >> What's the engagement model with CSPs? Is it led by Dell only, VMware partner? How does that work? >> Yeah, I can take that. So that depends on the customer, but typically customers they want to choose the cloud vendor. So they come to VMware, we want VMware. Typically, they come from the IT side. They said, "Oh, we want to manage the network side of the house the same way as we manage the IT. We don't want to have special skill sets, special teams." So they move from the IT to the network side and they want VMware there. And then obviously they have an RSP process and they have hardware choices. They can go with Dell, they can go with others. We leverage vSphere, other compatibility. So we can be flexible with the customer choice. And then depending on which customer, how large they are, they select the network equipment provider that the runs on top. We position our platform as multi-vendor. So many of them choose multiple network functions providers. So we work with Dell. So assuming that the customer is choosing Dell. We work very closely with them, offering the best solution for the customer. We work with them sometimes to even design the boxes to make sure that it fits their use cases and to make sure that it works properly. So we have a partnership validation certification end-to-end from the applications all the way down to the hardware. >> It's a fascinating place in history to be right now with 5G. Something that a lot of consumers sort of assume. It's like, "Oh, hey, yeah, we're already there. What's the 6G thing going to look like?" Well, wait a minute, we're just at the beginning stages. And so you talk about disaggregation, re-aggregation, or reintegration, the importance of that. Folks like Dell have experience in that space. Folks at VMware have a lot of experience in the virtualization space, but I heard that VMware is being acquired by Broadcom, if it all goes through, of course. You don't need to comment on it. But you mentioned something, SDDC, software-defined data center. That stack is sometimes misunderstood by the public at large and maybe the folks in the EU, I will editorialize for a moment here. It is eliminating capture in a way by larger hyperscale cloud providers. It absolutely introduces more competition into the market space. So it's interesting to hear Broadcom acknowledging that this is part of the future of VMware, no matter what else happens. These capabilities that spill into the telecom space are something that they say they're going to embrace and extend. I think that's important for anyone who's evaluating this if they're concern. Well, wait a minute. Yeah, when I reintegrate, do I want VMware as part of this mix? Is that an unknown? It's pretty clear that that's something that is part of the future of VMware moving forward. That's my personal opinion based on analysis. But you brought up SDDC, so I wanted to mention that. Again, I'm not going to ask you to get into trouble on that at all. What should we be, from a broad perspective, are there any services, outcomes that are going to come out of all of this work? The agility that's being built by you folks and folks in the open world. Are there any specific things that you personally are excited about? Or when we think about consumer devices, getting data, what are the other kinds of things that this facilitates? Anything cool, either one of you. >> So specific use cases? >> Yeah, anything. It's got to be cool though. If it's not cool we're going to ask you to leave. >> All right. I'll take that challenge. (laughs) I think one of the things that is interesting for something like OTEL as an exist, as being an Open Telecom Ecosystem, there are going to be some CSPs that it's very difficult for them to have this optionality existing for themselves. Especially when you start talking about tailoring it for specific CSPs and their needs. One of the things that becomes much more available to some of the smaller CSPs is the ability to leverage OTEL and basically act as one of their pre-production labs. So this would be something that would be very specific to a customer and we would obviously make sure that it's completely isolated but the intention there would be that it would open up the ability for what would normally take a much longer time period for them to receive some of the benefits of some of the changes that are happening within the industry. But they would have immediate benefit by leveraging specifically looking OTEL to provide them some of their solutions. And I know that you were also looking for specific use cases out of it, but like that's a huge deal for a lot of CSPs around the world that don't have the ability to lay out all the different permutations that they are most interested in and start to put each one of those through a test cycle. A specific use cases for what this looks like is honestly the most exciting that I've seen for right now is on the private 5G networks. Specifically within mining industry, we have a, sorry for the audience, but we have a demo at our booth that starts to lay out exactly how it was deployed and kind of the AB of what this looked like before the world of private 5G for this mining company and what it looks like afterwards. And the ability for both safety, as well as operational costs, as well as their ability to obviously do their job better is night and day. It completely opened up a very analog system and opened up to a very digitalized system. And I would be remiss, I didn't also mention OpenBrew, which is also an example in our booth. >> We saw it last night in action. >> We saw it. >> I hope you did. So OpenBrew is small brewery in Northeast America and we basically took a very manual process of checking temperature and pressure on multiple different tanks along the entire brewing process and digitized everything for them. All of that was enabled by a private 5G deployment that's built on Dell hardware. >> You asked for cool. I think we got it. >> Yeah, it's cool. >> Jared: I think beer. >> Cool brew, yes. >> Root beer, I think is trump card there. >> At least for folks from North America, we like our brew cool. >> Exactly. Guys, thank you so much for joining Dave and me talking about what Dell, OTEL, and VMware are doing together, what you're enabling CSPs to do and achieve. We appreciate your time and your insights. >> Absolutely. >> Thank you. >> All right, our pleasure. For our guests and for Dave Nicholson, I'm Lisa Martin. You watching theCUBE live from MWC '23. Day three of our coverage continues right after a short break. (upbeat music)

>> theCUBE's live coverage is made possible by funding from Dell Technologies. Creating technologies that drive human progress. (upbeat music) >> Lisa Martin: Good afternoon everyone. theCUBE live in Barcelona, Spain at MWC23. Lisa Martin with Dave Nicholson. Day three of our wall-to-wall coverage of four days of CUBE content. I know, it's amazing. We're going to have a great conversation next with DISH and Dell, talking about the value of automation and telecom for 5G. Please welcome Song Toh, Senior Director of Product Management Infrastructure Automation at Dell. And Sidd Chenumolu, VP of Technology Development at DISH. Guys, great to have you on theCUBE. >> Thanks for having us. >> Thank you, it's a pleasure. >> So let's go ahead and start with you. We know that DISH is developing its own open cloud native 5G network from the ground up. Talk to us about before you were working with Dell, what the situation was like and why you brought Dell in to help drive the innovation. >> Ah, that's a good question. So, three years ago we started the journey, and one thing that was very clear to us is that we want to work with the partners who are going to be the leaders in this space. And it was very clear we are going to be in the cloud side- we are going to be in hybrid cloud, we are going to have our own data centers. Everything that we built is going to replicate a cloud model. 'Cause it was very, like we said, what is 5G? Fundamentally, if you think about 5G, right? Everyone says people talk about speeds. Okay, get it. But it's also about vertical industries. It's about customization of a network, application driven network. That's the way I call it, because if you walk around the floor right now, everyone's talking about monetization of 5G, everyone keeps doing enterprise. So you put two and two together, what do you get? That means you have to work with the leaders who have been serving enterprises forever, who know the enterprises' pain, they know all the problem statements. So we said, "okay, let's see who's out there and who can help us." And then obviously, Dell comes to the picture. So we had a good conversation, there was an alignment in where Dell wanted to go long-term, so we saw synergies. So we had a vision, we needed their help. They wanted to get into this space too. So there was an agreement, let's do it together. And it's been a good partnership since then. >> What were some of the challenges that you had at that time? Going, "we've got some challenges here, some risks, we want to move DISH forward and automate." Talk about some of those challenges that helped you understand, "Yeah, Dell's the right partner for this." >> Oh, first is when we started this, right? I'll be honest, I don't think we anticipated the complexity. We didn't know what we didn't know. So initially it was learning from Dell, who was more like teaching us, "this is what you're going to see, this is how it's going to look like". And then we started bringing the telco aspects on top of it. So it was not like, "I'm going to build a 5G". We said, "no, Dell, tell me what does the data center look like? Tell me the day-to-day challenges. How do you bring a server in? How the rack looks like, what are the connectivity?" So, learning, then you bring the telco as an application, it was not like a telco first. It was like a software first, infrastructure second, now you bring in the telco part of it. So, I mean, challenges I would say, right? Everything was new, pretty much across the board for us. It was not just one thing. We were doing Open RAN, which was a brand new cloud native, was completely new. 5G standalone was new. No one had done that before, and (mumbles) was hybrid cloud. So I think we were on a stool sitting on the, with the four legs, all were wobbly. (laughs) We made it. So, automation was definitely the key. We knew we had to go at a scale, because we are in FCC deployment, we are meeting like- we will be at covering 230 million pops by June of this year. So, aggressive timelines- >> Dave Nicholson: Wait, say that again. How many, so say that ag- how many? >> 230 million. >> And, pops being points of presence? >> No, sorry, population. U. S.- >> Oh, population. Okay, I'm sorry, I'm sorry. Okay, okay. >> Okay. I'm sorry, I'm- >> So, very aggressive buildout for us. >> Wow. >> And automation has to be the key for it, because we just cannot- first is, we cannot scale a company. We are a startup. This wireless is a startup. That's how we started with a handful of people. We obviously hired a lot of people since then, but we said, "we will never be at the scale of the existing CSPs today." We can't. Time is not on our side, and we don't want to be at that scale anyway, 'cause we want to be nimble, move fast. So what do you need? Automation. Automation at every layer. And it's a journey. Never stops. >> No, it doesn't stop. >> Oh yeah, I'm sorry. Yeah, she's- >> Go ahead and get a question in. I don't want to hog. >> So when most people hear DISH, they think of streaming content, they think of alternative to cable provider. >> Sidd: Yeah. >> In that space. But just clarify for us all of the things that DISH is involved with today, and what DISH aspires to be involved with as we move forward. >> Good question. We want to be in the connectivity space. We want to connect everything. That's our goal, our mission statement. We started with the satellite, since then we moved on to the IPTV Sling, which is a leader. So we are not afraid to take risks, right? So what we own- we own satellites, we know content delivery very well. I think we are done there for many years. We agreed to that. Now we said, "now we understand wireless". What we want to do is, we want to deliver the data to the customers, and whether it could be videos, it could be audio data, like voice, anything, or it could be a machine. We just want to be in the connectivity space of connecting everything, and based on- you look around, right? It's all about connectivity. Everything requires connectivity. It's all about data monetization, and we want to be there in every aspect of it. >> Connectivity is almost the lifeblood these days of everything that we do, right? >> Sidd: Yep. >> Song: Indeed. >> And of every industry. Song, talk a little bit about the DISH Wireless use case. How some of their challenges in telco really maybe helped even Dell accelerate its presence in telco. >> Absolutely, right. I think one thing that Sidd mentioned, right, 230 million populations, but what does that translate to in terms of infrastructure deployment? 'Cause he said it's a startup. They started from not a whole lot in terms of coverage. So, in terms of 5G deployment, whether it's virtualized or open RAN, there needs to be distributed infrastructure that covers the entire United States, right? A certain percentage of the population is still a huge amount of coverage. So deploy tens of thousands, hundreds of thousands of servers around the country, get them set up, get 'em configured, and maintain and monitor and meter all of that. We help DISH to essentially roll that out, get it going, and then they deploy their RAN workload on top. I mean, that's a very significant undertaking. We were very proud to be able to offer our Bare Metal Orchestrator to facilitate that, but ultimately their success is their success. We are there to help, right? We are partnered, and we- happy to definitely be able to say we got to a point that we are happy, you know, in claims of success there. >> Well, that's why we selected Dell. >> Thank you. (chuckles) >> Let's unpack a little bit of some of the successes, some of the outcomes that you've achieved so far, working with Dell. >> Let me give an example. Today we have an ability to upgrade, update, even swap a RAN vendor overnight. Entire market, unheard of overnight. Give me hours, I'll do the entire thing for you from scratch. We can instantiate entire data center racks remotely in a matter of minutes. Cannot do that without automation, and with the help- >> Lisa Martin: Couldn't do it before. >> We have curated an extraordinary, what you call orchestration mechanism of finely tuned data sets and pipelines. It's like a machine. It keeps spinning. It's very good. And again, not something that happened overnight. Took us several months to get there with a lot of our partners, and Dell was there. >> Song: Right. >> I'd be curious to get your perspectives, each of you, on some of the buzz that was going on around the show where the telecom, "plumbing providers"- >> Sidd: Yep. >> have complained about the content streaming through, and maybe they need to charge more for access, and Netflix hit back and said, "well, hold on a minute. You wouldn't have anything to deliver to your customers if it weren't for the content we are producing. Maybe we need licensing fees from you." >> Song: (chuckles) >> What is your view on that, in terms of this whole over the top conversation? DISH seems sort of, kind of in a hybrid position there. >> Well, it's a very complex question. I think everyone is struggling with it, so I'm not sure if I have the right answer for it. We are definitely unique because we own the content too. We want to offer- we probably may offer our own content over the wireless service. There is a pros and cons. I mean, purely from a, as a M&O service provider, it's a lot of effort and cost for us to deliver huge amount of bandwidth. But again, the networks are being built to handle huge capacity. So if you don't have video, what do we do? That's also a realistic question. I think there is a mechanism where the cost and the value both have to be shared. So that it's a win-win for everyone. It's not lopsided to one. And said, "you carry most of the cost", and I'm transparent, it doesn't work that way long term. And especially given the 5G side, with all the slicing capabilities and ability to offer QoS, better quality of experience, I think there's a value to be created here. >> If you look at the infrastructure necessary to drive all of these things- >> Right. >> We've seen, just go back to our own consumer experience with the internet. We've gone from text to images to video. >> Song: Right. >> To high definition video. >> Sidd: Yeah. >> To, is 8K video absurd? Do we really need to be able to handle that? What are the things that need to be supported as we move forward? Is it that we scale out into this world of billions and billions of things that are connected? Or are there these much bigger, fatter pipelines for things like 8K video or it a combination of the two? What is Dell thinking of when it thinks of the infrastructure that it builds and how you customize that- >> Song: Right. >> to address those things? What's on the horizon? >> Dave, I think that's a very good question, right? Certainly communication service providers like DISH has built out the capacity to handle the customers that they want to serve. But there's another aspect of this I think I'd like to add on top of the question you posed, it's not about say, 10, say a thousand streams of 8K. I would need to be able to handle that. I think the present challenge right now is really, say there's a sports stadium that you need to activate so that, not about everyone filming that sports game, it's about, "Hey, I got to tell my, whoever- I got a 10 seconds video clip that I got to share with my friends." It's also not about copyright. It's more about- >> Dave Nicholson: (laughs) >> can you as a provider- >> The NFL is listening. >> Exactly. Can you as a provider handle that service? Because otherwise your customers say, "oh, I got into the sports stadium, every time I could not even text my daughter." >> Dave Nicholson: Yeah. >> So, how do you then scale up the infrastructure as needed, the bandwidth as needed, and scale back down when it's not? Maybe, because the infrastructure can potentially be repurposed for a different workload too. That requires automation, right? From bottom to top, all the way, infrastructure - all the way up to the workload. And that's I think a question that people are starting to ask. I'm not sure. I mean, still you guys have thought about that too as a- >> I mean, instant gratification is the new thing, right? Everyone wants instant response, everyone feedback, everything. So connectivity is given. I do think there is a space for both billions of devices and the 8K and probably 16K in the future. It's going to happen in the technology walls. That's why I like, say, the 5G, and especially the way we architect our own network. We call it network of networks. I'm not designing a network that is only for one monolithic application or one stack only. We are actually programmable network, because I know network A is for 8K. Network B is for IOT, network C is for regular, network D is for something else. And the list can keeps on growing. I don't think we can stifle innovation at any level and said, "well you can't do this because we are not ready." World is going to move too fast. Technology is too fast for all of us. >> But do you have to prioritize? >> If there is a business for- it's all top-down driven, not much of a technology driven. If there's a business, someone said there's a value to be made, it's prioritized. >> What's your - Sidd, we'll stick with you, your observations. This is day three of MWC 23. Lot of talk here on disaggregation. A lot of talk about open RAN, a lot of talk about private 5G wireless networks, but also some controversy. You brought up the Netflix controversy. >> Dave: Yep. >> What are some of the messages that you've heard so far from this event - and then, Song, we'll ask you the same question - that excite you about the direction that the industry's going and where DISH Wireless stands within it? >> Yeah. I mean, I didn't have a chance to walk the floor, but for wherever I have been in the last two and a half days, one thing that stood out is people are no longer talking about gigabits capacity anymore. They're talking about monetization of the network. Everyone is talking APIs now. >> Lisa Martin: Yeah. >> That's the buzzword. If I said monetization, API- I got a beautiful network not tell me how to make money off it and how do I work with each other? It's no longer about "I want to own it all." What can I do to partner with A, partner with B? How can we all grow together? I think that's the theme that I see this year compared to the previous years, where it was always about like, "hey, build the best 5G network with the high speeds, big radios." I don't even see radios, by the way. >> Lisa Martin: (chuckles) >> Interesting. Yeah. So the actual, it's almost fascinating when you toil in obscurity to build these critical components and then people ignore you. So I feel for the radio people. >> Song: (laughs) Being a long-term infrastructure guy, what have you been seeing here that's interesting? >> Well, a few things that I feel quite excited about from the conversation I've had. One is, on the private mobility side, Lisa, as you said, I'm seeing certainly customers, partners, and even in the booth talking about what the use cases are, right? Rather than, "Hey, here's a cool technology." But actually, people talking about use cases now. And, with the communication service providers and the operators, I'm hearing - of course, I mean, Sidd's doesn't have that problem because it's building whole new, >> (chuckles) >> but there are other providers that are saying, "Hey, we acknowledge that we need to transform and we are on the way too", rather than saying, "can I not do it and still, you know, live with the modern world." So I feel that we always need to be ready to change, because the world, the market, and all other factors will cause us to either change or really to change. And I think we are changing. Open system is becoming more of a expected, you know, future. It's just how do we get there, right? What do we need to learn as we get there? And we're happy to provide the support as a partner, the automation technology, and even the solutions to enable that, from Dell's perspective. >> So DISH in particular? DISH Wireless. >> Yep. >> Despite the fact that everyone's heard of DISH. >> Song: Yeah. >> DISH has been around for a long time. Where you sit within DISH Wireless, you described it as a startup. You don't feel encumbered by a lot of the legacy things that maybe some other providers do. Is that a fair statement or are you having to navigate that? We call it ambidextrous management >> (laughs) >> in the CTO world, where it's like, got to keep the lights on, got to keep the existing revenue flowing, also got to innovate. How do you blend the two? Is that a challenge? >> Well, probably not a challenge for me. I'm on the wireless technology and architecture side, so I get to do the cool stuff. >> Dave Nicholson: Okay. >> Don't have to worry about day to day operations, some complexity or revenue. Someone else is managing that complex part. They let me play with my toys. >> Well played, well played. >> Guys, it's been great having you on the program talking about what DISH Wireless is doing with Dell. Thanks to Dell. We're going to be watching this space to see how you continue to innovate. Thank you so much for joining us on the program. >> Thanks for having us. >> Thank you. >> Our pleasure. >> For our guests and for Dave Nicholson. I'm Lisa Martin. You're watching theCUBE live from MWC 23. Stick around. Our next guest joins Dave and me in just a minute. (upbeat music) (upbeat music) (upbeat music)

(intro music) >> Narrator: "theCUBE's" live coverage is made possible by funding from Dell Technologies, creating technologies that drive human progress. (gentle music) >> Hey everyone, welcome back to "theCUBE," the leader in live and emerging tech coverage. As you well know, we are live at MWC23 in Barcelona, Spain. Lisa Martin with Dave Nicholson. Day three of our coverage, as you know, 'cause you've been watching the first two days. A lot of conversations about ecosystem, a lot about disruption in the telco industry. We're going to be talking about Open RAN. You've heard some of those great conversations, the complexities, the opportunities. Two guests join Dave and me. Abdullah Abuzaid, Technical Product Manager at Dell, and Gil Hellmann, VP Telecom Solutions Engineering and Architecture at Wind River. Welcome to the program guys. >> Thank you. >> Nice to be here. >> Let's talk a little bit about Dell and Wind River. We'll each ask you both the same question, and talk to us about how you're working together to really address the complexities that organizations are having when they're considering moving from a closed environment to an open environment. >> Definitely. Thank you for hosting us. By end of the day, the relationship between Dell and Wind River is not a new. We've been collaborating in the open ecosystem for long a time enough. And that's one of the, our partnership is a result of this collaboration where we've been trying to make more efficient operation in the ecosystem. The open environment ecosystem, it has the plus and a concern. The plus of simplicity, choice of multiple vendors, and then the concern of complexity managing these vendors. Especially if we look at examples for the Open RAN ecosystem, dealing with multiple vendors, trying to align them. It bring a lot of operational complexity and TCO challenges for our customers, from this outcome where we build our partnership with Wind River in order to help our customer to simplify, or run deployment, operation, and lifecycle management and sustain it. >> And who are the customers, by the way? >> Mainly the CSP customers who are targeting Open RAN and Virtual RAN deployments. That digital transformation moving towards unified cloud environment, or a seamless cloud experience from Core to RAN, these are the customers we are working with them. >> You'll give us your perspective, your thoughts on the partnership, and the capabilities that you're enabling, the CSPs with that. >> Sure. It's actually started last year here in Barcelona, when we set together, and started to look at the, you know, the industry, the adoption of Open RAN, and the challenges. And Open RAN brings a lot of possibilities and benefit, but it does bring a lot of challenges of reintegrating what you desegregate. In the past, you purchase everything from one vendor, they provide the whole solution. Now you open it, you have different layers. So if you're looking at Open RAN, you have, I like to look at it as three major layers, the management, application, and the infrastructure. And we're starting to look what are the challenges. And the challenges of integration, of complexity, knowledge that operator has with cloud infrastructure. And this is where we basically, Dell and Winder River set together and say, "How can we ease this? "How we can make it simpler?" And we decided to partner and bring a joint infrastructure solution to market, that's not only integrated at a lab at the factory level, but it basically comes with complete lifecycle management from the day zero deployment, through the day two operation, everything done through location, through Dell supported, working out of the box. So basically taking this whole infrastructure layer integration pain out, de-risking everything, and then continuing from there to work with the ecosystem vendor to reintegrate, validate the application, on top of this infrastructure. >> So what is the, what is the Wind River secret sauce in this, in this mix, for folks who aren't familiar with what Wind River does? >> Yes, absolutely. So Wind River, for many, many don't know, we're in business since 1981. So over 40 years. We specialize high performance, high reliability infrastructure. We touch every aspect of your day and your life. From the airplane that you fly, the cars, the medical equipment. And if we go into the telco, most of the telco equipment that it's not virtualized, not throughout the fight today, using our operating system. So from all the leading equipment manufacturers and even the smaller one. And as the world started to go into desegregation in cloud, Wind River started to look at this and say, "Okay, everything is evolving. Instead of a device that included the application, the hardware, everything fused together, it's now being decomposed. So instead of providing the operating environment to develop and deploy the application to the device manufacturer, now we're providing it basically to build the cloud. So to oversimplify, I call it a cloud OS, okay. It's a lot more than OS, it's an operating environment. But we took basically our experience, the same experience that, you know, we used in all those years with the telco equipment manufacturer, and brought it into the cloud. So we're basically providing solution to build an on-premises scalable cloud from the core all the way to the far edge, that doesn't compromise reliability, doesn't compromise performance, and address all the telco needs. >> So I, Abdullah, maybe you can a answer this. >> Yeah. >> What is the, what does the go-to-market motion look like, considering that you have two separate companies that can address customers directly, separately. What does that, what does that look like if you're approaching a possible customer who is, who's knocking on the door? >> How does that work? >> Exactly. And this effort is a Dell turnkey sales service offering, or solution offering to our customers. Where Dell, in collaboration with Wind River, we proactively validate, integrate, and productize the solution as engineered system, knock door on our customer who are trying to transform to Open RAN or open ecosystem. We can help you to go through that seamless experience, by pre-validating with whatever workload you want to introduce, enable zero touch provisioning, and during the day one deployment, and ensure we have sustainable lifecycle management throughout the lifecycle of the product in, in operate, in operational network, as well as having a unified single call of support from Dell side. >> Okay. So I was just going to ask you about support. So I'm a CSP, I have the solution, I go to Dell for support. >> Exactly. >> Okay. So start with Dell, and level one, level two. And if there are complex issues related to the cloud core itself, then Wind River will be on our back supporting us. >> Talk a little bit about a cust, a CSP example that is, is using the technology, and some of the outcomes that they're able to achieve. I'd love to get both of your perspectives on that. >> Vodafone is a great example. We're here in Barcelona. Vodafone is the first ora network in Europe, and it's using our joint solution. >> What are some of the, the outcomes that it's helping them to achieve? >> Faster time to market. As you see, they already started to deploy the ORAN in commercial network, and very successful in the trials that they did last year. We're also not stopping there. We're evolving, working with them together to improve like stuff around energy efficiency. So continue to optimize. So the outcome, it's just simplifying it, and you know, ready to go. Using experience that we have, Wind River is powering the first basically virtualized RAN 5G network in the world. This is with Verizon. We're at the very large scale. We started this deployment in late '20 and '19, the first site. And then through 2020 to 2022, we basically rolled in large scale. We have a lot of experience learning from it, which what we brought into the table when we partnered with Dell. A lot of experience from how you deploy at scale. Many sites from a central location, updates, upgrade. So the whole day two operation, and this is coming to bearing the solution that basically Vodafone is deploying now, and which allowed them... If I, if I look at my engagement with Verizon, started years before we started. And it took quite some time until we got stuff running. And if you look at the Vodafone time schedule, was significantly compressed compared to the Verizon first deployment. And I can tell you that there are other service providers that were announced here by KDI, for example. It's another one moving even faster. So it's accelerating the whole movement to Ora. >> We've heard a lot of acceleration talk this week. I'd love to get your perspective, Abdullah, talking about, you know, you, you just mentioned two huge names in Telco, Vodafone and Verizon. >> Yep. >> Talk a little bit about Dell's commitment to helping telecommunications companies really advance, accelerate innovation so that all of us on the other end have this thing that just works wherever we are 24 by 7. >> Not exactly. And this, we go back to the challenges in Open ecosystem. Managing multiple vendors at the same time, is a challenge for our customers. And that's why we are trying to simplify their life cycle by have, by being a trusted partner, working with our customer through all the journey. We started with Dish in their 5G deployment. Also with Vodafone. We're finding the right partners working with them proactively before getting into, in front of the customer to, we've done our homework, we are ready to simplify the process for you to go for it. If you look at the RAN in particular, we are talking with the 5g. We have ran the simplification, but they still have on the other side, limited resources and skillset can support it. So, bringing a pro, ahead of time engineer system, with a zero touch of provisioning enablement, and sustainable life cycle management, it lead to the faster time to market deployment, TCO savings, improved margins for our customers, and faster business revenue for their end users. >> Solid outcomes. >> And, and what you just just described, justifies the pain associated with disaggregating and reintegrating, which is the way that Gill referenced it, which I think is great because you're not, you're not, you're not re-aggregating, (laughs) you're reintegrating, and you're creating something that's better. >> Exactly. >> Moving forward. Otherwise, why would you do it? >> Exactly. And if you look at it, the player in the ecosystem, you have the vendors, you have the service integrators, you have the automation enablers, but kind of they are talking in silos. Everyone, this is my raci, this is what I'm responsible for. I, I'm not able, I don't want to get into something else while we are going the extra mile by working proactively in that ecosystem to... Let's bring brains together, find out what's one plus one can bring three for our customers, so we make it end-to-end seamless experience, not only on the technical part, but also on the business aspect side of it. >> So, so the partnership, it's about reducing the pen. I will say eliminating it. So this is the, the core of it. And you mentioned getting better coverage for your phone. I do want to point out that the phones are great, but if you look at the premises of a 5G network, it's to enable a lot more things that will touch your life that are beyond the consumer and the phone. Stuff like connected vehicles. So for example, something as simple as collision avoidance, the ability for the car that goes in front of you to be able to see what's happening and broadcast this information to the car behind that have no ability to see it. And basically affect our life in a way that makes our driving safer. And for this, you need a ultra low, reliable low latency communication. You need a 5G network. >> I'm glad you brought that up, because you know, we think about, "Well we just have to be connected all the time." But those are some of the emerging technologies that are going to be potentially lifesaving, and, and really life transforming that you guys are helping to enable. So, really great stuff there, but so much promise coming down the road. What's next for Dell and Wind River? And, and when you're in conversations with prospective CSP's, what is the superpower that you deliver together? I'd love to get both of your perspectives. >> So, if you look at it, number one, customers look at it, last savings and their day-to-day operation. In 5G nature, we are talking the introduction of ORAN. This is still picking up. But there is a mutualization and densification of ORAN. And this is where we're talking on monetizing my deployment. Then the third phase, we're talking sustainability and advanced service introduction. Where I want to move not only ORAN, I want to bring the edge at the same side, I want to define the advanced use cases of edge, where it enables me with this pre-work being done to deliver more services and better SLA services. By end of the day, 5G as a girl mentioned earlier, is not about a good better phone coverage, or a better speed robot, but what customized SLA's I can deliver. So it enables me to deliver different business streams to my end users. >> Yeah. >> So yeah. I will say there are two pens. One, it's the technology side. So for an example, energy efficiency. It's a very big pin point. And sustainability. So we work a lot around this, and basically to advance this. So if you look at the integrated solution today, it's very highly optimized for resource consumption. But to be able to more dynamically be able to change your power profile without compromising the SLA. So this is one side. The other side, it's about all those applications that will come to the 5G network to make our life better. It's about integrating, validating, certifying those applications. So, it's not just easy to deploy an ORAN network, but it's easy to deploy those applications. >> I'd be curious to get your perspective on the question of ROI in this, in this space. Specifically with the sort of the macro headwinds (clears throat) the economies of the world are facing right now, if you accept that. What does the ROI timeline look like when you're talking about moving towards ORAN, adopting VRAN, an amazing, you know, a plethora of new services that can be delivered, but will these operators have the appetite to take that, make that investment and take on that risk based upon the ROI time horizon? Any thoughts on that? >> Yeah. So if you look at the early days or ORAN introduction in particular, most of the entrepreneurs of ORAN and Virtual RAN ran into the challenges of not only the complexity of open ecosystem, but the integration, is like the redos of the work. And that's where we are trying to address it via pre-engineered system or building an engineer system proactively before getting it to the customers. Per our result or outcomes we get, we are talking about 30 to 50% savings on the optics. We are talking 110 ROI for our customers, simply because we are reducing the redos, the time spent to discover and explore. Because we've done that rework ahead of time, we found the optimization issues. Just for example, any customer can buy the same components from any multiple vendors, but how I can bring them together and give, deliver for me the best performance that I can fully utilize, that's, that's where it brings the value for our customer, and accelerate the deployment and the operation of the network. >> Do you have anything to add before we close in the next 30 seconds? >> Yeah. Yeah. (laughs) >> Absolutely. I would say, we start to see the data coming from two years of operation at scale. And the data supports performance. It's the same or better than traditional system. And the cost of operation, it's as good or better than traditional. Unfortunately, I can't provide more specific data. But the point is, when something is unknown in the beginning, of course you're more afraid, you take more conservative approach. Now the data starts to flow. And from here, the intention needs to go even better. So more efficiency, so cost less than traditional system, both to operate as well as to build up. But it's definitely the data that we have today says, the, ORAN system is at part, at the minimum. >> So, definite ROI there. Guys, thank you so much for joining Dave and me talking about how you're helping organizations not just address the complexities of moving from close to open, but to your point, eliminating them. We appreciate your time and, and your insights. >> Thank you. >> All right. For our guests and for Dave Nicholson, I'm Lisa Martin. You're watching "theCUBE," the leader in live and emerging tech coverage. Live from MWC23. We'll be back after a short break. (outro music)

(upbeat music) >> Hello, everyone; I'm John Furrier with SiliconANGLE NEWS and host of theCUBE, and welcome to our SiliconANGLE NEWS MWC NEWS UPDATE in Barcelona where MWC is the premier event for the cloud telecommunication industry, and in the news here is Red Hat, Red Hat announcing a collaboration with NVIDIA, Samsung and Arm on Efficient Open Networks. Red Hat announced updates across various fields including advanced 5G telecommunications cloud, industrial edge, artificial intelligence, and radio access networks, RAN, and Efficiency. Red Hat's enterprise Kubernetes platform, OpenShift, has added support for NVIDIA's converged accelerators and aerial SDK facilitating RAND deployments on industry standard service across hybrid and multicloud platforms. This composable infrastructure enables telecom firms to support heavier compute demands for edge computing, AI, private 5G, and more, and just also helps network operators adopt open architectures, allowing them to choose non-proprietary components from multiple suppliers. In addition to the NVIDIA collaboration, Red Hat is working with Samsung to offer a new vRAN solution for service providers to better manage their open RAN networks. They're also working with UK chip designer, Arm, to create new networking solutions for energy efficient Red Hat Open Source Kubernetes-based Efficient Power Level Exporter project, or Kepler, has been donated to the open Cloud Native Compute Foundation, allowing enterprise to better understand their cloud native workloads and power consumptions. Kepler can also help in the development of sustainable software by creating less power hungry applications. Again, Red Hat continuing to provide OpenSource, OpenRAN, and contributing an open source project to the CNCF, continuing to create innovation for developers, and, of course, Red Hat knows what, a lot about operating systems and the telco could be the next frontier. That's SiliconANGLE NEWS. I'm John Furrier; thanks for watching. (monotone music)

>> Announcer: TheCUBE's live coverage is made possible by funding from Dell Technologies, creating technologies that drive human progress. (pleasant music) >> We're back. This is Dave Vellante for our live coverage of MWC '23 SiliconANGLE's wall to wall, four-day coverage. We're here with Greg Manganello, who's from Fuijitsu. He's the global head of network services business unit at the company. And Ryan McMeniman is the director of product management for the open telecom ecosystem. We've been talking about that all week, how this ecosystem has opened up. Ryan's with Dell Technologies. Gents, welcome to theCUBE. >> Thank you, Dave. >> Thank you. >> Good to be here. >> Greg, thanks for coming on. Let's hear Fuijitsu's story. We haven't heard much at this event from Fuijitsu. I'm sure you got a big presence, but welcome to theCUBE. Tell us your angle. >> Thanks very much. So Fuijitsu, we're big O-RAN advocates, open radio access network advocates. We're one of the leading founders of that open standard. We're also members of the Open RAN Policy Coalition. I'm a board member there. We're kind of all in on OpenRAN. The reason is it gives operators choices and much more vendor diversity and therefore a lot of innovation when they build out their 5G networks. >> And so as an entry point for Dell as well, I mean obviously you guys make a lot of hay with servers and storage and other sort of hardware, but O-RAN is just this disruptive change to this industry, but it's also compute intensive. So from Dell's perspective, what are the challenges of getting customers to the carriers to adopt O-RAN? How do you de-risk it for them? >> Right, I mean O-RAN really needs to be seen as a choice, right? And that choice comes with building out an ecosystem of partners, right? Working with people like Fuijitsu and others helps us build systems that the carriers can rely upon. Otherwise, it looks like another science experiment, a sandbox, and it's really anything but that. >> So what specifically are you guys doing together? Are you doing integrations, reference architectures engineered systems, all of the above? >> Yeah, so I think it's a little bit of all of the above. So we've announced our cooperation, so the engineering teams are linked, and that we're combining our both sweet spots together from Fuijitsu's virtual CU/DU, and our OpenRAN radios, and Dell's platforms and integration capabilities. And together we're offering a pre-integrated bundle to operators to reduce that risk and kind of help overcome some of the startup obstacles by shrinking the integration cost. >> So you've got Greenfield customers, that's pretty straightforward, white sheet of paper, go, go disrupt. And then there's traditional carriers, got 4G and 5G networks, and sort of hybrid if you will, and this integration there. Where do you see the action now? I presume it's Greenfield today, but isn't it inevitable that the traditional carriers have to go open? >> It is, a couple of different ways that they need to go and they want to go might be power consumption, it might be the cloudification of their network. They're going to have different reasons for doing it. And I think we have to make sure that when we work on collaborations like we do with Fuijitsu, we have to look at all of those vectors. What is it that somebody maybe here in Europe is dealing with high gas prices, high energy prices, in the U.S. or wherever it's expansion. They're going to be different justifications for it. >> Yeah, so power must be an increasing component of the operating expense, with energy costs up, and it's a power hungry environment. So how does OpenRAN solve that problem? >> So that's a great question. So by working together we can really optimize the configurations. So on the Fuijitsu side, our radios are multi-band and highly compact and super energy efficient so that the TCO for the carrier is much, much lower. And then we've also announced on the rApp side power savings, energy savings applications, which are really sophisticated AI enabled apps that can switch off the radio based upon traffic prediction models and we can save the operator 30% on their energy bill. That's a big number. >> And that intelligence that lives in the, does it live in the RIC, is it in the brain? >> In the app right above the RIC, absolutely. >> Okay, so it's a purpose-built app to deal with that. >> It's multi-vendor app, it can sit on anybody's O-RAN system. And one of the beauties of O-RAN is there is that open architecture, so that even if Dell and Fuijitsu only sell part of the, or none of the system, an app can be selected from any vendor including Fuijitsu. So that's one of the benefits of whoever's got the best idea, the best cost performance, the best energy performance, customers can really be enabled to make the choice and continue to make choices, not just way back at RFP time, but throughout their life cycle they can keep making choices. And so that's really meaning that, hey, if we miss the buying cycle then we're closed out for 5 or 10 years. No, it's constantly being reevaluated, and that's really exciting, the whole ecosystem. But what we really want to do is make sure we partner together with key partners, Dell and Fuijitsu, such that the customer, when they do select us they see a bundle, not just every person for themselves. It de-risks it. And we get a lot of that integration headache out of the way before we launch it. >> I think that's what's different. We've been talking about how we've kind of seen this move before, in the nineties we saw the move from the mainframe vertical stack to the horizontal stack. We talked about that, but there are real differences because back then you had, I don't know, five components of the stack and there was no integration, and even converged infrastructure was kind of bolts that brought that together. And then over time it's become engineered systems. When you talk to customers, Ryan, is the conversation today mostly TCO? Is it how to get the reliability and quality of service of traditional stacks? Where's the conversation today? >> Yeah, it's the flip side of choice, which is how do you make sure you have that reliability and that security to ensure that the full stack isn't just integrated, but it lives through that whole life cycle management. What are, if you're bringing in another piece, an rApp or an xApp, how do you actually make sure that it works together as a group? Because if you don't have that kind of assurance how can you actually guarantee that O-RAN in and of itself is going to perform better than a traditional RAN system? So overcoming that barrier requires partnerships and integration activity. That is an investment on the parts of our companies, but also the operators need to look back at us and say, yeah, that work has been done, and I trust as trusted advisors for the operators that that's been done. And then we can go validate it. >> Help our audience understand it. At what point in time do you feel that from a TCO perspective there'll be parity, or in my opinion it doesn't even have to be equal. It has to be close enough. And I don't know what that close enough is because the other benefits of openness, the innovation, so there's that piece of it as the cost piece and then there is the reliability. And I would say the same thing. It's got to be, well, maybe good enough is not good enough in this world, but maybe it is for some use cases. So really my question is around adoption and what are those factors that are going to affect adoption and when can we expect them to be? >> It's a good question, Dave, and what I would say is that the closed RAN vendors are making incremental improvements. And if you think in a snapshot there might be one answer, but if you think in kind of a flow model, a river over time, our O-RAN like-minded people are on a monster innovation curve. I mean the slope of the curve is huge. So in the OpenRAN policy coalition, 60 like-minded companies working together going north, and we're saying that let's bring all the innovation together, so you can say TCO, reliability, but we're bringing the innovation curve of software and integration curve from silicon and integration from system vendors all together to really out-innovate everybody else by working together. So that's the-- >> I like that curve analogy, Greg 'cause okay, you got the ogive or S curve, and you're saying that O-RAN is entering or maybe even before the steep part of the S curve, so you're going to go hyperbolic, whereas the traditional vendors are maybe trying to squeeze a little bit more out of the lemon. >> 1, 2%, and we're making 30% or more quantum leaps at a time every innovation. So what we tell customers is you can measure right now, but if you just do the time-based competition model, as an organization, as a group of us, we're going to be ahead. >> Is it a Moore's law innovation curve or is it actually faster because you've got the combinatorial factors of silicon, certain telco technologies, other integration software. Is it actually steeper than maybe historical Moore's law? >> I think it's steeper. I don't know Ryan's opinion, but I think it's steeper because Moore's law, well-known in silicon, and it's reaching five nanometers and more and more innovations. But now we're talking about AI software and machine learning as well as the system and device vendors. So when all that's combined, what is that? So that's why I think we're at an O-RAN conference today. I'm not sure we're at MWC. >> Well, it's true. It's funny they changed the name from Mobile World Congress and that was never really meant to be a consumer show, but these things change that, right? And so I think it's appropriate MWC because we're seeing really deep enterprise technology now enter, so that's your sweet spot, isn't it? >> It really is. But I think in some ways it's the path to that price performance parity, which we saw in IT a long time ago, making its way into telecom is there, but it doesn't work unless everybody is on board. And that involves players like this and even smaller companies and innovative startups, which we really haven't seen in this space for some time. And we've been having them at the Dell booth all week long. And there's really interesting stuff like Greg said, AI, ML, optimization and efficiency, which is exciting. And that's where O-RAN can also benefit the Industry. >> And as I say, there are other differences to your advantage. You've got engineered systems or you've been through that in enterprise IT, kind of learned how to do that. But you've also got the cloud, public cloud for experimentation, so you can fail cheaply, and you got AI, right, which is, really didn't have AI in the nineties. You had it, but nobody used it. And now you're like, everybody's using ChatGPT. >> Right, but now what's exciting, and the other thing that Ryan and we are working on together is linking our labs together because it's not about the first time system integration and connecting the hoses together, and okay, there it worked, but it's about the ongoing life cycle management of all the updates and upgrades. And by using Dell's OTEL Lab and Fuijitsu's MITC lab and linking them together, now we really have a way of giving operators confidence that as we bring out the new innovations it's battle tested by two organizations. And so two logos coming together and saying, we've looked at it from our different angles and then this is battle tested. There's a lot of value there. >> I think the labs are key. >> But it's interesting, the point there is by tying labs together, there's an acknowledged skills gap as we move into this O-RAN world that operators are looking to us and probably Fuijitsu saying, help our team understand how to thrive in this new environment because we're going from closed systems to open systems where they actually again, have more choice and more ability to be flexible. >> Yeah, if you could take away that plumbing, even though they're good plumbers. All right guys, we got to go. Thanks so much for coming on theCUBE. >> Thank you much. >> It's great to have you. >> Appreciate it, Dave. >> Okay, keep it right there. Dave Vellante, Lisa Martin, and Dave Nicholson will be back from the Fira in Barcelona on theCUBE. Keep it right there. (pleasant music)

(suspenseful music) >> Welcome back everyone, this is the SiliconANGLE news report, news flash, news update. I'm John Furrier, host of theCUBE, SiliconANGLE founder and editor. Got our team in Mobile World Congress, MWC. But here's some news flash: the GSMA debuted API toolkit as AWS and Microsoft roll out their offerings to make the cloud part of the telco world. The GSMA association, which runs this program and is the most important organization in telecommunications, unveiled the GSMA Open Gateway. This is a toolkit designed for creating applications that integrate with multiple carrier networks. The technology debuted at MWC23. This is the largest trade show opened in the telco area. This Open Gateway allows carriers to support APIs created with the technology that'll interoperate with each other. That means interoperability and cloud is coming to the telecommunication carriers. That's your cell phone, that's wireless. This allows developers to move applications from one carrier to another without needing to port their code. This is a huge game-changer. This is big news, and, of course, Microsoft and AWS are pounding stories out there as well. They got 21 carriers worldwide adopted and it's created using an open-source API toolkit called CAMARA. And Amazon and AWS are jumping on the cloud bandwagon with this and driving it hard into telco. And that's the big story, and, of course, more actions happening, theCUBE is onsite for four days in Barcelona for MWC23 and keep the news flowing. Check out SiliconANGLE.com, you'll see all the news there, and, of course, theCUBE.net for the livestream. I'm John Furrier, that's the news brief. (atmospheric music)

>> Announcer: "theCUBE's" live coverage is made possible by funding from Dell Technologies, creating technologies that drive human progress. (upbeat music) >> Good evening, everyone. Live from Barcelona, Spain, it's "theCUBE". We are at Mobile World, MWC, excuse me, '23. New name this year. I'm Lisa Martin with Dave Vellante. Dave, we have had some great conversations. This is only day one of four days of coverage from "theCUBE" but one of the things that we've been talking about is disaggregation. You've wrote about it in your breaking analysis. We've been talking about it. Today is a big thing that's happening. We're going to be talking about that next. >> Yeah, open ecosystems require integration. Integration requires certification. And so, you got to have labs. We're going to talk about that and what value that brings to the community. >> Right. Please welcome Tibor Fabry-Asztalos, senior vice president of telecom systems and product engineering at Dell. >> Hi. >> And back to "theCUBE" after a couple of hours, Gautam Bhagra, vice president of partnerships at Dell. Guys, great to have you here. >> I love to be here. Thank you. >> Great to be here. >> So, day one, I'm sure lots of conversations, lots of meetings, lots of jet lag that we're all trying to get over. Talk about, Gautam, we'll start with you. Talk about the disaggregation era. What it is intended to support? What is it intended to enable? >> Yeah, so I mean, I think to be honest with you, Lisa, we spoke about this earlier also, like the whole vision with the disaggregation is to make sure our telco providers can take the benefits of having the innovation that comes along with it, right? So currently, we all know they're tied into like lock systems, which kind of constricts them in going after this whole innovative space. So, our hope is by working with our operators and our partners, we can help make that disaggregation journey a lot easier and work on some of these challenges, and make it easier for the telcos to innovate and consolidate going forward. So, we're working very closely and we talked about the community this morning. We're working very closely with Tibor and his team from an engineering perspective to help build those solutions with our partners and we're excited about the announcements we made this morning. >> When you hear challenges from this ecosystem, can you stack rank 'em? What are you hearing? Kind of what's top of mind? And so, the top three, if you would. >> Some of the challenges are just to define moving from a closed system and open system, just to making sure that the acceptance of that to see what's the value proposition is for an open system and then for the carriers to see the path going from a closed system to an open system. Of course, at the end, people realize the value at the end and speed of innovation that you're going to get all the new technologies and new features, functionality you get in an open system. But then the challenge comes with it, how you actually integrate those and then validate them, and you are to deploy them. So in a sense, that's the opportunity and also some of the challenge along the way. And that's where, as Gautam said, that's where we are also looking at playing the key role with the OTEL lab, the Open Telecom Ecosystem Lab, where we take these pieces of the open ecosystem and have combined them, validate them, and provide the pipeline to the customer. Pre-integration and then full integration into the production network. >> Those challenges, I presume, vary whether you're talking to a greenfield network operator versus somebody who's got a 40, 50 year history, a hundred-year history in the business, right? I mean migration is a big issue for them, right? Whereas the greenfield, we heard from DISH earlier, they want to drive innovation so they might be willing to sacrifice some other areas. So, is that a fair summarization and what are you hearing? >> [Tibor and Gautam] Yeah. >> Absolutely it is. I mean, that's where you see that DISH being kind of a leader in the space, as they were deploying in greenfield, they defined what the open ecosystem should look like, defined all the components of it, how you integrate them, validate them, and they were able to, well, go through it and deploy it. To your point, for an open, closed systems, as how you actually start transforming the existing network into the open one, that's going to go to a different process, right? You need to figure out how these new open systems can interrupt and work together with existing networks. So, that's one likely some of those carriers will start in an isolated area and grow from there. Deploy an open system in a rural area, for example, and then build from there. >> So, what a bank would do is they say, "Okay, we're going to write in our own abstraction layer." >> Gautam: Yeah. >> Right? "Using microservices, we're going to connect to the cloud. And we're going to, you know, put maybe some lower risk applications in the cloud first and then we're going to create our own cloud." Is there a similar dynamic here? >> Yeah, I mean, so I think you're spot on, right? Like, I think one of the things that we are seeing with the telco operators that we've spoken to is they're very risk averse. >> Yep. >> Right, they have very strong SLA requirements. They cannot go down even for a second. So, what that basically means is the innovation aspect is constrained by the risks that they perceive on any changes that you want to make on the architecture. So, the question that comes up is how do we make it easier for them to not worry about the bare minimum requirements of making sure the network's running and working while thinking about the new innovative technologies and solutions you want to build on the start. So, back to your bank example, nine years ago, no one in a bank even was thinking about like applications that will run on the cloud. Like for them, it was like a side project. They'll try and test something, see if it works, and then they'll think about cloud in the future, right? But now, core applications on banks are actually being built on public cloud. I think we see the same happening with the telco operators as well. Right now, they're understanding the move from a closed ecosystem to an open ecosystem. They understand the value proposition. On the core side, it's already happening a lot. And I think they are slowly moving there and that's where I think Tibor and team have been doing a great job working with our customers to make the transition happen. >> But there are so many permutations. >> Right. >> And integration points. How is Dell addressing that across the ecosystem? >> So, to give you an example, we talked about OTEL, which is our brand new, kind of 13,000 square feet lab that we kind of inaugurated last year based in Round Rock, Texas. >> Dave: Open Telecom. >> Dave and Tibor: Ecosystem Lab. >> Correct, great. And so, as part of that, that's a physical lab but more importantly, that's kind of a community where partners, customers come together to actually, and collaborate and work on these solutions. And as part of this, we also develop what we call the SIP, or Solution Integration Platform, to enable exactly what you just said. Making sure that we have a platform that actually can take all these various components, validate them individually, combine them, and then provide a DevOps and GitOps model, how you actually combine them, provide the BOM or SBOM, and then push that to pre-production and deployments for our customers. So, that's part of the challenge as we talked earlier. And that's how Dell and we are looking at actually enabling this basically, the validation of this disaggregated wall. >> Oh. >> Sorry, I just wanted to- >> Go ahead. >> just going to add one more point, right? So, when we look at the partners that we are working with as well in the OTEL and there are three ways we are working with them. At the bare minimum, we want to make sure that solution will run on the Dell infrastructure and the hardware, right? So, we have the self-certification process. We had a lot of good uptake on it and we are seeing a lot more come in. In fact, I had a check-in with "theCUBE" this morning in our side and it's more than a hundred plus partners already interested in going through that. Awesome. Then we have other places where we work on with partners to build reference architectures together, right? So, we want some sort of validated solution that will work together that we can take to the market. And then we also have engineered solutions that we are building with partners like the infrastructure block offering that we have taken where it's all pre-packaged, pre-built by Dell, working very closely with our partners. So, the telcos don't have to worry about deployment, integration, and everything else that comes along. >> And I presume the security supply chain is part of that- >> Yes. >> bill of materials- >> Absolutely. >> you just described. >> Yeah. >> Exactly. >> And that would include all those levels, the engineered systems, the reference architectures as well? And how do you decide like candidates, we can't do it all, right? So, it's the big markets get the engineered system, is that right? How do you adjudicate there? >> Yeah, so I mean, I think there are a couple of angles to look at it, right? I think the first and foremost is where we see the biggest demand is coming from the customers in terms of the stack they already have and where they have the pain points. >> Dave: Okay. >> Right, so this is why we are working with Red Hat and Wind River, as an example, because they are in most of the deployments that we are aware of with the customers and where we see an opportunity for Dell to partner with these partners. I think we are seeing a lot of new players also coming up the stack. And as they come up the stack and we find opportunities to co-build and co-innovate, absolutely we'll be building joint solutions with them as well. >> Where are you on, from a partnership perspective, on the strategic vision? You mentioned a number of things that have already been accomplished, quite a few. But from your journey perspective on that strategy, where are you? >> Yeah, so it's a really good question. I think we really want to be the partner of choice for all technology and services company within the telecom space. We're looking to drive the transformation in the network area, right? So, that's the vision that we have in the telecom system business from a partnership side. We have created some really good strategic partnerships with key providers, with independent software vendors, the network equipment providers. We're having some really good, strategic conversations with them. You've heard some of the announcement come out today, the work we are doing with Nokia, with Samsung, the Red Hat announcement, the Wind River, and so on and so forth. And there's a lot more in the pipeline. But more importantly, we want to grow the impact of the ecosystem. So, that's why we are launching the partner community today as well to make that happen. >> How does the lab work? Who has access to it? Can I self-certify? If I can self-certify, how do you make sure that I'm following the rules, all of the stuff- >> Sure. >> that you would- >> Absolutely. >> expect. >> So yes, you can self-certify, that's Gautam just mentioned. We already had quite a few ISVs go through that self-certification. And then there's also, there's reference architecture that's being done and other engineered solutions that we talked about earlier. And the lab is set up in a way that when needed, test lines can be isolated. So, only certain set of partners have access to it. So, it's made up in a way that enables collaborations. At the same times, it kind of enables a certain set of customers and partners working together without having challenges of having a completely open system. >> Okay, but so, if I want to do something with you guys and let's say, I am a candidate for an engineered system, so how does it work? Somebody's got to buy the equipment, right? He's got to ship it, right? There's a lot of Dell equipment involved. >> Tibor: That's correct. >> There's other third-party CapEx software, et cetera. So, you fund that, the partners fund that, it's a hybrid funding model, how does that all get done? >> So today, for obviously, we work closely with those partners. The engineered solutions we've developed so far, we've been funding it largely and as you said, is Dell infrastructure plus the cast layers and the cloud players we work with. So, we actually put those in place. We funded them, of course, with participation from them. And that's being done through those labs. >> Okay, great. So, you guys are providing that benefit to the ecosystem. Writing checks, bringing engineering talent to the table. >> Gautam: Yeah. >> Okay. >> And at the same time, I mean, it's a partnership at the end of the day, right? So, depending on the kind of partnership we are. So, if you're an ISV, it's fairly simple. Come into our labs. You don't have to worry about the infrastructure. >> Sure. >> Run it all in our labs and you're good. If you're a hardware vendor or a NEP, network equipment provider, that's where it gets interesting where they need to send us stuff, we need to send them stuff. And usually, like Tibor mentioned, it's a joint collaboration. We all put in our chips on the table and we work together. >> So, when you're having conversations with prospective partners, obviously different types of partners, Gautam, that you just talked about, what's in it for them? What's the value proposition? What does this community- >> Gautam: Yeah. >> give them from a competitive advantage standpoint? >> Yeah, so I mean there are, so the way I think about it, right? There are three things that Dell is bringing to the table. The first one is our experience and expertise on doing this transformation within the enterprise space and the learnings we have from there that we're bringing to telco now, right? So, Dell's been working with enterprises for many, many years. We are one of the big providers there. We all know what transformation enterprise went through. >> Tibor: Telco transformation, IT transformation. >> Exactly. And that's the experience we have, which we're bringing to telco. The second one is our investment, both from a go-to market side as well as the way we are working with our sales and marketing, and so on and so forth, with the engineering side. And finally, I think, and this for me is the best one, is Dell is a very partner-centric organization. >> Lisa: Yes. >> Our strategy is built around partnerships. So, that's the other piece that we bring to the table. >> Where are the labs? Oh, go ahead. >> And what's one more note on that, and also, we are talking about the engineered solutions. There's also the supply chain then because that's a basically appliance and then that goes to Dell's supply chain, which is best in class. >> Dave: And where are the labs? How many are there? >> So Round Rock, Texas is the biggest one, the 13,000 square feet. We also have extension to it. We just announced opening one in Cork for the EME market to making sure that we can cover any regulatory challenges. But also, basically any test lines that we need to cover that have latency challenges. That's why we want to make sure that we have labs in other areas as well. >> And the go-to market, is it an overlay organization, a dedicated organization? >> Yeah, so it's a bit of both as you know. But yeah, in the telecom business unit, we have a dedicated sales organization as well as an alliance organization working very closely with product and engineering to take it to market. >> Given the strength and the breadth of the partner program in the community, based on this is only day one of MWC but is there anything that you've heard today that excites you where telecom is going and where Dell and its ecosystem is going and really burgeoning? >> Oh, I've had I don't know how many meetings since 6:00 AM this morning. So, it's been an amazing event and we're just having so many great conversations with partners, our customers. And I think a lot of today is all about figuring out what our strategy and our vision is, where is each side going and what the overlap is. I think the end result's going to be follow up conversations with a lot of these partners that we are working with or will be working with soon. And then thinking about, do we build engineered solutions together? Do we go validated route? Like we going to figure that out. But I mean, for me, this is like the perfect place to come and share your vision and strategy and understand what we are trying to solve for. >> To me, what's been interesting that all the interactions and discussions are about how to get to or render open ecosystem. That's great to see that the focus is on how to make it work versus still questioning it and I think that's pretty good. >> Well, you guys launched this business I think during the pandemic, right? >> Yes. >> Yeah, that's right. >> So I mean, you could do a lot over Zoom, but as we were talking about earlier, having the face-to-face interaction, there's no replacement for it. The 6:00 AM meetings versus the 30 minute zoom calls and your body language, I mean, you learn so much that you can take away from these events. >> Absolutely. Seeing someone in 3D is so different and it's good to build that relationship and rapport as well with the folks. >> I agree. >> It is. There's so much value in the hallway conversations that you can't have over Zoom. So, I guess last question for you as we head into to day two, what are some of the things that we can be on the lookout for from Dell and its ecosystem? >> Hmm. >> Interesting. (Tibor chuckling) >> I mean, all our announcements are out. I think what you can look at for us to really be leading in this segment, taking a leadership role, and continuously looking at how we can really enable the open ecosystem and how we can provide more value there, and how we can see how we can lead in this space. >> How you can lead in this space. >> Yeah, I mean for me, I mean, day two is like, I have a lot more meetings in day two than day one so I don't know if it's like people flying in today or what, but it's amazing to just meet the partners and customers. >> So, that theme of velocity for you is going to keep going. >> Oh, it's not stopping. (Lisa laughing) That's for sure. We are excited about it. >> Well, thank you for carving out some time to talk to with us on "theCUBE" about the partner program, the open ecosystem and the commitment to growing that and enabling partners to really differentiate their services with Dell. We appreciate it. >> We appreciate it as well. >> Thank you very much. >> Thank you for having us. >> Thanks. >> Our pleasure. For our guests and for Dave Vellante, I'm Lisa Martin. You're watching "theCUBE" live in Barcelona, Spain at MWC '23. Day one of our coverage. Be right back with our final guest of the day so stick around. (upbeat music continues)

>> theCUBE's live coverage is made possible by funding from Dell Technologies, creating technologies that drive human progress. (upbeat music) >> Hey everyone, guys and gals, good to see you. It's theCUBE live in Barcelona at MWC23. Lisa Martin here with Dave Vellante on day one of four days of wall to wall CUBE coverage. Dave, today is ecosystem day. We've had some great conversations about why the open ecosystem is so important and some of the key players in it. >> Well and I'm in search of disruptors, so I'm looking for, okay, who are the network operators that are going to actually lean into the future and drive it and challenge the existing incumbents. We'll talk about that today. >> And we're going to be talking about that next. We've got one of our alumni back with us. Satish Iyer is here, the Vice President of Emerging Services at Dell. Great to have you back on the program. >> Thank you. >> Richard Leitao is with us as well, the Vice President of National Development at DISH Network. Welcome. >> Pleasure to be here. >> So, lots of, this is day one, the theme is velocity. I feel like the day has gone by so quickly. But Dell and DISH have partnered together on a multi-year initiative to build your nationwide cloud-native 5G network that's going to cover a lot of the US. Talk a little bit about that partnership, we'll get both of your perspectives. Richard, we'll start with you. >> Sure. So thank you again for having me. So DISH had the opportunity of, of going through this experience, of innovating once more. For the ones that know DISH, DISH is a company that was founded in 1980 by an innovator, a disruptor. Of course, in the course of the next 40 years, we had the opportunities of even disrupting ourselves. We launched our first satellite TV service. We then launched the first streaming, video streaming platform, disrupting our own satellite business. And since 2008, we have been acquiring Spectrum and, you know, Spectrum, the most valuable asset of a wireless operator. We felt that this was the right opportunity, having 5G , having O-RAN, and we decided to go full in in a greenfield project building national network, 5G O-RAN cloud-based network, one of a kind network in in the US and, and most of all, using O-RAN, it's very important to us, what, what it can bring and it can bring to DISH but to the entire ecosystem of, of this sector in the US. >> Satish, talk a little bit about the partnership from Dell's perspective and some of the unique advantages that Dell is delivering to DISH. >> Oh absolutely. Again, like Richard was saying, I mean the telecom network is being desegregated as we speak. You know, companies like DISH and everybody else is looking at what are the best-in-class technologies we can bring to the table. I would like to say that, you know, the cloud is coming to the telco world, right? A lot of us have seen the tremendous transformation in the cloud world in the last few years. Now, you know, DISH is a big enterprise company. As you know, you know, we are pretty strong within the cloud space and enterprise space. So what we try to work with DISH is Dell, is to bring to DISH is, you know, that notion of cloud scale and the cloud ecosystem into telecom, right? By means best-in-class infrastructure products, best-in-class software products, to allow somebody like DISH to innovate and incre, you know, basically expand and build their O-RAN network. So it's absolutely important for us as we build and get into the telecom space to work with somebody like DISH who's also disrupting as a carrier in that space. >> So it's early days for Open RAN but you've decided, "okay, we're all in". >> Yeah. >> Right? So (chuckling) you burn the bridge, as they say, "go for it". (Lisa chuckles) So when you talk to most people, they say, "okay, it's, it's, it's, it's immature." It's got to be able to get to the levels of, of the, the the hardened stack reliability. But of course it brings the advantage of flexibility and speed. Are you optimizing for one or the other right now? How are you dealing with that balance? >> Well, it, it's, it's not mature in the sense that most of operators that think about it, they have a legacy network. And in order to go full in on the O-RAN side, they need to scrap a lot of things that they have and honestly, they don't want, and it doesn't make sense. So being a greenfield operator, give us that advantage. Give us the advantage and, and desegregation, it's all about chip sets, boxes and software and the chip sets part and what I like the most in desegregation is the time of innovation. The time that we can use new chip sets coming into the market, the size of the boxes that we are using. Obviously our footprint onsite is much smaller than traditional carriers or proprietary systems. So all of that Dell has been critical in supporting us. Supporting us having the best chip sets, having the smallest footprint and, you know, the software, the cycle of innovation is much faster than in proprietary systems. So ma-, it's maturing. I'm glad to say that probably two years ago here O-RAN was more like a, a pilot type of technology. It is not, we are live, we are live for more than 30 million customers in the US and, you know, the performance levels are very similar to traditional networks. >> So you don't just buy a nationwide cloud-native 5G network out of the box, you got to- >> No, you don't. >> You got to build it. So I'm curious as to what Dell's role is in that, in that build out. >> Right? >> How and how, I'm really curious how to, how you would grade Dell but we'll get there. >> Yeah, I mean, look, yes, you don't. So I think the, the, the first and foremost is again, as, as we, Dell, comes into the telco space, one of the things we have to look at is to understand what makes Dell better in the enterprise space, right? It is the best-in-class infrastructure. It is the software ties together. As you talk about desegregated networks, it's important to understand lot of these piece parts have to still be touched together, right? So I think the integration and integration aspects becomes really key which is really Dell is very good at. So one of the things we are working really closely with DISH Tech, you know Richard was alluding to, is bringing all, not just bringing all the software and hardware assets together, but how do you continuously innovate and keep fixing things faster, right? So in the old days, traditional ways, you have a software stack, it takes you 18 months, 20 months to actually get an upgrade done. Here we have continuously CI/CD pipelines where if you want to a change done within, within a week's or within a few days, where we can actually go and test and make sure these things work. So I think a lot of the best enterprise software practices, cloud practices, combined with whatever needs for telco, actually is what makes it very unique. >> I, I saw that this started out as an FCC compliance initiative that turned into a partnership, obviously a very successful one. Richard, talk about what DISH saw in Dell that really made it the right choice, knowing you have choices, you have options. >> You know, we saw the capability to execute, but we also saw the capability to innovate. From an execution level, at the end of the day, like we were talking, we started the project in the middle of COVID, and we had the first mandate to cover 20% of the US population by June, 2022. And now we have a second one, 70% of US population by June 2023. At the beginning of the project, it was all about availability of materials, logistics, how to distribute, how to transport material. So Dell has a world-class supply chain, we felt that working with Dell through all these challenges made things easier. So from an execution perspective, whenever you need to build a network and you, you are building thousands of sites, you need to have materials, you need to distribute them and you need to install them. Dell helped us across the board. Our expectations obviously will change. We have a network, we want to cooperate with Dell in many other areas. We want to, you know, leverage on Dell ability to reach the enterprise market, to have private 5G offers. So hopefully this collaboration will endure in time and, and, you know, will change and evolve in time. >> And it's a big bet. I mean, it's not like a single, it's not like a little transaction that you guys are doing. I feel like, you know Michael Dell and Eric Carlson had dinner and they said, "okay, we're going to, we're going to partner up and this is going to be a multi-decade partnership. You had to be transparent, "Hey, we're new at this, even though we're really good at enterprise tech and so you're going to, obviously if you take a chance on us, here's what we promise you." >> Absolutely. >> And vice versa, you guys had to say, "all right, hey, we're willing to roll the dice because we're trying to change the world." So what was that dynamic like? I mean, how did, I'm curious as to this has to be a lot of different levels, engineering, senior management, board level discussions. >> You know, we felt a huge buy-in from Dell on the Open RAN concept. >> Right. >> Yeah, okay. >> And, you know, edge computing and, and the ability to get us the best product and evolve the best product, Intel is is critical in all these offerings. Intel has a great relationship with Dell. Dell helped us. Dell sponsored the DISH program and some of these suppliers, So it was definitely good to have their support and the buy-in on the O-RAN concept. We felt it from day one and we felt secure on that. >> Yeah, I mean, I, to add to that, I mean, you know DISH was very instrumental in driving, dictating and executing to our roadmap, right? They're one of the key, I mean, since they are out there and they're really turning in a way, it's important that a customer who's actually at the out front of innovation, helps us drive our own roadmap. So to Richard's point, a lot of our product roadmaps, in terms of what have you built and all that, was based on what DISH thinks as going to be market-based requirements. They also helped us a lot in the integration aspects. Like I said, one of the things about open desegregation of these networks is there is a lot of integration because, you know, there is, it's not a one, one monolithic pipe smokestack anymore. You are picking up best-in-class pieces, bits and pieces and tying it together. And it's important to understand when you tie it together things will go wrong, right? So there is a lot of learnings from an integration standpoint. Supportability, deployment, one of the things Richard talked about was supply chain, you know. Other Dell's ability to, lot of these deployments, a lot of these configs in the factory, right, in the second part. So especially a lot of these partnerships started during COVID time and as you all know, you know what we went through two years ago. So we had to make sure that lot of these things are done in one place and a factory, and not done in the field because we couldn't do a lot of these things. So there's a lot of, lot of experimentation, lot of, lot, lot of innovation on that. >> So it's 2030, what's this look like? What's the vision if we can work backwards from there? Well, a, a great network coverage to the entire country, bringing new services to enterprises, to verticals, bringing value add to customers and, you know, technology cycles, they are lasting much less than they were. I cannot even say what will happen in three years. 2030, I mean, I know, I know somebody has a vision for 2030. That's another thing. (everyone laughs) >> A lot of it is "build it and they will come", right? >> Yeah. >> I mean it really is right? You put that network in place and then innovation happens on top. That's the best thing. >> Yeah. And look and and I think the biggest people think about Open RAN in terms of cost, which, you know, you, you have some things in cost that you appreciate in Open RAN. The footprint, the the possibility to diversify suppliers and and have more competition. But for me, Open RAN is about innovation and cycles of innovation. I used to work for Nokia, I used to work for Alcatel. I knew from the generation of an idea to an execution and having a feature delivered to a certain customer, it, it took months. We want innovation to take weeks. We are innovating at the speed, speed of the cloud. We are cooperating with new players, players on the cloud and, and we expect things to happen much faster than they traditionally happen on the telecom sector. >> Move fast and break things. >> Well, we also expect that speed- >> Break and fix. (everyone laughs) >> Yeah, thank you for that. >> But speaking of speed, your customers expect that, right? They expect the service to be up 24/7. They expect to be able to access whatever content they want, whenever they want from wherever they are. So comment, Richard, in our last few minutes here of, of how the, the Dell partnership is helping DISH to really deliver the excellent customer experience that your customers just expect that you're going to deliver. >> Well by setting up the system, number one, we are leveraging on a number of services. And I mentioned the supply chain, but in reality Dell made much more than that for our 20% milestone and is supporting our 70% milestone by installing, testing, verifying most of our data center equipment. We found that this offering from Dell was really addressing some of our needs because, you know, we, we believe they know a lot in this area and they, they can provide the best advice and the best speed to market in, in terms of having this equipment. Because we are working on a time clock, we need to have this done as soon as possible. You know for the future, I hope that they can help us in driving more services. I hope they can bring all the infrastructure that we need to offer to our customers. And, you know, we keep committed to O-RAN. O-RAN is really important. We are not compromising that. And I think the future is bright for both of us. >> Yeah, and Dell learns from the experience. >> Exactly. >> Absolutely. >> There's got to be a catalyst for expanding your roadmap and vision in telecom. >> Yeah, I mean, like you said, I mean, you asked a 2030 question and I think that, you know, know six, seven years from now I think people should look at what DISH and Dell and say they were the trailblazers of make, bringing Open RAN to the market and making 5G a reality. I mean, you talk about 5G, but every 5G is on a different stages. I do think that this combination, this partnership has the best chance to be the first ones to actually have a truly Open RAN network to be successful in commercial. >> Awesome guys. Trailblazers, Dell and DISH. Well, we look forward to watching this story unfold. Thank you- >> Thank you. >> for joining Dave and me on the program today talking about what you're doing together. We appreciate it. >> Thanks for having us. >> Our pleasure. >> Thank you, bye. >> For our guests and for Dave Vellante, I'm Lisa Martin. You're watching theCUBE live from Barcelona at MWC23. We'll be back after a short break, so we'll see you soon.

(light music) >> Narrator: theCUBE's live coverage is made possible by funding from Dell Technologies. Creating technologies that drive human progress. (upbeat music) >> Welcome back to Spain everyone. Lisa Martin here with theCUBE Dave Vellante, my co-host for the next four days. We're live in Barcelona, covering MWC23. This is only day one, but I'll tell you the theme of this conference this year is velocity. And I don't know about you Dave, but this day is flying by already. This is ecosystem day. We're going to have a great discussion on the ecosystem next. >> Well we're seeing the disaggregation of the hardened telco stack, and that necessitates an ecosystem open- we're going to talk about Open RAN, we've been talking about even leading up to the show. It's a critical technology enabler and it's compulsory to have an ecosystem to support that. >> Absolutely compulsory. We've got two guests here joining us, Gautam Bhagra, Vice President partnerships at Dell, and Scott Walker, Vice President of global Telco ecosystem at Wind River. Guys, welcome to the program. >> Nice to be here. >> Thanks For having us. >> Thanks for having us. >> So you've got some news, this is day one of the conference, there's some news, Gautam, and let's start with you, unpack it. >> Yeah, well there's a lot of news, as you know, on Dell World. One of the things we are very excited to announce today is the launch of the Open Telecom Ecosystems Community. I think Dave, as you mentioned, getting into an Open RAN world is a challenge. And we know some of the challenges that our customers face. To help solve for those challenges, Dell wants to work with like-minded partners and customers to build innovative solutions, and join go-to-market. So we are launching that today. Wind River is one of our flagship partners for that, and I'm excited to be here to talk about that as well. >> Can you guys talk a little bit about the partnership, maybe a little bit about Wind River so the audience gets that context? >> Sure, absolutely, and the theme of the show, Velocity, is what this partnership is all about. We create velocity for operators if they want to adopt Open RAN, right? We simplify it. Wind River as a company has been around for 40 years. We were part of Intel at one point, and now we're independent, owned by a company called Aptiv. And with that we get another round of investment to help continue our acceleration into this market. So, the Dell partnership is about, like I said, velocity, accelerating the adoption. When we talk to operators, they have told us there are many roadblocks that they face, right? Like systems integration, operating at scale. 'Cause when you buy a traditional radio access network solution from a single supplier, it's very easy. It's works, it's been tested. When you break these components apart and disaggregate 'em, as we talked about David, it creates integration points and support issues, right? And what Dell and Wind River have done together is created a cloud infrastructure solution that could host a variety of RAN workloads, and essentially create a two layer cake. What we're, overall, what we're trying to do is create a traditional RAN experience, with the innovation agility and flexibility of Open RAN. And that's really what this partnership does. >> So these work, this workload innovation is interesting to me because you've got now developers, you know, the, you know, what's the telco developer look like, you know, is to be defined, right? I mean it's like this white sheet of paper that can create all this innovation. And to do that, you've got to have, as I said earlier, an ecosystem. But you've got now, I'm interested in your Open RAN agenda and how you see that sort of maturity model taking place. 'Cause today, you got disruptors that are going to lean right in say "Hey, yeah, that's great." The traditional carriers, they have to have a, you know, they have to migrate, they have to have a hybrid world. We know that takes time. So what's that look like in the marketplace today? >> Yeah, so I mean, I can start, right? So from a Dell's perspective, what we see in the market is yes, there is a drive towards, everyone understands the benefits of being open, right? There's the agility piece, the innovation piece. That's a no-brainer. The question is how do we get there? And I think that's where partnerships become critical to get there, right? So we've been working with partners like Wind River to build solutions that make it easier for customers to start adopting some of the foundational elements of an open network. The, one of the purposes in the agenda of building this community is to bring like-minded developers, like you said like we want those guys to come and work with the customers to create new solutions, and come up with something creative, which no one's even thought about, that accelerates your option even quicker, right? So that's exactly what we want to do as well. And that's one of the reasons why we launched the community. >> Yeah, and what we find with a lot of carriers, they are used to buying, like I said, traditional RAN solutions which are provided from a single provider like Erickson or Nokia and others, right? And we break this apart, and you cloudify that network infrastructure, there's usually a skills gap we see at the operator level, right? And so from a developer standpoint, they struggle with having the expertise in order to execute on that. Wind River helps them, working with companies like Dell, simplify that bottom portion of the stack, the infrastructure stack. So, and we lifecycle manage it, we test- we're continually testing it, and integrating it, so that the operator doesn't have to do that. In addition to that, wind River also has a history and legacy of working with different RAN vendors, both disruptors like Mavenir and Parallel Wireless, as well as traditional RAN providers like Samsung, Erickson, and others soon to be announced. So what we're doing on the northbound side is making it easy by integrating that, and on the southbound side with Dell, so that again, instead of four or five solutions that you need to put together, it's simply two. >> And you think about today how we- how you consume telco services are like there's these fixed blocks of services that you can buy, that has to change. It's more like the, the app stores. It's got to be an open marketplace, and that's where the innovation's going to come in, you know, from the developers, you know, top down maybe. I don't know, how do you see that maturity model evolving? People want to know how long it's going to take. So many questions, when will Open RAN be as reliable. Does it even have to be? You know, so many interesting dynamics going on. >> Yeah, and I think that's something we at Dell are also trying to find out, right? So we have been doing a lot of good work here to help our customers move in that direction. The work with Dish is an example of that. But I think we do understand the challenges as well in terms of getting, adopting the technologies, and adopting the innovation that's being driven by Open. So one of the agendas that we have as a company this year is to work with the community to drive this a lot further, right? We want to have customers adopt the technology more broadly with the tier one, tier two telcos globally. And our sales organizations are going to be working together with Wind Rivers to figure out who's the right set of customers to have these conversations with, so we can drop, drive, start driving this agenda a lot quicker than what we've seen historically. >> And where are you having those customer conversations? Is that at the operator level, is it higher, is it both? >> Well, all operators are deploying 5G in preparation for 6G, right? And we're all looking for those killer use cases which will drive top line revenue and not just make it a TCO discussion. And that starts at a very basic level today by doing things like integrating with Juniper, for their cloud router. So instead of at the far edge cell site, having a separate device that's doing the routing function, right? We take that and we cloudify that application, run it on the same server that's hosting the RAN applications, so you eliminate a device and reduce TCO. Now with Aptiv, which is primarily known as an automotive company, we're having lots of conversations, including with Dell and Intel and others about vehicle to vehicle communication, vehicle to anything communication. And although that's a little bit futuristic, there are shorter term use cases that, like, vehicle to vehicle accident avoidance, which are going to be much nearer term than autonomous driving, for example, which will help drive traffic and new revenue streams for operators. >> So, oh, that's, wow. So many other things (Scott laughs) that's just opened up there too. But I want to come back to, sort of, the Open RAN adoption. And I think you're right, there's a lot of questions that that still have to be determined. But my question is this, based on your knowledge so far does it have to be as hardened and reliable, obviously has to be low latency as existing networks, or can flexibility, like the cloud when it first came out, wasn't better than enterprise IT, it was just more flexible and faster, and you could rent it. And, is there a similar dynamic here where it doesn't have to replicate the hardened stack, it can bring in new benefits that drive adoption, what are your thoughts on that? >> Well there's a couple of things on that, because Wind River, as you know, where our legacy and history is in embedded devices like F-15 fighter jets, right? Or the Mars Rover or the James Web telescope, all run Wind River software. So, we know about can't fail ultra reliable systems, and operators are not letting us off the hook whatsoever. It has to be as hardened and locked down, as secure as a traditional RAN environment. Otherwise they will (indistinct). >> That's table stakes. >> That's table stakes that gets us there. And when River, with our legacy and history, and having operator experience running live commercial networks with a disaggregated stack in the tens of thousands of nodes, understand what this is like because they're running live commercial traffic with live customers. So we can't fail, right? And with that, they want their cake and eat it too, right? Which is, I want ultra reliable, I want what I have today, but I want the agility and flexibility to onboard third party apps. Like for example, this JCNR, this Juniper Cloud-Native Router. You cannot do something as simple as that on a traditional RAN Appliance. In an open ecosystem you can take that workload and onboard it because it is an open ecosystem, and that's really one of the true benefits. >> So they want the mainframe, but they want (Scott laughs) the flexibility of the developer cloud, right? >> That's right. >> They want their, have their cake eat it too and not gain weight. (group laughs) >> Yeah I mean David, I come from the public cloud world. >> We all don't want to do that. >> I used to work with a public cloud company, and nine years ago, public cloud was in the same stage, where you would go to a bank, and they would be like, we don't trust the cloud. It's not secure, it's not safe. It was the digital natives that adopted it, and that that drove the industry forward, right? And that's where the enterprises that realized that they're losing business because of all these innovative new companies that came out. That's what I saw over the last nine years in the cloud space. I think in the telco space also, something similar might happen, right? So a lot of this, I mean a lot of the new age telcos are understanding the value, are looking to innovate are adopting the open technologies, but there's still some inertia and hesitancy, for the reasons as Scott mentioned, to go there so quickly. So we just have to work through and balance between both sides. >> Yeah, well with that said, if there's still some inertia, but there's a theme of velocity, how do you help organizations balance that so they trust evolving? >> Yeah, and I think this is where our solution, like infrastructure block, is a foundational pillar to make that happen, right? So if we can take away the concerns that the organizations have in terms of security, reliability from the fundamental elements that build their infrastructure, by working with partners like Wind River, but Dell takes the ownership end-to-end to make sure that service works and we have those telco grade SLAs, then the telcos can start focusing on what's next. The applications and the customer services on the top. >> Customer service customer experience. >> You know, that's an interesting point Gautam brings up, too, because support is an issue too. We all talk about when you break these things apart, it creates integration points that you need to manage, right? But there's also, so the support aspect of it. So imagine if you will, you had one vendor, you have an outage, you call that one vendor, one necktie to choke, right, for accountability for the network. Now you have four or five vendors that you have to work. You get a lot of finger pointing. So at least at the infrastructure layer, right? Dell takes first call support for both the hardware infrastructure and the Wind River cloud infrastructure for both. And we are training and spinning them up to support, but we're always behind them of course as well. >> Can you give us a favorite customer example of- that really articulates the value of the partnership and the technologies that it's delivering to customers? >> Well, Infra Block- >> (indistinct) >> Is quite new, and we do have our first customer which is LG U plus, which was announced yesterday. Out of Korea, small customer, but a very important one. Okay, and I think they saw the value of the integrated system. They don't have the (indistinct) expertise and they're leveraging Dell and Wind River in order to make that happen. But I always also say historically before this new offering was Vodafone, right? Vodafone is a leader in Europe in terms of Open RAN, been very- Yago and Paco have been very vocal about what they're doing in Open RAN, and Dell and Wind River have been there with them every step of the way. And that's what I would say, kind of, led up to where we are today. We learned from engagements like Vodafone and I think KDDI as well. And it got us where we are today and understanding what the operators need and what the impediments are. And this directly addresses that. >> Those are two very different examples. You were talking about TCO before. I mean, so the earlier example is, that's an example to me of a disruptor. They'll take some chances, you know, maybe not as focused on TCO, of course they're concerned about it. Vodafone I would think very concerned about TCO. But I'm inferring from your comments that you're trying to get the industry, you're trying to check the TCO box, get there. And then move on to higher levels of value monetization. The TCO is going to come down to how many humans it takes to run the network, is it not, is that- >> Well a lot of, okay- >> Or is it devices- >> So the big one now, particularly with Vodafone, is energy cost, right? >> Of course, greening the network. >> Two-thirds of the energy consumption in RAN is the the Radio Access Network. Okay, the OPEX, right? So any reductions, even if they're 5% or 10%, can save tens or hundreds of millions of dollars. So we do things creatively with Dell to understand if there's a lot of traffic at the cell site and if it's not, we will change the C state or P state of the server, which basically spins it down, so it's not consuming power. But that's just at the infrastructure layer. Where this gets really powerful is working with the RAN vendors like Samsung and Ericson and others, and taking data from the traffic information there, applying algorithms to that in AI to shut it down and spin it back up as needed. 'Cause the idea is you don't want that thing powered up if there's no traffic on it. >> Well there's a sustainability, ESG, benefit to that, right? >> Yes. >> And, and it's very compute intensive. >> A hundred percent. >> Which is great for Dell. But at the same time, if you're not able to manage that power consumption, the whole thing fails. I mean it's, because there's going to be so much data, and such a intense requirement. So this is a huge issue. Okay, so Scott, you're saying that in the TCO equation, a big chunk is energy consumption? >> On the OPEX piece. Now there's also the CapEx, right? And Open RAN solutions are now, what we've heard from our customers today, are they're roughly at parity. 'Cause you can do things like repurpose servers after the useful life for a lower demand application which helps the TCO, right? Then you have situations like Juniper, where you can take, now software that runs on the same device, eliminating at a whole other device at the cell site. So we're not just taking a server and software point of view, we're taking a whole cell site point of view as it relates to both CapEx and OPEX. >> And then once that infrastructure it really gets adopted, that's when the innovation occurs. The ecosystem comes in. Developers now start to think of new applications that we haven't thought of yet. >> Gautam: Exactly. >> And that's where, that's going to force the traditional carriers to respond. They're responding, but they're doing so very carefully right now, it's understandable why. >> Yeah, and I think you're already seeing some news in the, I mean Nokia's announcement yesterday with the rebranding, et cetera. That's all positive momentum in my opinion, right? >> What'd you think of the logo? >> I love the logo. >> I liked it too. (group laughs) >> It was beautiful. >> I thought it was good. You had the connectivity down below, You need pipes, right? >> Exactly. >> But you had this sort of cool letters, and then the the pink horizon or pinkish, it was like (Scott laughs) endless opportunity. It was good, I thought it was well thought out. >> Exactly. >> Well, you pick up on an interesting point there, and what we're seeing, like advanced carriers like Dish, who has one of the true Open RAN networks, publishing APIs for programmers to build in their 5G network as part of the application. But we're also seeing the network equipment providers also enable carriers do that, 'cause carriers historically have not been advanced in that way. So there is a real recognition that in order for these networks to monetize new use cases, they need to be programmable, and they need to publish standard APIs, so you can access the 5G network capabilities through software. >> Yeah, and the problem from the carriers, there's not enough APIs that the carriers have produced yet. So that's where the ecosystem comes in, is going to >> A hundred percent >> I think there's eight APIs that are published out of the traditional carriers, which is, I mean there's got to be 8,000 for a marketplace. So that's where the open ecosystem really has the advantage. >> That's right. >> That's right. >> That's right. >> Yeah. >> So it all makes sense on paper, now you just, you got a lot of work to do. >> We got to deliver. Yeah, we launched it today. We got to get some like-minded partners and customers to come together. You'll start seeing results coming out of this hopefully soon, and we'll talk more about it over time. >> Dave: Great Awesome, thanks for sharing with us. >> Excellent. Guys, thank you for sharing, stopping by, sharing what's going on with Dell and Wind River, and why the opportunity's in it for customers and the technological evolution. We appreciate it, you'll have to come back, give us an update. >> Our pleasure, thanks for having us. (Group talks over each other) >> All right, thanks guys >> Appreciate it. >> For our guests and for Dave Vellante, I'm Lisa Martin. You're watching theCUBE, Live from MWC23 in Barcelona. theCUBE is the leader in live tech coverage. (upbeat music)

(soft electronic music) >> Hey everyone, welcome to this CUBE conversation as part of the AWS Startup Showcase, season three, episode one, featuring Astronomer. I'm your host, Lisa Martin. I'm in the CUBE's Palo Alto Studios, and today excited to be joined by a couple of guests, a couple of co-founders from Astronomer. Viraj Parekh is with us, as is Paola Peraza-Calderon. Thanks guys so much for joining us. Excited to dig into Astronomer. >> Thank you so much for having us. >> Yeah, thanks for having us. >> Yeah, and we're going to be talking about the role of data orchestration. Paola, let's go ahead and start with you. Give the audience that understanding, that context about Astronomer and what it is that you guys do. >> Mm-hmm. Yeah, absolutely. So, Astronomer is a, you know, we're a technology and software company for modern data orchestration, as you said, and we're the driving force behind Apache Airflow. The Open Source Workflow Management tool that's since been adopted by thousands and thousands of users, and we'll dig into this a little bit more. But, by data orchestration, we mean data pipeline, so generally speaking, getting data from one place to another, transforming it, running it on a schedule, and overall just building a central system that tangibly connects your entire ecosystem of data services, right. So what, that's Redshift, Snowflake, DVT, et cetera. And so tangibly, we build, we at Astronomer here build products powered by Apache Airflow for data teams and for data practitioners, so that they don't have to. So, we sell to data engineers, data scientists, data admins, and we really spend our time doing three things. So, the first is that we build Astro, our flagship cloud service that we'll talk more on. But here, we're really building experiences that make it easier for data practitioners to author, run, and scale their data pipeline footprint on the cloud. And then, we also contribute to Apache Airflow as an open source project and community. So, we cultivate the community of humans, and we also put out open source developer tools that actually make it easier for individual data practitioners to be productive in their day-to-day jobs, whether or not they actually use our product and and pay us money or not. And then of course, we also have professional services and education and all of these things around our commercial products that enable folks to use our products and use Airflow as effectively as possible. So yeah, super, super happy with everything we've done and hopefully that gives you an idea of where we're starting. >> Awesome, so when you're talking with those, Paola, those data engineers, those data scientists, how do you define data orchestration and what does it mean to them? >> Yeah, yeah, it's a good question. So, you know, if you Google data orchestration you're going to get something about an automated process for organizing silo data and making it accessible for processing and analysis. But, to your question, what does that actually mean, you know? So, if you look at it from a customer's perspective, we can share a little bit about how we at Astronomer actually do data orchestration ourselves and the problems that it solves for us. So, as many other companies out in the world do, we at Astronomer need to monitor how our own customers use our products, right? And so, we have a weekly meeting, for example, that goes through a dashboard and a dashboarding tool called Sigma where we see the number of monthly customers and how they're engaging with our product. But, to actually do that, you know, we have to use data from our application database, for example, that has behavioral data on what they're actually doing in our product. We also have data from third party API tools, like Salesforce and HubSpot, and other ways in which our customer, we actually engage with our customers and their behavior. And so, our data team internally at Astronomer uses a bunch of tools to transform and use that data, right? So, we use FiveTran, for example, to ingest. We use Snowflake as our data warehouse. We use other tools for data transformations. And even, if we at Astronomer don't do this, you can imagine a data team also using tools like, Monte Carlo for data quality, or Hightouch for Reverse ETL, or things like that. And, I think the point here is that data teams, you know, that are building data-driven organizations have a plethora of tooling to both ingest the right data and come up with the right interfaces to transform and actually, interact with that data. And so, that movement and sort of synchronization of data across your ecosystem is exactly what data orchestration is responsible for. Historically, I think, and Raj will talk more about this, historically, schedulers like KRON and Oozie or Control-M have taken a role here, but we think that Apache Airflow has sort of risen over the past few years as the defacto industry standard for writing data pipelines that do tasks, that do data jobs that interact with that ecosystem of tools in your organization. And so, beyond that sort of data pipeline unit, I think where we see it is that data acquisition is not only writing those data pipelines that move your data, but it's also all the things around it, right, so, CI/CD tool and Secrets Management, et cetera. So, a long-winded answer here, but I think that's how we talk about it here at Astronomer and how we're building our products. >> Excellent. Great context, Paola. Thank you. Viraj, let's bring you into the conversation. Every company these days has to be a data company, right? They've got to be a software company- >> Mm-hmm. >> whether it's my bank or my grocery store. So, how are companies actually doing data orchestration today, Viraj? >> Yeah, it's a great question. So, I think one thing to think about is like, on one hand, you know, data orchestration is kind of a new category that we're helping define, but on the other hand, it's something that companies have been doing forever, right? You need to get data moving to use it, you know. You've got it all in place, aggregate it, cleaning it, et cetera. So, when you look at what companies out there are doing, right. Sometimes, if you're a more kind of born in the cloud company, as we say, you'll adopt all these cloud native tooling things your cloud provider gives you. If you're a bank or another sort of institution like that, you know, you're probably juggling an even wider variety of tools. You're thinking about a cloud migration. You might have things like Kron running in one place, Uzi running somewhere else, Informatics running somewhere else, while you're also trying to move all your workloads to the cloud. So, there's quite a large spectrum of what the current state is for companies. And then, kind of like Paola was saying, Apache Airflow started in 2014, and it was actually started by Airbnb, and they put out this blog post that was like, "Hey here's how we use Apache Airflow to orchestrate our data across all their sources." And really since then, right, it's almost been a decade since then, Airflow emerged as the open source standard, and there's companies of all sorts using it. And, it's really used to tie all these tools together, especially as that number of tools increases, companies move to hybrid cloud, hybrid multi-cloud strategies, and so on and so forth. But you know, what we found is that if you go to any company, especially a larger one and you say like, "Hey, how are you doing data orchestration?" They'll probably say something like, "Well, I have five data teams, so I have eight different ways I do data orchestration." Right. This idea of data orchestration's been there but the right way to do it, kind of all the abstractions you need, the way your teams need to work together, and so on and so forth, hasn't really emerged just yet, right? It's such a quick moving space that companies have to combine what they were doing before with what their new business initiatives are today. So, you know, what we really believe here at Astronomer is Airflow is the core of how you solve data orchestration for any sort of use case, but it's not everything. You know, it needs a little more. And, that's really where our commercial product, Astro comes in, where we've built, not only the most tried and tested airflow experience out there. We do employ a majority of the Airflow Core Committers, right? So, we're kind of really deep in the project. We've also built the right things around developer tooling, observability, and reliability for customers to really rely on Astro as the heart of the way they do data orchestration, and kind of think of it as the foundational layer that helps tie together all the different tools, practices and teams large companies have to do today. >> That foundational layer is absolutely critical. You've both mentioned open source software. Paola, I want to go back to you, and just give the audience an understanding of how open source really plays into Astronomer's mission as a company, and into the technologies like Astro. >> Mm-hmm. Yeah, absolutely. I mean, we, so we at Astronomers started using Airflow and actually building our products because Airflow is open source and we were our own customers at the beginning of our company journey. And, I think the open source community is at the core of everything we do. You know, without that open source community and culture, I think, you know, we have less of a business, and so, we're super invested in continuing to cultivate and grow that. And, I think there's a couple sort of concrete ways in which we do this that personally make me really excited to do my own job. You know, for one, we do things like we organize meetups and we sponsor the Airflow Summit and there's these sort of baseline community efforts that I think are really important and that reminds you, hey, there just humans trying to do their jobs and learn and use both our technology and things that are out there and contribute to it. So, making it easier to contribute to Airflow, for example, is another one of our efforts. As Viraj mentioned, we also employ, you know, engineers internally who are on our team whose full-time job is to make the open source project better. Again, regardless of whether or not you're a customer of ours or not, we want to make sure that we continue to cultivate the Airflow project in and of itself. And, we're also building developer tooling that might not be a part of the Apache Open Source project, but is still open source. So, we have repositories in our own sort of GitHub organization, for example, with tools that individual data practitioners, again customers are not, can use to make them be more productive in their day-to-day jobs with Airflow writing Dags for the most common use cases out there. The last thing I'll say is how important I think we've found it to build sort of educational resources and documentation and best practices. Airflow can be complex. It's been around for a long time. There's a lot of really, really rich feature sets. And so, how do we enable folks to actually use those? And that comes in, you know, things like webinars, and best practices, and courses and curriculum that are free and accessible and open to the community are just some of the ways in which I think we're continuing to invest in that open source community over the next year and beyond. >> That's awesome. It sounds like open source is really core, not only to the mission, but really to the heart of the organization. Viraj, I want to go back to you and really try to understand how does Astronomer fit into the wider modern data stack and ecosystem? Like what does that look like for customers? >> Yeah, yeah. So, both in the open source and with our commercial customers, right? Folks everywhere are trying to tie together a huge variety of tools in order to start making sense of their data. And you know, I kind of think of it almost like as like a pyramid, right? At the base level, you need things like data reliability, data, sorry, data freshness, data availability, and so on and so forth, right? You just need your data to be there. (coughs) I'm sorry. You just need your data to be there, and you need to make it predictable when it's going to be there. You need to make sure it's kind of correct at the highest level, some quality checks, and so on and so forth. And oftentimes, that kind of takes the case of ELT or ETL use cases, right? Taking data from somewhere and moving it somewhere else, usually into some sort of analytics destination. And, that's really what businesses can do to just power the core parts of getting insights into how their business is going, right? How much revenue did I had? What's in my pipeline, salesforce, and so on and so forth. Once that kind of base foundation is there and people can get the data they need, how they need it, it really opens up a lot for what customers can do. You know, I think one of the trendier things out there right now is MLOps, and how do companies actually put machine learning into production? Well, when you think about it you kind of have to squint at it, right? Like, machine learning pipelines are really just any other data pipeline. They just have a certain set of needs that might not not be applicable to ELT pipelines. And, when you kind of have a common layer to tie together all the ways data can move through your organization, that's really what we're trying to make it so companies can do. And, that happens in financial services where, you know, we have some customers who take app data coming from their mobile apps, and actually run it through their fraud detection services to make sure that all the activity is not fraudulent. We have customers that will run sports betting models on our platform where they'll take data from a bunch of public APIs around different sporting events that are happening, transform all of that in a way their data scientist can build models with it, and then actually bet on sports based on that output. You know, one of my favorite use cases I like to talk about that we saw in the open source is we had there was one company whose their business was to deliver blood transfusions via drone into remote parts of the world. And, it was really cool because they took all this data from all sorts of places, right? Kind of orchestrated all the aggregation and cleaning and analysis that happened had to happen via airflow and the end product would be a drone being shot out into a real remote part of the world to actually give somebody blood who needed it there. Because it turns out for certain parts of the world, the easiest way to deliver blood to them is via drone and not via some other, some other thing. So, these kind of, all the things people do with the modern data stack is absolutely incredible, right? Like you were saying, every company's trying to be a data-driven company. What really energizes me is knowing that like, for all those best, super great tools out there that power a business, we get to be the connective tissue, or the, almost like the electricity that kind of ropes them all together and makes so people can actually do what they need to do. >> Right. Phenomenal use cases that you just described, Raj. I mean, just the variety alone of what you guys are able to do and impact is so cool. So Paola, when you're with those data engineers, those data scientists, and customer conversations, what's your pitch? Why use Astro? >> Mm-hmm. Yeah, yeah, it's a good question. And honestly, to piggyback off of Viraj, there's so many. I think what keeps me so energized is how mission critical both our product and data orchestration is, and those use cases really are incredible and we work with customers of all shapes and sizes. But, to answer your question, right, so why use Astra? Why use our commercial products? There's so many people using open source, why pay for something more than that? So, you know, the baseline for our business really is that Airflow has grown exponentially over the last five years, and like we said has become an industry standard that we're confident there's a huge opportunity for us as a company and as a team. But, we also strongly believe that being great at running Airflow, you know, doesn't make you a successful company at what you do. What makes you a successful company at what you do is building great products and solving problems and solving pin points of your own customers, right? And, that differentiating value isn't being amazing at running Airflow. That should be our job. And so, we want to abstract those customers from meaning to do things like manage Kubernetes infrastructure that you need to run Airflow, and then hiring someone full-time to go do that. Which can be hard, but again doesn't add differentiating value to your team, or to your product, or to your customers. So, folks to get away from managing that infrastructure sort of a base, a base layer. Folks who are looking for differentiating features that make their team more productive and allows them to spend less time tweaking Airflow configurations and more time working with the data that they're getting from their business. For help, getting, staying up with Airflow releases. There's a ton of, we've actually been pretty quick to come out with new Airflow features and releases, and actually just keeping up with that feature set and working strategically with a partner to help you make the most out of those feature sets is a key part of it. And, really it's, especially if you're an organization who currently is committed to using Airflow, you likely have a lot of Airflow environments across your organization. And, being able to see those Airflow environments in a single place and being able to enable your data practitioners to create Airflow environments with a click of a button, and then use, for example, our command line to develop your Airflow Dags locally and push them up to our product, and use all of the sort of testing and monitoring and observability that we have on top of our product is such a key. It sounds so simple, especially if you use Airflow, but really those things are, you know, baseline value props that we have for the customers that continue to be excited to work with us. And of course, I think we can go beyond that and there's, we have ambitions to add whole, a whole bunch of features and expand into different types of personas. >> Right? >> But really our main value prop is for companies who are committed to Airflow and want to abstract themselves and make use of some of the differentiating features that we now have at Astronomer. >> Got it. Awesome. >> Thank you. One thing, one thing I'll add to that, Paola, and I think you did a good job of saying is because every company's trying to be a data company, companies are at different parts of their journey along that, right? And we want to meet customers where they are, and take them through it to where they want to go. So, on one end you have folks who are like, "Hey, we're just building a data team here. We have a new initiative. We heard about Airflow. How do you help us out?" On the farther end, you know, we have some customers that have been using Airflow for five plus years and they're like, "Hey, this is awesome. We have 10 more teams we want to bring on. How can you help with this? How can we do more stuff in the open source with you? How can we tell our story together?" And, it's all about kind of taking this vast community of data users everywhere, seeing where they're at, and saying like, "Hey, Astro and Airflow can take you to the next place that you want to go." >> Which is incredibly- >> Mm-hmm. >> and you bring up a great point, Viraj, that every company is somewhere in a different place on that journey. And it's, and it's complex. But it sounds to me like a lot of what you're doing is really stripping away a lot of the complexity, really enabling folks to use their data as quickly as possible, so that it's relevant and they can serve up, you know, the right products and services to whoever wants what. Really incredibly important. We're almost out of time, but I'd love to get both of your perspectives on what's next for Astronomer. You give us a a great overview of what the company's doing, the value in it for customers. Paola, from your lens as one of the co-founders, what's next? >> Yeah, I mean, I think we'll continue to, I think cultivate in that open source community. I think we'll continue to build products that are open sourced as part of our ecosystem. I also think that we'll continue to build products that actually make Airflow, and getting started with Airflow, more accessible. So, sort of lowering that barrier to entry to our products, whether that's price wise or infrastructure requirement wise. I think making it easier for folks to get started and get their hands on our product is super important for us this year. And really it's about, I think, you know, for us, it's really about focused execution this year and all of the sort of core principles that we've been talking about. And continuing to invest in all of the things around our product that again, enable teams to use Airflow more effectively and efficiently. >> And that efficiency piece is, everybody needs that. Last question, Viraj, for you. What do you see in terms of the next year for Astronomer and for your role? >> Yeah, you know, I think Paola did a really good job of laying it out. So it's, it's really hard to disagree with her on anything, right? I think executing is definitely the most important thing. My own personal bias on that is I think more than ever it's important to really galvanize the community around airflow. So, we're going to be focusing on that a lot. We want to make it easier for our users to get get our product into their hands, be that open source users or commercial users. And last, but certainly not least, is we're also really excited about Data Lineage and this other open source project in our umbrella called Open Lineage to make it so that there's a standard way for users to get lineage out of different systems that they use. When we think about what's in store for data lineage and needing to audit the way automated decisions are being made. You know, I think that's just such an important thing that companies are really just starting with, and I don't think there's a solution that's emerged that kind of ties it all together. So, we think that as we kind of grow the role of Airflow, right, we can also make it so that we're helping solve, we're helping customers solve their lineage problems all in Astro, which is our kind of the best of both worlds for us. >> Awesome. I can definitely feel and hear the enthusiasm and the passion that you both bring to Astronomer, to your customers, to your team. I love it. We could keep talking more and more, so you're going to have to come back. (laughing) Viraj, Paola, thank you so much for joining me today on this showcase conversation. We really appreciate your insights and all the context that you provided about Astronomer. >> Thank you so much for having us. >> My pleasure. For my guests, I'm Lisa Martin. You're watching this Cube conversation. (soft electronic music)

(energetic music plays) >> Lisa: Hey everyone, we're so glad you're here with us. theCUBE is covering Cloud Native Security Con 23. Lisa Martin here with John Furrier. This is our second day of coverage of the event. We've had some great conversations with a lot of intellectual, exciting folks, as you know cuz you've been watching. John and I are very pleased to welcome back one of our alumni to theCUBE Taylor Dolezal joins us the head of ecosystem at CNCF. Taylor, welcome back to theCUBE. Great to see you. >> Taylor: Hey everybody, great to see you again. >> Lisa: So you are on the ground in Seattle. We're jealous. We've got fomo as John would say. Talk to us about, this is a inaugural event. We were watching Priyanka keynote yesterday. Seemed like a lot of folks there, 72 sessions a lot of content, a lot of discussions. What's the buzz, what's the reception of this inaugural event from your perspective? >> Taylor: So it's been really fantastic. I think the number one thing that has come out of this conference so far is that it's a wonderful chance to come together and for people to see one another. It's, it's been a long time that we've kind of had that opportunity to be able to interact with folks or you know, it's just a couple months since last Cube Con. But this is truly a different vibe and it's nice to have that focus on security. We're seeing a lot of folks within different organizations work through different problems and then finally have a vendor neutral space in which to talk about all of those contexts and really raise everybody up with all this new knowledge and new talking points, topics, and different facets of knowledge. >> John: Taylor, we were joking on our yesterday's summary of the keynotes, Dave Vellante and I, and the guests, Lisa and I, about the CNCF having an event operating system, you know, very decoupled highly cohesive events, strung together beautifully through the Linux Foundation, you know, kind of tongue in cheek but it was kind of fun to play on words because it's a very technical community. But the business model of, of hackers is booming. The reality of businesses booming and Cloud Native is the preferred developer environment for the future application. So the emphasis, it's very clear that this is a good move to do and targeting the community around security's a solid move. Amazon's done it with reinforce and reinvent. We see that Nice segmentation. What's the goal? Because this is really where it connects to Cube Con and Cloud Native Con as well because this shift left there too. But here it's very much about hardcore Cloud Native security. What's your positioning on this? Am I getting it right or is there is that how you guys see it? >> Taylor: Yeah, so, so that's what we've see that's what we were talking about as well as we were thinking on breaking this event out. So originally this event was a co-located event during the Cube Con windows in both Europe and North America. And then it just was so consistently popular clearly a topic that people wanted to talk, which is good that people want to talk of security. And so when we saw this massive continued kind of engagement, we wanted to break this off into its own conference. When we were going through that process internally, like you had mentioned the events team is just phenomenal to work with and they, I love how easy that they make it for us to be able to do these kinds of events too though we wanted to talk through how we differentiate this event from others and really what's changed for us and kind of how we see this space is that we didn't really see any developer-centric open source kinds of conferences. Ones that were really favoring of the developer and focus on APIs and ways in which to implement these things across all of your workloads within your organization. So that's truly what we're looking to go for here during these, all of these sessions. And that's how it's been playing out so far which has been really great to see. >> John: Taylor, I want to ask you on the ecosystem obviously the built-in ecosystem at CNCF.IO with Cube Cons Cloud Cons there, this is a new ecosystem opportunity to add more people that are security focused. Is their new entrance coming into the fold and what's been the reaction? >> Taylor: So short answer is yes we've seen a huge uptick across our vendor members and those are people that are creating Cloud offerings and selling those and working with others to implement them as well as our end users. So people consuming Cloud Native projects and using them to power core parts of their business. We have gotten a lot of data from groups like IBM and security, IBM security and put 'em on institute. They gave us a cost of data breach report that Priyanka mentioned and talked about 43% of those organizations haven't started or in the early stages of updating security practices of their cloud environments and then here on the ground, you know, talking through some best practices and really sharing those out as well. So it's, I've gotten to hear pieces and parts of different conversations and and I'm certain we'll hear more about those soon but it's just really been great to, to hear everybody with that main focus of, hey, there's more that we can do within the security space and you know, let's let's help one another out on that front just because it is such a vast landscape especially in the security space. >> Lisa: It's a huge landscape. And to your point earlier, Taylor it's everyone has the feeling that it's just so great to be back together again getting folks out of the silos that they've been operating in for such a long time. But I'd love to get some of your, whatever you can share in terms of some of the Cloud Native security projects that you've heard about over the last day or so. Anything exciting that you think is really demonstrating the value already and this inaugural event? >> Taylor: Yes, so I I've been really excited to hear a lot of, personally I've really liked the talks around EBPF. There are a whole bunch of projects utilizing that as far as runtime security goes and actually getting visibility into your workloads and being able to see things that you do expect and things that you don't expect and how to remediate those. And then I keep hearing a lot of talks about open policy agents and projects like Caverno around you know, how do we actually automate different policies or within regulated industries, how do we actually start to solve those problems? So I've heard even more around CNCF projects and other contexts that have come up but truly most of them have been around the telemetry space EBPF and, and quite a few others. So really great to, to see all those projects choosing something to bind to and making it that much more accessible for folks to implement or build on top of as well. >> John: I love the reference you guys had just the ChatGPT that was mentioned in the keynote yesterday and also the reference to Dan Kaminsky who was mentioned on the reference to DNS and Bind, lot of root level security going on. It seems like this is like a Tiger team event where all the top alpha security gurus come together, Priyanka said, experts bottoms up, developer first practitioners, that's the vibe. Is that kind of how you guys want it to be more practitioners hardcore? >> Taylor: Absolutely, absolutely. I think that when it comes to security, we really want to help. It's definitely a grassroots movement. It's great to have the people that have such a deep understanding of certain security, just bits of knowledge really when it comes to EBPF. You know, we have high surveillance here that we're talking things through. Falco is here with Sysdig and so it it's great to have all of these people here, though I have seen a good spread of folks that are, you know, most people have started their security journey but they're not where they want to be. And so people that are starting at a 2 0 1, 3 0 1, 4 0 1 level of understanding definitely seeing a good spread of knowledge on that front. But it's really, it's been great to have folks from all varying experiences, but then to have the expertise of the folks that are writing these specifications and pushing the boundaries of what's possible with security to to ensure that we're all okay and updated on that front too, I think was most notable yesterday. Like you had said >> Lisa: Sorry Taylor, when we think of security, again this is an issue that, that organizations in every industry face, nobody is immune to this. We can talk about the value in it for the hackers in terms of ransomware alone for example. But you mentioned a stat that there's a good amount of organizations that are really either early in their security journeys or haven't started yet which kind of sounds a bit scary given the landscape and how much has changed in the last couple of years. But it sounds like on the good news front it isn't too late for organizations. Talk a little bit about some of the recommendations and best practices for those organizations who are behind the curve knowing that the next attack is going to happen. >> Taylor: Absolutely. So fantastic question. I think that when it comes to understanding the fact that people need to implement security and abide by best practices, it's like I I'm sure that many of us can agree on that front, you know, hopefully all of us. But when it comes to actually implementing that, that's I agree with you completely. That's where it's really difficult to find where where do I start, where do I actually look at? And there are a couple of answers on that front. So within the CNTF ecosystem we have a technical action group security, so tag security and they have a whole bunch of working groups that cover different facets of the Cloud Native experience. So if you, for example, are concerned about runtime security or application delivery concerns within there, those are some really good places to find people knowledgeable about, that even when the conference isn't going on to get a sense of what's going on. And then TAG security has also published recently version two of their security report which is free accessible online. They can actually look through that, see what some of the recent topics are and points of focus and of interest are within our community. There are also other organizations like Open SSF which is taking a deeper dive into security. You know, initially kind of having a little bit more of an academic focus on that space and then now getting further into things around software bill materials or SBOMs supply chain security and other topics as well. >> John: Well we love you guys doing this. We think it's very big deal. We think it's important. We're starting to see events post COVID take a certain formation, you know joking aside about the event operating systems smaller events are happening, but they're tied together. And so this is key. And of course the critical need is our businesses are under siege with threats, ransomware, security challenges, that's IT moves to Cloud Native, not everyone's moved over yet. So that's in progress. So there's a huge business imperative and the hackers have a business model. So this isn't like pie in the sky, this is urgent. So, that being said, how do you see this developing from who should attend the next one or who are you looking for to be involved to get input from you guys are open arms and very diverse and great great culture there, but who are you looking for? What's the makeup persona that you hope to attract and nurture and grow? >> Taylor: Absolutely. I, think that when it comes to trying the folks that we're looking for the correct answer is it varies you know, from, you know, you're asking Priyanka or our executive director or Chris Aniszczyk our CTO, I work mostly with the end users, so for me personally I really want to see folks that are operating within our ecosystem and actually pulling these down, these projects down and using them and sharing those stories. Because there are people creating these projects and contributing to them might not always have an idea of how they're used or how they can be exploited too. A lot of these groups that I work with like Mercedes or Intuit for example, they're out there in the world using these, these projects and getting a sense for, you know, what can come up. And by sharing that knowledge I think that's what's most important across the board. So really looking for those stories to be told and novel ways in which people are trying to exploit security and attacking the supply chain, or building applications, or just things we haven't thought about. So truly that that developer archetype is really helpful to have the consumers, the end users, the folks that are actually using these. And then, yeah, and I'm truly anywhere knowledgeable about security or that wants to learn more >> John: Super important, we're here to help you scale those stories up whatever you need, send them our way. We're looking forward to getting those. This is a super important movement getting the end users who are on the front lines bringing it back into the open, building, more software, making it secure and verified, all super important. We really appreciate the mission you guys are on and again we're here to help. So send those stories our way. >> Taylor: Cool, cool. We couldn't do it without you. Yeah, just everyone contributing, everyone sharing the news. This is it's people, people is the is the true operating system of our ecosystem. So really great to, really great to share. >> Lisa: That's such a great point Taylor. It is all about people. You talked about this event having a different vibe. I wanted to learn a little bit more about that as we, as we wrap up because there's so much cultural change that's required for organizations to evolve their security practices. And so people of course are at the center of culture. Talk a little bit about why that vibe is different and do you think that yeah, it's finally time. Everyone's getting on the same page here we're understanding, we're learning from each other. >> Taylor: Yes. So, so to kind of answer that, I think it's really a focus on, there's this term shift left and shift right. And talking about where do we actually put security in the mix as it comes to people adopting this and and figuring out where things go. And if you keep shifting at left, that meaning that the developers should care more deeply about this and a deeper understanding of all of these, you know, even if it's, even if they don't understand how to put it together, maybe understand a little bit about it or how these topics and, and facets of knowledge work. But you know, like with anything, if you shift everything off to one side or the other that's also not going to be efficient. You know, you want a steady stream of knowledge flowing throughout your whole organization. So I think that that's been something that has been a really interesting topic and, and hearing people kind of navigate and try to get through, especially groups that have had, you know, deployed an app and it's going to be around for 40 years as well. So I think that those are some really interesting and unique areas of focus that I've come up on the floor and then in a couple of the sessions here >> Lisa: There's got to be that, that balance there. Last question as we wrap the last 30 seconds or so what are you excited about given the success and the momentum of day one? What excites you about what's ahead for us on day two? >> Taylor: So on day two, I'm really, it's, there's just so many sessions. I think that it was very difficult for me to, you know pick which one I was actually going to go see. There are a lot of favorites that I had kind of doubled up at each of the time so I'm honestly going to be in a lot of the sessions today. So really excited about that. Supply chain security is definitely one that's close to my heart as well but I'm really curious to see what new topics, concepts or novel ideas people have to kind of exploit things. Like one for example is a package is out there it's called Browser Test but somebody came up with one called Bowser Test. Just a very simple misname and then when you go and run that it does a fake kind of like, hey you've been exploited and just even these incorrect name attacks. That's something that is really close and dear to me as well. Kind of hearing about all these wild things people wouldn't think about in terms of exploitation. So really, really excited to hear more stories on that front and better protect myself both at home and within the Cloud Community as I stand these things up. >> Lisa: Absolutely you need to clone yourself so that you can, there's so many different sessions. There needs to be multiple versions of Taylor that you can attend and then you can all get together and talk about and learn. But that's actually a really good problem to have as we mentioned when we started 72 sessions yesterday and today. Lots of great content. Taylor, we thank you for your participation. We thank you for bringing the vibe and the buzz of the event to us and we look forward as well to hearing and seeing what day two brings us today. Thank you so much for your time Taylor. >> Taylor: Thank you for having me. >> John: All right >> Lisa: Right, for our guest and John Furrier, I'm Lisa Martin. You're watching theCube's Day two coverage of Cloud Native Security Con 23. (energetic music plays)

(lively music) >> Good afternoon cloud community and welcome back to beautiful Las Vegas, Nevada. We are here at AWS re:Invent, day four of our wall to wall coverage. It is day four in the afternoon and we are holding strong. I'm Savannah Peterson, joined by my fabulous co-host Paul Gillen. Paul, how you doing? >> I'm doing well, fine Savannah. You? >> You look great. >> We're in the home stretch here. >> Yeah, (laughs) we are. >> You still look fresh as a daisy. I don't know how you do it. >> (laughs) You're too kind. You're too kind, but I'm vain enough to take that compliment. I'm very excited about the conversation that we're going to have up next. We get to get a little DevRel and we got a little swagger on the stage. Welcome, Austin. How you doing? >> Hey, great to be here. Thanks for having me. >> Savannah: Yeah, it's our pleasure. How's the show been for you so far? >> Busy, exciting. Feels a lot like, you know it used to be right? >> Yeah, I know. A little reminiscent of the before times. >> Well, before times. >> Before we dig into the technical stuff, you're the most intriguingly dressed person we've had on the show this week. >> Austin: I feel extremely underdressed. >> Well, and we were talking about developer fancy. Talk to me a little bit about your approach to fashion. Wasn't expecting to lead with this, but I like this but I like this actually. >> No, it's actually good with my PR. You're going to love it. My approach, here's the thing, I give free advice all the time about developer relations, about things that work, have worked, and don't work in community and all that stuff. I love talking about that. Someone came up to me and said, "Where do you get your fashion tips from? What's the secret Discord server that I need to go on?" I'm like, "I will never tell." >> Oh, okay. >> This is an actual trait secret. >> Top secret. Wow! Talk about. >> If someone else starts wearing the hat, then everyone's going to be like, "There's so many white guys." Look, I'm a white guy with a beard that works in technology. >> Savannah: I've never met one of those. >> Exactly, there's none of them at all. So, you have to do something to kind stand out from the crowd a little bit. >> I love it, and it's a talk trigger. We're talking about it now. Production team loved it. It's fantastic. >> It's great. >> So your DevRel for Lightstep, in case the audience isn't familiar tell us about Lightstep. >> So Lightstep is a cloud native observability platform built at planet scale, and it powers observability at some places you've heard of like Spotify, GitHub, right? We're designed to really help developers that are working in the cloud with Kubernetes, with these huge distributed systems, understand application performance and being able to find problems, fix problems. We're also part of the ServiceNow family and as we all know ServiceNow is on a mission to help the world of work work better by powering digital transformation around IT and customer experiences for their many, many, many global 2000 customers. We love them very much. >> You know, it's a big love fest here. A lot of people have talked about the collaboration, so many companies working together. You mentioned unified observability. What is unified observability? >> So if you think about a tradition, or if you've heard about this traditional idea of observability where you have three pillars, right? You have metrics, and you have logs, and you have traces. All those three things are different data sources. They're picked up by different tools. They're analyzed by different people for different purposes. What we believe and what we're working to accomplish right now is to take all that and if you think those pillars, flip 'em on their side and think of them as streams of data. If we can take those streams and integrate them together and let you treat traces and metrics and logs not as these kind of inviolate experiences where you're kind of paging between things and going between tab A to tab B to tab C, and give you a standard way to query this, a standard way to display this, and letting you kind of find the most relevant data, then it really unlocks a lot of power for like developers and SREs to spend less time like managing tools. You know, figuring out where to build their query or what dashboard to check, more just being able to like kind of ask a question, get an answer. When you have an incident or an outage that's the most important thing, right? How quickly can you get those answers that you need so that you can restore system health? >> You don't want to be looking in multiple spots to figure out what's going on. >> Absolutely. I mean, some people hear unified observability and they go to like tool consolidation, right? That's something I hear from a lot of our users and a lot of people in re:Invent. I'll talk to SREs, they're like, "Yeah, we've got like six or seven different metrics products alone, just on services that they cover." It is important to kind of consolidate that but we're really taking it a step lower. We're looking at the data layer and trying to say, "Okay, if the data is all consistent and vendor neutral then that gives you flexibility not only from a tool consolidation perspective but also you know, a consistency, reliability. You could have a single way to deploy your observability out regardless of what cloud you're on, regardless if you're using Kubernetes or Fargate or whatever else. or even just Bare Metal or EC2 Bare Metal, right? There's been so much historically in this space. There's been a lot of silos and we think that unify diversability means that we kind of break down those silos, right? The way that we're doing it primarily is through a project called OpenTelemetry which you might have heard of. You want to talk about that in a minute? . >> Savannah: Yeah, let's talk about it right now. Why don't you tell us about it? Keep going, you're great. You're on a roll. >> I am. >> Savannah: We'll just hang out over here. >> It's day four. I'm going to ask the questions and answer the questions. (Savannah laughs) >> Yes, you're right. >> I do yeah. >> Open Tele- >> OpenTelemetry . >> Explain what OpenTelemetry is first. >> OpenTelemetry is a CNCF project, Cloud Native Computing Foundation. The goal is to make telemetry data, high quality telemetry data, a builtin feature of cloud native software right? So right now if you wanted to get logging data out, depending on your application stack, depending on your application run time, depending on language, depending on your deployment environment. You might have a lot... You have to make a lot of choices, right? About like, what am I going to use? >> Savannah: So many different choices, and the players are changing all the time. >> Exactly, and a lot of times what people will do is they'll go and they'll say like, "We have to use this commercial solution because they have a proprietary agent that can do a lot of this for us." You know? And if you look at all those proprietary agents, what you find very quickly is it's very commodified right? There's no real difference in what they're doing at a code level and what's stopped the industry from really adopting a standard way to create this logs and metrics and traces, is simply just the fact that there was no standard. And so, OpenTelemetry is that standard, right? We've got dozens of companies many of them like very, many of them here right? Competitors all the same, working together to build this open standard and implementation of telemetry data for cloud native software and really any software right? Like we support over 12 languages. We support Kubernetes, Amazon. AWS is a huge contributor actually and we're doing some really exciting stuff with them on their Amazon distribution of OpenTelemetry. So it's been extremely interesting to see it over the past like couple years go from like, "Hey, here's this like new thing that we're doing over here," to really it's a generalized acceptance that this is the way of the future. This is what we should have been doing all along. >> Yeah. >> My opinion is there is a perception out there that observability is kind of a commodity now that all the players have the same set of tools, same set of 15 or 17 or whatever tools, and that there's very little distinction in functionality. Would you agree with that? >> I don't know if I would characterize it that way entirely. I do think that there's a lot of duplicated effort that happens and part of the reason is because of this telemetry data problem, right? Because you have to wind up... You know, there's this idea of table stakes monitoring that we talk about right? Table stakes monitoring is the stuff that you're having to do every single day to kind of make sure your system is healthy to be able to... When there's an alert, gets triggered, to see why it got triggered and to go fix it, right? Because everyone has the kind of work on that table stake stuff and then build all these integrations, there's very little time for innovation on top of that right? Because you're spending all your time just like working on keeping up with technology. >> Savannah: Doing the boring stuff to make sure the wheels don't fall off, basically. >> Austin: Right? What I think the real advantage of OpenTelemetry is that it really, from like a vendor perspective, like it unblocks us from having to kind of do all this repetitive commodified work. It lets us help move that out to the community level so that... Instead of having to kind of build, your Kubernetes integration for example, you can just have like, "Hey, OpenTelemetry is integrated into Kubernetes and you just have this data now." If you are a commercial product, or if you're even someone that's interested in fixing a, scratching a particular itch about observability. It's like, "I have this specific way that I'm doing Kubernetes and I need something to help me really analyze that data. Well, I've got the data now I can just go create a project. I can create an analysis tool." I think that's what you'll see over time as OpenTelemetry promulgates out into the ecosystem is more people building interesting analysis features, people using things like machine learning to analyze this large amount, large and consistent amount of OpenTelemetry data. It's going to be a big shakeup I think, but it has the potential to really unlock a lot of value for our customers. >> Well, so you're, you're a developer relations guy. What are developers asking for right now out of their observability platforms? >> Austin: That's a great question. I think there's two things. The first is that they want it to just work. It's actually the biggest thing, right? There's so many kind of... This goes back to the tool proliferation, right? People have too much data in too many different places, and getting that data out can still be really challenging. And so, the biggest thing they want is just like, "I want something that I can... I want a lot of these questions I have to ask, answered already and OpenTelemetry is going towards it." Keep in mind it's the project's only three years old, so we obviously have room to grow but there are people running it in production and it works really well for them but there's more that we can do. The second thing is, and this isn't what really is interesting to me, is it's less what they're asking for and more what they're not asking for. Because a lot of the stuff that you see people, saying around, "Oh, we need this like very specific sort of lower level telemetry data, or we need this kind of universal thing." People really just want to be able to get questions or get questions answered, right? They want tools that kind of have these workflows where you don't have to be an expert because a lot of times this tooling gets locked behind sort of is gate kept almost in a organization where there are teams that's like, "We're responsible for this and we're going to set it up and manage it for you, and we won't let you do things outside of it because that would mess up- >> Savannah: Here's your sandbox and- >> Right, this is your sandbox you can play in and a lot of times that's really useful and very tuned for the problems that you saw yesterday, but people are looking at like what are the problems I'm going to get tomorrow? We're deploying more rapidly. We have more and more intentional change happening in the system. Like it's not enough to have this reactive sort of approach where our SRE teams are kind of like or this observability team is building a platform for us. Developers want to be able to get in and have these kind of guided workflows really that say like, "Hey, here's where you're starting at. Let's get you to an answer. Let's help you find the needle in the haystack as it were, without you having to become a master of six different or seven different tools." >> Savannah: Right, and it shouldn't be that complicated. >> It shouldn't be. I mean we've certainly... We've been working on this problem for many years now, starting with a lot of our team that started at Google and helped build Google's planet scale monitoring systems. So we have a lot of experience in the field. It's actually one... An interesting story that our founder or now general manager tells BHS, Ben Sigelman, and he told me this story once and it's like... He had built this really cool thing called Dapper that was a tracing system at Google, and people weren't using it. Because they were like, "This is really cool, but I don't know how to... but it's not relevant to me." And he's like, the one thing that we did to get to increase usage 20 times over was we just put a link. So we went to the place that people were already looking for that data and we added a link that says, "Hey, go over here and look at this." It's those simple connections being able to kind of draw people from like point A to point B, take them from familiar workflows into unfamiliar ones. You know, that's how we think about these problems right? How is this becoming a daily part of someone's usage? How is this helping them solve problems faster and really improve their their life? >> Savannah: Yeah, exactly. It comes down to quality of life. >> Warner made the case this morning that computer architecture should be inherently event-driven and that we are moving toward a world where the person matters less than what the software does, right? The software is triggering events. Does this complicate observability or simplify it? >> Austin: I think that at the end of the day, it's about getting the... Observability to me in a lot of ways is about modeling your system, right? It's about you as a developer being able to say this is what I expect the system to do and I don't think the actual application architecture really matters that much, right? Because it's about you. You are building a system, right? It can be event driven, can be support request response, can be whatever it is. You have to be able to say, "This is what I expect to... For these given inputs, this is the expected output." Now maybe there's a lot of stuff that happens in the middle that you don't really care about. And then, I talk to people here and everyone's talking about serverless right? Everyone... You can see there's obviously some amazing statistics about how many people are using Lambda, and it's very exciting. There's a lot of stuff that you shouldn't have to care about as a developer, but you should care about those inputs and outputs. You will need to have that kind of intermediate information and understand like, what was the exact path that I took through this invented system? What was the actual resources that were being used? Because even if you trust that all this magic behind the scenes is just going to work forever, sometimes it's still really useful to have that sort of lower level abstraction, to say like, "Well, this is what actually happened so that I can figure out when I deployed a new change, did I make performance better or worse?" Or being able to kind of segregate your data out and say like... Doing AB testing, right? Doing canary releases, doing all of these things that you hear about as best practices or well architected applications. Observability is at the core of all that. You need observability to kind of do any of, ask any of those higher level interesting questions. >> Savannah: We are here at ReInvent. Tell us a little bit more about the partnership with AWS. >> So I would have to actually probably refer you to someone at Service Now on that. I know that we are a partner. We collaborate with them on various things. But really at Lightstep, we're very focused on kind of the open source part of this. So we work with AWS through the OpenTelemetry project, on things like the AWS distribution for OpenTelemetry which is really... It's OpenTelemetry, again is really designed to be like a neutral standard but we know that there are going to be integrators and implementers that need to package up and bundle it in a certain way to make it easy for their end users to consume it. So that's what Amazon has done with ADOT which is the shortening for it. So it's available in several different ways. You can use it as like an SDK and drop it into your application. There's Lambda layers. If you want to get Lambda observability, you just add this extension in and then suddenly you're getting OpenTelemetry data on the other side. So it's really cool. It's been a really exciting to kind of work with people on the AWS side over the past several years. >> Savannah: It's exciting, >> I've personally seen just a lot of change. I was talking to a PM earlier this week... It's like, "Hey, two years ago I came and talked to you about OpenTelemetry and here we are today. You're still talking about OpenTelemetry." And they're like, "What changes?" Our customers have started coming to us asking for OpenTelemetry and we see the same thing now. >> Savannah: Timing is right. >> Timing is right, but we see the same thing... Even talking to ServiceNow customers who are... These very big enterprises, banks, finance, healthcare, whatever, telcos, it used to be... You'd have to go to them and say like, "Let me tell you about distributed tracing. Let me tell you about OpenTelemetry. Let me tell you about observability." Now they're coming in and saying, "Yeah, so we're standard." If you think about Kubernetes and how Kubernetes, a lot of enterprises have spent the past five-six years standardizing, and Kubernetes is a way to deploy applications or manage containerized applications. They're doing the same journey now with OpenTelemetry where they're saying, "This is what we're betting on and we want partners we want people to help us go along that way." >> I love it, and they work hand in hand in all CNCF projects as well that you're talking about. >> Austin: Right, so we're integrated into Kubernetes. You can find OpenTelemetry and things like kept in which is application standards. And over time, it'll just like promulgate out from there. So it's really exciting times. >> A bunch of CNCF projects in this area right? Prometheus. >> Prometheus, yeah. Yeah, so we inter-operate with Prometheus as well. So if you have Prometheus metrics, then OpenTelemetry can read those. It's a... OpenTelemetry metrics are like a super set of Prometheus. We've been working with the Prometheus community for quite a while to make sure that there's really good compatibility because so many people use Prometheus you know? >> Yeah. All right, so last question. New tradition for us here on theCUBE. We're looking for your 32nd hot take, Instagram reel, biggest theme, biggest buzz for those not here on the show floor. >> Oh gosh. >> Savannah: It could be for you too. It could be whatever for... >> I think the two things that are really striking to me is one serverless. Like I see... I thought people were talking about servers a lot and they were talking about it more than ever. Two, I really think it is observability right? Like we've gone from observability being kind of a niche. >> Savannah: Not that you're biased. >> Huh? >> Savannah: Not that you're biased. >> Not that I'm biased. It used to be a niche. I'd have to go niche thing where I would go and explain what this is to people and nowpeople are coming up. It's like, "Yeah, yeah, we're using OpenTelemetry." It's very cool. I've been involved with OpenTelemetry since the jump, since it was started really. It's been very exciting to see and gratifying to see like how much adoption we've gotten even in a short amount of time. >> Yeah, absolutely. It's a pretty... Yeah, it's been a lot. That was great. Perfect soundbite for us. >> Austin: Thanks, I love soundbites. >> Savannah: Yeah. Awesome. We love your hat and your soundbites equally. Thank you so much for being on the show with us today. >> Thank you for having me. >> Savannah: Hey, anytime, anytime. Will we see you in Amsterdam, speaking of KubeCon? Awesome, we'll be there. >> There's some real exciting OpenTelemetry stuff coming up for KubeCon. >> Well, we'll have to get you back on theCUBE. (talking simultaneously) Love that for us. Thank you all for tuning in two hour wall to wall coverage here, day four at AWS re:Invent in fabulous Las Vegas, Nevada, with Paul Gillin. I'm Savannah Peterson and you're watching theCUBE, the leader in high tech coverage. (lively music)

(upbeat music) (background crowd chatter) >> Hello, fantastic cloud community and welcome back to Las Vegas where we are live from the show floor at AWS re:Invent. My name is Savannah Peterson. Joined for the first time. >> Yeah, Doobie. >> VIP, I know. >> All right, let's do this. >> Thanks for having me Dave, I really appreciate it. >> I appreciate you doing all the hard work. >> Yeah. (laughs) >> You, know. >> I don't know about that. We wouldn't be here without you and all these wonderful stories that all the businesses have. >> Well, when I host with John it's hard for me to get a word in edgewise. I'm just kidding, John. (Savannah laughing) >> Shocking, I've never want that experience. >> We're like knocking each other, trying to, we're elbowing. No, it's my turn to speak, (Savannah laughing) so I'm sure we're going to work great together. I'm really looking forward to it. >> Me too Dave, I feel very lucky to be here and I feel very lucky to introduce our guest this afternoon, Clint Sharp, welcome to the show. You are with Cribl. Yeah, how does it feel to be on the show floor today? >> It's amazing to be back at any conference in person and this one is just electric, I mean, there's like a ton of people here love the booth. We're having like a lot of activity. It's been really, really exciting to be here. >> So you're a re:Ieinvent alumni? Have you been here before? You're a Cube alumni. We're going to have an OG conversation about observability, I'm looking forward to it. Just in case folks haven't been watching theCUBE for the last nine years that you've been on it. I know you've been with a few different companies during that time period. Love that you've been with us since 2013. Give us the elevator pitch for Cribl. >> Yeah, so Cribl is an observability company which we're going to talk about today. Our flagship product is a telemetry router. So it just really helps you get data into the right places. We're very specifically in the observability and security markets, so we sell to those buyers and we help them work with logs and metrics and open telemetry, lots of different types of data to get it into the right systems. >> Why did observability all of a sudden become such a hot thing? >> Savannah: Such a hot topic. >> Right, I mean it just came on the scene so quickly and now it's obviously a very crowded space. So why now, and how do you guys differentiate from the crowd? >> Yeah, sure, so I think it's really a post-digital transformation thing Dave, when I think about how I interact with organizations you know, 20 years ago when I started this business I called up American Airlines when things weren't working and now everything's all done digitally, right? I rarely ever interact with a human being and yet if I go on one of these apps and I get a bad experience, switching is just as easy as booking another airline or changing banks or changing telecommunications providers. So companies really need an ability to dive into this data at very high fidelity to understand what Dave's experience with their service or their applications are. And for the same reasons on the security side, we need very, very high fidelity data in order to understand whether malicious actors are working their way around inside of the enterprise. And so that's really changed the tooling that we had, which, in prior years, it was really hard to ask arbitrary questions of that data. You really had to deal with whatever the vendor gave you or you know, whatever the tool came with. And observability is really an evolution, allowing people to ask and answer questions of their data that they really weren't planning in advance. >> Dave: Like what kind of questions are people asking? >> Yeah sure so what is Dave's performance with this application? I see that a malicious actor has made their way on the inside of my network. Where did they go? What did they do? What files did they access? What network connections did they open? And the scale of machine data of this machine to machine communication is so much larger than what you tend to see with like human generated data, transactional data, that we really need different systems to deal with that type of data. >> And what would you say is your secret sauce? Like some people come at it, some search, some come at it from security. What's your sort of superpower as Lisa likes to say? >> Yeah, so we're a customer's first company. And so one of the things I think that we've done incredibly well is go look at the market and look for problems that are not being solved by other vendors. And so when we created this category of an observability pipeline, nobody was really marketing an observability pipeline at that time. And really the problem that customers had is they have data from a lot of different sources and they need to get it to a lot of different destinations. And a lot of that data is not particularly valuable. And in fact, one of the things that we like to say about this class of data is that it's really not valuable until it is, right? And so if I have a security breach, if I have an outage and I need to start pouring through this data suddenly the data is very, very valuable. And so customers need a lot of different places to store this data. I might want that data in a logging system. I might want that data in a metric system. I might want that data in a distributed tracing system. I might want that data in a data lake. In fact AWS just announced their security data lake product today. >> Big topic all day. >> Yeah, I mean like you can see that the industry is going in this way. People want to be able to store massively greater quantities of data than they can cost effectively do today. >> Let's talk about that just a little bit. The tension between data growth, like you said it's not valuable until it is or until it's providing context, whether that be good or bad. Let's talk about the tension between data growth and budget growth. How are you seeing that translate in your customers? >> Yeah, well so data's growing in a 25% CAGR per IDC which means we're going to have two and a half times the data in five years. And when you talk to CISOs and CIOs and you ask them, is your budget growing at a 25% CAGR, absolutely not, under no circumstances am I going to have, you know, that much more money. So what got us to 2022 is not going to get us to 2032. And so we really need different approaches for managing this data at scale. And that's where you're starting to see things like the AWS security data lake, Snowflake is moving into this space. You're seeing a lot of different people kind of moving into the database for security and observability type of data. You also have lots of other companies that are competing in broad spectrum observability, companies like Splunk or companies like Datadog. And these guys are all doing it from a data-first approach. I'm going to bring a lot of data into these platforms and give users the ability to work with that data to understand the performance and security of their applications. >> Okay, so carry that through, and you guys are different how? >> Yeah, so we are this pipeline that's sitting in the middle of all these solutions. We don't care whether your data was originally intended for some other tool. We're going to help you in a vendor-neutral way get that data wherever you need to get it. And that gives them the ability to control cost because they can put the right data in the right place. If it's data that's not going to be frequently accessed let's put it in a data lake, the cheapest place we can possibly put that data to rest. Or if I want to put it into my security tool maybe not all of the data that's coming from my vendor, my vendor has to put all the data in their records because who knows what it's going to be used for. But I only use half or a quarter of that information for security. And so what if I just put the paired down results in my more expensive storage but I kept full fidelity data somewhere else. >> Okay so you're observing the observability platforms basically, okay. >> Clint: We're routing that data. >> And then creating- >> It's meta observability. >> Right, observability pipeline. When I think a data pipeline, I think of highly specialized individuals, there's a data analyst, there's a data scientist, there's a quality engineer, you know, etc, et cetera. Do you have specific roles in your customer base that look at different parts of that pipeline and can you describe that? >> Yeah, absolutely, so one of the things I think that we do different is we sell very specifically to the security tooling vendors. And so in that case we are, or not to the vendors, but to the customers themselves. So generally they have a team inside of that organization which is managing their security tooling and their operational tooling. And so we're building tooling very specifically for them, for the types of data they work with for the volumes and scale of data that they work with. And that is giving, and no other vendor is really focusing on them. There's a lot of general purpose data people in the world and we're really the only ones that are focusing very specifically on observability and security data. >> So the announcement today, the security data lake that you were talking about, it's based on the Open Cybersecurity Framework, which I think AWS put forth, right? And said, okay, everybody come on. [Savannah] Yeah, yeah they did. >> So, right, all right. So what are your thoughts on that? You know, how does it fit with your strategy, you know. >> Yeah, so we are again a customer's first neutral company. So if OCSF gains traction, which we hope it does then we'll absolutely help customers get data into that format. But we're kind of this universal adapter so we can take data from other vendors, proprietary schemas, maybe you're coming from one of the other send vendors and you want to translate that to OCSF to use it with the security data lake. We can provide customers the ability to change and reshape that data to fit into any schema from any vendor so that we're really giving security data lake customers the ability to adapt the legacy, the stuff that they have that they can't get rid of 'cause they've had it for 10 years, 20 years and nothing inside of an enterprise ever goes away. That stuff stays forever. >> Legacy. >> Well legacy is working right? I mean somebody's actually, you know, making money on top of this thing. >> We never get rid of stuff. >> No, (laughing) we just added the toolkit. It's like all the old cell phones we have, it's everything. I mean we even do it as individual users and consumers. It's all a part of our little personal library. >> So what's happened in the field company momentum? >> Yeah let's talk trends too. >> Yeah so the company's growing crazily fast. We're north of 400 employees and we're only a hundred and something, you know, a year ago. So you can kind of see we're tripling you know, year over year. >> Savannah: Casual, especially right now in a lot of companies are feeling that scale back. >> Yeah so obviously we're keeping our eye closely on the macro conditions, but we see such a huge opportunity because we're a value player in this space that there's a real flight to value in enterprises right now. They're looking for projects that are going to pay themselves back and we've always had this value prop, we're going to come give you a lot of capabilities but we're probably going to save you money at the same time. And so that's just really resonating incredibly well with enterprises today and giving us an opportunity to continue to grow in the face of some challenging headwinds from a macro perspective. >> Well, so, okay, so people think okay, security is immune from the macro. It's not, I mean- >> Nothing, really. >> No segment is immune. CrowdStrike announced today the CrowdStrike rocket ship's still growing AR 50%, but you know, stocks down, I don't know, 20% right now after our- >> Logically doesn't make- >> Okay stuff happens, but still, you know, it's interesting, the macro, because it was like, to me it's like a slingshot, right? Everybody was like, wow, pandemic, shut down. All of a sudden, oh wow, need tech, boom. >> Savannah: Yeah, digitally transformed today. >> It's like, okay, tap the brakes. You know, when you're driving down the highway and you get that slingshotting effect and I feel like that's what's going on now. So, the premise is that the real leaders, those guys with the best tech that really understand the customers are going to, you know, get through this. What are your customers telling you in terms of, you know they're spending patterns, how they're trying to maybe consolidate vendors and how does that affect you guys? >> Yeah, for sure, I mean, I think, obviously, back to that flight to value, they're looking for vendors who are aligned with their interests. So, you know, as their budgets are getting pressure, what vendors are helping them provide the same capabilities they had to provide to the business before especially from a security perspective 'cause they're going to get cut along with everybody else. If a larger organization is trimming budgets across, security's going to get cut along with everybody else. So is IT operations. And so since they're being asked to do more with less that's you know, really where we're coming in and trying to provide them value. But certainly we're seeing a lot of pressure from IT departments, security departments all over in terms of being able to live and do more with less. >> Yeah, I mean, Celip's got a great quote today. "If you're looking to tighten your belt the cloud is the place to do it." I mean, it's probably true. >> Absolutely, elastic scalability in this, you know, our new search product is based off of AWS Lambda and it gives you truly elastic scalability. These changes in architectures are what's going to allow, it's not that cloud is cheaper, it's that cloud gives you on-demand scalability that allows you to truly control the compute that you're spending. And so as a customer of AWS, like this is giving us capabilities to offer products that are scalable and cost effective in ways that we just have not been able to do in the cloud. >> So what does that mean for the customer that you're using serverless using Lambda? What does that mean for them in terms of what they don't have to do that they maybe had to previously? >> It offers us the ability to try to charge them like a truly cloud native vendor. So in our cloud product we sell a credit model whereby which you deduct credits for usage. So if you're streaming data, you pay for gigabytes. If you're searching data then you're paying for CPU consumption, and so it allows us to charge them only for what they're consuming which means we don't have to manage a whole fleet of servers, and eventually, well we go to managing our own compute quite possibly as we start to get to scale at certain customers. But Lambda allowed us to not have to launch that way, not have to run a bunch of infrastructure. And we've been able to align our charging model with something that we think is the most customer friendly which is true consumption, pay for what you consume. >> So for example, you're saying you don't have to configure the EC2 Instance or figure out the memory sizing, you don't have to worry about any of that. You just basically say go, it figures that out and you can focus on upstream, is that right? >> Yep, and we're able to not only from a cost perspective also from a people perspective, it's allowed us velocity that we did not have before, which is we can go and prototype and build significantly faster because we're not having to worry, you know, in our mature products we use EC2 like everybody else does, right? And so as we're launching new products it's allowed us to iterate much faster and will we eventually go back to running our own compute, who knows, maybe, but it's allowed us a lot faster velocity than we were able to get before. >> I like what I've heard you discuss a lot is the agility and adaptability. We're going to be moving and evolving, choosing different providers. You're very outspoken about being vendor agnostic and I think that's actually a really unique and interesting play because we don't know what the future holds. So we're doing a new game on that note here on theCUBE, new game, new challenge, I suppose I would call it to think of this as your 30 second thought leadership highlight reel, a sizzle of the most important topic or conversation that's happening theme here at the show this year. >> Yeah, I mean, for me, as I think, as we're looking, especially like security data lake, et cetera, it's giving customers ownership of their data. And I think that once you, and I'm a big fan of this concept of open observability, and security should be the same way which is, I should not be locking you in as a vendor into my platform. Data should be stored in open formats that can be analyzed by multiple places. And you've seen this with AWS's announcement, data stored in open formats the same way other vendors store that. And so if you want to plug out AWS and you want to bring somebody else in to analyze your security lake, then great. And as we move into our analysis product, our search product, we'll be able to search data in the security data lake or data that's raw in S3. And we're really just trying to give customers back control over their future so that they don't have to maintain a relationship with a particular vendor. They're always getting the best. And that competition fuels really great product. And I'm really excited for the next 10 years of our industry as we're able to start competing on experiences and giving customers the best products, the customer wins. And I'm really excited about the customer winning. >> Yeah, so customer focused, I love it. What a great note to end on. That was very exciting, very customer focused. So, yo Clint, I have really enjoyed talking to you. Thanks. >> Thanks Clint. >> Thanks so much, it's been a pleasure being on. >> Thanks for enhancing our observability over here, I feel like I'll be looking at things a little bit differently after this conversation. And thank all of you for tuning in to our wonderful afternoon of continuous live coverage here at AWS re:Ieinvent in fabulous Las Vegas, Nevada with Dave Vellante. I'm Savannah Peterson. We're theCUBE, the leading source for high tech coverage. (bright music)

(upbeat music) >> Hello, everyone and welcome back to fabulous Las Vegas, Nevada, where we are here on the show floor at AWS re:Invent. We are theCUBE. I am Savannah Peterson, joined with John Furrier. John, afternoon, day two, we are in full swing. >> Yes. >> What's got you most excited? >> Just got lunch, got the food kicking in. No, we don't get coffee. (Savannah laughing) >> Way to bring the hype there, John. >> No, there's so many people here just in Amazon. We're back to 2019 levels of crowd. The interest levels are high. Next gen, cloud security, big part of the keynote. This next segment, I am super excited about. CUBE Alumni, going back to 2013, 10 years ago he was on theCUBE. Now, 10 years later we're at re:Invent, looking forward to this guest and it's about security, great topic. >> I don't want to delay us anymore, please welcome Mark. Mark, thank you so much for being here with us. Massive day for you and the team. I know you oversee three different units at Amazon, Inspector, Detective, and the most recently announced, Security Lake. Tell us about Amazon Security Lake. >> Well, thanks Savannah. Thanks John for having me. Well, Security Lake has been in the works for a little bit of time and it got announced today at the keynote as you heard from Adam. We're super excited because there's a couple components that are really unique and valuable to our customers within Security Lake. First and foremost, the foundation of Security Lake is an open source project we call OCFS, Open Cybersecurity Framework Schema. And what that allows is us to work with the vendor community at large in the security space and develop a language where we can all communicate around security data. And that's the language that we put into Security Data Lake. We have 60 vendors participating in developing that language and partnering within Security Lake. But it's a communal lake where customers can bring all of their security data in one place, whether it's generated in AWS, they're on-prem, or SaaS offerings or other clouds, all in one location in a language that allows analytics to take advantage of that analytics and give better outcomes for our customers. >> So Adams Selipsky big keynote, he spent all the bulk of his time on data and security. Obviously they go well together, we've talked about this in the past on theCUBE. Data is part of security, but this security's a little bit different in the sense that the global footprint of AWS makes it uniquely positioned to manage some security threats, EKS protection, a very interesting announcement, runtime layer, but looking inside and outside the containers, probably gives extra telemetry on some of those supply chains vulnerabilities. This is actually a very nuanced point. You got Guard Duty kind of taking its role. What does it mean for customers 'cause there's a lot of things in this announcement that he didn't have time to go into detail. Unpack all the specifics around what the security announcement means for customers. >> Yeah, so we announced four items in Adam's keynote today within my team. So I'll start with Guard Duty for EKS runtime. It's complimenting our existing capabilities for EKS support. So today Inspector does vulnerability assessment on EKS or container images in general. Guard Duty does detections of EKS workloads based on log data. Detective does investigation and analysis based on that log data as well. With the announcement today, we go inside the container workloads. We have more telemetry, more fine grain telemetry and ultimately we can provide better detections for our customers to analyze risks within their container workload. So we're super excited about that one. Additionally, we announced Inspector for Lambda. So Inspector, we released last year at re:Invent and we focused mostly on EKS container workloads and EC2 workloads. Single click automatically assess your environment, start generating assessments around vulnerabilities. We've added Lambda to that capability for our customers. The third announcement we made was Macy sampling. So Macy has been around for a while in delivering a lot of value for customers providing information around their sensitive data within S3 buckets. What we found is many customers want to go and characterize all of the data in their buckets, but some just want to know is there any sensitive data in my bucket? And the sampling feature allows the customer to find out their sensitive data in the bucket, but we don't have to go through and do all of the analysis to tell you exactly what's in there. >> Unstructured and structured data. Any data? >> Correct, yeah. >> And the fourth? >> The fourth, Security Data Lake? (John and Savannah laughing) Yes. >> Okay, ocean theme. data lake. >> Very complimentary to all of our services, but the unique value in the data lake is that we put the information in the customer's control. It's in their S3 bucket, they get to decide who gets access to it. We've heard from customers over the years that really have two options around gathering large scale data for security analysis. One is we roll our own and we're security engineers, we're not data engineers. It's really hard for them to build these distributed systems at scale. The second one is we can pick a vendor or a partner, but we're locked in and it's in their schemer and their format and we're there for a long period of time. With Security Data Lake, they get the best of both worlds. We run the infrastructure at scale for them, put the data in their control and they get to decide what use case, what partner, what tool gives them the most value on top of their data. >> Is that always a good thing to give the customers too much control? 'Cause you know the old expression, you give 'em a knife they play with and they they can cut themselves, I mean. But no, seriously, 'cause what's the provisions around that? Because control was big part of the governance, how do you manage the security? How does the customer worry about, if I have too much control, someone makes a mistake? >> Well, what we finding out today is that many customers have realized that some of their data has been replicated seven times, 10 times, not necessarily maliciously, but because they have multiple vendors that utilize that data to give them different use cases and outcomes. It becomes costly and unwieldy to figure out where all that data is. So by centralizing it, the control is really around who has access to the data. Now, ultimately customers want to make those decisions and we've made it simple to aggregate this data in a single place. They can develop a home region if they want, where all the data flows into one region, they can distribute it globally. >> They're in charge. >> They're in charge. But the controls are mostly in the hands of the data governance person in the company, not the security analyst. >> So I'm really curious, you mentioned there's 60 AWS partner companies that have collaborated on the Security lake. Can you tell us a little bit about the process? How long does it take? Are people self-selecting to contribute to these projects? Are you cherry picking? What does that look like? >> It's a great question. There's three levels of collaboration. One is around the open source project that we announced at Black Hat early in this year called OCSF. And that collaboration is we've asked the vendor community to work with us to build a schema that is universally acceptable to security practitioners, not vendor specific and we've asked. >> Savannah: I'm sorry to interrupt you, but is this a first of its kind? >> There's multiple schemes out there developed by multiple parties. They've been around for multiple years, but they've been built by a single vendor. >> Yeah, that's what I'm drill in on a little bit. It sounds like the first we had this level of collaboration. >> There's been collaborations around them, but in a handful of companies. We've really gone to a broad set of collaborators to really get it right. And they're focused around areas of expertise that they have knowledge in. So the EDR vendors, they're focused around the scheme around EDR. The firewall vendors are focused around that area. Certainly the cloud vendors are in their scope. So that's level one of collaboration and that gets us the level playing field and the language in which we'll communicate. >> Savannah: Which is so important. >> Super foundational. Then the second area is around producers and subscribers. So many companies generate valuable security data from the tools that they run. And we call those producers the publishers and they publish the data into Security Lake within that OCSF format. Some of them are in the form of findings, many of them in the form of raw telemetry. Then the second one is in the subscriber side and those are usually analytic vendors, SIM vendors, XDR vendors that take advantage of the logs in one place and generate analytic driven outcomes on top of that, use cases, if you will, that highlight security risks or issues for customers. >> Savannah: Yeah, cool. >> What's the big customer focus when you start looking at Security Lakes? How do you see that planning out? You said there's a collaboration, love the open source vibe on that piece, what data goes in there? What's sharing? 'Cause a big part of the keynote I heard today was, I heard clean rooms, I've cut my antenna up. I'd love to hear that. That means there's an implied sharing aspect. The security industry's been sharing data for a while. What kind of data's in that lake? Give us an example, take us through. >> Well, this a number of sources within AWS, as customers run their workloads in AWS. We've identified somewhere around 25 sources that will be natively single click into Amazon Security Lake. We were announcing nine of them. They're traditional network logs, BBC flow, cloud trail logs, firewall logs, findings that are generated across AWS, EKS audit logs, RDS data logs. So anything that customers run workloads on will be available in data lake. But that's not limited to AWS. Customers run their environments hybridly, they have SaaS applications, they use other clouds in some instances. So it's open to bring all that data in. Customers can vector it all into this one single location if they decide, we make it pretty simple for them to do that. Again, in the same format where outcomes can be generated quickly and easily. >> Can you use the data lake off on premise or it has to be in an S3 in Amazon Cloud? >> Today it's in S3 in Amazon. If we hear customers looking to do something different, as you guys know, we tend to focus on our customers and what they want us to do, but they've been pretty happy about what we've decided to do in this first iteration. >> So we got a story about Silicon Angle. Obviously the ingestion is a big part of it. The reporters are jumping in, but the 53rd party sources is a pretty big number. Is that coming from the OCSF or is that just in general? Who's involved? >> Yeah, OCSF is the big part of that and we have a list of probably 50 more that want to join in part of this. >> The other big names are there, Cisco, CrowdStrike, Peloton Networks, all the big dogs are in there. >> All big partners of AWS, anyway, so it was an easy conversation and in most cases when we started having the conversation, they were like, "Wow, this has really been needed for a long time." And given our breadth of partners and where we sit from our customers perspective in the center of their cloud journey that they've looked at us and said, "You guys, we applaud you for driving this." >> So Mark, take us through the conversations you're having with the customers at re:Inforce. We saw a lot of meetings happening. It was great to be back face to face. You guys have been doing a lot of customer conversation, security Data Lake came out of that. What was the driving force behind it? What were some of the key concerns? What were the challenges and what's now the opportunity that's different? >> We heard from our customers in general. One, it's too hard for us to get all the data we need in a single place, whether through AWS, the industry in general, it's just too hard. We don't have those resources to data wrangle that data. We don't know how to pick schema. There's multiple ones out there. Tell us how we would do that. So these three challenges came out front and center for every customer. And mostly what they said is our resources are limited and we want to focus those resources on security outcomes and we have security engines. We don't want to focus them on data wrangling and large scale distributed systems. Can you help us solve that problem? And it came out loud and clear from almost every customer conversation we had. And that's where we took the challenge. We said, "Okay, let's build this data layer." And then on top of that we have services like Detective and Guard Duty, we'll take advantage of it as well. But we also have a myriad of ISV third parties that will also sit on top of that data and render out. >> What's interesting, I want to get your reaction. I know we don't have much time left, but I want to get your thoughts. When I see Security Data Lake, which is awesome by the way, love the focus, love how you guys put that together. It makes me realize the big thing in re:Invent this year is this idea of specialized solutions. You got instances for this and that, use cases that require certain kind of performance. You got the data pillars that Adam laid out. Are we going to start seeing more specialized data lakes? I mean, we have a video data lake. Is there going to be a FinTech data lake? Is there going to be, I mean, you got the Great Lakes kind of going on here, what is going on with these lakes? I mean, is that a trend that Amazon sees or customers are aligning to? >> Yeah, we have a couple lakes already. We have a healthcare lake and a financial lake and now we have a security lake. Foundationally we have Lake Formation, which is the tool that anyone can build a lake. And most of our lakes run on top of Lake Foundation, but specialize. And the specialization is in the data aggregation, normalization, enridgement, that is unique for those use cases. And I think you'll see more and more. >> John: So that's a feature, not a bug. >> It's a feature, it's a big feature. The customers have ask for it. >> So they want roll their own specialized, purpose-built data thing, lake? They can do it. >> And customer don't want to combine healthcare information with security information. They have different use cases and segmentation of the information that they care about. So I think you'll see more. Now, I also think that you'll see where there are adjacencies that those lakes will expand into other use cases in some cases too. >> And that's where the right tools comes in, as he was talking about this ETL zero, ETL feature. >> It be like an 80, 20 rule. So if 80% of the data is shared for different use cases, you can see how those lakes would expand to fulfill multiple use cases. >> All right, you think he's ready for the challenge? Look, we were on the same page. >> Okay, we have a new challenge, go ahead. >> So think of it as an Instagram Reel, sort of your hot take, your thought leadership moment, the clip we're going to come back to and reference your brilliance 10 years down the road. I mean, you've been a CUBE veteran, now CUBE alumni for almost 10 years, in just a few weeks it'll be that. What do you think is, and I suspect, I think I might know your answer to this, so feel free to be robust in this. But what do you think is the biggest story, key takeaway from the show this year? >> We're democratizing security data within Security Data Lake for sure. >> Well said, you are our shortest answer so far on theCUBE and I absolutely love and respect that. Mark, it has been a pleasure chatting with you and congratulations, again, on the huge announcement. This is such an exciting day for you all. >> Thank you Savannah, thank you John, pleasure to be here. >> John: Thank you, great to have you. >> We look forward to 10 more years of having you. >> Well, maybe we don't have to wait 10 years. (laughs) >> Well, more years, in another time. >> I have a feeling it'll be a lot of security content this year. >> Yeah, pretty hot theme >> Very hot theme. >> Pretty odd theme for us. >> Of course, re:Inforce will be there this year again, coming up 2023. >> All the res. >> Yep, all the res. >> Love that. >> We look forward to see you there. >> All right, thanks, Mark. >> Speaking of res, you're the reason we are here. Thank you all for tuning in to today's live coverage from AWS re:Invent. We are in Las Vegas, Nevada with John Furrier. My name is Savannah Peterson. We are theCUBE and we are the leading source for high tech coverage. (upbeat music)

(gentle music) >> Good morning from Las Vegas. It's theCUBE live at AWS Reinvent 2022 with tons of thousands of people today. Really kicks off the event. Big keynote that I think is probably just wrapping up. Lisa Martin here with Dave Vellante. Dave, this is going to be an action packed week on theCUBE no doubt. We talked with so many different companies. Every company's a software company these days but we're also seeing a lot of companies leaving software that can help them operate more efficiently in the background. >> Yeah, well some things haven't changed at Reinvent. A lot of people here, you know, back to 2019 highs and I think we exceeded those two hour keynotes. Peter DeSantis last night talking about new Graviton instances and then Adam Selipsky doing the typical two hour keynote. But what was different he was a lot more poetic than we used to hear from Andy Jassy, right? He was talking about the universe as an analogy for data. >> I loved that. >> Talked about ocean exploration as for the security piece and then exploring into the Antarctic for, you know, better chips, you know? So yeah, I think he did a good job there. I think a lot of people might not love it but I thought it was very well done. >> I thought so too. We're having kicking off a great day of live content for you all day today. We've got Eleanor Dorfman joining us, the sales leader at Retool. Eleanor, welcome to theCUBE. It's great to have you. >> Thank you so much for having me. >> So let's talk a little bit about Retool. I was looking on your LinkedIn page. I love the tagline, build custom internal tools best. >> Eleanor: Yep. >> Talk to us a little bit about the company you recently raised, series C two. Give us the backstory. >> Yeah, so the company was founded in 2017 by two co-founders who are best friends from college. They actually set out to build a FinTech company, a payments company. And as they were building that, they needed to build a ton of custom operations software that goes with that. If you're going to be managing people's money, you need to be able to do refunds. You need to be able to look up accounts, you need to be able to detect fraud, you need to do know your customer operations. And as they were building the sort of operations software that supports the business, they realized that there were patterns to all of it and that the same components were used at and again. And had the insight that that was actually probably a better direction to go in than recreating Venmo, which was I think the original idea. And that actually this is a problem every company has because every company needs operations engineering and operations software to run their business. And so they pivoted and started building Retool which is a platform for building custom operations software or internal tools. >> Dave: Good pivot. >> In hindsight, actually probably in the moment as well, was a good pivot. >> But you know, when you talk about some of those things, refunds, fraud, you know, KYC, you know, you think of operations software, you think of it as just internal, but all those things are customer facing. >> Eleanor: Yep. >> Right so, are we seeing as sort of this new era? Is that a trend that you guys, your founders saw that hey, these internal operations can be pointed at customers to support what, a better customer service, maybe even generate revenue, subscriptions? >> I think it's a direction we're actually heading now but we're just starting to scratch the surface of that. The focus for the last five years has very much been on this operations software and sort of changing the economics of developing it and making it easy and fast to productize workflows that were previously being done in spreadsheets or hacky workarounds and make it easier for companies to prioritize those so they can run their business more efficiently. >> And where are you having your customer conversations these days? Thinking of operations software in the background, but to Dave's point, it ends up being part of the customer experience. So where are you having your customer conversations, target audience, who's that persona? >> Mainly developers. So we're working almost exclusively with developer teams who have backlogs and backlogs of internal tools requests to build that sales teams are building manual forecasts. Support teams are in 19 different tools. Their supply chain teams are using seven different spreadsheets to do demand forecasting or freight forwarding or things like that. But they've never been able to be prioritized to the top of the list because customer facing software, revenue generating software, always takes prioritization. And in this economic environment, which is challenging for many companies right now, it's important to be able to do more with less and maximize the productivity especially of high value employees like engineers and developers. >> So what would you say the biggest business outcomes are? If the developer is really the focus, productivity is the- >> Productivity. It's for both, I would say. Developer productivity and being able to maximize your sort of R and D and maximize the productivity of your engineers and take away some of the very boring parts of the job. But, so I would say developer productivity, but then also the tools and the software that they're building are very powerful for end users. So I would say efficiency and productivity across your business. >> Across the business. >> I mean historically, you know, operations is where we focused IT and code. How much of the code out there is dedicated to sort of operations versus that customer facing? >> So I think it would actually be, it's kind of surprising. We have run a few surveys on this sort of, we call them the state of engineering time, and focusing on what developers are spending their time on. And a third of all code that is being written today is actually for this internal operations software. >> Interesting. And do you guys have news at the show? Are you announcing anything interesting or? >> Yeah, so our focus historically, you sort of gave away with one of your early questions, but our focus has always been on this operations, this building web applications on building UIs on top of databases and APIs and doing that incredibly fast and being able to do it all in one place and integrate with as any data source that you need. We abstract away access authentication deployment and you build applications for your internal teams. But recently, we've launched two new products. We're actually supporting more external use cases and more customer facing use cases as well as automating CRON jobs, ETL jobs alerting with the new retail workflows product. So we're expanding the scope of operations software from web applications to also internal operations like CRON jobs and ETL jobs. >> Explain that. Explain the scourge of CRON jobs to the audience. >> Yeah, so operations software businesses run on operations software. It's interesting, zooming out, it's actually something you said earlier as well. Every company has become a software company. So when you think about software, you tend to think about here. Very cool software that people are selling. And software that you use as a consumer. But Coca-Cola for example, has hundreds of software engineers that are building tools to make the business run for forecasting, for demand gen, for their warehouse distribution and monitoring inventory. And there's two types of that. There's the applications that they build and then the operations that have to run behind that. Maybe a workflow that is detecting how many bottles of Coca-Cola are in every warehouse and sending a notification to the right person when they're out or when they, a refill is very strong, but you know when you need a refill. So it does that, it takes those tasks, those jobs that run in the background and enables you to customize them and build them very rapidly in a code first way. >> So some of the notes that you guys provided say that there's over 500 million software apps that are going to be built in the next few years alone. That's tremendous. How much of that is operation software? >> I mean I think at least a third of that, if not more. To the point where every company is being forced to maximize their resources today and operational efficiency is the way to do that. And so it can become a competitive advantage when you can take the things that humans are doing in spreadsheets with 19 open tabs and automate that. That saves hours a day. That's a significant, significant driver of efficiency and productivity for a business >> It does, and there's direct correlation to the customer experience. The use experience. >> Almost certainly. When you think about building support tooling, I was web chat, chatting on the with Gogo wifi support on my flight over here and they asked for my order number and I sent it and they looked up my account and that's a custom piece of software they were using to look up the account, create a new account for me, and restore my second wifi purchase. And so when you think about it, you're actually, even just as a consumer, interacting with this custom software on the day time. And that's because that's what companies use to have a good customer experience and have an efficient business. >> And what's the relationship with AWS? You guys started, I think you said 2017, so you obviously started in the cloud, but I'm particularly interested in from a seller perspective, what that's like. Working with Amazon, how's that affected your business? >> Yeah, I mean so we're built on AWS, so we're customers and big fans. And obviously like from a selling perspective, we have a ton of integrations with AWS so we're able to integrate directly into all the different AWS products that people are using for databases, for data warehouses, for deployment configurations, for monitoring, for security, for observability, we can basically fit into your existing AWS stack in order to make it as seamless integration with your software so that building in Retool is just as seamless as building it on your own, just much, much faster. >> So in your world, I know you wanted to but, in your world is it more analytics? is it more transactional, sort of? Is it both? >> It's all of the above. And I think what's, over Thanksgiving, I was asked a lot to explain what Retool did with people who were like, we just got our first iPhone. And so I tried to explain with an example because I have yet to stumble on the perfect metaphor. But the example I typically use is DoorDash is a customer of ours. And for about three years, and three years ago, they had a problem. They had no way of turning off delivery in certain zip codes during storms. Which as someone who has had orders canceled during a storm, it's an incredibly frustrating experience. And the way it worked is that they had operation team members manually submitting requests to engineers to say there's a storm in this zip code and an engineer would run a manual task. This didn't scale with Doordash as they were opening in new countries all over the world that have very different weather patterns. And so they looked, they had one, they were sort of confronted with a choice. They could buy a piece of software out of the box. There is not a startup that does this yet. They could build it by hand, which would mean scoping the requirements designing a UI, building authentication, building access controls, putting it into a, putting it into a sprint, assigning an engineer. This would've taken months and months. And then it would take just as long to iterate on it or they could use Retool. So they used Retool, they built this app, it saved, I think they were saying up to two years of engineering time for this one application because of how quickly it was. And since then they've built, I think 50 or 60 more automating away other tasks like that that were one out of spreadsheets or in Jira or in Slack notifications or an email saying, "Hey, could you please do this thing? There's a storm." And so now they use us for dozens and dozens of operations like that. >> A lot of automation and of course a lot of customer delight on the other end of the spectrum as you were talking about. It is frustrating when you don't get that order but it's also the company needs to be able to have the the tools in place to automate to be able to react quickly. >> Eleanor: Exactly. >> Because the consumers are, as we know, quite demanding. I wanted to ask you, I mentioned the tagline in the beginning, build custom internal tools fast. You just gave us a great example of DoorDash. Huge business outcomes they're achieving but how fast are we talking? How fast can the average developer build these internal tools? >> Well, we've been doing a fun thing at our booth where we ask people what a problem is and build a tool for them while we're there. So for something lightweight, you can build it in 10 minutes. For something a little more complex, it can take up to a few weeks depending on what the requirements are. But we all have people who will be on a call with us introducing them to our software for the first time and they'll start telling us about their problems and in the background we'll be building it and then at the end we're like, is this what you meant? And they're like, we'd like to add that to our cart. And obviously, it's a platform so you can't do that. But we've been able to build applications on a call before while people are telling us what they need. >> So fast is fast. >> I would say very fast, yeah. >> Now how do you price? >> Right now, we have a couple different plans. We actually have a motion where you can sign up on our website and get started. So we have a free plan, we've got plans for startups, and then we've got plans all the way up to the enterprise. >> Right. And that's a subscription pricing kind of thing? >> Subscription model, yes. >> So I get a subscription to the platform and then what? Is there also a consumption component? >> Exactly. So there's a consumption component as well. So there's access to the platform and then you can build as many applications as you need. Or build as many workflows. >> When you're having customer conversations with prospects, what do you define as Retool's superpowers? You're the sales leader. What are some of those key superpowers that you think really differentiate Retool? >> I do think, well, the sales team first and foremost, but that's not a fair answer. I would say that people are a bit differentiator though. We have a lot of very talented people who are have a ton of domain expertise and care a ton about the customer outcomes, which I do actually think is a little more rare than it should be. But we're one of the only products out there that's built with a developer first mindset, a varied code first mindset, built to integrate with your software development life cycle but also built with the security and robustness that enterprise companies require. So it's able to take an enterprise grade software with a developer first approach while still having a ton of agility and nimbleness which is what people are really craving as the earth keeps moving around them. So I would say that's something that really sets us apart from the field. >> And then talk about some of the what developers are saying, some of the feedback, some of the responses, and maybe even, I know we're just on day one of the show, but any feedback from the booth so far? >> We've had a few people swing by our booth and show us their Retool apps, which is incredibly cool. That's my absolute favorite thing is encountering a Retool application in the wild which happens a lot more than I would've thought, which I shouldn't say, but is incredibly rewarding. But people love it. It's the reason I joined is I'd never heard someone have a product that customers talked about the way they talk about Retool because Retool enables them to do things. For some folks who use it, it enables them to do something they previously couldn't do. So it gives them super powers in their job and to triple their impact. And then for others, it just makes things so fast. And it's a very delightful experience. It's very much built by developers, for developers. And so it's built with a developer's first mindset. And so I think it's quite fun to build in Retool. Even I can build and Retool, though not well. And then it's extremely impactful and people are able to really impact their business and delight their coworkers which I think can be really meaningful. >> Absolutely. Delighting the coworkers directly relates to delighting the customers. >> Eleanor: Exactly. >> Those customer experience, employee experience, they're like this. >> Eleanor: Exactly. >> They go hand in hand and the employee experience has to be outstanding to be able to delight those customers, to reduce churn, to increase revenue- >> Eleanor: Exactly. >> And for brand reputation. >> And it also, I think there is something as someone who is customer facing, when my coworkers and developers I work with build tools that enable me to do my job better and feel better about my own performance and my ability to impact the customer experience, it's just this incredibly virtuous cycle. >> So Retool.com is where folks can go to learn more and also try that subscription that you said was free for up to five users. >> Yes, exactly. >> All right. I guess my last question, well couple questions for you. What are some of the things that excited you that you heard from Adam Selipsky this morning? Anything from the keynote that stood out in terms of- >> Dave: Did you listen to the keynote? >> I did not. I had customer calls this morning. >> Okay, so they're bringing- >> East coast time, east coast time. >> One of the things that will excite you I think is they're connecting, making it easier to connect their databases. >> Eleanor: That would very much exciting. >> Aurora and Redshift, right? Okay. And they're making it easier to share data. I dunno if it goes across regions, but they're doing better integration. >> Amazing. >> Right? And you guys are integrating with those tools, right? Those data platforms. So that to me was a big thing for you guys. >> It is also and what a big thing Retool does is you can build a UI layer for your application on top of every single data source. And you hear, it's funny, you hear people talk about the 360 degree review of the customer so much. This is another, it's not our primary value proposition, but it is certainly another way to get there is if you have data from their desk tickets from in Redshift, you have data from Stripe, from their payments, you have data from Twilio from their text messages, you have data from DataDog where they're having your observability where you can notice analytics issues. You can actually just use Retool to build an app that sits on top of that so that you can give your support team, your sales team, your account management team, customer service team, all of the data that they need on their customers. And then you can build workflows so that you can do automated customer engagement reports. I did a Slack every week that shows what our top customers are doing with the product and that's built using all of our automation software as well. >> The integration is so important, as you just articulated, because every, you know, we say every company's a software company these days. Every company's a data company. But also, the data democratization that needs to happen to be able for lines of business so that data moves out of certain locked in functions and enables lines of business to use it. To get that visibility that you were just talking about is really going to be a competitive advantage for those that survive and thrive and grow in this market. >> It's able to, I think it's first it's visibility, but then it's action. And I think that's what Retool does very uniquely as well is it can take and unite the data from all the places, takes it out of the black box, puts it in front of the teams, and then enables them to act on it safely and securely. So not only can you see who might be fraudulent, you can flag them as fraud. Not only can you see who's actually in danger, you can click a button and send them an email and set up a meeting. You can set up an approval workflow to bring in an exec for engagement. You can update a password for someone in one place where you can see that they're having issues and not have to go somewhere else to update the password. So I think that's the key is that Retool can unlock the data visibility and then the action that you need to serve your customers. >> That's a great point. It's all about the actions, the insights that those actions can be acted upon. Last question for you. If you had a billboard that you could put any message that you want on Retool, what would it say? What's the big aha? This is why Retool is so great. >> I mean, I think the big thing about Retool is it's changing the economics of software development. It takes something that previously would've been below the line and that wouldn't get prioritized because it wasn't customer facing and makes it possible. And so I would say one of two billboards if I could be a little bit greedy, one would be Retool changed the economics of software development and one would be build operations software at the speed of thought. >> I love that. You're granted two billboards. >> Eleanor: Thank you. >> Those are both outstanding. Eleanor, it's been such a pleasure having you on the program. Thank you for talking to us about Retool. >> Eleanor: Thank you. >> Operations software and the massive impact that automating it can make for developers, businesses alike, all the way to the top line. We appreciate your insights. >> Thank you so much. >> For our guests and Dave Vellante, I'm Lisa Martin. You're watching theCUBE, the leader in live, emerging, and enterprise tech coverage. (gentle music)