More bottoms up and have more technical early adopters. And generally speaking, they're free to use. They're free to try. They're very commonly community source or open source companies where you have a large technical community that's supporting them. So there's a, there's kind of a new normal now I think in great enterprise software and it starts with great technical founders with great products and great bottoms of emotions. And I think there's no better place to, uh, service those people than in the cloud and uh, in, in your community. >>Well, first of all, congratulations, and by the way, you got a great pedigree and great background, super smart, but Myer of your work and your, and, and your founding, but let's face it. Enterprise is hot because digital transformation is all companies there's no, I mean, consumer is enterprise now, everything is what was once a niche. No, I won't say niche category, but you know, not for the faint of heart, you know, investors, >>You know, it's so funny that you say that enterprise is hot because you, and I feel that way now. <laugh> but remember, like right now there's also a tech and VC conference in Miami <laugh> and it's covering cryptocurrencies and FCS and web three. So I think beauty is definitely in the eye of the beholder <laugh> but no, I, I will tell you, >>Ts is one big enterprise, cuz you gotta have imutability you got performance issues. You have, I IOPS issues. >>Well, and, and I think all of us here that are, uh, may maybe students of history and have been involved in open source in the cloud would say that we're, you know, much of what we're doing is, uh, the predecessors of the web web three movement. And many of us I think are contributors to the web three >>Movement. The hype is definitely one web three. Yeah. >>But, >>But you know, >>For sure. Yeah, no, but now you're taking us further east of Miami. So, uh, you know, look, I think, I, I think, um, what is unquestioned with the case now? And maybe it's, it's more obvious the more time you spend in this world is this is the fastest growing part of enterprise software. And if you include cloud infrastructure and cloud infrastructure spend, you know, it is by many measures over, uh, $500 billion in growing, you know, 20 to 30% a year. So it it's a, it's a just incredibly fast, well, >>Let's get, let's get into some of the cultural and the, the shifts that are happening, cuz again, you, you have the luxury of being in enterprise when it was hard, it's getting easier and more cooler. I get it and more relevant <laugh> but there's also the hype of like the web three, for instance, but you know, for, uh, um, um, the CEO snowflake, okay. Has wrote a book and Dave Valenti and I were talking about it and uh, Frank Luman has says, there's no playbooks. We always ask the CEOs, what's your playbook. And he's like, there's no playbook, situational awareness, always Trump's playbooks. So in the enterprise playbook, oh, higher, a direct sales force and SAS kind of crushed that now SAS is being redefined, right. So what is SAS is snowflake assassin or is that a platform? So again, new unit economics are emerging, whole new situation, you got web three. So to me there's a cultural shift, the young entrepreneurs, the, uh, user experience, they look at Facebook and say, ah, you know, they own all my data and you know, we know that that cliche, um, they, you know, the product. So as this next gen, the gen Z and the millennials come in and our customers and the founders, they're looking at things a little bit differently and the tech better. >>Yeah. I mean, I mean, I think we can, we can see a lot of common across all successful startups and the overall adoption of technology. Um, and, and I would tell you, this is all one big giant revolution. I call it the user driven revolution. Right. It's the rise of the user. Yeah. And you might say product like growth is currently the hottest trend in enterprise software. It's actually like growth, right. They're one and the same. So sometimes people think the product, uh, is what is driving growth. >>You just pull the product >>Through. Exactly, exactly. And so that's that I, that I think is really this revolution that you see, and, and it does extend into things like cryptocurrencies and web three and, you know, sort of like the control that is taken back by the user. Um, but you know, many would say that, that the origins of this, but maybe started with open source where users were contributors, you know, contributors were users and looking back decades and seeing how it, how it fast forward to today. I think that's really the trend that we're all writing. It's enabling these end users. And these end users in our world are developers, data engineers, cybersecurity practitioners, right. They're really the, and they're really the, the beneficiaries and the most, you know, kind of valued people in >>This. I wanna come back to the data engineers in a second, but I wanna make a comment and get your reaction to, I have a, I'm a gen Xer technically. So for not a boomer, but I have some boomer friends who are a little bit older than me who have, you know, experienced the sixties. And I have what been saying on the cube for probably about eight years now that we are gonna hit digital hippie revolution, meaning a rebellion against in the sixties was rebellion against the fifties and the man and, you know, summer of love. That was a cultural differentiation from the other one other group, the predecessors. So we're kind of having that digital moment now where it's like, Hey boomers, Hey people, we're not gonna do that anymore. You, we hate how you organize shit. >>Right. But isn't this just technology. I mean, isn't it, isn't it like there used to be the old adage, like, you know, you would never get fired for buying IBM, but now it's like, you obviously probably would get fired if you bought IBM. And I mean, it's just like the, the, I think, I think >>During the mainframe days, those renegades were breaking into Stanford, starting the home group. So what I'm trying to get at is that, do you see the young cultural revolution also, culturally, just, this is my identity NFTs to me speak volumes about my, I wanna associate with NFTs, not single sign on. Well, >>Absolutely. And, and I think like, I think you're hitting on something, which is like this convergence of, of, you know, societal it'll trends with technology trends and how that manifests in our world is yes. I think like there is unquestionably almost a religion yeah. Around the way in which a product is built. Right. And we can use open source, one example of that religion. Some people will say, look, I'll just never try a product in the cloud if it's not open source. Yeah. I think cloud, native's another example of that, right? It's either it's, you know, it either is cloud native or it's not. And I think a lot of people will look at a product and say, look, you know, you were not designed in the cloud era. Therefore I just won't try you. And sometimes, um, like it or not, it's a religious decision, right? Yeah. It's so it's something that people just believe to be true almost without, uh, necessarily caring >>About data. Data drives all decision making. Let me ask you this next question. As a VC. Now you look at pitch, well, you've been a VC for many years, but you also have the founder entrepreneurial mindset, but you can get empathize with the founders. You know, hustle is a big part of the, that first founder check, right? You gotta convince someone to part with their ch their money and the first money in which you do a lot of it's about believing in the person. So faking it till you make it is hard. Now you, the data's there, you either have it cloud native, you either have the adaption or traction. So honesty is a big part of that pitch. You can't fake it. >>Oh, AB absolutely. You know, there used to be this concept of like the persona of an entrepreneur. Right. And the persona of the entrepreneur would be, you know, so somebody who was a great salesperson or somebody who tell a great story, and I still think that that's important, right. It still is a human need for people to believe in narratives and stories. Yeah. But having said that you're right. The proof is in the pudding, right. At some point you click download and you try the product and it does what it says it gonna it's gonna do, or it doesn't, or it either stands up to the load test or it doesn't. And so I, I feel like in the new economy that we live in, really, it's a shift from maybe the storytellers and the creators to, to the builders, right. The people that know how to build great product. And in some ways the people that can build great product yeah. Stand out from the crowd. And they're the ones that can build communities around their products. And, you know, in some ways can, um, you know, kind of own more of the narrative of because their product begins exactly >>The volume you back to the user led growth. >>Exactly. And it's the religion of, I just love your product. Right. And I, I, I, um, Doug song is the founder of du security used to say, Hey, like, you know, the, the really like in today's world of like consumption based software, like the user is only gonna give you 90 seconds to figure out whether or not you're a company that's easy to do business with. Right. And so you can say, and do all the things that you want about how easy you are to work with. But if the product isn't easy to install, if it's not easy to try, if it's not, if, if the it's gotta speak to the, >>Speak to the user, but let me ask a question now that for the people watching, who are maybe entrepreneurial entre, preneurs, um, masterclass here in session. So I have to ask you, do you prefer, um, an entrepreneur come in and say, look at John. Here's where I'm at. Okay. First of all, storytelling's fine with you an extrovert or introvert, have your style, sell the story in a way that's authentic, but do you, what do you prefer to say? Here's where I'm at? Look, I have an idea. Here's my traction. I think here's my MVP prototype. I need help. Or do, do you wanna just see more stats? What's the, what's the preferred way that you like to see entrepreneurs come in and engage? >>There's tons of different styles, man. I think the single most important thing that every founder should know is that we, we don't invest in what things are today. We invest in what we think something will become. Right. And I think that's why we all get up in the morning and try to build something different, right? It's that we see the world a different way. We want it to be a different way. And we wanna work every single moment of the day to try to make that vision a reality. So I think the more that you can show people where you want to be the, of more likely somebody is gonna align with your vision and, and wanna invest in you and wanna be along for the ride. So I, I wholeheartedly believe in showing off what you got today, because eventually we all get down to like, where are we and what are we gonna do together? But, um, no, I, you gotta >>Show the >>Path. I think the single most important thing for any founder and VC relationship is that they have the same vision. Uh, if you have the same vision, you can, you can get through bumps in the road, you can get through short term spills. You can all sorts of things in the middle. The journey can happen. Yeah. But it doesn't matter as much if you share the same long term vision, >>Don't flake out and, and be fashionable with the latest trends because it's over before you can get there. >>Exactly. I think many people that, that do what we do for a living, we'll say, you know, ultimately the future is relatively easy to predict, but it's the timing that's impossible to predict. <laugh> so you, you know, you sort of have to balance the, you know, we, we know that the world is going in this way and therefore we're gonna invest a lot of money to try to make this a reality. Uh, but some times it happens in six months. Sometimes it takes six years. Sometimes it takes 16 years. Uh, >>What's the hottest thing in enterprise that you see the biggest wave that people should pay attention to that you're looking at right now with Bel partners, Tebel dot your site. What's the big wave. What's your big >>Wave. There's three big trends that we invest in. And the they're the only things we do day in, day out one is the explosion and open source software. So I think many people think that all software is unquestionably moving to an open source model in some form or another yeah. Tons of reasons to debate whether or not that is gonna happen, an alwa timeline >>Happening forever. >>But, uh, it is, it is accelerating faster than we've ever seen. So I, I think it's, it's one big, massive wave that we continue to ride. Um, second is the rise of data engineering. Uh, I think data engineering is in and of itself now, a category of software. It's not just that we store data. It's now we move data and we develop applications on data. And, uh, I think data is in and of itself as big of a market as any of the other markets that we invest in. Uh, and finally, it's the gift that keeps on giving. I've spent my entire career in it. We still feel that security is a market that is underinvested. It is, it continues to be the place where people need to continue to invest and spend more money. Yeah. Uh, and those are the three major trends that we run >>And security, you think we all need a dessert do over, right? I mean, do we need you do over in security or is what's the core problem? I, >>I, I keep using this word underinvested because I think it's the right way to think about the problem. I think if you, I think people generally speaking, look at cybersecurity as an add-on. Yeah. But if you think about it, the whole economy is moving online. And so in, in some ways like security is core to protecting the digital economy. And so it's, it shouldn't be an afterthought, right? It should be core to what everyone is doing. And that's why I think relative to the trillions of dollars that are at stake, uh, I believe the market size for cybersecurity is run $150 billion. And it still is a fraction of what we're, >>What we're and national security even boom is booming now. So you get the convergence of national security, geopolitics, internet digital that's >>Right. You mean arguably, right? I mean, arguably again, it's the area of the world that people should be spending more time and more money given what to stake. >>I love your thesis. I gotta, I gotta say, you gotta love your firm. Love. You're doing we're big supporters, your mission. Congratulations on your entrepreneurial venture. And, uh, we'll be, we'll be talking and maybe see a Cuban. Uh, absolutely not. Certainly EU maybe even north Americans in Detroit this year. >>Huge fan of what you guys are doing here. Thank you so much for helping me on the show. >>Guess be VC Johnson here on the cube. Check him out. Founder for founders here on the cube, more coverage from San Francisco, California. After this short break, stay with us. Everyone. Welcome to the cue here. Live in San Francisco. K warn you for AWS summit 2022 we're live we're back with events. Also we're virtual. We got hybrid all kinds of events. This year, of course, summit in New York city is happening this summer. We'll be there with the cube as well. I'm John. Again, John host of the cube. Got a great guest here, Justin Kobe owner, and CEO of innovative solutions. Their booth is right behind us. Justin, welcome to the cube. >>Thank you. Thank you for having me. >>So we're just chatting, uh, uh, off camera about some of the work you're doing. You're the owner of and CEO. Yeah. Of innovative. Yeah. So tell us the story. What do you guys do? What's the elevator pitch. >>Yeah. <laugh> so the elevator pitch is we are, uh, a hundred percent focused on small to mid-size businesses that are moving to the cloud, or have already moved to the cloud and really trying to understand how to best control security, compliance, all the good stuff that comes along with it. Um, exclusively focused on AWS and, um, you know, about 110 people, uh, based in Rochester, New York, that's where our headquarters is, but now we have offices down in Austin, Texas, up in Toronto, uh, Canada, as well as Chicago. Um, and obviously in New York, uh, you know, the business was never like this, uh, five years ago, um, founded in 1989, made the decision in 2018 to pivot and go all in on the cloud. And, uh, I've been a part of the company for about 18 years, bought the company about five years ago. And it's been a great ride. >>It's interesting. The manages services are interesting with cloud cause a lot of the heavy liftings done by a of us. So we had Matt on your team on earlier talking about some of the edge stuff. Yeah. But you guys are a managed cloud service. You got cloud advisory, you know, the classic service that's needed, but the demands coming from cloud migrations and application modernization, but obviously data is a huge part of it. Huge. How is this factoring into what you guys do and your growth cuz you guys are the number one partner on the SMB side for edge. Yeah. For AWS, you got results coming in. Where's the, where's the forcing function. What's the pressure point. What's the demand like? >>Yeah. It's a great question. Every CEO I talk to, that's a small mids to size business. They're all trying to understand how to leverage technology better to help either drive a revenue target for their own business, uh, help with customer service as so much has gone remote now. And we're all having problems or troubles or issues trying to hire talent. And um, you know, tech is really at the, at the forefront and the center of that. So most customers are coming to us and they're of like, listen, we gotta move to the cloud or we move some things to the cloud and we want to do that better. And um, there's this big misnomer that when you move to the cloud, you gotta automatically modernize. Yeah. And what we try to help as many customers understand as possible is lifting and shifting, moving the stuff that you maybe currently have OnPrem and a data center to the cloud first is a first step. And then so, uh, progressively working through a modernization strategy is always the better approach. And so we spend a lot of time with small to mid-size businesses who don't have the technology talent on staff to be able to do >>That. Yeah. And they want to get set up. But the, the dynamic of like latency is huge. We're seeing that edge product is a big part of it. This is not a one-off happening around everywhere. It is not it's manufacturing, it's the physical plant or location >>Literally. >>And so, and you're seeing more IOT devices. What's that like right now from a challenge and problem statement standpoint, are the customers, not staff, is the it staff kind of old school? Is it new skills? What's the core problem. And you guys solve >>In the SMB space. The core issue nine outta 10 times is people get enamored with the latest and greatest. And the reality is not everything that's cloud based. Not all cloud services are the latest and greatest. Some things have been around for quite some time and our hardened solutions. And so, um, what we try to do with, to technology staff that has traditional on-prem, uh, let's just say skill sets and they're trying to move to a cloud-based workload is we try to help those customers through education and through some practical, let's just call it use case. Um, whether that's a proof of concept that we're doing or whether that's, we're gonna migrate a small workload over, we try to give them the confidence to be able to not, not necessarily go it alone, but, but to, to, to have the, uh, the Gusto and to really have the, um, the, the opportunity to, to do that in a wise way. Um, and what I find is that most CEOs that I talk to yeah. Feel like, listen, at the end of the day, I'm gonna be spending money in one place or another, whether that's on primer in the cloud, I just want know that I'm doing that way. That helps me grow as quickly as possible status quo. I think every, every business owner knows that COVID taught us anything that status quo is, uh, is, is no. No. Good. >>How about factoring in the, the agility and speed equation? Does that come up a lot? It >>Does. I think, um, I think there's also this idea that if, uh, if we do a deep dive analysis and we really take a surgical approach to things, um, we're gonna be better off. And the reality is the faster you move with anything cloud based, the better you are. And so there's this assumption that we gotta get it right the first time. Yeah. In the cloud, if you start down your journey in one way and you realize midway that it's not the right, let's just say the right place to go. It's not like buying a piece of iron that you put in the closet and now you own it in the cloud. You can turn those services on and off. It's a, gives you a much higher density for making decisions and failing >>Forward. Well actually shutting down the abandoning, the projects that early, not worrying about it, you got it mean most people don't abandon stuff cuz they're like, oh, I own it. >>Exactly. >>And they get, they get used to it. Like, and then they wait too long. >>That's exactly. >>Yeah. Frog and boiling water, as we used to say, oh, it's a great analogy. So I mean, this, this is a dynamic. That's interesting. I wanna get more thoughts on it because like I'm a, if I'm a CEO of a company, like, okay, I gotta make my number. Yeah. I gotta keep my people motivated. Yeah. And I gotta move faster. So this is where you guys come in. I get the whole thing. And by the way, great service, um, professional services in the cloud right now are so hot because so hot, you can build it and then have option optionality. You got path decisions, you got new services to take advantage of. It's almost too much for customers. It is. I mean, everyone I talked to at reinvent, that's a customer. Well, how many announcements did Andy jazzy announcer Adam? You know, the 5,000 announcement or whatever. They did huge amounts. Right. Keeping track of it all. Oh, is huge. So what's the, what's the, um, the mission of, of your company. How does, how do you talk to that alignment? Yeah. Not just processes. I can get that like values as companies, cuz they're betting on you and your people. >>They are, they are >>Values. >>Our mission is, is very simple. We want to help every small to midsize business leverage the power of the cloud. Here's the reality. We believe wholeheartedly. This is our vision that every company is going to become a technology company. So we go to market with this idea that every customer's trying to leverage the power of the cloud in some way, shape or form, whether they know it or don't know it. And number two, they're gonna become a 10 a company in the process of that because everything is so tech-centric. And so when you talk about speed and agility, when you talk about the, the endless options and the endless permutations of solutions that a customer can buy in the cloud, how are you gonna ask a team of one or two people in your it department to make all those decisions going it alone or trying to learn it as you go, it only gets you so far working with a partner. >>I'll just give you some perspective. We work with about a thousand small to midsize business customers. More than 50% of those customers are on our managed services. Meaning they know that we have their back and we're the safety net. So when a customer is saying, right, I'm gonna spend a couple thousand and dollars a month in the cloud. They know that that bill, isn't gonna jump to $10,000 a month going in alone. Who's there to help protect that. Number two, if you have a security posture and let's just say your high profile and you're gonna potentially be more vulnerable to security attacks. If you have a partner that's offering you some managed services. Now you, again, you've got that backstop and you've got those services and tooling. We, we offer, um, seven different products, uh, that are part of our managed services that give the customer the tooling, that for them to go out and buy on their own for a customer to go out today and go buy a new Relic solution on their own. It, it would cost 'em a four, >>The training alone would be insane. A risk factor. I mean the cost. Yes, absolutely opportunity cost is huge, >>Huge, absolutely enormous training and development. Something. I think that is often, you know, it's often overlooked technologists. Typically they want to get their skills up. They, they love to get the, the stickers and the badges and the pins, um, at innovative in 2018. When, uh, when we, he made the decision to go all in on the club, I said to the organization, you know, we have this idea that we're gonna pivot and be aligned with AWS in such a way that it's gonna really require us all to get certified. My executive assistant at the time looks at me. She said, even me, I said, yeah, even you, why can't you get certified? Yeah. And so we made, uh, a conscious, it wasn't requirement. It still isn't today to make sure everybody in the company has the opportunity to become certified. Even the people that are answering the phones at the front >>Desk and she could be running the Kubernetes clusters. I >>Love it. It's >>Amazing. >>But I'll tell you what, when that customer calls and they have a real Kubernetes issue, she'll be able to assist and get >>The right people with. And that's a cultural factor that you guys have. So, so again, this is back to my whole point out SMBs and businesses in general, small and large it staffs are turning over the gen Z and millennials are in the workforce. They were provisioning top of rack switches. Right. First of all. And so if you're a business, there's also the, I call the buildout, um, uh, return factor, ROI piece. At what point in time as an owner, SMB, do I get to ROI? Yeah. I gotta hire a person to manage it. That person's gonna have five zillion job offers. Yep. Uh, maybe who knows? Right. I got cyber security issues. Where am I gonna find a cyber person? Yeah. A data compliance. I need a data scientist and a compliance person. Right. Maybe one in the same. Right. Good luck. Trying to find a data scientist. Who's also a compliance person. Yep. And the list goes on. I can just continue. Absolutely. I need an SRE to manage the, the, uh, the sock report and we can pen test. Right. >>Right. >>These are, these are >>Like critical issues. >>This is just like, these are the table stakes. >>Yeah. And, and every, every business owner's thinking about this, >>That's, that's what, at least a million in loading, if not three or more Just to get that app going. Yeah. Then it's like, where's the app. Yeah. So there's no cloud migration. There's no modernization on the app side. No. And they remind AI and ML. >>That's right. That's right. So to try to go it alone, to me, it's hard. It it's incredibly difficult. And the other thing is, is there's not a lot of partners, so the partner, >>No one's raising their hand boss. I'll do all that exactly. In the it department. >>Exactly. >>So like, can we just call up, uh, you know, our old vendor that's >>Right. <laugh> right. Our old vendor. I like it, >>But that's so true. I mean, when I think about how, if I was a business owner starting a business today and I had to build my team, um, and the amount of investment that it would take to get those people skilled up and then the risk factor of those people now having the skills and being so much more in demand and being recruited away, that's a real, that's a real issue. And so how you build your culture around that is, is very important. It's something that we talk about every, with every one of our small to mid-size >>Businesses. So just, I want get, I want to get your story as CEO. Okay. Take us through your journey. You said you bought the company and your progression to, to being the owner and CEO of innovative yeah. Award winning guys doing great. Uh, great bet on a good call. Yeah. Things are good. Tell your story. What's your journey? >>It's real simple. I was, uh, I was a sophomore at the Rochester Institute of technology in 2003. And, uh, I knew that I, I was going to school for it and I, I knew I wanted to be in tech. I didn't know what I wanted to do, but I knew I didn't wanna code or configure routers and switches. So I had this great opportunity with the local it company that was doing managed services. We didn't call it at that time innovative solutions to come in and, uh, jump on the phone and dial for dollars. I was gonna cold call and introduced other, uh, small to midsize businesses locally in Rochester, New York go to Western New York, um, who innovative was now. We were 19 people at the time. Yeah. I came in, I did an internship for six months and I loved it. I learned more in those six months than I probably did in my first couple of years at, uh, at RT long story short. >>Um, for about seven years, I worked, uh, to really help develop, uh, sales process and methodology for the business so that we could grow and scale. And we grew to about 30 people. And, um, I went to the owners at the time in 2000 and I was like, Hey, I'm growing the value of this business. And who knows where you guys are gonna be another five years? What do you think about making me an owner? And they were like, listen, you got long ways before you're gonna be an owner. But if you stick it out in your patient, we'll, um, we'll work through a succession plan with you. And I said, okay, there were four other individuals at the time that were gonna also buy the business with me. >>And they were the owners, no outside capital, >>None zero, well, 2014 comes around. And, uh, the other folks that were gonna buy into the business with me that were also working at innovative for different reasons. They all decided that it wasn't for them. One started a family. The other didn't wanna put capital in. Didn't wanna write a check. Um, the other had a real big problem with having to write a check. If we couldn't make payroll, I'm like, well, that's kind of like, if we're own, we're gonna have to like cover that stuff. <laugh> so >>It's called the pucker factor. >>Exactly. So, uh, I sat down with the CEO in early 2015 and, uh, we made the decision that I was gonna buy the three partners out, um, go through an earn out process, uh, coupled with, uh, an interesting financial strategy that wouldn't strap the BI cuz they cared very much. The company still had the opportunity to keep going. So in 2016 I bought the business, um, became the sole owner. And, and at that point we, um, we really focused hard on what do we want this company to be? We had built this company to this point. Yeah. And, uh, and by 2018 we knew that pivoting all going all in on the cloud was important for us. And we haven't looked back. >>And at that time, the proof points were coming clearer and clearer 2012 through 15 was the early adopters, the builders, the startups and early enterprises. Yes. The capital ones of the world. Exactly the, uh, and those kinds of big enterprises. The GA I don't wanna say gamblers, but ones that were very savvy. The innovators, the FinTech folks. Yep. The hardcore glass eating enterprises >>Agreed, agreed to find a small to midsize business to migrate completely to the cloud is as infrastructure was considered, that just didn't happen as often. Um, what we were seeing where the, a lot of our small to midsize business customers, they wanted to leverage cloud based backup, or they wanted to leverage a cloud for disaster recovery because it lent itself. Well, early days, our most common cloud customer though, was the customer that wanted to move messaging and collaboration. The, the Microsoft suite to the cloud. And a lot of 'em dipped their toe in the water. But by 2017 we knew infrastructure was around the corner. Yeah. And so, uh, we only had two customers on AWS at the time. Um, and we, uh, we, we made the decision to go all in >>Justin. Great to have you on the cube. Thank you. Let's wrap up. Uh, tell me the hottest product that you have. Is it migrations? Is the app modernization? Is it data? What's the hot product and then put a plugin for the company. Awesome. >>So, uh, there's no question. Every customer is looking migrate workloads and try to figure out how to modernize for the future. We have very interesting, sophisticated yet elegant funding solutions to help customers with the cash flow, uh, constraints that come along with those migrations. So any SMB that's thinking about migrating into the cloud, they should be talking innovative solutions. We know how to do it in a way that allows those customer is not to be cash strapped and gives them an opportunity to move forward in a controlled, contained way so they can modernize. So >>Like insurance, basically for them not insurance class in the classic sense, but you help them out on the, on the cash exposure. >>Absolutely. We are known for that and we're known for being creative with those customers and being empathetic to where they are in their journey. >>And that's the cloud upside is all about doubling down on the variable win that's right. Seeing the value and ING down on it. Absolutely not praying for it. Yeah. <laugh> all right, Justin. Thanks for coming on. You really appreciate >>It. Thank you very much for having me. >>Okay. This is the cube coverage here live in San Francisco, California for AWS summit, 2022. I'm John for your host. Thanks for watching. We're back with more great coverage for two days after this short break >>Live on the floor in San Francisco for Aus summit. I'm John for host of the cube here for the next two days, getting all the actual back in person we're at AWS reinvent a few months ago. Now we're back events are coming back and we're happy to be here with the cube. Bring all the action. Also virtual. We have a hybrid cube, check out the cube.net, Silicon angle.com for all the coverage. After the event. We've got a great guest ticking off here. Matthew Park, director of solutions, architecture with innovation solutions. The booth is right here. Matthew, welcome to the cube. >>Thank you very much. I'm glad to be here. >>So we're back in person. You're from Tennessee. We were chatting before you came on camera. Um, it's great to be back through events. It's >>Amazing. This is the first, uh, summit I've been to, to in what two, three >>Years. That's awesome. We'll be at the, uh, a AWS summit in New York as well. A lot of developers and the big story this year is as developers look at cloud going distributed computing, you got on premises, you got public cloud, you got the edge. Essentially the cloud operations is running everything devs sec ops, everyone kind of sees that you got containers, you got Benet, he's got cloud native. So the, the game is pretty much laid out. Mm-hmm <affirmative> and the edge is with the actions you guys are number one, premier partner at SMB for edge. >>That's >>Right. Tell us about what you guys doing at innovative and, uh, what you do. >>That's right. Uh, so I'm the director of solutions architecture. Uh, me and my team are responsible for building out the solutions. The at our around, especially the edge public cloud for us edge is anything outside of an AWS availability zone. Uh, we are deploying that in countries that don't have AWS infrastructure in region. They don't have it. Uh, give >>An example, >>Uh, example would be Panama. We have a customer there that, uh, needs to deploy some financial tech data and compute is legally required to be in Panama, but they love AWS and they want to deploy AWS services in region. Uh, so they've taken E EKS anywhere. We've put storage gateway and, uh, snowball, uh, in region inside the country and they're running or FinTech on top of AWS services inside Panama. >>You know, what's interesting, Matthew is that we've been covering Aw since 2013 with the cube about their events. And we watched the progression and jazzy was, uh, was in charge and became the CEO. Now Adam slaps in charge, but the edge has always been that thing they've been trying to avoid. I don't wanna say trying to avoid, of course, Amazon would listens to the customer. They work backwards from the customer. We all know that. Uh, but the real issue was they were they're bread and butters EC two and S three. And then now they got tons of services and the cloud is obviously successful and seeing that, but the edge brings up a whole nother level. >>It does >>Computing. >>It >>Does. That's not centralized in the public cloud now they got regions. So what is the issue with the edge what's driving? The behavior. Outpost came out as a reaction to competitive threats and also customer momentum around OT, uh, operational technologies. And it merging. We see with the data at the edge, you got five GM having. So it's pretty obvious, but there was a slow transition. What was the driver for the edge? What's the driver now for edge action for AWS >>Data in is the driver for the edge. Data has gravity, right? And it's pulling compute back to where the customer's generating that data and that's happening over and over again. You said it best outpost was a reaction to a competitive situation. Whereas today we have over 15 AWS edge services and those are all reactions to things that customers need inside their data centers on location or in the field like with media companies. >>Outpost is interesting. We always use the riff on the cube, uh, cause it's basically Amazon in a box, pushed in the data center, running native, all this stuff, but now cloud native operations are kind of becoming standard. You're starting to see some standard. Deepak syncs group is doing some amazing work with opensource Raul's team on the AI side, obviously, uh, you got SW who's giving the keynote tomorrow. You got the big AI machine learning big part of that edge. Now you can say, okay, outpost, is it relevant today? In other words, did outpost do its job? Cause EKS anywhere seems to be getting a lot of momentum. You see local zones, the regions are kicking ass for Amazon. This edge piece is evolving. What's your take on EKS anywhere versus say outpost? >>Yeah, I think outpost did its job. It made customers that were looking at outpost really consider, do I wanna invest in this hardware? Do I, do I wanna have, um, this outpost in my datas center, do I want to manage this over the long term? A lot of those customers just transitioned to the public cloud. They went into AWS proper. Some of those customers stayed on prem because they did have use cases that were, uh, not a good fit for outpost. They weren't a good fit. Uh, in the customer's mind for the public AWS cloud inside an availability zone now happening is as AWS is pushing these services out and saying, we're gonna meet you where you are with 5g. We're gonna meet you where you are with wavelength. We're gonna meet you where you are with EKS anywhere. Uh, I think it has really reduced the amount of times that we have conversations about outposts and it's really increased. We can deploy fast. We don't have to spin up outpost hardware can go deploy EKS anywhere in your VMware environment. And it's increasing the speed of adoption >>For sure. Right? So you guys are making a lot of good business decisions around managed cloud service. That's right. Innovative. Does that get the cloud advisory, the classic professional services for the specific edge piece and, and doing that outside of the availability zones and regions for AWS, um, customers in these new areas that you're helping out are they want cloud, like they want to have modernization a modern applications. Obviously they got data machine learning and AI, all part of that. What's the main product or, or, or gap that you're filling for AWS, uh, outside of their availability zones or their regions that you guys are delivering. What's the key is that they don't have a footprint. Is it that it's not big enough for them? What's the real gap. What's why, why are you so successful? >>So what customers want when they look towards the cloud is they want to focus on what's making them money as a business. They wanna focus on their applications. They wanna focus on their customers. So they look towards AWS cloud and a AWS. You take the infrastructure, you take, uh, some of the higher layers and we'll focus on our revenue generating business, but there's a gap there between infrastructure and revenue generating business that innovative slides into, uh, we help manage the AWS environment. Uh, we help build out these things in local data centers for 32 plus year old company. We have traditional on-premises people that know about deploying hardware that know about deploying VMware to host EKS anywhere. But we also have most of our company totally focused on the AWS cloud. So we're that gap in helping deploy these AWS services, manage them over the long term. So our customers can go to just primarily and totally focusing on their revenue generating business. So >>Basically you guys are basically building AWS edges, >>Correct? >>For correct companies, correct? Mainly because the, the needs are there, you got data, you got certain products, whether it's, you know, low latency type requirements, right. And then they still work with the regions, right. It's all tied together, right. Is that how it >>Works? Right. And, and our customers, even the ones in the edge, they also want us to build out the AWS environment inside the availability zone, because we're always gonna have a failback scenario. If we're gonna deploy fin in the Caribbean, we're gonna talk about hurricanes. And we're gonna talk about failing back into the AWS availability zones. So innovative is filling that gap across the board, whether it be inside the AWS cloud or on the AWS edge. >>All right. So I gotta ask you on the, since you're at the edge in these areas, I won't say underserved, but developing areas where now have data and you have applications that are tapping into that, that requirement. It makes total sense. We're seeing that across the board. So it's not like it's a, it's an outlier it's actually growing. Yeah. There's also the crypto angle. You got the blockchain. Are you seeing any traction at the edge with blockchain? Because a lot of people are looking at the web three in these areas like Panama, you mentioned FinTech. And in, in the islands there a lot of, lot of, lot of web three happening. What's your, what your view on the web three world right now, relative >>To we, we have some customers actually deploying crypto, especially, um, especially in the Caribbean. I keep bringing the Caribbean up, but it's, it's top of my mind right now we have customers that are deploying crypto. A lot of, uh, countries are choosing crypto to underlie parts of their central banks. Yeah. Um, so it's, it's up and coming. Uh, I, I have some, you know, personal views that, that crypto is still searching for a use case. Yeah. And, uh, I think it's searching a lot and, and we're there to help customers search for that use case. Uh, but, but crypto, as a, as a, uh, technology, um, lives really well on the AWS edge. Yeah. Uh, and, and we're having more and more people talk to us about that. Yeah. And ask for assistance in the infrastructure, because they're developing new cryptocurrencies every day. Yeah. It's not like they're deploying Ethereum or anything specific. They're actually developing new currencies and, and putting them out there on >>It's interesting. I mean, first of all, we've been doing crypto for many, many years. We have our own little, um, you know, project going on. But if you look talk to all the crypto people that say, look, we do a smart contract, we use the blockchain. It's kind of over a lot of overhead and it's not really their technical already, but it's a cultural shift, but there's underserved use cases around use of money, but they're all using the blockchain just for like smart contracts, for instance, or certain transactions. And they go to Amazon for the database. Yeah. <laugh> they all don't tell anyone we're using a centralized service. Well, what happened to decentralized? >>Yeah. And that's, and that's the conversation performance issue. Yeah. And, and it's a cost issue. Yeah. And it's a development issue. Um, so I think more and more as, as some of these, uh, currencies maybe come up, some of the smart contracts get into, uh, they find their use cases. I think we'll start talking about how does that really live on, on AWS and, and what does it look like to build decentralized applications, but with AWS hardware and services. >>Right. So take me through, uh, a use case of a customer Matthew around the edge. Okay. So I'm a customer, pretend I'm a customer, Hey, you know, I'm, we're in an underserved area. I want to modernize my business. And I got my developers that are totally peaked up on cloud, but we've identified that it's just a lot of overhead latency issues. I need to have a local edge and serve my a, I also want all the benefit of the cloud. So I want the modern, and I wanna migrate to the cloud for all those cloud benefits and the goodness of the cloud. What's the answer. >>Yeah. Uh, big thing is, uh, industrial manufacturing, right? That's, that's one of the best use cases, uh, inside industrial manufacturing, we can pull in many of the AWS edge services we can bring in, uh, private 5g, uh, so that all the, uh, equipment that, that manufacturing plant can be hooked up, they don't have to pay huge overheads to deploy 5g it's, uh, better than wifi for the industrial space. Um, when we take computing down to that industrial area, uh, because we wanna do pre-procesing on the data. Yeah. We want to gather some analytics. We deploy that with a regular commercially available hardware running VMware, and we deploy EKS anywhere on that. Inside of that manufacturing plant, we can do pre-procesing on things coming out of the robotics, depending on what we're manufacturing. Right. And then we can take those refined analytics and for very low cost with maybe a little bit longer latency transmit those back, um, to the AWS availability zone, the, the standard >>For data, data lake, or whatever, >>To the data lake. Yeah. Data lake house, whatever it might be. Um, and we can do additional data science on that once it gets to the AWS cloud. Uh, but a lot of that, uh, just in time business decisions, just time manufacturing decisions can all take place on an AWS service or services inside that manufacturing plant. And that's, that's one of the best use cases that we're >>Seeing. And I think, I mean, we've been seeing this on the queue for many, many years, moving data around is very expensive. Yeah. But also compute going to the data that saves that cost yeah. On the data transfer also on the benefits of the latency. So I have to ask you, by the way, that's standard best practice now for the folks watching don't move the data unless you have to. Um, but those new things are developing. So I wanna ask you what new patterns are you seeing emerging once this new architecture's in place? Love that idea, localize everything right at the edge, manufacturing, industrial, whatever, the use case, retail, whatever it is. Right. But now what does that change in the, in the core cloud? There's a, there's a system element here. Yeah. What's the new pattern. There's >>Actually an organizational element as well, because once you have to start making the decision, do I put this compute at the point of use or do I put this compute in the cloud? Uh, now you start thinking about where business decisions should be taking place. Uh, so not only are you changing your architecture, you're actually changing your organization because you're thinking, you're thinking about a dichotomy you didn't have before. Uh, so now you say, okay, this can take place here. Uh, and maybe, maybe this decision can wait. Right. And then how do I visualize that? By >>The way, it could be a bot tube doing the work for management. Yeah. <laugh> exactly. You got observability going, right. But you gotta change the database architecture on the back. So there's new things developing. You've got more benefit. There >>Are, there are, and we have more and more people that, that want to talk less about databases and want to talk about data lakes because of this. They want to talk more about customers are starting to talk about throwing away data. Uh, you know, for the past maybe decade. Yeah. It's been store everything. And one day we will have a data science team that we hire in our organization to do analytics on this decade of data. And well, >>I mean, that's, that's a great point. We don't have time to drill into, maybe we do another session this, but the one pattern we're seeing come of the past year is that throwing away data's bad. Even data lakes that so-called turn into data swamps, actually, it's not the case. You look at data, brick, snowflake, and other successes out there. And even time series data, which may seem irrelevant efforts over actually matters when people start retrain their machine learning algorithms. Yep. So as data becomes co as we call it in our last showcase, we did a whole whole an event on this. The data's good in real time and in the lake. Yeah. Because the iteration of the data feeds the machine learning training. Things are getting better with the old data. So it's not throw away. It's not just business benefits. Yeah. There's all kinds of new scale. There >>Are. And, and we have, uh, many customers that are running petabyte level. Um, they're, they're essentially data factories on, on, on premises, right? They're, they're creating so much data and they're starting to say, okay, we could analyze this, uh, in the cloud, we could transition it. We could move petabytes of data to AWS cloud, or we can run, uh, computational workloads on premises. We can really do some analytics on this data transition, uh, those high level and sort of raw analytics back to AWS run 'em through machine learning. Um, and we don't have to transition 10, 12 petabytes of data into AWS. >>So I gotta end the segment on a, on a, kind of a, um, fun, I was told to ask you about your personal background on premise architect, Aus cloud, and skydiving instructor. How does that all work together? What tell, what does this mean? >>Yeah. Uh, I, >>You jumped out a plane and got a job. You got a customer to jump >>Out kind of. So I was, you jumped out. I was teaching Scott eing, uh, before I, before I started in the cloud space, this was 13, 14 years ago. I was a, I still am a Scott I instructor. Uh, I was teaching Scott eing and I heard out of the corner of my ear, uh, a guy that owned an MSP that was lamenting about, um, you know, storing data and how his customers are working. And he can't find enough people to operate all these workloads. So I walked over and said, Hey, this is, this is what I went to school for. Like, I'd love to, you know, I was living in a tent in the woods, teaching skydiving. I was like, I'd love to not live in a tent in the woods. So, uh, I started in the first day there, we had a, and, uh, EC two had just come out <laugh> um, and, uh, like, >>This is amazing. >>Yeah. And so we had this discussion, we should start moving customers here. And, uh, and that totally revolutionized that business, um, that, that led to, uh, that that guy actually still owns a skydiving airport. But, um, but through all of that, and through being in on premises, migrated me and myself, my career into the cloud, and now it feels like, uh, almost, almost looking back and saying, now let's take what we learned in the cloud and, and apply those lessons and those services to premises. >>So it's such a great story. You know, I was gonna, you know, you know, the, the, the, the whole, you know, growth mindset pack your own parachute, you know, uh, exactly. You know, the cloud in the early days was pretty much will the shoot open. Yeah. It was pretty much, you had to roll your own cloud at that time. And so, you know, you, you jump on a plane, you gotta make sure that parachute is gonna open. >>And so was Kubernetes by the way, 2015 or so when, uh, when that was coming out, it was, I mean, it was, it was still, and I, maybe it does still feel like that to some people, right. Yeah. But, uh, it was, it was the same kind of feeling that we had in the early days of AWS, the same feeling we have when we >>It's much now with you guys, it's more like a tandem jump. Yeah. You know, but, but it's a lot of, lot of this cutting stuff like jumping out of an airplane. Yeah. You guys, the right equipment, you gotta do the right things. Exactly. >>Right. >>Matthew, thanks for coming on the cube. Really appreciate it. Absolutely great conversation. Thanks for having me. Okay. The cubes here, lot in San Francisco for AWS summit, I'm John for your host of the cube. Uh, we'll be at a summit in New York coming up in the summer as well. Look up for that. Look at this calendar for all the cube, actually@thecube.net. We'll right back with our next segment after this break. >>Okay. Welcome back everyone to San Francisco live coverage here, we're at the cube, a summit 2022. We're back in person. I'm John furry host of the cube. We'll be at the, a us summit in New York city this summer, check us out then. But right now, two days in San Francisco getting all coverage, what's going on in the cloud, we got a cube alumni and friend of the cube, my dos car CEO, investor, a Sierra, and also an investor and a bunch of startups, angel investor. Gonna do great to see you. Thanks for coming on the cube. Good to see you. Good to see you, Pam. Cool. How are you? Good. >>How are you? >>So congratulations on all your investments. Uh, you've made a lot of great successes, uh, over the past couple years, uh, and your company raising, uh, some good cash as Sarah so give us the update. How much cash have you guys raised? What's the status of the company product what's going on? First >>Of all, thank you for having me. We're back to be business with you never while after. Great to see you. Um, so is a company started around four years back. I invested with a few of the investors and now I'm the CEO there. Um, we have raised close to a hundred million there. Uh, the investors are people like nor west Menlo, true ventures, coast, lo ventures, Ram Shera, and all those people, all known guys that Antibe chime Paul Mayard web. So a whole bunch of operating people and, uh, Silicon valley vs are involved. >>And has it gone? >>It's going well. We are doing really well. We are going almost 300% year over year. Uh, for last three years, the space ISR is going after is what I call the applying AI for customer service. It operations, it help desk the same place I used to work at ServiceNow. We are partners with ServiceNow to take, how can we argument for employees and customers, Salesforce, and ServiceNow to take it to the next stage? Well, >>I love having you on the cube, Dave and I, and Dave Valenti as well loves having you on too, because you not only bring the entrepreneurial CEO experience, you're an investor. You're like a, you're like a guest analyst. <laugh>, >>You know, >>You >>Get, the comment is fun to talk to you though. >>You get the commentary, you, your, your finger on the pulse. Um, so I gotta ask you obviously, AI and machine learning, machine learning AI, or you want to phrase it. Isn't every application. Now, AI first, uh, you're seeing a lot of that going on. You're starting to see companies build the modern applications at the top of the stack. So the cloud scale has hit. We're seeing cloud out scale. You predicted that we talked about in the cube many times. Now you have that past layer with a lot more services and cloud native becoming a standard layer. Containerizations growing Docker just raised a hundred million on our $2 billion valuation back from the dead after they pivoted from an enterprise services. So open source developers are booming. Um, where's the action. I mean, is there data control, plane emerging, AI needs data. There's a lot of challenges around this. There's a lot of discussions and a lot of companies being funded observability there's 10 million observability companies. Data is the key. This is what's your angle on this. What's your take. Yeah, >>No, look, I think I'll give you the view that I see, right? I, from my side, obviously data is very clear. So the things that room system of record that you and me talked about, the next layer is called system of intelligence. That's where the AI will play. Like we talk cloud native, it'll be called AI. NA NA is a new buzzword and using the AI for customer service, it operations. You talk about observability. I call it AI ops, applying AOPs for good old it operation management, cloud management. So you'll see the AOPs applied for whole list of, uh, application from observability doing the CMDB, predicting the events insurance. So I see a lot of work clicking for AIOps and AI service desk. What needs to be helped desk with ServiceNow BMC <inaudible> you see a new ALA emerging as a system of intelligence. Uh, the next would be is applying AI with workflow automation. So that's where you'll see a lot of things called customer workflows, employee workflows. So think of what UI path automation, anywhere ServiceNow are doing, that area will be driven with AI workflows. So you'll see AI going >>Off is RPA a company is AI, is RPA a feature of something bigger? Or can someone have a company on RPA UI S one will be at their event this summer? Um, or is it a product company? I mean, I mean, RPA is almost, should be embedded in everything. >>It's a feature. It is very good point. Very, very good thinking. So one is, it's a category for sure. Like, as we thought, it's a category, it's an area where RPA may change the name. I call it much more about automation, workflow automation, but RPA and automation is a category. Um, it's a company also, but that automation should be a, in every area. Yeah. Like we call cloud NA and AI NATO it'll become automation. NA yeah. And that's your thinking. >>It's almost interesting me. I think about the, what you're talking about what's coming to mind is I'm kind having flashbacks to the old software model of middleware. Remember at middleware, it was very easy to understand it was middleware. It sat between two things and then the middle and it was software was action. Now you have all kinds of workflows abstractions everywhere. Right? So multiple databases, it's not a monolithic thing. Right? Right. So as you break that down, is this the new modern middleware? Because what you're talking about is data workflows, but they might be siloed or they integrated. I mean, these are the challenges. This is crazy. What's the, >>So don't about the databases become all polyglot databases. I call this one polyglot automation. So you need automation as a layer, as a category, but you also need to put automation in every area, like, as you were talking about, it should be part of ServiceNow. It should be part of ISRA, like every company, every Salesforce. So that's why you see MuleSoft and Salesforce buying RPA companies. So you'll see all the SaaS companies could cloud companies having an automation as a core. So it's like how you have a database and compute and sales and networking. You'll also will have an automation as a layer <inaudible> inside every stack. >>All right. So I wanna shift gears a little bit and get your perspective on what's going on behind us. You can see, uh, behind us, you got the expo hall. You got, um, we're back to vents, but you got, you know, am Clume Ove, uh, Dynatrace data dog, innovative all the companies out here that we know, we interview them all. They're trying to be suppliers to this growing enterprise market. Right. Okay. But now you also got the entrepreneurial equation. Okay. We're gonna have John Sado on from Deibel later today. He's a former NEA guy and we always talk to Jerry, Jen, we know all the, the VCs. What does the startups look like? What does the state of the, in your mind, cause you, I know you invest the entrepreneurial founder situation. Cloud's bigger. Mm-hmm <affirmative> global, right? Data's part of it. You mentioned data's. Yes. Basically. Data's everything. What's it like for a first an entrepreneur right now who's starting a company. What's the white space. What's the attack plan. How do they get in the market? How do they engineer everything? >>Very good. So I'll give it to, uh, two things that I'm seeing out there. Remember leaders, how Amazon created the startups 15 years back, everybody built on Amazon now, Azure and GCP. The next layer would be is people don't just build on Amazon. They're gonna build it on top of snowflake. Companies are snowflake becomes a data platform, right? People will build on snowflake. Right? So I see my old boss flagman try to build companies on snowflake. So you don't build it just on Amazon. You build it on Amazon and snowflake. Snowflake will become your data store. Snowflake will become your data layer. Right? So I think that's the next level of <inaudible> trying to do that. So if I'm doing observability AI ops, if I'm doing next level of Splunk SIM, I'm gonna build it on snowflake, on Salesforce, on Amazon, on Azure, et cetera. >>It's interesting. You know, Jerry Chan has it put out a thesis of a couple months ago called castles in the cloud where your Mo is what you do in the cloud. Not necessarily in, in the, in the IP. Um, Dave LAN and I had last reinvent, coined the term super cloud, right? He's got a lot of traction and a lot of people throwing, throwing mud at us, but we were, our thesis was, is that what Snowflake's doing? What Goldman S Sachs is doing. You starting to see these clouds on top of clouds. So Amazon's got this huge CapEx advantage, and guys, Charles Fitzgerald out there who we like was kind of shitting on us saying, Hey, you guys terrible, they didn't get it. Like, yeah, I don't think he gets it, but that's a whole, can't wait to debate him publicly on this. <laugh> cause he's cool. Um, but snowflake is on Amazon. Now. They say they're on Azure now. Cause they've got a bigger market and they're public, but ultimately without a AWS snowflake doesn't exist. And, and they're reimagining the data warehouse with the cloud, right? That's the billion dollar opportunity. It >>Is. It is. They both are very tight. So imagine what Frank has done at snowflake and Amazon. So if I'm a startup today, I want to build everything on Amazon where possible whatever is, I cannot build. I'll make the pass layer. Remember the middle layer pass will be snowflake so I can build it on snowflake. I can use them for data layer if I really need to size build it on force.com Salesforce. Yeah. Right. So I think that's where you'll see. So >>Basically the, if you're an entrepreneur, the, the north star in terms of the, the outcome is be a super cloud. >>It is, >>That's the application on another big CapEx ride, the CapEx of AWS or cloud, >>And that reduce your product development, your go to market and you get use the snowflake marketplace to drive your engagement. Yeah. >>Yeah. How are, how is Amazon and the clouds dealing with these big whales, the snowflakes of the world? I mean, I know they got a great relationship, uh, but snowflake now has to run a company they're public. Yeah. So, I mean, I'll say, I think they had Redshift. Amazon has got Redshift. Um, but Snowflake's a big customer in the, they're probably paying AWS, I think big bills too. So >>Joe on very good. Cause it's like how Netflix is and Amazon prime, right. Netflix runs on Amazon, but Amazon has Amazon prime that co-optation will be there. So Amazon will have Redshift, but Amazon is also partnering with, uh, snowflake to have native snowflake data warehouses or data layer. So I think depending on the application use case, you have to use each of the above. I think snowflake is here for a long term. Yeah. Yeah. So if I'm building an application, I want to use snowflake then writing from stats. >>Well, I think that it comes back down to entrepreneurial hustle. Do you have a better product? Right. Product value will ultimately determine it as long as the cloud doesn't, you know, foreclose, your, you that's right with some sort of internal hack. Uh, but I think, I think the general question that I have is that I, I think it's okay to have a super cloud like that because the rising tide is still happening at some point, when does the rising tide stop and do the people shopping up their knives, it gets more competitive or is it just an infinite growth? So >>I think it's growth. You call it cloud scale, you invented the word cloud scale. So I think look, cloud will continually agree, increase. I think there's as long as there more movement from on, uh, OnPrem to the classical data center, I think there's no reason at this point, the rumor, the old lift and shift that's happening in like my business. I see people lift and shifting from the it operations. It helpless, even the customer service service now and, uh, ticket data from BMCs CAS like Microfocus, all those workloads are shifted to the cloud, right? So cloud ticketing system is happening. Cloud system of record is happening. So I think this train has still a long way to go >>Made. I wanna get your thoughts for the folks watching that are, uh, enterprise buyers are practitioners, not suppliers to the more market, feel free to text me or DMing. The next question's really about the buying side, which is if I'm a customer, what's the current, um, appetite for startup products, cuz you know, the big enterprises now and you know, small, medium, large and large enterprise are all buying new companies cuz a startup can go from zero to relevant very quickly. So that means now enterprises are engaging heavily with startups. What's it like what's is there a change in order of magnitude of the relationship between the startup selling to, or growing startup selling to an enterprise? Um, have you seen changes there? I mean I'm seeing some stuff, but why don't get your thoughts on that? What, >>No, it is. If I growing by or 2007 or eight, when I used to talk to you back then and Amazon started very small, right? We are an Amazon summit here. So I think enterprises on the average used to spend nothing with startups. It's almost like 0% or 1% today. Most companies are already spending 20, 30% with startups. Like if I look at a CIO or line of business, it's gone. Yeah. Can it go more? I think it can in the next four, five years. Yeah. Spending on the startups. >>Yeah. And check out, uh, AWS startups.com. That's a site that we built for the startup community for buyers and startups. And I want to get your reaction because I reference the URL cause it's like, there's like a bunch of companies we've been promoting because the solutions that startups have actually are new stuff. Yes. It's bending, it's shifting for security or using data differently or um, building tools and platforms for data engineering. Right. Which is a new persona that's emerging. So you know, a lot of good resources there. Um, and goes back now to the data question. Now, getting back to your, what you're working on now is what's your thoughts around this new, um, data engineering persona, you mentioned AIOps, we've been seeing AIOps IOPS booming and that's creating a new developer paradigm that's right. Which we call coin data as code data as code is like infrastructure is code, but it's for data, right? It's developing with data, right? Retraining machine learnings, going back to the data lake, getting data to make, to do analysis, to make the machine learning better post event or post action. So this, this data engineers like an SRE for data, it's a new, scalable role we're seeing. Do you see the same thing? Do you agree? Um, do you disagree or can you share >>Yourself a lot of first is I see the AIOP solutions in the future should be not looking back. I need to be like we are in San Francisco bay. That means earthquake prediction. Right? I want AOPs to predict when the outages are gonna happen. When there's a performance issue. I don't think most AOPs vendors have not gone there yet. Like I spend a lot of time with data dog, Cisco app Dyna, right? Dynatrace, all this solution. We will go future towards predict to proactive solution with AOPs. But what you bring up a very good point on the data side. I think like we have a Amazon marketplace and Amazon for startup, there should be data exchange where you want to create for AOPs and AI service desk. Customers are give the data, share the data because we thought the data algorithms are useless. I can them, but I gotta train them, modify them, tweak them, make them >>Better, >>Make them better. Yeah. And I think their whole data exchange is the industry has not thought through something you and me talk many times. Yeah. Yeah. I think the whole, that area is very important. >>You've always been on, um, on the Vanguard of data because, uh, it's been really fun. Yeah. >>Going back to big data days back in 2009, you know, >>Look at, look how much data Rick has grown. >>It is. They doubled the >>Key cloud air kinda went private. So good stuff, man. What are you working on right now? Give a, give a, um, plug for what you're working on. You'll still investing. >>I do still invest, but look, I'm a hundred percent on ISRA right now. I'm the CEO there. Yeah. Okay. So right. ISRA is my number one baby right now. So I'm looking at that growing customers and my customers are some of them, you like it's zoom auto desk McAfee, uh, grand to so all the top customers, um, mainly for it help desk customer service. AIOps those are three product lines and going after enterprise and commercial deals. >>And when should someone buy your product? What's what's their need? What category is it? >>I think they look whenever somebody needs to buy the product is if you need AOP solution to predict, keep your lights on predict is one area. If you want to improve employee experience, you are using a slack teams and you want to automate all your workflows. That's another value problem. Third is customer service. You don't want to hire more people to do it. Some of the areas where you want to scale your company, grow your company, eliminate the cost customer service. >>Great stuff, man. Great to see you. Thanks for coming on. Congratulations on the success of your company and your investments. Thanks for coming on the cube. Okay. I'm John fur here at the cube live in San Francisco for day one of two days of coverage of Aish summit 2022. And we're gonna be at Aus summit in San, uh, in New York in the summer. So look for that on this calendar, of course go to eight of us, startups.com. I mentioned that it's decipher all the hot startups and of course the cube.net and Silicon angle.com. Thanks for watching. We'll be back more coverage after this short break. >>Okay. Welcome back everyone. This the cubes coverage here in San Francisco, California, a Davis summit, 2022, the beginning of the event season, as it comes back, little bit smaller footprint, a lot of hybrid events going on, but this is actually a physical event, a summit in new York's coming in the summer. We'll be there too with the cube on the set. We're getting back in the groove psych to be back. We were at reinvent, uh, as well, and we'll see more and more cube, but you're can see a lot of virtual cube outta hybrid cube. We wanna get all those conversations, try to get more interviews, more flow going. But right now I'm excited to have Corey Quinn here on the back on the cube chief cloud economists with bill group. He's the founder, uh, and chief content person always got great angles, fun comedy, authoritative Corey. Great to see you. Thank >>You. Thanks. Coming on. Sure is a lot of words to describe is shit posting, which is how I describe what I tend to do. Most days, >>Shit posting is an art form now. And if you look at mark, Andrew's been doing a lot of shit posting lately. All a billionaires are shit hosting, but they don't know how to do it. Like they're not >>Doing it right? So there's something opportunity there. It's like here's how to be even more obnoxious and incisive. It's honestly the most terrifying scenario for anyone is if I have that kind of budget to throw at my endeavors, it's like, I get excited with a nonsense I can do with a $20 gift card for an AWS credit compared to, oh well, if I could buy a midsize island, do begin doing this from, oh, then we're having fun. >>This shit posting trend. Interesting. I was watching a thread go on about, saw someone didn't get a job because of their shit posting and the employer didn't get it. And then someone on this side I'll hire the guy cuz I get that's highly intelligent shit posting. So for the audience that doesn't know what shit posting is, what is shit posting? >>It's more or less talking about the world of enter prize technology, which even that sentence is hard to finish without falling asleep and toppling out of my chair in front of everyone on the livestream. But it's doing it in such a way that brings it to life that says the quiet part. A lot of the audience is thinking, but generally doesn't say either because they're polite or not a jackass or more prosaically are worried about getting fired for better or worse. I don't don't have that particular constraint, >>Which is why people love you. So let's talk about what you, what you think is, uh, worthy and not worthy in the industry right now, obviously, uh, coupons coming up in Spain, which they're having a physical event, you see the growth of cloud native Amazon's of all the Adams, especially new CEO. Andy's move on to be the chief of all Amazon. Just so I'm the cover of was it time met magazine? Um, he's under a lot of stress. Amazon's changed. Invoice has changed. What's working. What's not, what's rising, what's falling. What's hot. What's not, >>It's easy to sit here and criticize almost anything. These folks do. They're they're effectively in a fishbowl, but I have trouble imagining the logistics. It takes to wind up handling the catering for a relatively downscale event like this one this year, let alone running a 1.7 million employee company having to balance all the competing challenges and pressures and the rest. I, I just can't fathom what it would be like to look at all of AWS. And it's, it's sprawling immense that dominates our entire industry and say, okay, this is a good start, but I, I wanna focus on something with a broader remit. What is that? How do you even get into that position? And you can't win once you're there. All you can do is hold onto the tiger and hope you don't get mold. >>Well, there's a lot of force for good conversations. Seeing a lot of that going on, Amazon's trying to port eight of us is trying to portray themselves as you know, the Pathfinder, you know, you're the pioneer, um, force for good. And I get that and I think that's a good angle as cloud goes mainstream. There's still the question of, we had a guy on just earlier, who was a skydiving instructor and we were joking about the early days of cloud. Like that was like skydiving, build a parachute open, you know, and now same kind of thing. As you move to edge, things are like reliable in some areas, but still new, new fringe, new areas. That's crazy. Well, >>Since the last time we've spoken, uh, Steve Schmidt is now the CISO for all of Amazon and his backfill replacement. The AWS CISO is CJ. Moses who as a hobby races, a as a semi-pro race car driver to my understanding, which either, I don't know what direction to take that in either. This is what he does to relax or ultimately, or ultimately it's. Huh? That, that certainly says something about risk assessment. I'm not entirely sure what, but okay. <laugh> either way, sounds like more exciting. Like I better >>Have a replacement ready <laugh> I, in case something goes wrong on the track, highly >>Available >>CSOs. I gotta say one of the things I do like in the recent trend is that the tech companies are getting into the formula one, which I was never a fan of until I watched that Netflix series. But when you look at the formula one, it's pretty cool. Cause it's got some tech angles, I get the whole data instrumentation thing, but the most coolest thing about formula one is they have these new rigs out. Yeah. Where you can actually race in east sports with other people in pure simulation of the race car. You gotta get the latest and videographic card, but it's basically a tricked out PC with amazing monitors and you have all the equipment of F1 and you're basically simulating racing. >>Oh, it's great too. And I can see the appeal of these tech companies getting into it because these things are basically rocket shifts. When those cars go, like they're sitting there, we can instrument every last part of what is going on inside that vehicle. And then AWS crops up. And we can bill on every one of those dimensions too. And it's like slow down their hasty pudding one step at a time. But I do see the appeal. >>So I gotta ask you about, uh, what's going on in your world. I know you have a lot of great success. We've been following you in the queue for many, many years. Got a great newsletter, check out Corey Quinn's newsletter, uh, screaming in the cloud program. Uh, you're on the cutting edge and you've got a great balance between really being snarky and, and, and really being delivering content. That's exciting, uh, for people, uh, with a little bit of an edge, um, how's that going? Uh, what's the blowback, any blowback late? Has there been uptick? What was, what are some of the things you're hearing from your audience, more Corey, more Corey. And then of course the, the PR team's calling you >>The weird thing about having an audience beyond a certain size is far and away as a landslide. The most common response I get is silence where it's high. I'm emailing an awful lot of people at last week in AWS every week and okay. They must not have heard me it. That is not actually true. People just generally don't respond to email because who responds to email newsletters. That sounds like something, a lunatic might do same story with response to live streams and podcasts. It's like, I'm gonna call into that am radio show and give them a piece of my mind. People generally don't do >>That. We should do that. Actually. I think you're people would call in, oh, >>I, I think >>I guarantee we had that right now. People would call in and say, Corey, what do you think about X? >>Yeah. It not, everyone understands the full context of what I do. And in fact, increasingly few people do and that's fine. I, I keep forgetting that sometimes people do not see what I'm doing in the same light that I do. And that's fine. Blowback has been largely minimal. Honestly, I am surprised about anything by how little I have gotten over the last five years of doing this, but it would be easier to dismiss me if I weren't generally. Right. When, okay, so you launch this new service and it seems pretty crappy to me cuz when I try and build something, it falls over and begs for help. And people might not like hearing that, but it's what customers are finding too. Yeah. I really am the voice of the >>Customer. You know, I always joke with Dave Alane about how John Fort's always at, uh, um, reinvent getting the interview with jazzy now, Andy we're there, you're there. And so we have these rituals at the events. It's all cool. Um, one of the rituals I like about your, um, your content is you like to get on the naming product names. Um, and, and, and, and, and kind of goof on that. Now why I like is because I used to work at ETT Packard where they used to name things as like engineers, HP 1 0, 0 5, or we can't call, we >>Have a new monitor. How are we gonna name it? Throw the wireless keyboard down the stairs again. And then there you go. Yeah. >>It's and the old joke at HP was if they, if they invented SU sushi, they'd say, yeah, we can't call sushi. It's cold, dead fish. That's what it is. And so the joke was cold. Dead fish is a better name than sushi. So you know is fun. So what's the, what are the, how's the Amazon doing in there? Have they changed their naming, uh, strategy, uh, on some of their, their >>Producting. So they're going in different directions. When they named Amazon Aurora, they decided to explore a new theme of Disney princesses as they go down those paths. And some things are more descriptive. Some people are clearly getting bonused on number of words, they can shove into it. Like the better a service is the longer it's name. Like AWS systems manager, session manager is a great one. I love the service ridiculous name. They have a systems manager, parameter store, which is great. They have secrets manager, which does the same thing. It's two words less, but that one costs money in a way that systems manage your parameter store does not. It's fun. >>What's your, what's your favorite combination of acronyms >>Combination >>Of gots. You got EMR, you got EC two, you got S3 SQS. Well, RedShift's not an acronym you >>Gets is one of my personal favorites because it's either elastic block store or elastic bean stock, depending entirely on the context of the conversation, they >>Shook up bean stock or is that still around? Oh, >>They never turn anything off. They're like the anti Google, Google turns things off while they're still building it. Whereas Amazon is like, well, we built this thing in 2005 and everyone hates it, but while we certainly can't change it, now it has three customers on it. John three <laugh>. Okay. Simple BV still haunts our dreams. >>I, I actually got an email on, I saw one of my, uh, servers, all these C twos were being deprecated and I got an email I'm I couldn't figure out. Why can you just like roll it over? Why, why are you telling me? Just like, give me something else. All right. Okay. So let me talk about, uh, the other things I want to ask you, is that like, okay. So as Amazon better in some areas where do they need more work in your opinion? Because obviously they're all interested in new stuff and they tend to like put it out there for their end to end customers. But then they've got ecosystem partners who actually have the same product. Yes. And, and this has been well documented. So it's, it's not controversial. It's just that Amazon's got a database Snowflake's got out database service. So Redshift, snowflake data breach is out there. So you got this co-op petition. Yes. How's that going? And what do you hearing about the reaction to any of that stuff? >>Depends on who you ask. They love to basically trot out a bunch of their partners who will say nice things about them. And it very much has heirs of, let's be honest, a hostage video, but okay. Cuz these companies do partner with, and they cannot afford to rock the boat too far. I'm not partnered with anyone. I can say what I want. And they're basically restricted to taking away my birthday at worse so I can live with that. >>All right. So I gotta ask about multicloud. Cause obviously the other cloud shows are coming up. Amazon hated that word multicloud. Um, a lot of people though saying, you know, it's not a real good marketing word. Like multicloud sounds like, you know, root canal. Mm-hmm <affirmative> right. So is there a better description for multicloud? >>Multiple single >>Cloudant loves that term. Yeah. >>You know, you're building in multiple single points of failure, do it for the right reasons or don't do it as a default. I believe not doing it is probably the right answer. However, and if I were, if I were Amazon, I wouldn't want to talk about my multi-cloud either as the industry leader, let's talk about other clouds, bad direction to go in from a market cap perspective. It doesn't end well for you, but regardless of what they want to talk about, or don't want to talk about what they say, what they don't say, I tune all of it out. And I look at what customers are doing and multi-cloud exists in a variety of forms. Some brilliant, some brain dead. It depends a lot on, but my general response is when someone gets on stage from a company and tells me to do a thing that directly benefits their company. I am skeptical at best. Yeah. When customers get on stage and say, this is what we're doing because it solves problems. That's when I shut up and listen. >>Yeah, course. Awesome. Corey, I gotta ask you a question cause I know you we've been, you know, fellow journeyman and the, and the cloud journey going to all the events and then the pandemic hit. We now in the third year, who knows what it's gonna gonna end. Certainly events are gonna look different. They're gonna be either changing footprint with the virtual piece, new group formations. Community's gonna emerge. You've got a pretty big community growing and it's growing like crazy. What's the weirdest or coolest thing or just big changes you've seen with the pandemic, uh, from your perspective, cuz you've been in the you're in the middle of the whitewater rafting. You've seen the events you circle offline. You saw the online piece, come in, you're commentating, you're calling balls and strikes in the industry. You got a great team developing over there. Duck build group. What's the big aha moment that you saw with the pandemic. Weird, funny, serious, real in the industry and with customers what's >>Accessibility. Reinvent is a great example. When in the before times it's open to anyone who wants to attend, who can pony up two grand and a week in Las Vegas and get to Las Vegas from wherever they happen to be by moving virtually suddenly it, it embraces the reality that talent is evenly. Distributed. Opportunity is not. And that means that suddenly these things are accessible to a wide swath of audience and potential customer base and the rest that hadn't been invited to the table previously, it's imperative that we not lose that. It's nice to go out and talk to people and have people come up and try and smell my hair from time to time, I smelled delightful. Let me assure you. But it was, but it's also nice to be. >>I have a product for you if you want, you know? Oh, >>Oh excellent. I look forward to it. What is it? Pudding? Why not? <laugh> >>What else have you seen? So when accessibility for talent. Yes. Which by the way is totally home run. What weird things have happened that you've seen? Um, that's >>Uh, it's, it's weird, but it's good that an awful lot of people giving presentation have learned to tighten their message and get to the damn point because most people are not gonna get up from a front row seat in a conference hall, midway through your Aing talk and go somewhere else. But they will change a browser tab and you won't get them back. You've gotta be on point. You've gotta be compelling if it's going to be a virtual discussion. Yeah. >>And you turn off your iMessage too. >>Oh yes. It's always fun in the, in the meetings when you're ho to someone and their colleague is messaging them about, should we tell 'em about this? And I'm sitting there reading it and it's >>This guy is really weird. Like, >>Yes I am and I bring it into the conversation and then everyone's uncomfortable. It goes, wow. Why >>Not? I love when my wife yells at me over I message. When I'm on a business call, like, do you wanna take that about no, I'm good. >>No, no. It's better off. I don't the only entire sure. It's >>Fine. My kids text. Yeah, it's fine. Again, that's another weird thing. And, and then group behavior is weird. Now people are looking at, um, communities differently. Yes. Very much so, because if you're fatigued on content, people are looking for the personal aspect. You're starting to see much more of like yeah. Another virtual event. They gotta get better. One and two who's there. >>Yeah. >>The person >>That's a big part of it too is the human stories are what are being more and more interesting. Don't get up here and tell me about your product and how brilliant you are and how you built it. That's great. If I'm you, or if I wanna work with you or I want to compete with you or I want to put on my engineering hat and build it myself. Cause why would I buy anything? That's more than $8. But instead, tell me about the problem. Tell me about the painful spot that you specialize in. Yeah. Tell me a story there. >>I, I think >>That gets a glimpse in a hook and makes >>More, more, I think you nailed it. Scaling storytelling. Yes. And access to better people because they don't have to be there in person. I just did a thing. I never, we never would've done the queue. We did. Uh, Amazon stepped up in sponsors. Thank you, Amazon for sponsoring international women's day, we did 30 interviews, APAC. We did five regions and I interviewed this, these women in Asia, Pacific eight, PJ, they call for in this world. And they're amazing. I never would've done those interviews cuz I never, would've seen 'em at an event. I never would've been in pan or Singapore, uh, to access them. And now they're in the index, they're in the network. They're collaborating on LinkedIn. So a threads are developing around connections that I've never seen before. Yes. Around the content. >>Absolutely >>Content value plus and >>Effecting. And that is the next big revelation of this industry is going to realize you have different companies. And, and I Amazon's case different service teams all competing with each other, but you have the container group and you have the database group and you have the message cuing group. But customers don't really want to build things from spare parts. They want a solution to a problem. I want to build an app that does Twitter for pets or whatever it is I'm trying to do. I don't wanna basically have to pick and choose and fill my shopping cart with all these different things. I want something that's gonna basically give me what I'm trying to get as close to turnkey as possible. Moving up the stack. That is the future. And just how it gets here is gonna be >>Well we're here at Corey Quinn, the master of the master of content here in the a ecosystem. Of course we we've been following up from the beginning. His great guy, check out his blog, his site, his newsletter screaming podcast. Corey, final question for, uh, what are you here doing? What's on your agenda this week in San Francisco and give a plug for the duck build group. What are you guys doing? I know you're hiring some people what's on the table for the company. What's your focus this week and put a plug in for the group. >>I'm here as a customer and basically getting outta my cage cuz I do live here. It's nice to actually get out and talk to folks who are doing interesting things at the duck bill group. We solved one problem. We fixed the horrifying AWS bill, both from engineering and architecture, advising as well as negotiating AWS contracts because it turns out those things are big and complicated. And of course my side media projects last week in aws.com, we are, it it's more or less a content operation where I in my continual and ongoing love affair with the sound of my own voice. >><laugh> and you're good. It's good content it's on, on point fun, Starky and relevant. So thanks for coming to the cube and sharing with us. Appreciate it. No >>Thank you button. >>You. Okay. This the cube covers here in San Francisco, California, the cube is back going to events. These are the summits, Amazon web services summits. They happen all over the world. We'll be in New York and obviously we're here in San Francisco this week. I'm John fur. Keep, keep it right here. We'll be back with more coverage after this short break. Okay. Welcome back everyone. This's the cubes covers here in San Francisco, California, we're live on the show floor of AWS summit, 2022. I'm John for host of the cube and remember AWS summit in New York city coming up this summer, we'll be there as well. And of course reinvent the end of the year for all the cube coverage on cloud computing and AWS two great guests here from the APN global APN Sege chef Jenko and Jeff Grimes partner lead Jeff and Sege is doing partnerships global APN >>AWS global startup program. Yeah. >>Okay. Say that again. >>AWS. We'll start >>Program. That's the official name. >>I love >>It too long, too long for me. Thanks for coming on. Yeah, >>Of course. >>Appreciate it. Tell us about what's going on with you guys. What's the, how was you guys organized? You guys we're obviously we're in San Francisco bay area, Silicon valley, zillions of startups here, New York. It's got another one we're gonna be at tons of startups. A lot of 'em getting funded, big growth and cloud big growth and data secure hot in all sectors. >>Absolutely. >>So maybe, maybe we could just start with the global startup program. Um, it's essentially a white glove service that we provide to startups that are built on AWS. And the intention there is to help identify use cases that are being built on top of AWS. And for these startups, we want to pro vibe white glove support in co building products together. Right. Um, co-marketing and co-selling essentially, um, you know, the use cases that our customers need solved, um, that either they don't want to build themselves or are perhaps more innovative. Um, so the, a AWS global startup program provides white glove support. Dedicat at headcount for each one of those pillars. Um, and within our program, we've also provided incentives, programs go to market activities like the AWS startup showcase that we've built for these startups. >>Yeah. By the way, AWS startup, AWS startups.com is the URL, check it out. Okay. So partnerships are key. Jeff, what's your role? >>Yeah. So I'm responsible for leading the overall effort for the AWS global startup program. Um, so I've got a team of partner managers that are located throughout the us, uh, managing a few hundred startup ISVs right now. <laugh> >>Yeah, you got a >>Lot. We've got a lot. >>There's a lot. I gotta, I gotta ask a tough question. Okay. I'm I'm a startup founder. I got a team. I just got my series a we're grown. I'm trying to hire people. I'm super busy. What's in it for me. Yeah. What do you guys bring to the table? I love the white glove service, but translate that what's in it for what do I get out of it? What's >>A story. Good question. I focus, I think. Yeah, because we get, we get to see a lot of partners building their businesses on AWS. So, you know, from our perspective, helping these partners focus on what, what do we truly need to build by working backwards from customer feedback, right? How do we effectively go to market? Because we've seen startups do various things, um, through trial and error, um, and also just messaging, right? Because oftentimes partners or rather startups, um, try to boil the ocean with many different use cases. So we really help them, um, sort of laser focus on what are you really good at and how can we bring that to the customer as quickly as possible? >>Yeah. I mean, it's truly about helping that founder accelerate the growth of their company, right. And there's a lot that you can do with AWS, but focus is truly the key word there because they're gonna be able to find their little piece of real estate and absolutely deliver incredible outcomes for our customers. And then they can start their growth curve there. >>What are some of the coolest things you've seen with the APN that you can share publicly? I know you got a lot going on there, a lot of confidentiality. Um, but you know, we're here a lot of great partners on the floor here. I'm glad we're back at events. Uh, a lot of stuff going on digitally with virtual stuff and, and hybrid. What are some of the cool things you guys have seen in the APN that you can point to? >>Yeah, absolutely. I mean, I can point to few, you can take them. So, um, I think what's been fun over the years for me personally, I came from a startup brand sales at an early stage startup and, and I went through the whole thing. So I have a deep appreciation for what these guys are going through. And what's been interesting to see for me is taking some of these early stage guys, watching them progress, go public, get acquired and see that big day mm-hmm <affirmative>, uh, and being able to point to very specific items that we help them to get to that point. Uh, and it's just a really fun journey to watch. >>Yeah. I, and part of the reason why I really, um, love working at the AWS, uh, global startup program is working with passionate founders. Um, I just met with a founder today that it's gonna, he's gonna build a very big business one day, um, and watching them grow through these stages and supporting that growth. Um, I like to think of our program as a catalyst for enterprise is sort of scale. Yeah. Um, and through that we provide visibility, credibility and growth opportunities. >>Yeah. A lot, a lot of partners too. What I found talking to staff founders is when they have that milestone, they work so hard for it. Whether it's a B round C round Republic or get bought. Yeah. Um, then they take a deep breath and they look back at wow, what a journey it's been. So it's kind of emotional for sure. But still it's a grind. Right? You gotta, I mean, when you get funding, it's still day one. You don't stop. It's no celebrate, you got a big round or valuation. You still gotta execute >>And look it's hypercompetitive and it's brutally difficult. And our job is to try to make that a little less difficult and navigate those waters. Right. Where ever everyone's going after similar things. >>Yeah. And I think as a group element too, I observe that startups that I, I meet through the APN has been interesting because they feel part of AWS. Yeah, totally. As a group of community, as a vibe there. Um, I know they're hustling, they're trying to make things happen. But at the same time, Amazon throws a huge halo effect. I mean, that's a huge factor. I mean, you guys are the number one cloud in the business, the growth in every sector is booming. Yeah. And if you're a startup, you don't have that luxury yet. And look at companies like snowflake that built on top of AWS. I mean, people are winning by building on AWS. >>Yeah. And our, our, our program really validates their technology first. So we have, what's all the foundation's technical review that we put all of our startups through before we go to market. So that when enterprise customers are looking at startup technology, they know that it's already been vetted. And, um, to take that a step further and help these partners differentiate, we use programs like the competency programs, the DevOps competencies, the security competency, which continues to help, um, provide sort of a platform for these startups, help them differentiate. And also there's go to market benefits that are associated with that. >>Okay. So let me ask the, the question that's probably on everyone's mind, who's watching, certainly I asked this a lot. There's a lot of companies startups out there who makes the cut, is there a criteria cut? It's not like it's sports team or anything, but like sure. Like there's activate program, which is like, there's hundreds of thousands of startups out there. Not everyone is at the APN. Right? Correct. So ISVs again, that's a whole nother, that's a more mature partner that might have, you know, huge market cap or growth. How, how do you guys focus? How do you guys focus? I mean, you got a good question, you know, thousand flowers blooming all the time. Is there a new way you guys are looking at it? I know there's been some talk about restructure or, or new focus. What's the focus. >>Yeah. It's definitely not an easy task by any means. Um, but you know, I recently took over this role and we're really trying to establish focus areas, right. So obviously a lot of the ISVs that we look after are infrastructure ISVs. That's what we do. Uh, and so we have very specific pods that look after different type of partners. So we've got a security pod, we've got a DevOps pod, we've got core infrastructure, et cetera. And really, we're trying to find these ISVs that can solve, uh, really interesting AWS customer. >>You guys have a deliberate, uh, focus on these pillars. So what infrastructure, >>Security, DevOps, and data and analytics, and then line of business >>Line, business line business, like web >>Marketing, business apps, >>Owner type thing. Exactly. >>Yeah, exactly. >>So solutions there. Yeah. More solutions and the other ones are like hardcore. So infrastructure as well, like storage back up ransomware kind of stuff, or, >>Uh, storage, networking. >>Okay. Yeah. The classic >>Database, et cetera. Right. >>And so there's teams on each pillar. >>Yep. So I think what's, what's fascinating for the startups that we cover is that they've got, they truly have support from a build market sell perspective, right. So you've got someone who's technical to really help them get the technology, figured out someone to help them get the marketing message dialed and spread, and then someone to actually do the co-sell, uh, day to day activities to help them get in front of customers. >>Probably the number one request that we always ask for Amazon is can wish that sock report, oh, download it on the console, which we use all the time. <laugh> exactly. But security's a big deal. I mean, you know, ask the res are evolving, that role of DevOps is taking on dev SecOps. Um, I, I can see a lot of customers having that need for a relationship to move things faster. Do you guys provide like escalation or is that a part of a service or that not part of, uh, uh, >>Yeah, >>So the partner development manager can be an escalation for absolutely. Think of that. 'em as an extension of your business inside of AWS. >>Great. And you guys, how is that partner managers, uh, measure >>On those three pillars? Right. Got it. Are we billing, building valuable use cases? So product development go to market, so go to market activities, think blog, posts, webinars, case studies, so on and so forth. And then co-sell not only are we helping these partners win their current opportunities that they are sourcing, but can we also help them source net new deals? Yeah. Right. That's very, >>I mean, top asked from the partners is get me in front of customers. Right. Um, not an easy task, but that's a huge goal of ours to help them grow their top line. >>Right. Yeah. In fact, we had some interviews here on the cube earlier talking about that dynamic of how enterprise customers are buying. And it's interesting, a lot more POCs. I have one partner here that you guys work with, um, on observability, they got a huge POC with capital one mm-hmm <affirmative> and the enterprises are engaging the star ups and bringing them in. So the combination of open source software enterprises are leaning into that hard and bringing young growing startups in mm-hmm <affirmative>. Yep. So I could see that as a huge service that you guys can bring people in. >>Right. And they're bringing massively differentiated technology to the table. The challenge is they just might not have the brand recognition. The, at the big guys have mm-hmm <affirmative>. And so that's, our job is how do you get that great tech in front of the right situations? >>Okay. So my next question is about the show here, and then we'll talk globally. So here in San Francisco sure. You know, Silicon valley bay area, San Francisco bay area, a lot of startups, a lot of VCs, a lot of action. Mm-hmm <affirmative> so probably a big market for you guys. Yeah. So what's exciting here in SF. And then outside of SF, you guys have a global pro, have you see any trends that are geography based or is it sure areas more mature? There's certain regions that are better. I mean, I just interviewed a company here. That's doing, uh, a AWS edge really well in these cases. It's interesting that these, the partners are filling a lot of holes and gaps in the opportunities with a AWS. So what's exciting here. And then what's the global perspective. >>Yeah, totally. So obviously see a ton of partners from the bay area that we support. Um, but we're seeing a lot of really interesting technology come out of AMEA specifically. Yeah. Uh, and making a lot of noise here in the United States, which is great. Um, and so, you know, we definitely have that global presence and, and starting to see super differentiated technology come out of those regions. >>Yeah. Especially Tel Aviv. Yeah. >>Amy and real quick before you get into surge. It's interesting. The VC market in, in Europe is hot. They've got a lot of unicorns coming in. We've seen a lot of companies coming in. They're kind of rattling their own, you know, cage right now. Hey, look at us. Let's see if they crash, you know, but we don't see that happening. I mean, people have been predicting a crash now in, in the startup ecosystem for least a year. It's not crashing. In fact, funding's up. >>Yeah. The pandemic was hard on a lot of startups for sure. Yeah. Um, but what we've seen is many of these startups, they, as quickly as they can grow, they can also pivot as, as, as well. Um, and so I've actually seen many of our startups grow through the demo because their use cases are helping customers either save money, become more operationally efficient and provide value to leadership teams that need more visibility into their infrastructure during a pandemic. >>It's an interesting point. I talked to Andy jazzy and Adam Celski both say the same thing during the pandemic. Necessity's the mother of all invention. Yep. And startups can move fast. So with that, you guys are there to assist if I'm a startup and I gotta pivot cuz remember iterate and pivot, iterate and pivot. So you get your economics, that's the playbook of the ventures and the models. >>Exactly. How >>Do you guys help me do that? Give me an example of what me through. Pretend me, I'm a start up. Hey, I'm on the cloud. Oh my God. Pandemic. They need video conferencing. Hey cube. Yeah. What do I need? Search? What, what do >>I do? That's a good question. First thing is just listen. Yeah. I think what we have to do is a really good job of listening to the partner. Um, what are their needs? What is their problem statement? Where do they want to go at the end of the day? Um, and oftentimes because we've worked with, so how many successful startups that have come out of our program, we have, um, either through intuition or a playbook determined what is gonna be the best path forward and how do we get these partners to stop focusing on things that will eventually, um, just be a waste of time. Yeah. And, or not provide, or, you know, bring any fruit to the table, which, you know, essentially revenue. >>Well, we love startups here in the cube because one, um, they have good stories, they're oil and cutting edge, always pushing the envelope and they're kind of disrupting someone else. Yeah. And so they, they have an opinion. They don't mind sharing on camera. So love talking to startups. We love working with you guys on our startups. Showcases startups.com. Check out AWS startups.com and she got the showcase. So is, uh, final word. I'll give you guys the last word. What's the bottom line bumper sticker for AP globe. The global APN program summarize the opportunity for startups, what you guys bring to the table and we'll close it out. Totally. We'll start >>With you. Yeah. I think the AWS global startup programs here to help companies truly accelerate their business full stop. Right. And that's what we're here for. Love it. >>It's a good way to, it's a good way to put it. Dato yeah. >>All right. Thanks for coming out. Thanks John. Great to see you love working with you guys. Hey, startups need help. And the growing and huge market opportunities, the shift cloud scale data engineering, security infrastructure, all the markets are exploding in growth because of the digital transformation of realities here, open source and cloud. I'll making it happen here in the cube in San Francisco, California. I'm John furrier, your host. Thanks for >>Watching Cisco, John. >>Hello and welcome back to the Cube's live coverage here in San Francisco, California for AWS summit, 2022. I'm John for host of the cube. Uh, two days of coverage, AWS summit, 2022 in New York city coming up this summer will be there as well. Events are back. The cube is back of course, with the cube virtual cube hybrid, the cube.net. Check it out a lot of content this year more than ever a lot more cloud data cloud native, modern applic is all happening. Got a great guest here. Jeremy Burton, Cub alumni, uh, CEO of observe Inc in the middle of all the cloud scale, big data observability, Jeremy. Great to see you. Thanks. >>Coming on. Always great to come and talk to you on the queue, man. It's been been a few years, so, >>Um, well you, you got your hands. You're in the trenches with great startup, uh, good funding, great board, great people involved in the observability Smith hot area, but also you've been a senior executive president of Dell EMC. Um, 11 years ago you had a vision and you actually had an event called cloud meets big data. Um, yeah. And it's here, you predicted it 11 years ago. Um, look around it's cloud meets big data. >>Yeah. I mean the, the cloud thing I think, you know, was, was probably already a thing, but the big data thing I do claim credit for, for sort of catching that bus early, um, you know, we, we were on the, the, the bus early and, and I think it was only inevitable. Like, you know, if you could bring the economics and the compute of cloud to big data, you, you could find out things you could never possibly imagine. >>So you're close to a lot of companies that we've been covering deeply snowflake, obviously you involved, uh, at the board level, the other found, you know, the people there, uh, cloud, you know, Amazon, you know, what's going on here? Yeah. You're doing a startup as the CEO at the helm, uh, chief of observ, Inc, which is an observability, which is to me in the center of this confluence of data engineering, large scale integrations, um, data as code integrating into applications. I mean, it's a whole nother world developing, like you see with snowflake, it means snowflakes is super cloud as we call it. So a whole nother wave is here. What's your, what's this wave we're on what's how would you describe the wave? >>Well, a couple of things, I mean, people are, I think right in more software than, than ever before are why? Because they've realized that if, if you don't take your business online and offer a service, then you become largely irrelevant. And so you you've got a whole set of new applications. I think, I think more applications now than any point. Um, not, not just ever, but the mid nineties, I always looked at as the golden age of application development. Now, back then people were building for windows. Well, well now they're building for things like AWS is now the platform. Um, so you've got all of that going on. And then at the same time, the, the side effect of these applications is they generate data and lots of data. And the, you know, there's sort of the transactions, you know, what you bought today are something like that. But then there's what we do, which is all the telemetry, all the exhaust fumes. And I think people really are realizing that their differentiation is not so much their application. It's their understanding of the data. Can, can I understand who my best customers are, what I sell today. If people came to my website and didn't buy, then why not? Where did they drop off all of that? They wanna analyze. And, and the answers are all in the data. The question is, can you understand it >>In our last startup showcase, we featured data as code one of the insights that we got out of that, and I wanna get your opinion on our reaction to is, is that data used to be put into a data lake and turns into a data swamp or throw into the data warehouse. And then we'll do some queries, maybe a report once in a while. And so data, once it was done, unless it was real time, even real time was not good anymore after real time. That was the old way. Now you're seeing more and more, uh, effort to say, let's go look at the data, cuz now machine learning is getting better. Not just train once mm-hmm <affirmative> they're iterating. Yeah. This notion of iterating and then pivoting, iterating and pivoting. Yeah, that's a Silicon valley story. That's like how startups work, but now you're seeing data being treated the same way. So now you have another, this data concept that's now yeah. Part of a new way to create more value for the apps. So this whole, this whole new cycle of >>Yeah. >>Data being reused and repurposed and figured out and yeah, >>Yeah. I'm a big fan of, um, years ago. Uh, uh, just an amazing guy, Andy McAfee at the MIT C cell labs I spent time with and he, he had this line, which still sticks to me this day, which is look I'm I'm. He said I'm part of a body, which believes that everything is a matter of data. Like if you have enough data, you can answer any question. And, and this is going back 10 years when he was saying these kind of things and, and certainly, you know, research is on the forefront. But I think, you know, starting to see that mindset of the, the sort of MIT research be mainstream, you know, in enterprises, they they're realizing that. Yeah, it is about the data. You know, if I can better understand my data better than my competitor, then I've got an advantage. And so the question is is, is how, what, what technologies and what skills do I need in my organization to, to allow me to do that. >>So let's talk about observing you the CEO of, okay. Given you've seen the ways before you're in the front lines of observability, which again is in the center of all this action what's going on with the company. Give a quick minute to explain, observe for the folks who don't know what you guys do. What's the company doing? What's the funding status, what's the product status and what's the customer status. Yeah. >>So, um, we realized, you know, a handful of years ago, let's say five years ago that, um, look, the way people are building applications is different. They they're way more functional. They change every day. Uh, but in some respects they're a lot more complicated. They're distributed. They, you know, microservices architectures and when something goes wrong, um, the old way of troubleshooting and solving problems was not gonna fly because you had SA so much change going into production on a daily basis. It was hard to tell like where the problem was. And so we thought, okay, it's about time. Somebody looks at the exhaust fumes from this application and all the telemetry data and helps people troubleshoot and make sense of the problems that they're seeing. So, I mean, that's observability, it's actually a term that goes back to the 1960s. It was a guy called, uh, Rudolph like, like everything in tech, you know, it's, it's a reinvention of something from years gone by. >>Um, there's a guy called, um, Rudy Coleman in 1960s coiner term and, and, and the term was being able to determine the state of a system by looking at its external outputs. And so we've been going on this for, uh, the best part of four years now. Um, it took us three years just to build the product. I think, I think what people don't appreciate these days often is the barrier to entry in a lot of these markets is quite high. You, you need a lot of functionality to have something that's credible with a customer. Um, so yeah, this last year we, we, we did our first year selling, uh, we've got about 40 customers now. Um, we just we've got great investors for the hill ventures. Uh, I mean, Mike SP who was, you know, the, the guy who was the, really, the first guy in it snowflake and the, the initial investor were fortunate enough to, to have Mike and our board. And, um, you know, part of the observed story is closely knit with snowflake all of that time with your data, you know, we, we store in there. >>So I want to get, uh, yeah. Pivot to that. Mike SP snowflake, Jeremy Burton, the cube kind of, kind of same thinking this idea of a super cloud or what snowflake became. Yeah. Snowflake is massively successful on top of AWS. Mm-hmm <affirmative> and now you're seeing startups and companies build on top of snowflake. Yeah. So that's become an entrepreneurial story that we think that to go big in the cloud, you can have a cloud on a cloud, uh, like as Jerry, Jerry Chan and Greylock calls it, castles in the cloud where there are moats in the cloud. So you're close to it. I know you, you're doing some stuff with snowflake. So as a startup, what's your view on building on top of say a snowflake or an AWS, because again, you gotta go where the data is. You need all the data. >>Yeah. So >>What's your take on that? I mean, >>Having enough gray hair now, um, you know, again, in tech, I think if you wanna predict the future, look at the past. And, uh, you know, 20 years ago, 25 years ago, I was at a, a smaller company called Oracle and an Oracle was the database company. And, uh, their, their ambition was to manage all of the world's transactional data. And they built on a platform or a couple of platforms, one, one windows, and the other main one was Solaris. And so at that time, the operating system was the platform. And, and then that was the, you know, ecosystem that you would compete on top of. And then there were companies like SAP that built applications on top of Oracle. So then wind the clock forward 25 years gray hairs. <laugh> the platform, isn't the operating system anymore. The platform is AWS, you know, Google cloud. I gotta probably look around if I say that in. Yeah, >>It's okay. Columbia, but hyperscale. Yeah. CapX built out >>That is the new platform. And then snowflake comes along. Well, their aspiration is to manage all of the, not just human generated data, but machine generated data in the world of cloud. And I think they they've done an amazing job are doing for the, I'd say, say the, the big data world, what Oracle did for the relational data world, you know, way back 25 years ago. And then there are folks like us come along and, and of course my ambition would be, look, if, if we can be as successful as an SAP building on top of snowflake, uh, as, as they were on top of Oracle, then, then we'd probably be quite happy, >>Happy. So you're building on top of snowflake, >>We're building on top of snowflake a hundred percent. And, um, you know, I've had folks say to me, well, aren't you worried about that? Isn't that a risk? It's like, well, that that's a risk. You're >>Still on the board. >>Yeah. I'm still on the board. Yeah. That's a risk I'm prepared to take. I am more on snowing. >>It sounds well, you're in a good spot. Stay on the board, then you'll know what's going on. Okay. No, yeah. Serious one. But the, this is a real dynamic. It is. It's not a one off its >>Well, and I do believe as well that the platform that you see now with AWS, if you look at the revenues of AWS is in order of magnitude, more than Microsoft was 25 years ago with windows mm-hmm <affirmative>. And so I've believe the opportunity for folks like snowflake and, and folks like observe it. It's an order of magnitude more than it was for the Oracle and the SAPs of the old world. >>Yeah. And I think this is really, I think this is something that this next generation of entrepreneurship is the go big scenario is you gotta be on a platform. Yeah. >>It's quite easy >>Or be the platform, but it's hard. There's only like how seats were at that table left >>Well value migrates up over time. So, you know, when the cloud thing got going, there were probably 10, 20, 30, you know, rack space and there's 1,000,001 infrastructure, a service platform as a service. My, my old, uh, um, employee EMC, we had pivotal, you know, pivotal was a platform as a service. Don't hear so much about it these days, but initially there's a lot of players and then it consolidates. And then to, to like extract, uh, a real business, you gotta move up, you gotta add value, you gotta build databases, then you gotta build applications. So >>It's interesting. Moving from the data center of the cloud was a dream for starters within if the provision, the CapEx. Yeah. Now the CapEx is in the cloud. Then you build on, on top of that, you got snowflake. Now you got on top of that. >>The assumption is almost that compute and storage is free. I know it's not quite free. Yeah. It's almost free, but you can, you know, as an application vendor, you think, well, what can I do if I assume compute and storage is free, that's the mindset you've gotta get >>Into. And I think the platform enablement to value. So if I'm an entrepreneur, I'm gonna get a series us multiple of value in what I'm paying. Yeah. Most people don't even blanket their Avis pills unless they're like massively huge. Yeah. Then it's a repatriation question or whatever discount question, but for most startups or any growing company, the Amazon bill should be a small factor. >>Yeah. I mean, a lot of people, um, ask me, uh, like, look you build in on snowflake. Um, you, you know, you, you, you're gonna be, you're gonna be paying their money. How, how, how, how does that work with your business model? If you're paying their money, you know, do, do you have a viable business? And it's like, well, okay. I, we could build a database as well and observe, but then I've got half the development team working on something that will never be as good as snowflake. And so we made the call early on that. No, no, we, we want a eight above the database. Yeah. Right. Snowflake are doing a great job of innovating on the database and, and the same is true of something like Amazon, like, like snowflake could have built their own cloud and their own platform, but they didn't. >>Yeah. And what's interesting is that Dave <inaudible> and I have been pointing this out and he's obviously a more on snowflake. I've been looking at data bricks, um, and the same dynamics happening, the proof is the ecosystem. Yeah. I mean, if you look at Snowflake's ecosystem right now and data bricks it's exploding. Right. I mean, the shows are selling out the floor. Space's book. That's the old days at VMware. Yeah. The old days at AWS. >>Well, and for snowflake and, and any platform from VI, it's a beautiful thing because, you know, we build on snowflake and we pay them money. They don't have to sell to us. Right. And we do a lot of the support. And so the, the economics work out really, really well. If you're a platform provider and you've got a lot of >>Ecosystems. Yeah. And then also you get, you get a, um, a trajectory of, uh, economies of scale with the institutional knowledge of snowflake integrations, right. New product, you're scaling a step function with them. >>Yeah. I mean, we manage 10 petabytes of data right now. Right. When I, when I, when I arrived at EMC in 2010, we had, we had one petabyte customer. And, and so at observe, we've been only selling the product for a year. We have 10 petabytes of data under management. And so been able to rely on a platform that can manage that is inve >>You know, well, Jeremy great conversation. Thanks for sharing your insights on the industry. Uh, we got a couple minutes left, um, put a plug in for observe. What do you guys know? You got some good funding, great partners. I don't know if you can talk about your, your, your POC customers, but you got a lot of high ends folks that are working with you. You getting in traction. >>Yeah. Yeah. Scales >>Around the corner. Sounds like, are you, is that where you are scale? >>We've got a big that that's when coming up in two or three weeks, we've got, we've got new funding, um, which is always great. Um, the product is, uh, really, really close. I think, as a startup, you always strive for market fit, you know, which is at which point can you just start hiring salespeople? And the revenue keeps going. We're getting pretty close to that right now. Um, we've got about 40 SaaS companies that run on the platform. They're almost all AWS Kubernetes, uh, which is our sweet spot to begin with, but we're starting to get some really interesting, um, enterprise type customers. We're, we're, you know, F five networks we're POC in right now with capital one, we got some interest in news around capital one coming up. I, I can't share too much, but it's gonna be exciting. And, and like I said, so hill continue to, to, >>I think capital one's a big snowflake customer as well. Right. >>They were early in one of the things that attracted me to capital one was they were very, very good with snowflake early on. And, and they put snowflake in a position in the bank where they thought that snowflake could be successful. And, and today that, that is one of Snowflake's biggest accounts, >>Capital, one, very innovative cloud, obviously Atos customer, and very innovative, certainly in the CISO and CIO, um, on another point on where you're at. So you're, Prescale meaning you're about to scale, >>Right? >>So you got POCs, what's that trajectory look like? Can you see around the corner? What's, what's going on? What's on, around the corner. That you're, that you're gonna hit this straight and narrow and, and gas it fast. >>Yeah. I mean, the, the, the, the key thing for us is we gotta get the product. Right. Um, the nice thing about having a guy like Mike Pfizer on the board is he doesn't obsess about revenue at this stage. His questions that the board are always about, like is the product, right? Is the product right? Is the product right? Have you got the product right? And cuz we know when the product's right, we can then scale the sales team and, and the revenue will take care of itself. Yeah. So right now all the attention is on the product. Um, the, this year, the exciting thing is we we're, we're adding all the tracing visualizations. So people will be able to the kind of things that by in the day you could do with the new relics and AppDynamics, the last generation of, of APM tools, you're gonna be able to do that within observe. And we've already got the logs and the metrics capability in there. So for us this year is a big one, cuz we sort of complete the trifecta, you know, the, the >>Logs, what's the secret sauce observe. What if you had the, put it into a, a, a sentence what's the secret sauce? >>I, I, I think, you know, an amazing founding engineering team, uh, number one, I mean, at the end of the day, you have to build an amazing product and you have to solve a problem in a different way. And we've got great long term investors and, and the biggest thing our investors give is it actually, it's not just money. It gives us time to get the product, right. Because if we get the product right, then we can get the growth. >>Got it. Final question. While I got you here, you've been on the enterprise business for a long time. What's the buyer landscape out there. You got people doing POCs on capital one scale. So we know that goes on. What's the appetite at the buyer side for startups and what are their requirements that you're seeing? Uh, obviously we're seeing people go in and dip into the startup pool because new ways to refactor their, this restructure. So, so a lot of happening in cloud, what's the criteria. How are enterprises engaging in with startups? >>Yeah. I mean, enterprises, they know they've gotta spend money transforming the business. I mean, this was, I almost feel like my old Dell or EMC self there, but, um, what, what we were saying five years ago is happening. Um, everybody needs to figure out a way to take their business to this digital world. Everybody has to do it. So the nice thing from a startup standpoint is they know at times they need to risk or, or take a bet on new technology in order to, to help them do that. So I think you've got buyers that a have money, uh, B it prepared to take risks and it's, it's a race against time to you'll get their, their offerings in this, a new digital footprint. >>Final, final question. What's the state of AWS. Where do you see them going next? Obviously they're continuing to be successful. How does cloud 3.0, or they always say it's day one, but it's more like day 10, but what's next for Aw. Where do they go from here? Obviously they're doing well. They're getting bigger and bigger. Yeah, >>Better. It's an amazing story. I mean, you know, we're, we're on AWS as well. And so I, I think if they keep nurturing the builders and the ecosystem, then that is their superpower. They, they have an early leads. And if you look at where, you know, maybe the likes of Microsoft lost the plot in the, in the late nineties, it was, they stopped, uh, really caring about developers in the folks who were building on top of their ecosystem. In fact, they started buying up their ecosystem and competing with people in their ecosystem. And I see with AWS, they, they have an amazing headstart and if they did more, you know, if they do more than that, that's, what's gonna keep this juggernaut rolling for many years to come. >>Yeah. They got the Silicon and got the stack. They're developing Jeremy Burton inside the cube, great resource for commentary, but also founding with the CEO of a company called observing in the middle of all the action on the board of snowflake as well. Um, great startup. Thanks for coming on the cube. Always a pleasure. Okay. Live from San Francisco. It's to cube. I'm John for your host. Stay with us more coverage from San Francisco, California after the short break. >>Hello. Welcome back to the cubes coverage here live in San Francisco, California. I'm John furrier, host of the cubes cube coverage of AWS summit 2022 here in San Francisco. We're all the developers are the bay air at Silicon valley. And of course, AWS summit in New York city is coming up in the summer. We'll be there as well. SF and NYC cube coverage. Look for us. Of course, reinforcing Boston and re Mars with the whole robotics, AI. They all coming together. Lots of coverage stay with us today. We've got a great guest from Bel VC. John founding partner, entrepreneurial venture is a venture firm. Your next act, welcome to the cube. Good to see you. >>Good to see you, man. I feel like it's been forever since we've been able to do something in person. Well, >>I'm glad you're here because we run into each other all the time. We've known each other for over decade. Um, >>It's been at least 10 years, >>At least 10 years more. And we don't wanna actually go back as bring back the old school web 1.0 days. But anyway, we're in web three now. So we'll get to that in a second. We, >>We are, it's a little bit of a throwback to the path though, in my opinion, >>It's all the same. It's all distributed computing and software. We ran each other in cube con. You're investing in a lot of tech startup founders. Okay. This next level, next gen entrepreneurs have a new makeup and it's software. It's hardcore tech in some cases, not hardcore tech, but using software to take an old something old and make it better new, faster. So tell us about Bel what's the firm. I know you're the founder, uh, which is cool. What's going on. Explain >>What you, I mean, you remember I'm a recovering entrepreneur, right? So of course I, I, >>No, you're never recovering. You're always entrepreneur >>Always, but we are also always recovering. So I, um, started my first company when I was 24. If you remember, before there was Facebook and friends, there was instant messaging. People were using that product at work every day, they were creating a security vulnerability between their network and the outside world. So I plugged that hole and built an instant messaging firewall. It was my first company. The company was called IM logic and we were required by Symantec. Uh, then spent 12 years investing in the next generation of software companies, uh, early investor in open source companies and cloud companies and spent a really wonderful years, uh, at a firm called NEA. So I, I feel like my whole life I've been either starting enterprise software companies or helping founders start enterprise software companies. And I'll tell you, there's never been a better time than right now to start an enterprise software company. >>So, uh, the passion for starting a new firm was really a recognition that founders today that are starting an enterprise software company, they, they tend to be, as you said, a more technical founder, right? Usually it's a software engineer or a builder mm-hmm <affirmative>, uh, they are building that are serving a slightly different market than what we've traditionally seen in enterprise software. Right? I think traditionally we've seen it buyers or CIOs that have agendas and strategies, which, you know, purchase software that is traditionally bought and sold tops down. But you know, today I think the most successful enterprise software companies are the ones that are built more bottoms up and have more technical early adopters. And generally speaking, they're free to use. They're free to try. They're very commonly community source or open source companies where you have a large technical community that's supporting them. So there's a, there's kind of a new normal now I think in great enterprise software. And it starts with great technical founders with great products and great bottoms of motions. And I think there's no better place to, uh, service those people than in the cloud and uh, in, in your community. >>Well, first of all, congratulations, and by the way, you got a great pedigree and great background. You're super smart admire of your work and your, and, and your founding, but let's face it. Enterprise is hot because digital transformation is, is all companies there's no, I mean, consumer is enterprise now. Everything is what was once a niche, not, I won't say niche category, but you know, not for the faint of heart, you know, investors, >>You know, it's so funny that you say that enterprise is hot because you, and I feel that way now. But remember, like right now, there's also a giant tech in VC conference in Miami <laugh> and it's covering cryptocurrencies and FCS and web three. So I think beauty is definitely in the eye of the beholder <laugh> but no, I, I will tell you, well, >>MFTs is one big enterprise, cuz you gotta have imutability you got performance issues. You have, I IOPS issues. >>Well, and, and I think all of us here that are of may, maybe students of his stream have been involved in open source in the cloud would say that we're, you know, much of what we're doing is, uh, the predecessors of the web web three movement. And many of us I think are contributors to the web three >>Movement. The hype is definitely web >>Three. Yeah. But, >>But you know, >>For sure. Yeah, no, but now you're taking us further east to Miami. So, uh, you know, look, I think, I, I think, um, what is unquestioned with the case and maybe it's, it's more obvious the more time you spend in this world is this is the fastest growing part of enterprise software. And if you include cloud infrastructure and cloud infrastructure spend, you know, it is by many measures over, uh, $500 billion in growing, you know, 20 to 30 a year. So it it's a, it's a just incredibly fast >>Let's getting, let's get into some of the cultural and the, the shifts that are happening, cuz again, you, you have the luxury of being in enterprise when it was hard, it's getting easier and more cooler. I get it and more relevant <laugh> but there's also the hype of like the web three, for instance, but you know, for, uh, um, um, the CEO snowflake, okay. Has wrote a book and Dave Valenti and I were talking about it and uh, Frank Lutman has says, there's no playbooks. We always ask the CEOs, what's your playbook. And he's like, there's no playbook, situational awareness, always Trump's playbooks. So in the enterprise playbook, oh, hire a direct sales force and sass kind of crushed that now SAS is being redefined, right. So what is SAS? Is snowflake a SAS or is that a platform? So again, new unit economics are emerging, whole new situation, you got web three. So to me there's a cultural shift, the young entrepreneurs, the, uh, user experience, they look at Facebook and say, ah, you know, and they own all my data. And you know, we know that that cliche, um, they, you know, the product. So as this next gen, the gen Z and the millennials come in and our customers and the founders, they're looking at things a little bit differently and the tech better. >>Yeah. I mean, I mean, I think we can, we can see a lot of commonalities across all six of startups and the overall adoption of technology. Uh, and, and I would tell you, this is all one big giant revolution. I call it the user driven revolution. Right. It's the rise of the user. Yeah. And you might say product like growth is currently the hottest trend in enterprise software. It's actually user like growth, right. They're one in the same. So sometimes people think the product, uh, is what is driving. >>You just pull the product >>Through. Exactly, exactly. And so that's that I, that I think is really this revolution that you see, and, and it does extend into things like cryptocurrencies and web three and, you know, sort of like the control that is taken back by the user. Um, but you know, many would say that, that the origins of this movement may be started with open source where users were contributors, you know, contributors were users and looking back decades and seeing how it, how it fast forward to today. I think that's really the trend that we're all writing and it's enabling these end users. And these end users in our world are developers, data engineers, cybersecurity practitioners, right. They're really the users. And they're really the, the offic and the most, you know, kind of valued people in >>This. I wanna come back to the data engineers in a second, but I wanna make a comment and get your reaction to, I have a, I'm a gen Xer technically. So for not a boomer, but I have some boomer friends who are a little bit older than me who have, you know, experienced the sixties. And I've, I've been saying on the cube for probably about eight years now that we are gonna hit a digital hippie Revolut, meaning a rebellion against in the sixties was rebellion against the fifties and the man and, you know, summer of love. That was a cultural differentiation from the other one of group, the predecessors. So we're kind of having that digital moment now where it's like, Hey boomers, Hey people, we're not gonna do that anymore. We hate how you organize shit. >>Right. But isn't this just technology. I mean, isn't it, isn't it like there used to be the old adage, like, you know, you would never get fired for buying IBM, but now it's like, you obviously probably would get fired if you bought IBM. And I mean, it's just like the, the, I think, I think >>During the mainframe days, those renegades were breaking into Stanford, starting the home brew club. So what I'm trying to get at is that, do you see the young cultural revolution also, culturally, just, this is my identity NFTs to me speak volumes about my, I wanna associate with NFTs, not single sign on like, well, >>Absolutely. And, and I think like, I think you're hitting on something, which is like this convergence of, of, you know, societal trends with technology trends and how that manifests in our world is yes. I think like there is unquestionably almost a religion around the way in which a product is built. Right. And we can use open source. One example of that religion. Some people say, look, I'll just never try a product in the cloud if it's not open source. Yeah. I think cloud, native's another example of that, right? It's either it's, you know, it either is cloud native or it's not. And I think a lot of people will look at a product and say, look, you know, you were not designed in the cloud era. Therefore I just won't try you. And sometimes, um, like it or not, it's a religious decision, right? It's, it's something that people just believe to be true almost without, uh, necessarily. I mean, >>The data drives all decision making. Let me ask you this next question. As a VC. Now you look at pitch, well, you've been a VC for many years, but you also have the founder entrepreneurial mindset, but you can empathize with the founders. You know, hustle is a big part of the, that first founder check, right? You gotta convince someone to part with their ch their money and the first money in which you do a lot of is about believing in the first. So faking it till you make it is hard. Now you, the data's there, you either have it cloud native, you either have the adaption or traction. So honesty is a big part of that pitch. You can't fake it. Oh, >>AB absolutely. You know, there used to be this concept of like the persona of an entrepreneur, right. And the persona of the entrepreneur would be, you know, somebody who was a great salesperson or somebody who tell a great story. And I still think that that's important, right. It still is a human need for people to believe in narratives and stories. Yeah. But having said that you're right. The proof is in the pudding, right. At some point you click download and you try the product and it does what it says it's gonna, it's gonna do, or it doesn't, or it either stands up to the load test or it doesn't. And so I, I feel like in this new economy, that're, we live in really, it's a shift from maybe the storytellers and the creators to, to the builders, right. The people that know how to build great product. And in some ways the people that can build great product yeah. Stand out from the crowd. And they're the ones that can build communities around their products. And, you know, in some ways can, um, you know, kind of own more of the narrative because their product begin for exactly >>The volume you back to the user led growth. >>Exactly. And it's the religion of, I just love your product. Right. And I, I, I, um, Doug song is the founder of du security used to say, Hey, like, you know, the, the really like in today's world of like consumption based software, like the user is only gonna give you 90 seconds to figure out whether or not you're a company that's easy to do business with for right. And so you can say, and do all the things that you want about how easy you are to work with. But if the product isn't easy to install, if it's not easy to try, if it's not, if, if the it's gotta speak to the, >>Exactly. Speak to the user. But let me ask a question now that for the people watching, who are maybe entrepreneurial entre entrepreneurs, um, masterclass here is in session. So I have to ask you, do you prefer, um, an entrepreneur to come in and say, look at John. Here's where I'm at. Okay. First of all, storytelling's fine. Whether you're an extrovert or introvert, have your style, sell the story in a way that's authentic, but do you, what do you prefer to say? Here's where I'm at? Look, I have an idea. Here's my traction. I think here's my MVP prototype. I need help. Or do you wanna just see more stats? What's the, what's the preferred way that you like to see entrepreneurs come in and engage? >>There's tons of different styles, man. I think the single most important thing that every founder should know is that we, we don't invest in what things are today. We invest in what we think will become, right. And I think that's why we all get up in the morning and try to build something different, right? It's that we see the world a different way. We want it to be a different way, and we wanna work every single moment of the day to try to make that vision a reality. So I think the more that you can show people where you want to be, the more likely somebody is gonna to align with your vision and, and want to invest in you and wanna be along for the ride. So I, I wholeheartedly believe in showing off what you got today, because eventually we all get down to like, where are we and what are we gonna do together? But, um, no, I, you gotta show the path. I think the single most important thing for any founder and VC relationship is that they have the same vision. Uh, if you have the same vision, you can, you can get through bumps in the road, you can get through short term spills. You can all sorts of things in the middle of the journey can happen. Yeah. But it doesn't matter as much if you share the same long term vision, >>Don't flake out and, and be fashionable with the, the latest trends because it's over before you even get there. >>Exactly. I think many people that, that do what we do for a living will say, you know, ultimately the future is relatively easy to predict, but it's the timing that's impossible to predict. So you, you know, you sort of have to balance the, you know, we, we know that the world is going this way and therefore we're gonna invest a lot of money to try to make this a reality. Uh, but sometimes it happens ins six months. Sometimes it takes six years. Sometimes it takes 16 years. Uh, >>What's the hottest thing in enterprise that you see the biggest wave that people should pay attention to that you're looking at right now with Tebel partners, Tebel dot your site. What's the big wave. What's your big >>Wave. There there's three big trends that we invest in. And then the, the only things we do day in day out one is the explosion at open source software. So I think many people think that all software is unquestionably moving to an open source model in some form or another yeah. Tons of reasons to debate whether or not that is gonna happen an alwa timeline happening forever, but it is, it is accelerating faster than we've ever seen. So I, I think it's its one big mass of wave that we continue to ride. Um, second is the rise of data engineering. Uh, I think data engineering is in and of itself now a category of software. It's not just that we store data. It's now we move data and we develop applications on data. And, uh, I think data is in and of itself as big of a market as any of the other markets that we invest in. Uh, and finally it's the gift that keeps on giving. I've spent my entire career in it. We still feel that security is a market that is underinvested. It is, it continues to be the place where people need to continue to invest and spend more money. Yeah. Uh, and those are the three major trends that we run >>And security, you think we all need a do over, right? I mean, do we need a do over in security or is what's the core problem? I, >>I, I keep using this word underinvested because I think it's the right way to think about the problem. I think if you, I think people generally speaking, look at cyber security as an add-on. Yeah. But if you think about it, the whole like economy is moving online. And so in, in some ways like security is core to protecting the digital economy. And so it's, it shouldn't be an afterthought, right? It should be core to what everyone is doing. And that's why I think relative to the trillions of dollars that are at stake, uh, I believe the market size for cybersecurity is around 150 billion and it still is a fraction of what >>We're, what we're and even boom is booming now. So you get the convergence of national security, geopolitics, internet digital >>That's right. You mean arguably, right. Arguably again, it's the area of the world that people should be spending more time and more money given what to stake. >>I love your thesis. I gotta, I gotta say you gotta love your firm. Love who you're doing. We're big supporters of your mission. Congrat is on your entrepreneurial venture. And uh, we'll be, we'll be talking and maybe see a Cuban. Uh, >>Absolutely >>Not. Certainly EU maybe even north America's in Detroit this year. >>Huge fan of what you guys are doing here. Thank you so much for helping me on the show. >>Des bell VC Johnson here on the cube. Check him out. Founder for founders here on the cube, more coverage from San Francisco, California, after the short break, stay with us. Hey everyone. Welcome to the cue here. Live in San Francisco, California for AWS summit, 2022 we're live we're back with events. Also we're virtual. We got hybrid all kinds of events. This year, of course, 80% summit in New York city is happening this summer. We'll be there with the cube as well. I'm John. Again, John host of the cube. Got a great guest here. Justin Colby, owner and CEO of innovative solutions they booth is right behind us. Justin, welcome to the cube. >>Thank you. Thank you for having me. >>So we're just chatting, uh, off camera about some of the work you're doing. You're the owner of and CEO. Yeah. Of innovative. Yeah. So tell us the story. What do you guys do? What's the elevator pitch. Yeah. >><laugh> so the elevator pitch is we are, uh, a hundred percent focused on small to midsize businesses that are moving to the cloud or have already moved to the cloud and really trying to understand how to best control, cost, security, compliance, all the good stuff, uh, that comes along with it. Um, exclusively focused on AWS and, um, you know, about 110 people, uh, based in Rochester, New York, that's where our headquarters is. But now we have offices down in Austin, Texas up in Toronto, uh, Canada, as well as Chicago. Um, and obviously in New York, uh, you know, the, the business was never like this, uh, five years ago, um, founded in 1989, made the decision in 2018 to pivot and go all in on the cloud. And, uh, I've been a part of the company for about 18 years, bought the company about five years ago. And it's been a great ride. >>It's interesting. The manages services are interesting with cloud cause a lot of the heavy liftings done by AWS. So we had Matt on your team on earlier talking about some of the edge stuff. Yeah. But you guys are a managed cloud service. You got cloud advisory, you know, the classic service that's needed, but the demands coming from cloud migrations and application modernization and obviously data is a huge part of it. Huge. How is this factoring into what you guys do and your growth cuz you guys are the number one partner on the SMB side for edge. Yeah. For AWS, you got results coming in. Where's the, where's the forcing function. What's the pressure point. What's the demand like? Yeah. >>It's a great question. Every CEO I talk to, that's a small to mid-size business. I'll try and understand how to leverage technology better to help either drive a revenue target for their own business, uh, help with customer service as so much has gone remote now. And we're all having problems or troubles or issues trying to hire talent. And um, you know, tech is really at the, at the forefront and the center of that. So most customers are coming to us and they're like, listen, we gotta move to the out or we move some things to the cloud and we want to do that better. And um, there's this big misnomer that when you move to the cloud, you gotta automatically modernize. Yeah. And what we try to help as many customers understand as possible is lifting and shifting, moving the stuff that you maybe currently have OnPrem and a data center to the cloud first is a first step. And then, uh, progressively working through a modernization strategy is always the better approach. And so we spend a lot of time with small to midsize businesses who don't have the technology talent on staff to be able to do >>That. Yeah. They want to get set up. But the, the dynamic of like latency is huge. We're seeing that edge product is a big part of it. This is not a one-off happening around everywhere. It is. And it's not, it's manufacturing, it's the physical plant or location >>Literally. >>And so, and you're seeing more IOT devices. What's that like right now from a challenge and problem statement standpoint, are the customers, not staff, is the it staff kind of old school? Is it new skills? What's the core problem you guys solve >>The SMB space. The core issue nine outta 10 times is people get enamored with the latest and greatest. And the reality is not everything that's cloud based. Not all cloud services are the latest and greatest. Some things have been around for quite some time and are hardened solutions. And so, um, what we try to do with technology staff that has additional on-prem, uh, let's just say skill sets and they're trying to move to a cloud-based workload is we try to help those customers through education and through some practical, let's just call it use case. Um, whether that's a proof of concept that we're doing or whether that's, we're gonna migrate a small workload over, we try to give them the confidence to be able to not, not necessarily go it alone, but to, to, to have the, uh, the Gusto and to really have the, um, the, the opportunity to, to do that in a wise way. Um, and what I find is that most CEOs that I talk to, yeah, they're like, listen, the end of the day, I'm gonna be spending money in one place or another, whether that's OnPrem or in the cloud. I just want to know that I'm doing that in a way that helps me grow as quickly as possible status quo. I think every, every business owner knows that COVID taught us anything that status quo is, uh, is, is no. No. Good. >>How about factoring in the, the agility and speed equation? Does that come up a lot? It >>Does. I think, um, I think there's also this idea that if, uh, if we do a deep dive analysis and we really take a surgical approach to things, um, we're gonna be better off. And the reality is the faster you move with anything cloud based, the better you are. And so there's this assumption that we gotta get it right the first time. Yeah. In the cloud, if you start the, on your journey in one way, and you realize midway that it's not the right, let's just say the right place to go. It's not like buying a piece of iron that you put in the closet and now you own it in the cloud. You can turn those services on and off. It's a, gives you a much higher density for making decisions and failing >>Forward. Well actually shutting down the abandoning, the projects that early and not worrying about it, you got it. I mean, most people don't abandon stuff cuz they're like, oh, I own it. >>Exactly. >>And they get, they get used to it. Like, and then they wait too long. >>That's exactly. Yeah. >>Frog and boiling water as we used to say so, oh, it's a great analogy. So I mean this, this is a dynamic that's interesting. I wanna get more thoughts on it because like I'm a, if I'm a CEO of a company, like, okay, I gotta make my number. Yeah. I gotta keep my people motivated. Yeah. And I gotta move faster. So this is where you guys come in. I get the whole thing. And by the way, great service, um, professional services in the cloud right now are so hot because so hot, you can build it and then have option optionality. You got path decisions, you got new services to take advantage of. It's almost too much for customers. It is. I mean, everyone I talk to at reinvent, that's a customer. Well, how many announcements did Andy jazzy announcer Adam, you know, five, a thousand announcement or whatever they did with huge amounts. Right. Keeping track of it all. Oh, is huge. So what's the, what's the, um, the mission of, of your company. How does, how do you talk to that alignment? Yeah. Not just product. I can get that like values as companies, cuz they're betting on you and your people. >>They are, they are >>The values. >>Our mission is, is very simple. We want to help every small to mid-size business, leverage the power of the cloud. Here's the reality. We believe wholeheartedly. This is our vision that every company is going to become a technology company. So we go to market with this idea that every customer's trying to leverage the power of the cloud in some way, shape or form, whether they know it or don't know it. And number two, they're gonna become a tech company in the pro of that because everything is so tech-centric. And so when you talk about speed and agility, when you talk about the, the endless options and the endless permutations of solutions that a customer can buy in the cloud, how are you gonna ask a team of one or two people in your it department to make all those decisions going it alone or trying to learn it as you go, it only gets you so far working with a partner. >>I'll just give you some perspective. We work with about a thousand small to midsize business customers. More than 50% of those customers are on our managed services. Meaning know that we have their back and we're the safety net. So when a customer is saying, all right, I'm gonna spend a couple thousand dollars a month in the cloud. They know that that bill, isn't gonna jump to $10,000 a month going on loan. Who's there to help protect that. Number two, if you have a security posture and let's just say you're high profile and you're gonna potentially be more vulnerable to security attack. If you have a partner that's offering you some managed services. Now you, again, you've got that backstop and you've got those services and tooling. We, we offer, um, seven different products that are part of our managed services that give the customer the tooling, that for them to go out and buy on their own for a customer to go out today and go buy a new Relic solution on their own, it would cost 'em a fortune. If >>It's training alone would be insane. A risk factor not mean the cost. Yes, absolutely. Opportunity cost is huge, >>Huge, absolutely enormous training and development. Something. I think that is often, you know, it's often overlooked technologists. Typically they want to get their skills up. Yeah. They, they love to get the, the stickers and the badges and the pins, um, at innovative in 2018, when, uh, when we made the decision to go all on the club, I said to the organization, you know, we have this idea that we're gonna pivot and be aligned with AWS in such a way that it's gonna really require us all to get certified. My executive assistant at the time looks at me. She said, even me, I said, yeah, even you, why can't you get certified? Yeah. And so we made, uh, a conscious decision. It wasn't requirement isn't today to make sure everybody in the company has the opportunity to become certified. Even the people that are answering the phones at the front desk >>And she could be running the Kubernetes clusters. I >>Love it. It's amazing. So I'll tell you what, when that customer calls and they have a real Kubernetes issue, she'll be able to assist and get the right >>People involved. And that's a cultural factor that you guys have. So, so again, this is back to my whole point about SMBs and BIS is in general, small and large. It staffs are turning over the gen Z and millennials are in the workforce. They were provisioning top of rack switches. Right. First of all. And so if you're a business, there's also the, I call the build out, um, uh, return factor, ROI piece. At what point in time as an owner or SMB, do I get the why? Yeah. I gotta hire a person to manage it. That person's gonna have five zillion job offers. Yep. Uh, maybe who knows? Right. I got cyber security issues. Where am I gonna find a cyber person? Yeah. A data compliance. I need a data scientist and a compliance person. Right. Maybe one in the same. Right. Good luck. Trying to find a data scientist. Who's also a compliance person. Yep. And the list goes on. I can just continue. Absolutely. I need an SRE to manage the, the, uh, the sock report and we can pen test. Right. >>Right. >>These are, these are >>Like critical issues. This >>Is just like, these are the table stakes. >>Yeah. And, and every, every business owner's thinking about this, that's, >>That's what, at least a million in bloating, if not three or more Just to get that going. Yeah. Then it's like, where's the app. Yeah. So there's no cloud migration. There's no modernization on the app side now. Yeah. No. And nevermind AI and ML. That's >>Right. That's right. So to try to go it alone, to me, it's hard. It's incredibly difficult. And the other thing is, is there's not a lot of partners, so the partner, >>No one's raising their hand boss. I'll do all that exactly. In the it department. >>Exactly. >>Like, can we just call up, uh, you know, our old vendor that's >>Right. <laugh> right. Our old vendor. I like >>It, >>But that's so true. I mean, when I think about how, if I were a business owner starting a business today and I had to build my team, um, and the amount of investment that it would take to get those people skilled up and then the risk factor of those people now having the skills and being so much more in demand and being recruited away, that's a real, that's a real issue. And so how you build your culture around that is, is very important. And it's something that we tell, talk about every, with every one of our small to mid-size >>Businesses. So just, I wanna get, I want to get your story as CEO. Okay. Take us through your journey. You said you bought the company and your progression to, to being the owner and CEO of innovative yeah. Award winning guys doing great. Uh, great bet on a good call. Yeah. Things are good. Tell your story. What's your journey? >>It's real simple. I was, uh, I was a sophomore at the Rochester Institute of technology in 2003. And, uh, I knew that I, I was going to school for it and I, I knew I wanted to be in tech. I didn't know what I wanted to do, but I knew I didn't wanna code or configure routers and switches. So I had this great opportunity with the local it company that was doing managed services. We didn't call it at that time innovative solutions to come in and, uh, jump on the phone and dial for dollars. I was gonna cold call and introduce other, uh, small to midsize businesses locally in Rochester, New York go to Western New York, um, who innovative was now. We were 19 people at the time. And I came in, I did an internship for six months and I loved it. I learned more in those six months that I probably did in my first couple of years at, uh, at RT long story short. >>Um, for about seven years, I worked, uh, to really help develop, uh, sales process and methodology for the business so that we could grow and scale. And we grew to about 30 people. And, um, I went to the owners at the time in 2010 and I was like, Hey, on the value of this business and who knows where you guys are gonna be another five years, what do you think about making me an owner? And they were like, listen, you got long ways before you're gonna be an owner, but if you stick it out in your patient, we'll, um, we'll work through a succession plan with you. And I said, okay, there were four other individuals at the time that were gonna also buy into the business with me. >>And they were the owners, no outside capital, none >>Zero, well, 2014 comes around. And, uh, the other folks that were gonna buy into the business with me that were also working at innovative for different reasons, they all decided that it wasn't for them. One started a family. The other didn't wanna put capital in. Didn't wanna write a check. Um, the other had a real big problem with having to write a check. If we couldn't make payroll, I'm like, well, that's kind of like if we're owners, we're gonna have to like cover that stuff. <laugh> so >>It's called the pucker factor. >>Exactly. So, uh, I sat down with the CEO in early 2015, and, uh, we made the decision that I was gonna buy the three partners out, um, go through an early now process, uh, coupled with, uh, an interesting financial strategy that wouldn't strap the business, cuz they cared very much. The company still had the opportunity to keep going. So in 2016 I bought the business, um, became the sole owner. And, and at that point we, um, we really focused hard on what do we want this company to be? We had built this company to this point. Yeah. And, uh, and by 2018 we knew that pivoting going all in on the cloud was important for us and we haven't looked back. >>And at that time the proof points were coming clearer and clearer 2012 through 15 was the early adopters, the builders, the startups and early enterprises. Yes. The capital ones of the world. Exactly. And those kinds of big enterprises, the GA I don't wanna say gamblers, but ones that were very savvy. The innovators, the FinTech folks. Yep. The hardcore glass eating enterprises >>Agreed, agreed to find a small to mid-size business, to migrate completely to the cloud as, as infrastructure was considered. That just didn't happen as often. Um, what we were seeing where a lot of our small to mid-size as customers, they wanted to leverage cloud-based backup or they wanted to leverage a cloud for disaster recovery because it lent itself. Well, early days, our most common cloud customer though, was the customer that wanted to move messaging and collaboration, the Microsoft suite to the cloud. And a lot of 'em dipped their toe in the water. But by 2017 we knew infrastructure was around the corner. Yeah. And so, uh, we only had two customers on AWS at the time. Um, and we, uh, we, we made the decision to go all in >>Justin. Great to have you on the cube. Thank you. Let's wrap up. Uh, tell me the hottest product that you have. Is it migrations? Is it the app modernization? Is it data? What's the hot product and then put a plug in for the company. Awesome. >>So, uh, there's no question. Every customer is looking to migrate workloads and try to figure out how to modernize for the future. We have very interesting, sophisticated yet elegant funding solutions to help customers with the cash flow, uh, constraints that come along with those migrations. So any SMB that's thinking about migrating to the cloud, they should be talking innovative solutions. We know how to do it in a way that allows those customers not to be cash strap and gives them an opportunity to move forward in a controlled, contained way so that they can modernize. >>So like insurance, basically for them not insurance class in the classic sense, but you help them out on the, on the cash exposure. >>Absolutely. We are known for that and we're known for being creative with those customers and being empathetic to where they are in their journey. >>And that's the cloud upside is all about doubling down on the variable wind. That's right. Seeing the value and Ling down on it. Absolutely not praying for it. Yeah. <laugh> all right, Justin. Thanks for coming on. You really appreciate it. >>Thank you very much for having me. >>Okay. This is the cube coverage here live in San Francisco, California for AWS summit, 2022. I'm John for your host. Thanks for watching. We're back with more great coverage for two days after this short break, >>Live on the floor and see San Francisco for a AWS summit. I'm John ferry, host of the cube here for the next two days, getting all the action we're back in person. We're at a AWS reinvent a few months ago. Now we're back. Events are coming back and we're happy to be here with the cube. Bring all the action. Also virtual. We have a hybrid cube. Check out the cube.net, Silicon angle.com for all the coverage. After the event. We've got a great guest ticking off here. Matthew Park, director of solutions, architecture with innovation solutions. The booth is right here. Matthew, welcome to the cube. >>Thank you very much. I'm glad to be >>Here. So we're back in person. You're from Tennessee. We were chatting before you came on camera. Um, it's great to have to be back through events. >>It's amazing. This is the first, uh, summit I've been to and what two, three years. >>It's awesome. We'll be at the UHS summit in New York as well. A lot of developers and a big story this year is as developers look at cloud going distributed computing, you got on premises, you got public cloud, you got the edge. Essentially the cloud operations is running everything dev sec ops, everyone kind of sees that you got containers, you got Kubernetes, you got cloud native. So the game is pretty much laid out mm-hmm <affirmative> and the edge is with the actions you guys are number one, premier partner at SMB for edge. >>That's right. >>Tell us about what you guys doing at innovative and, uh, what you do. >>That's right. Uh, so I'm the director of solutions architecture. Uh, me and my team are responsible for building out the solutions that are around, especially the edge public cloud for us edge is anything outside of an AWS availability zone. Uh, we are deploying that in countries that don't have AWS infrastructure in region. They don't have it. Uh, give an example, uh, example would be Panama. We have a customer there that, uh, needs to deploy some financial tech and compute is legally required to be in Panama, but they love AWS and they want to deploy AWS services in region. Uh, so they've taken E EKS anywhere. We've put storage gateway and, uh, snowball, uh, in region inside the country and they're running their FinTech on top of AWS services inside Panama. >>You know, it's interesting, Matthew is that we've been covering a, since 2013 with the cube about their events. And we watched the progression and jazzy was, uh, was in charge and became the CEO. Now Adam's in charge, but the edge has always been that thing they've been trying to avoid. I don't wanna say trying to avoid, of course, Amazon would listen to the customers. They work backwards from the customer. We all know that. Uh, but the real issue was they were they're bread and butters EC two and S three. And then now they got tons of services and the cloud is obviously successful and seeing that, but the edge brings up a whole nother level. >>It does computing. It >>Does. That's not centralized in the public cloud now they got regions. So what is the issue at the edge what's driving the behavior. Outpost came out as a reaction to competitive threats and also customer momentum around OT, uh, operational technologies. And it merging. We see that the data at the edge, you got 5g having. So it's pretty obvious, but there's a slow transition. What was the driver for the edge? What's the driver now for edge action for AWS >>Data is the driver for the edge. Data has gravity, right? And it's pulling compute back to where the customer's generating that data and that's happening over and over again. You said it best outpost was a reaction to a competitive situation where today we have over 15 AWS edge services and those are all reactions to things that customers need inside their data centers on location or in the field like with media companies. >>Outpost is interesting. We always used to riff on the cube cause it's basically Amazon and a box pushed in the data center, running native, all the stuff, but now cloud native operations are kind of becoming standard. You're starting to see some standard Deepak syncs. Group's doing some amazing work with open source Rauls team on the AI side, obviously, uh, you got SW, he was giving the keynote tomorrow. You got the big AI machine learning big part of that edge. Now you can say, okay, outpost, is it relevant today? In other words, did outpost do its job? Cause EKS anywhere seems to be getting a lot of momentum. You see local zones, the regions are kicking ass for Amazon. This edge piece is evolving. What's your take on EKS anywhere versus say outpost? >>Yeah, I think outpost did its job. It made customers that were looking at outpost really consider, do I wanna invest in this hardware? Do I, do I wanna have, um, this outpost in my data center, do I want to manage this over the long term? A lot of those customers just transitioned to the public cloud. They went into AWS proper. Some of those customers stayed on prem because they did have use cases that were, uh, not a good fit for outposts. They weren't a good fit. Uh, in the customer's mind for the public AWS cloud inside an availability zone. Now what's happening is as AWS is pushing these services out and saying, we're gonna meet you where you are with 5g. We're gonna meet you where you are with wavelength. We're gonna meet you where you are with EKS anywhere. Uh, I think it has really reduced the amount of times that we have conversations about outposts and it's really increased. We can deploy fast. We don't have to spin up outpost hardware. We can go deploy EKS anywhere or in your VMware environment. And it's increasing the speed of adoption >>For sure. Right? So you guys are making a lot of good business decisions around managed cloud service. That's right. Innovative as that you get the cloud advisory, the classic professional services for the specific edge piece and, and doing that outside of the availability zones and regions for AWS, um, customers in, in these new areas that you're helping out are, they want cloud, like they want to have modernization a modern applications. Obviously they got data machine learning and AI, all part of that. What's the main product or, or, or gap that you're filling for AWS, uh, outside of their availability zones or their regions that you guys are delivering. What's the key is it. They don't have a footprint. Is it that it's not big enough for them? What's the real gap. What's why, why are you so successful? >>So what customers want when they look towards the cloud is they want to focus on, what's making them money as a business. They want on their applications. They want to focus on their customers. So they look towards AWS cloud and say, AWS, you take the infrastructure. You take, uh, some of the higher layers and we'll focus on our revenue generating business, but there's a gap there between infrastructure and revenue generating business that innovative slides into, uh, we help manage the AWS environment. Uh, we help build out these things in local data centers for 32 plus year old company. We have traditional on-premises people that know about deploying hardware that know about deploying VMware to host EKS anywhere. But we also have most of our company totally focused on the AWS cloud. So we're filling that gap in helping of these AWS services, manage them over the long term. So our customers can go to just primarily and totally focusing on their revenue generating business. So >>Basically you guys are basically building AWS edges, >>Correct? >>For correct companies, correct? Mainly because the, the needs are there, you got data, you got certain products, whether it's, you know, low latency type requirements, right. And then they still work with the regions, right. It's all tied together, right. Is that how it works? Right. >>And, and our customers, even the ones in the edge, they also want us to build out the AWS environment inside the availability zone, because we're always gonna have a failback scenario. If we're gonna deploy FinTech in the Caribbean, we talk about hurricanes and we're gonna talk about failing back into the AWS availability zones. So innovative is filling that gap across the board, whether it be inside the AWS cloud or on the AWS edge. >>All right. So I gotta ask you on the, since you're at the edge in these areas, I won't say underserved, but developing areas where you now have data and you have applications that are tapping into that, that required. It makes total sense. We're seeing that across the board. So it's not like it's, it's an outlier it's actually growing. Yeah. There's also the crypto angle. You got the blockchain. Are you seeing any traction at the edge with blockchain? Because a lot of people are looking at the web three in these areas like Panama, you mentioned FinTech. And in, in the islands there a lot of, lot of, lot of web three happening. What's your, what's your view on the web three world right now, relative >>To we, we have some customers actually deploying crypto, especially, um, especially in the Caribbean. I keep bringing the Caribbean up, but it's, it's top of my mind right now we have customers that are deploying crypto. A lot of, uh, countries are choosing crypto to underlie parts of their central banks. Yeah. Um, so it's, it's up and coming a, uh, I, I have some, you know, personal views that, that crypto is still searching for a use case. Yeah. And, uh, I think it's searching a lot and, and we're there to help customers search for that use case. Uh, but, but crypto, as a, as a, uh, technology, um, lives really well on the AWS edge. Yeah. Uh, and, and we're having more and more people talk to us about that. Yeah. And ask for assistance in the infrastructure, because they're developing new cryptocurrencies every day. Yeah. It's not like they're deploying Ethereum or anything specific. They're actually developing new currencies and, and putting them out there on it's >>Interesting. I mean, first of all, we've been doing crypto for many, many years. We have our own little, um, you know, projects going on. But if you look talk to all the crypto people that say, look, we do a smart concept. We use the blockchain. It's kind of over a lot of overhead and it's not really their technical already, but it's a cultural shift, but there's underserved use cases around use of money, but they're all using the blockchain, just for this like smart contracts for instance, or certain transactions. And they go into Amazon for the database. Yeah. <laugh> they all don't tell anyone we're using a centralized service, but what happened to decentralized. >>Yeah. And that's, and that's the conversation performance issue. Yeah. And, and it's a cost issue. Yeah. And it's a development issue. Um, so I think more and more as, as some of these, uh, currencies maybe come up, some of the smart contracts get into, uh, they find their use cases. I think we'll start talking about how does that really live on, on AWS and, and what does it look like to build decentralized applications, but with AWS hardware and services. >>Right. So take me through, uh, a use case of a customer, um, Matthew around the edge. Okay. So I'm a customer, pretend I'm a customer, Hey, you know, I'm, we're in an underserved area. I want to modernize my business. And I got my developers that are totally peaked up on cloud. Um, but we've identified that it's just a lot of overhead latency issues. I need to have a local edge and serve my ad. And I also want all the benefit of the cloud. So I want the modernization and I wanna migrate to the cloud for all those cloud benefits and the goodness of the cloud. What's the answer. Yeah. >>Uh, big thing is, uh, industrial manufacturing, right? That's, that's one of the best use cases, uh, inside industrial manufacturing, we can pull in many of the AWS edge services we can bring in, uh, private 5g, uh, so that all the, uh, equipment inside that, that manufacturing plant can be hooked up. They don't have to pay huge overheads to deploy 5g it's, uh, better than wifi for the industrial space. Um, when we take computing down to that industrial area, uh, because we wanna do pre-procesing on the data. Yeah. We want to gather some analytics. We deploy that with, uh, regular commercial available hardware running VMware, and we deploy EKS anywhere on that. Uh, inside of that manufacturing plant, uh, we can do pre-procesing on things coming out of the, uh, the robotics that depending on what we're manufacturing, right. Uh, and then we can take those refined analytics and for very low cost with maybe a little bit longer latency transmit those back, um, to the AWS availability zone, the, the standard for >>Data, data lake, or whatever, to >>The data lake. Yeah. Data lake house, whatever it might be. Um, and we can do additional data science on that once it gets to the AWS cloud. Uh, but a lot of that, uh, just in time business decisions, just in time, manufacturing decisions can all take place on an AWS service or services inside that manufacturing plant. And that's, that's one of the best use cases that we're >>Seeing. And I think, I mean, we've been seeing this on the queue for many, many years, moving data around is very expensive. Yeah. But also compute going to the data that saves that cost yep. On the data transfer also on the benefits of the latency. So I have to ask you, by the way, that's standard best practice now for the folks watching don't move the data, unless you have to, um, those new things are developing. So I wanna ask you what new patterns are you seeing emerging once this new architecture's in place? Love that idea, localize everything right at the edge, manufacturing, industrial, whatever, the use case, retail, whatever it is. Right. But now what does that change in the, in the core cloud? This is a, there's a system element here. Yeah. What's the new pattern. There's >>Actually an organizational element as well, because once you have to start making the decision, do I put this compute at the point of use or do I put this compute in the cloud out? Uh, now you start thinking about where business decisions should be taking place. Uh, so not only are you changing your architecture, you're actually changing your organization because you're thinking, you're thinking about a dichotomy you didn't have before. Uh, so now you say, okay, this can take place here. Uh, and maybe maybe decision can wait. Right? Yeah. Uh, and then how do I visualize that? By >>The way, it could be a bot too, doing the work for management. Yeah. <laugh> exactly. You got observability going, right. But you gotta change the database architecture on the back. So there's new things developing. You've got more benefit. There >>Are, there are. And, and we have more and more people that, that want to talk less about databases and want to talk more about data lakes because of this. They want to talk more about customers are starting to talk about throwing away data, uh, you know, for the past maybe decade. Yeah. It's been store everything. And one day we will have a data science team that we hire in our organization to do analytics on this decade of data. And >>Well, I mean, that's, that's a great point. We don't have time to drill into, maybe we do another session on this, but the one pattern was income of the past year is that throwing away data's bad. Even data lakes that so-called turn into data swamps, actually, it's not the case. You look at data, brick, snowflake, and other successes out there. And even time series data, which may seem irrelevant efforts over actually matters when people start retrain their machine learning algorithms. Yep. So as data becomes code, as we call it our lab showcase, we did a whole, whole, that event on this. The data's good in real time and in the lake. Yeah. Because the iteration of the data feeds the machine learning training. Things are getting better with the old data. So it's not throw away. It's not just business benefits. Yeah. There's all kinds of new scale. There >>Are. And, and we have, uh, many customers that are run petabyte level. Um, they're, they're essentially data factories on, on, uh, on premises, right? They're, they're creating so much data and they're starting to say, okay, we could analyze this, uh, in the cloud, we could transition it. We could move petabytes of data to the AWS cloud, or we can run, uh, computational workloads on premises. We can really do some analytics on this data transition, uh, those high level and sort of raw analytics back to AWS run 'em through machine learning. Um, and we don't have to transition 10, 12 petabytes of data into AWS. >>So I gotta end the segment on a, on a kind of a, um, fun note. I was told to ask you about your personal background on premise architect, a cloud and skydiving instructor. <laugh> how does that all work together? What tell, what does this mean? Yeah. >>Uh, you >>Jumped out a plane and got a job. You, you got a customer to jump out >>Kind of. So I was jump, I was teaching Scott eing, uh, before I, before I started in the cloud space, this was 13, 14 years ago. I was a, I still am a Scott I instructor. Yeah. Uh, I was teaching Scott eing and I heard out of the corner of my ear, uh, a guy that owned an MSP that was lamenting about, um, you know, storing data and, and how his cus customers are working. And he can't find enough people to operate all these workloads. So I walked over and said, Hey, this is, this is what I went to school for. Like, I'd love to, you know, uh, I was living in a tent in the woods teaching scout. I think I was like, I'd love to not live in a tent in the woods. So, uh, uh, I started in the first day there, uh, we had a, a discussion, uh, EC two, just come out <laugh> um, and, uh, like, >>This is amazing. >>Yeah. And so we had this discussion, we should start moving customers here. And, uh, and that totally revolutionized that business, um, that, that led to, uh, that that guy actually still owns a skydiving airport. But, um, but through all of that and through being an on premises migrated me and myself, my career into the cloud, and now it feels like, uh, almost, almost looking back and saying, now let's take what we learned in the cloud and, and apply those lessons and those services to >>It's. So it's such a great story, you know, I was gonna, you know, you know, the, the, the, the whole, you know, growth mindset pack your own parachute, you know, uh, exactly. You know, the cloud in the early day was pretty much will the shoot open. Yeah. It was pretty much, you had to roll your own cloud at that time. And so, you know, you, you jump on a plane, you gotta make sure that parachute is gonna open. >>And so was Kubernetes by the way, 2015 or so when, um, when that was coming out, it was, I mean, it was, it was still, and I, maybe it does still feel like that to some people. Right. But, uh, it was, it was the same kind of feeling that we had in the early days, AWS, the same feeling we have when we >>It's pretty much now with you guys, it's more like a tandem jump. Yeah. You know, but, but it's a lot of, lot of this cutting edge stuff, like jumping out of an airplane. Yeah. You guys, the right equipment, you gotta do the right things. Exactly. >>Right. >>Matthew, thanks for coming on the cube. Really appreciate it. Absolutely great conversation. Thanks for having me. Okay. The cubes here live and San Francisco for summit. I'm John Forry host of the cube. Uh, we'll be at a summit in New York coming up in the summer as well. Look up for that. look@thiscalendarforallthecubeactionatthecube.net. We'll be right back with our next segment after this break. >>Okay. Welcome back everyone to San Francisco live coverage here, we're at the cube a be summit 2022. We're back in person. I'm John fury host to the cube. We'll be at the eight of his summit in New York city. This summer, check us out then. But right now, two days in San Francisco, getting all the coverage what's going on in the cloud, we got a cube alumni and friend of the cube, my dudes, car CEO, investor, a Sierra, and also an investor and a bunch of startups, angel investor. Gonna do great to see you. Thanks for coming on the cube. Good to see you. Good to see you, sir. Chris. Cool. How are, are you >>Good? How are you? >>So congratulations on all your investments. Uh, you've made a lot of great successes, uh, over the past couple years, uh, and your company raising, uh, some good cash as Sarah. So give us the update. How much cash have you guys raised? What's the status of the company product what's going on? First >>Of all, thank you for having me back to be business with you. Never great to see you. Um, so is a company started around four years back. I invested with a few of the investors and now I'm the CEO there. Um, we have raised close to a hundred million there. Uh, the investors are people like Norwes Menlo, Tru ventures, coast, lo ventures, Ram Sheam and all those people, all well known guys. The Andy Beckel chime, Paul Mo uh, main web. So a whole bunch of operating people and, uh, Silicon valley VCs are involved >>And has it come? >>It's going well. We are doing really well. We are going almost 300% year over year. Uh, for last three years, the space ISR is going after is what I call the applying AI for customer service. It operations, it help desk, uh, the same place I used to work at ServiceNow. We are partners with ServiceNow to take, how can we argument for employees and customers, Salesforce, and ServiceNow to take it to the next stage? >>Well, I love having you on the cube, Dave and I, Dave Valenti as well loves having you on too, because you not only bring the entrepreneurial CEO experience, you're an investor. You're like a GE, you're like a guest analyst. <laugh> >>You know who you >>Get to call this fun to talk. You though, >>You got the commentary, you, your, your finger on the pulse. Um, so I gotta ask you obviously, AI and machine learning, machine learning AI, or you want to phrase it. Isn't every application. Now, AI first, uh, you're seeing a lot of that going on. You're starting to see companies build the modern applications at the top of the stack. So the cloud scale has hit. We're seeing cloud scale. You predicted that we talked about on cube many times. Now you have that past layer with a lot more services and cloud native becoming a standard layer. Containerizations growing DACA just raised a hundred million on a 2 billion valuation back from the dead after they pivoted from an enterprise services. So open source developers are booming. Um, where's the action. I mean, is there data control, plane emerging, AI needs data. There's a lot of challenges around this. There's a lot of discussions and a lot of companies being funded, observability there's 10 million observability companies. Data is the key. What's your angle on this? What's your take. Yeah, >>No, look, I think I'll give you the view that I see right from my side. Obviously data is very clear. So the things that remember system of recorded you and me talked about the next layer is called system of intelligence. That's where the AI will play. Like we talk cloud NA it'll be called AI, NA AI native is a new buzzword and using the AI customer service it operations. You talk about observability. I call it, AIOps applying AOPs for good old it operation management, cloud management. So you'll see the AOPs applied for whole list of, uh, application from observability doing the CMDB, predicting the events insurance. So I see a lot of work clicking for AIOps and service desk. What needs to be helped us with ServiceNow BMC G you see a new ELA emerging as a system of intelligence. Uh, the next would be is applying AI with workflow automation. So that's where you'll see a lot of things called customer workflow, employee workflows. So think of what UI path automation, anywhere ServiceNow are doing, that area will be driven with a AI workflows. So you'll see AI going >>Off is RPA a company is AI, is RPA a feature of something bigger? Or can someone have a company on RPA UI pass? One will be at their event this summer? Um, is it a product company? I mean, I mean, RPA is almost, should be embedded in everything. It's >>A feature. It is very good point. Very, very good thinking. So one is, it's a category for sure. Like, as we thought, it's a category, it's an area where RPA may change the name. I call it much more about automation, workflow automation, but RPA and automation is a category. Um, it's a company, or, but that automation should be embedded in every area. Yeah. Like we call cloud NA and AI NATO it'll become automation. NA yeah. And that's your thinking. >>It's almost interesting me. I think about the, what you're talking about what's coming to mind is I'm kinda having flashbacks to the old software model of middleware. Remember at middleware, it was very easy to understand it. It was middleware. It sat between two things and then the middle, and it was software abstraction. Now you have all, all kinds of workflows, abstractions everywhere. So multiple databases, it's not a monolithic thing. Right? Right. So as you break that down, is this the new modern middleware? Because what you're talking about is data workflows, but they might be siloed or they integrated. I mean, these are the challenges. This is crazy. What's the, >>So don't about the databases become called poly databases. Yeah. I call this one polyglot automation. So you need automation as a layer, as a category, but you also need to put automation in every area like you were talking about. It should be part of service. Now it should be part of ISRA, like every company, every Salesforce. So that's why you see MuleSoft and Salesforce buying RPA companies. So you'll see all the SaaS companies, cloud companies having an automation as a core. So it's like how you have a database and compute and sales and networking. You'll also have an automation as a layer <inaudible> inside every stack. >>All right. So I wanna shift gears a little bit and get your perspective on what's going on behind us. You can see, uh, behind us, you've got the expo hall. We got, um, we're back to vents, but you got, you know, AMD, Clum, Ove, uh, Dynatrace data, dog, innovative, all the companies out here that we know, we interview them all. They're trying to be suppliers to this growing enterprise market. Right. Okay. But now you also got the entrepreneurial equation. Okay. We're gonna have John Sado on from Bel later today. He's a former NEA guy and we always talk to Jerry, Jen. We know all the, the VCs. What does the startups look like? What does the state of the, in your mind, cause you, I know you invest the entrepreneurial founder situation, clouds bigger. Mm-hmm <affirmative> global, right? Data's part of it. You mentioned data's code. Yes. Basically data is everything. What's it like for a first an entrepreneur right now who's starting a company. What's the white space. What's the attack plan. How do they get in the market? How do they engineer everything? >>Very good. So I'll give it to, uh, two things that I'm seeing out there. Remember leaders of Amazon created the startups 15 years back. Everybody built on Amazon now, Azure and GCP. The next layer would be is people don't just build on Amazon. They're going to build it on top of snowflake. Companies are snowflake becomes a data platform, right? People will build on snowflake. Right? So I see my old boss flagman try to build companies on snowflake. So you don't build it just on Amazon. You build it on Amazon and snowflake. Snowflake will become your data store. Snowflake will become your data layer. Right? So I think that's in the of, <inaudible> trying to do that. So if I'm doing observability AI ops, if I'm doing next level of Splunk SIM, I'm gonna build it on snowflake, on Salesforce, on Amazon, on Azure, et cetera. >>It's interesting. You know, Jerry Chan has it put out a thesis a couple months ago called castles in the cloud where your moat is, what you do in the cloud. Not necessarily in the, in the IP. Um, Dave LAN and I had last reinvent, coined the term super cloud, right? He's got a lot of traction and a lot of people throwing, throwing mud at us, but we were, our thesis was, is that what Snowflake's doing? What Goldman S Sachs is doing. You starting to see these clouds on top of clouds. So Amazon's got this huge CapEx advantage. And guys like Charles Fitzgeral out there, who we like was kind of shit on us saying, Hey, you guys terrible, they didn't get it. Like, yeah. I don't think he gets it, but that's a whole, can't wait to debate him publicly on this. <laugh> if he's cool. Um, but snowflake is on Amazon. Yes. Now they say they're on Azure now. Cause they've got a bigger market and they're public, but ultimately without a AWS snowflake doesn't exist. And, and they're reimagining the data warehouse with the cloud, right? That's the billion dollar opportunity. >>It is. It is. They both are very tight. So imagine what Frank has done at snowflake and Amazon. So if I'm a startup today, I want to build everything on Amazon where possible whatever is, I cannot build. I'll make the pass layer. Remember the middle layer pass will be snowflake. So can build it on snowflake. I can use them for data layer. If I really need to size, I'll build it on four.com Salesforce. So I think that's where you'll see. So >>Basically if you're an entrepreneur, the north star in terms of the outcome is be a super cloud. >>It is, >>That's the application on another big CapEx ride, the CapEx of AWS or cloud, >>And that reduce your product development, your go to market and you get use the snowflake marketplace to drive your engagement. >>Yeah. Yeah. How are, how is Amazon and the clouds dealing with these big whales? The snowflakes of the world? I mean, I know they got a great relationship, uh, but snowflake now has to run a company they're public. Yeah. So, I mean, I'll say, I think got Redshift. Amazon has got red, um, but Snowflake's a big customer. They're probably paying AWS think big bills too. >>So John, very good. Cause it's like how Netflix is and Amazon prime, right. Netflix runs on Amazon, but Amazon has Amazon prime that co-option will be there. So Amazon will have Redshift, but Amazon is also partnering with, uh, snowflake to have native snowflake data warehouse as a data layer. So I think depending on the application use case, you have to use each of the above. I think snowflake is here for a long term. Yeah. Yeah. So if I'm building an application, I want to use snowflake then writing from stats. >>Well, I think that comes back down to entrepreneurial hustle. Do you have a better product? Right. Product value will ultimately determine it as long as the cloud doesn't, You know, foreclose your value that's right. But some sort of internal hack, but I think, I think the general question that I have is that I think it's okay to have a super cloud like that because the rising tide is still happening at some point. When does the rising tide stop >>And >>Do the people shopping up their knives, it gets more competitive or is it just an infinite growth cycle? I >>Think it's growth. You call it cloud scale. You invented the word cloud scale. So I think look, cloud will continually agree, increase. I think there's, as long as there are more movement from on, uh, OnPrem to the classical data center, I think there's no reason at this point, the rumor, the old lift and shift that's happening in like my business. I see people lift and shifting from the it operations. It helpless, even the customer service service now and, uh, ticket data from BMCs CAS like Microfocus, all those workloads are shifted to the cloud, right? So cloud ticketing system is happening. Cloud system of record is happening. So I think this train has still a long way to go made. >>I wanna get your thoughts for the folks watching that are, uh, enterprise buyers or practitioners, not suppliers to the market, feel free to, to XME or DMing. Next question's really about the buying side, which is if I'm a customer, what's the current, um, appetite for startup products. Cause you know, the big enterprises now and, you know, small, medium, large, and large enterprise are all buying new companies cuz a startup can go from zero to relevant very quickly. So that means now enterprises are engaging heavily with startups. What's it like what's is there a change in order of magnitude of the relationship between the startup selling to, or a growing startup selling to an enterprise? Um, have you seen changes there? I mean I'm seeing some stuff, but why don't we get your thoughts on that? What, no, it is. >>If I remember going back to our 2007 or eight, it, when I used to talk to you back then when Amazon started very small, right? We are an Amazon summit here. So I think enterprises on the average used to spend nothing with startups. It's almost like 0% or 1% today. Most companies are already spending 20, 30% with startups. Like if I look at a CIO line business, it's gone. Yeah. Can it go more? I think it can double in the next four, five years. Yeah. Spending on the startups. >>Yeah. And check out, uh, AWS startups.com. That's a site that we built for the startup community for buyers and startups. And I want to get your reaction because I reference the URL cause it's like, there's like a bunch of companies we've been promoting because the solutions that startups have actually are new stuff. Yes. It's bending, it's shifting left for security or using data differently or um, building tools and platforms for data engineering. Right. Which is a new persona that's emerging. So you know, a lot of good resources there, um, and gives back now to the data question. Now, getting back to your, what you're working on now is what's your thoughts around this new, um, data engineering persona, you mentioned AIOps, we've been seeing AIOps IOPS booming and that's creating a new developer paradigm that's right. Which we call coin data as code data as code is like infrastructure as code, but it's for data, right? It's developing with data, right? Retraining machine learnings, going back to the data lake, getting data to make, to do analysis, to make the machine learning better post event or post action. So this, this data engineers like an SRE for data, it's a new, scalable role we're seeing. Do you see the same thing? Do you agree? Um, do you disagree or can you share >>Yourself? No, I have a lot of thoughts that plus I see AIOP solutions in the future should be not looking back. I need to be like we are in San Francisco bay. That means earthquake prediction. Right? I want AOPs to predict when the outages are gonna happen. When there's a performance issue. I don't think most AOPs vendors have not gone there yet. Like I spend a lot of time with data dog, Cisco app Dyna, right? Dynatrace, all this solution will go future towards to proactive solution with AOPs. But what you bring up a very good point on the data side. I think like we have a Amazon marketplace and Amazon for startup, there should be data exchange where you want to create for AOPs and AI service that customers are give the data, share the data because we thought the data algorithms are useless. I can come the best algorithm, but I gotta train them, modify them, tweak them, make them better, make them better. Yeah. And I think their whole data exchange is the industry has not thought through something you and me talk many times. Yeah. Yeah. I think the whole, that area is very important. >>You've always been on, um, on the Vanguard of data because, uh, it's been really fun. Yeah. >>Going back to our big data days back in 2009, you know, >>Look at, look how much data bricks has grown. >>It is uh, double, the key >>Cloud kinda went private, so good stuff. What are you working on right now? Give a, give a, um, plug for what you're working on. You'll still investing. >>I do still invest, but look, I'm a hundred percent on ISRA right now. I'm the CEO there. Yeah. Okay. So right. ISRA is my number one baby right now. So I'm looking at that growing customers and my customers are some of them, you like it's zoom auto desk, Mac of fee, uh, grandchildren, all the top customers. Um, mainly for it help desk customer service. AIOps those are three product lines and going after enterprise and commercial deals. >>And when should someone buy your product? What's what's their need? What category is it? >>I think they look whenever somebody needs to buy the product is if you need AOP solution to predict, keep your lights on predict S one area. If you want to improve employee experience, you are using a slack teams and you want to automate all your workflows. That's another value problem. Third is customer service. You don't want to hire more people to do it. Some of the areas where you want to scale your company, grow your company, eliminate the cost customer service, >>Great stuff, man. Doing great to see you. Thanks for coming on. Congratulations on the success of your company and your investments. Thanks for coming on the cube. Okay. I'm John fur here at the cube live in San Francisco for day one of two days of coverage of 80 summit, 2022. And we're gonna be at 80 summit in San, uh, in New York and the summer. So look for that on this calendar, of course go to eight of us, startups.com. I mentioned that it's a site for all the hot startups and of course the cube.net and Silicon angle.com. Thanks for watching. We'll be back more coverage after this short break. >>Okay. Welcome back everyone. This to cubes coverage here in San Francisco, California, a Davis summit, 2022, the beginning of the event season, as it comes back a little bit smaller footprint, a lot of hybrid events going on, but this is actually a physical event, a summit new York's coming in the summer. We'll be there too with the cube on the set. We're getting back in the groove, psyched to be back. We were at reinvent, uh, as well, and we'll see more and more cube, but you're gonna see a lot of virtual cube, a lot of hybrid cube. We wanna get all those conversations, try to get more interviews, more flow going. But right now I'm excited to have Corey Quinn here on the back on the cube chief cloud economists with duck, bill groove, he founder, uh, and chief content person always got great angles, fun comedy, authoritative Corey. Great to see you. Thank you. >>Thanks. Coming on. Sure is a lot of words to describe as shit posting, which is how I describe what I tend to do. Most days, >>Shit posting is an art form now. And if you look at Mark's been doing a lot of shit posting lately, all a billionaires are shit posting, but they don't know how to do it. Like they're not >>Doing it right. Something opportunity there. It's like, here's how to be even more obnoxious and incisive. It's honestly the most terrifying scenario for anyone is if I have that kind of budget to throw at my endeavors, it's like, I get excited with a nonsense I can do with a $20 gift card for an AWS credit compared to, oh well, if I could buy a mid-size island to begin doing this from, oh, then we're having fun. This >>Shit posting trend. Interesting. I was watching a thread go on about, saw someone didn't get a job because of their shit posting and the employer didn't get it. And then someone on the other side, I'll hire the guy cuz I get that's highly intelligent shit posting. So for the audience that doesn't know what shit posting is, what is shit posting? >>It's more or less talking about the world of enterprise tech, which even that sentence is hard to finish without falling asleep and toppling out of my chair in front of everyone on the livestream. But it's doing it in such a way that brings it to life that says the quiet part. A lot of the audience is thinking, but generally doesn't say either because they're polite or not a jackass or more prosaically are worried about getting fired for better or worse. I don't have that particular constraint, >>Which is why people love you. So let's talk about what you, what you think is, uh, worthy and not worthy in the industry right now, obviously, uh, coupons coming up in Spain, which they're having a physical event, you can see the growth of cloud native Amazons, all, all the Adams let see new CEO, Andy move on to be the chief of all. Amazon just saw him. The cover of was it time magazine. Um, he's under a lot of stress. Amazon's changed. Invoice has changed. What's working. What's not, what's rising, what's falling. What's hot. What's not, >>It's easy to sit here and criticize almost anything these folks do. They they're effectively in a fishbowl, but I have trouble imagining the logistics. It takes to wind up handling the catering for a relatively downscale event like this one this year, let alone running a 1.7 million employee company having to balance all the competing challenges and pressures and the rest. I, I just can't fathom what it would be like to look at all of AWS. It's, it's sprawling, immense that dominates our entire industry and say, okay, this is a good start, but I, I wanna focus on something with a broader remit. What is that? How do you even get into that position? And you can't win once you're there. All you can do is hold onto the tiger and hope you don't get mold. Well, >>There's a lot of force for good conversations, seeing a lot of that going on, Amazon's trying to port and he was trying to portray themselves as you know, the Pathfinder, you know, you're the pioneer, um, force for good. And I get that and I think that's a good angle as cloud goes mainstream. There's still the question of, we had a guy on just earlier, who was a skydiving instructor and we were joking about the early days of cloud. Like that was like skydiving, build a parachute open, you know, and now it same kind of thing. As you move to edge, things are like reliable in some areas, but still new, new fringe, new areas. That's crazy. Well, >>Since the last time we've spoken, uh, Steve Schmidt is now the CISO for all of Amazon and his backfill replacement. The AWS CISO is CJ. Moses who as a hobby races, a as a semi-pro race car driver to my understanding, which either, I don't know what direction to take that in either. This is what he does to relax or ultimately, or ultimately it's. Huh? That, that certainly says something about risk assessment. I'm not entirely sure what, but okay. Either way, sounds like more exciting >>Replacement ready <laugh> in case something goes wrong. I, the track highly >>Available >>CSOs. I gotta say one of the things I do like in the recent trend is that the tech companies are getting into the formula one, which I was never a fan of until I watched that Netflix series. But when you look at the formula one, it's pretty cool. Cause it's got some tech angles, I get the whole data instrumentation thing, but the most coolest thing about formula one is they have these new rigs out. Yeah. Where you can actually race in e-sports with other, in pure simulation of the race car. You gotta get the latest and video graphics card, but it's basically a tricked out PC with amazing monitors and you have all the equipment of F1 and you're basically simulating racing. >>Oh, it's great too. And I can see the appeal of these tech companies getting into it because these things are basically rocket shifts. When those cars go, like they're sitting there, we can instrument every last part of what is going on inside that vehicle. And then AWS crops up. And we can bill on every one of those dimensions too. And it's like slow down their hasty pudding one step at a time. But I do see the appeal. >>So I gotta ask you about, uh, what's going in your world. I know you have a lot of great success. We've been following you in the queue for many, many years. Got a great newsletter. Check out Corey Quinn's newsletter, uh, screaming in the cloud program. Uh, you're on the cutting edge and you've got a great balance between really being snarky and, and, and really being delivering content. That's exciting, uh, for people, uh, with a little bit of an edge, um, how's that going? Uh, what's back any blow back late there been uptick. What was, what are some of the things you're hearing from your audience, more Corey, more Corey. And then of course the, the PR team's calling you >>The weird thing about having an audience beyond a certain size is far and away as a landslide. The most common response I get is silence where it's high. I'm emailing an awful lot of people at last week in AWS every week and okay. They must not have heard me it. That is not actually true. People just generally don't respond to email because who responds to email newsletters. That sounds like something, a lunatic might do same story with response to live streams and podcasts. It's like, I'm gonna call into that am radio show and give them a piece of my mind. People generally don't do that. >>We should do that. Actually. I think sure would call in. Oh, I, >>I think >>Chief, we had that right now. People would call in and say, Corey, what do you think about X? >>Yeah. It not, everyone understands the full context of what I do. And in fact, increasingly few people do and that's fine. I, I keep forgetting that sometimes people do not see what I'm doing in the same light that I do. And that's fine. Blowback has been largely minimal. Honestly, I am surprised anything by how little I have gotten over the last five years of doing this, but it would be easier to dismiss me if I weren't generally. Right. When, okay, so you launch this new service and it seems pretty crappy to me cuz when I try and build something, it falls over and begs for help. And people might not like hearing that, but it's what customers are finding too. Yeah. I really am the voice of the customer. >>You know, I always joke with Dave ante about how John Fort's always at, uh, reinvent getting the interview with jazzy now, Andy we're there, you're there. And so we have these rituals at the events. It's all cool. Um, one of the rituals I like about your, um, your content is you like to get on the naming product names. Um, and, and, and, and, and kind of goof on that. Now why I like is because I used to work at ETT Packard where they used to name things as like engineers, HP 1 0 5, or we can't, >>We have a new monitor. How are we gonna name it? Throw the wireless keyboard down the stairs again. And there you go. Yeah. >>It's and the old joke at HP was if they, if they invented sushi, they'd say, yeah, we can't call sushi. It's cold, dead fish. That's what it is. And so the joke was cold. Dead fish is a better name than sushi. So you know is fun. So what's the, what are the, how's the Amazon doing in there? Have they changed their naming, uh, strategy, uh, on some of their, their >>Producting, they're going in different directions. When they named Amazon Aurora, they decided to explore a new theme of Disney princesses as they go down those paths. And some things are more descriptive. Some people are clearly getting bonused on a number of words. They can shove into it. Like the better a service is the longer it's name. Like AWS systems manager, session manager is a great one. I love the service, ridiculous name. They have systems manager, parameter store, which is great. They have secrets manager, which does the same thing. It's two words less, but that one costs money in a way that systems manage your parameter store does not. It's >>Fun. What's your, what's your favorite combination of acronyms >>Combination of you >>Got Ks. You got EMR, you got EC two. You got S three SQS. Well, Redshift the on an acronym, you >>Gots is one of my personal favorites because it's either elastic block store or elastic bean stock, depending entirely on the context of the conversation. >>They still up bean stalk. Or is that still around? Oh, >>They never turn anything off. They're like the anti Google, Google turns things off while they're still building it. Whereas Amazon is like, wow, we built this thing in 2005 and everyone hates it. But while we certainly can't change it, now it has three customers on it. John three <laugh>. >>Okay. >>Simple BV still haunts our dreams. >>I, I actually got an email. I saw one of my, uh, servers, all these C two S were being deprecated and I got an email I'm like, I couldn't figure out. Why can you just like roll it over? Why, why are you telling me just like, give me something else. Right. Okay. So let me talk about, uh, the other things I want to ask you is that like, okay. So as Amazon gets better in some areas, where do they need more work in your opinion? Because obviously they're all interested in new stuff and they tend to like put it out there for their end to end customers. But then they've got ecosystem partners who actually have the same product. Yes. And, and this has been well documented. So it's, it's not controversial. It's just that Amazon's got a database, Snowflake's got a database service. So Redshift, snowflake database is, so you got this co-op petition. Yes. How's that going? And what are you hearing about the reaction to any of that stuff? >>Depends on who you ask. They love to basically trot out a bunch of their partners who will say nice things about them. And it very much has heirs of, let's be honest, a hostage video, but okay. Cuz these companies do partner with Amazon and they cannot afford to rock the boat too far. I'm not partnered with anyone. I can say what I want and they're basically restricted to taking away my birthday at worse so I can live with that. >>All right. So I gotta ask about multi-cloud cause obviously the other cloud shows are coming up. Amazon hated that word. Multi-cloud um, a lot of people are saying, you know, it's not a real good marketing word, like multi sounds like, you know, root canal. Mm-hmm <affirmative> right. So is there a better description for multi-cloud >>Multiple single points? >>Dave loves that term. Yeah. >>Yeah. You're building in multiple single points of failure. Do it for the right reasons or don't do it as a default. I believe not doing it is probably the right answer. However, and if I were, if I were Amazon, I wouldn't want to talk about multi-cloud either as the industry leader, talk about other clouds, bad direction to go in from a market cap perspective, it doesn't end well for you, but regardless of what they want to talk about, or don't want to talk about what they say, what they don't say, I tune all of it out. And I look at what customers are doing and multi-cloud exists in a variety of forms. Some brilliant, some brain dead. It depends a lot on context. But my general response is when someone gets on stage from a company and tells me to do a thing that directly benefits their company. I am skeptical at best. Yeah. When customers get on stage and say, this is what we're doing, because it solves problems. That's when I shut up and listen. Yeah. >>Cool. Awesome. Corey, I gotta ask you a question, cause I know you, we you've been, you know, fellow journeymen and the, and the cloud journey going to all the events and then the pandemic hit where now in the third year, who knows what it's gonna gonna end. Certainly events are gonna look different. They're gonna be either changing footprint with the virtual piece, new group formations. Community's gonna emerge. You got a pretty big community growing and it's throwing like crazy. What's the weirdest or coolest thing, or just big chain angels. You've seen with the pandemic, uh, from your perspective, cuz you've been in the you're in the middle of the whitewater rafting. You've seen the events you circle offline. You saw the online piece, come in, you're commentating. You're calling balls and strikes in the industry. You got a great team developing over there. Duck bill group. What's the big aha moment that you saw with the pandemic. Weird, fun, serious, real in the industry and with customers what's >>Accessibility. Reinvent is a great example. When in the before times it's open to anyone who wants to attend, who can pony up two grand and a week in Las Vegas and get to Las Vegas from wherever they happen to be by moving virtually suddenly it, it embraces the reality that talent is even distributed. Opportunity is not. And that means that suddenly these things are accessible to a wide swath of audience and potential customer base and the rest that hadn't been invited to the table previously, it's imperative that we not lose that. It's nice to go out and talk to people and have people come up and try and smell my hair from time to time, I smell delightful. Let make assure you, but it was, but it's also nice to be. >>I have a product for you if you want, you know. >>Oh, excellent. I look forward to it. What is it putting? Why not? <laugh> >>What else have you seen? So when accessibility for talent, which by the way is totally home run. What weird things have happened that you've seen? Um, that's >>Uh, it's, it's weird, but it's good that an awful lot of people giving presentations have learned to tighten their message and get to the damn point because most people are not gonna get up from a front row seat in a conference hall, midway through your Aing talk and go somewhere else. But they will change a browser tab and you won't get them back. You've gotta be on point. You've gotta be compelling if it's going to be a virtual discussion. >>Yeah. And also turn off your IMEs too. >>Oh yes. It's always fun in the, in the meetings when you're talking to someone and their co is messaging them about, should we tell 'em about this? And I'm sitting there reading it and it's >>This guy is really weird. Like, >>Yes I am and I bring it into the conversation and then everyone's uncomfortable. It goes, wow. >>Why not? I love when my wife yells at me over I message. When I'm on a business call, like, do you wanna take that about no, I'm good. >>No, no. It's better off. I don't. No, the only encourager it's fine. >>My kids. Excellent. Yeah. That's fun again. That's another weird thing. And, and then group behavior is weird. Now people are looking at, um, communities differently. Yes. Very much so, because if you're fatigued on content, people are looking for the personal aspect. You're starting to see much more of like yeah. Another virtual event. They gotta get better. One and two who's there. >>Yeah. >>The person >>That's a big part of it too is the human stories are what are being more and more interesting. Don't get up here and tell me about your product and how brilliant you are and how you built it. That's great. If I'm you, or if I wanna work with you or I want to compete with you, or I wanna put on my engineering hat and build it myself. Cause why would I buy anything? That's more than $8. But instead, tell me about the problem. Tell me about the painful spot that you specialize in. Tell me a story there. >>I, I >>Think that gets a glimpse in a hook and >>Makes more, more, I think you nailed it. Scaling storytelling. Yes. And access to better people because they don't have to be there in person. I just did it thing. I never, we never would've done the queue. We did. Uh, Amazon stepped up in sponsors. Thank you, Amazon for sponsoring international women's day, we did 30 interviews, APAC. We did five regions and I interviewed this, these women in Asia, Pacific eight, PJ, they called for in this world. And they're amazing. I never would've done those interviews cuz I never, would've seen 'em at an event. I never would've been in Japan or Singapore to access them. And now they're in the index. They're in the network. They're collaborating on LinkedIn. So a threads are developing around connections that I've never seen before. Yes. Around the content, >>Absolutely >>Content value plus >>The networking. And that is the next big revelation of this industry is going to realize you have different companies. And in Amazon's case, different service teams, all, all competing with each other, but you have the container group and you have the database group and you have the message cuing group. But customers don't really want to build things from spare parts. They want a solution to a problem. I want to build an app that does Twitter for pets or whatever it is I'm trying to do. I don't wanna basically have to pick and choose and fill my shopping cart with all these different things. I want something that's gonna give me what I'm trying to get as close to turnkey as possible. Moving up the stack. That is the future. And just how it gets here is gonna be >>Well we're here with Corey Quinn, the master of the master of content here in the a ecosystem. Of course we we've been following up in the beginnings. Great guy. Check out his blog, his site, his newsletter screaming podcast. Cory, final question for you. Uh, what do you hear doing what's on your agenda this week in San Francisco and give a plug for the duck build group. What are you guys doing? I know you're hiring some people what's on the table for the company. What's your focus this week and put a plug in for the group. >>I'm here as a customer and basically getting outta my cage cuz I do live here. It's nice to actually get out and talk to folks who are doing interesting things at the duck build group. We solve one problem. We fixed the horrifying AWS bill, both from engineering and architecture, advising as well as negotiating AWS contracts because it turns out those things are big and complicated. And of course my side media projects last week in aws.com, we are, it it's more or less a content operation where I indulge my continual and ongoing law of affair with the sound of my own voice. >><laugh> and you good. It's good content. It's on, on point fun, Starky and relevant. So thanks for coming to the cube and sharing with us. Appreciate it. No, thank you. Fun. You. Okay. This the cube covers here in San Francisco, California, the cube is back at to events. These are the summits, Amazon web services summits. They happen all over the world. We'll be in New York and obviously we're here in San Francisco this week. I'm John furry. Keep, keep it right here. We'll be back with more coverage after this short break. Okay. Welcome back everyone. This's the cubes covers here in San Francisco, California, we're live on the show floor of AWS summit, 2022. I'm John for host of the cube and remember AWS summit in New York city coming up this summer, we'll be there as well. And of course reinvent the end of the year for all the cube coverage on cloud computing and AWS. The two great guests here from the APN global APN se Jenko and Jeff Grimes partner leader, Jeff and se is doing partnerships global APN >>AWS global startup program. Yeah. >>Okay. Say that again. >>AWS global startup program. >>That's the official name. >>I love >>It too long, too long for me. Thanks for coming on. Yeah, of course. Appreciate it. Tell us about what's going on with you guys. What's the, how was you guys organized? You guys we're obviously were in San Francisco bay area, Silicon valley, zillions of startups here, New York. It's got another one we're gonna be at tons of startups. Lot of 'em getting funded, big growth and cloud big growth and data security, hot and sectors. >>Absolutely. >>So maybe, maybe we could just start with the global startup program. Um, it's essentially a white glove service that we provide to startups that are built on AWS. And the intention there is to help identify use cases that are being built on top of AWS. And for these startups, we want to provide white glove support in co building products together. Right. Um, co-marketing and co-selling essentially, um, you know, the use cases that our customers need solved, um, that either they don't want to build themselves or are perhaps more innovative. Um, so the, a AWS global startup program provides white glove support, dedicated headcount for each one of those pillars. Um, and within our program, we've also provided incentives, programs go to market activities like the AWS startup showcase that we've built for these startups. >>Yeah. By the way, start AWS startups.com is the URL, check it out. Okay. So partnerships are key. Jeff, what's your role? >>Yeah. So I'm responsible for leading the overall F for, for the AWS global startup program. Um, so I've got a team of partner managers that are located throughout the us, uh, managing a few hundred startup ISVs right now. <laugh> >>Yeah, I got >>A lot. We've got a lot. >>There's a lot. I gotta, I gotta ask the tough question. Okay. I'm I'm a startup founder. I got a team. I just got my series a we're grown. I'm trying to hire people. I'm super busy. What's in it for me. Yeah. What do you guys bring to the table? I love the white glove service, but translate that what's in it. What do I get out of it? What's >>A good story. Good question. I focus, I think. Yeah, because we get, we get to see a lot of partners building their businesses on AWS. So, you know, from our perspective, helping these partners focus on what, what do we truly need to build by working backwards from customer feedback, right? How do we effectively go to market? Because we've seen startups do various things, um, through trial and error, um, and also just messaging, right? Because oftentimes partners or rather startups, um, try to boil the ocean with many different use cases. So we really help them, um, sort of laser focus on what are you really good at and how can we bring that to the customer as quickly as possible? >>Yeah. I mean, it's truly about helping that founder accelerate the growth of their company. Yeah. Right. And there's a lot that you can do with AWS, but focus is truly the key word there because they're gonna be able to find their little piece of real estate and absolutely deliver incredible outcomes for our customers. And then they can start their growth curve there. >>What are some of the coolest things you've seen with the APN that you can share publicly? I know you got a lot going on there, a lot of confidentiality. Um, but you know, we're here lot of great partners on the floor here. I'm glad we're back at events. Uh, a lot of stuff going on digitally with virtual stuff and, and hybrid. What are some of the cool things you guys have seen in the APN that you can point to? >>Yeah, absolutely. I mean, I can point to few, you can take them. Sure. So, um, I think what's been fun over the years for me personally, I came from a startup, ran sales at an early stage startup and, and I went through the whole thing. So I have a deep appreciation for what these guys are going through. And what's been interesting to see for me is taking some of these early stage guys, watching them progress, go public, get acquired, and see that big day mm-hmm <affirmative>, uh, and being able to point to very specific items that we help them to get to that point. Uh, and it's just a really fun journey to watch. >>Yeah. I, and part of the reason why I really, um, love working at the AWS, uh, global startup program is working with passionate founders. Um, I just met with a founder today that it's gonna, he's gonna build a very big business one day, um, and watching them grow through these stages and supporting that growth. Um, I like to think of our program as a catalyst for enterprise sort of scale. Yeah. Um, and through that we provide visibility, credibility and growth opportunities. >>Yeah. A lot, a lot of partners too. What I found talking to staff founders is when they have that milestone, they work so hard for it. Whether it's a B round C round Republic or get bought. Yeah. Um, then they take a deep breath and they look back at wow, what a journey it's been. So it's kind of emotional for sure. Yeah. Still it's a grind. Right? You gotta, I mean, when you get funding, it's still day one. You don't stop. It's no celebrate, you got a big round or valuation. You still gotta execute >>And look it's hypercompetitive and it's brutally difficult. And our job is to try to make that a little less difficult and navigate those waters right. Where everyone's going after similar things. >>Yeah. I think as a group element too, I observe that startups that I, I meet through the APN has been interesting because they feel part of AWS. Yeah, totally. As a group of community, as a vibe there. Um, I know they're hustling, they're trying to make things happen. But at the same time, Amazon throws a huge halo effect. I mean, that's a huge factor. I mean, yeah. You guys are the number one cloud in the business, the growth in every sector is booming. Yeah. And if you're a startup, you don't have that luxury yet. And look at companies like snowflake, they're built on top of AWS. Yeah. I mean, people are winning by building on AWS. >>Yeah. And our, our, our program really validates their technology first. So we have, what's called a foundation's technical review that we put all of our startups through before we go to market. So that when enterprise customers are looking at startup technology, they know that it's already been vetted. And, um, to take that a step further and help these partners differentiate, we use programs like the competency programs, the DevOps compet, the, the security competency, which continues to help, um, provide sort of a platform for these startups, help them differentiate. And also there's go to market benefits that are associated with that. >>Okay. So let me ask the, the question that's probably on everyone's mind, who's watching. Certainly I asked this a lot. There's a lot of companies startups out there who makes the, is there a criteria? Oh God, it's not like his sports team or anything, but like sure. Like there's activate program, which is like, there's hundreds of thousands of startups out there. Not everyone is at the APN. Right? Correct. So ISVs again, that's a whole nother, that's a more mature partner that might have, you know, huge market cap or growth. How do you guys focus? How do you guys focus? I mean, you got a good question, you know, a thousand flowers blooming all the time. Is there a new way you guys are looking at it? I know there's been some talk about restructure or, or new focus. What's the focus. >>Yeah. It's definitely not an easy task by any means. Um, but you know, I recently took over this role and we're really trying to establish focus areas, right. So obviously a lot of the fees that we look after our infrastructure ISVs, that's what we do. Uh, and so we have very specific pods that look after different type of partners. So we've got a security pod, we've got a DevOps pod, we've got core infrastructure, et cetera. And really we're trying to find these ISVs that can solve, uh, really interesting AWS customer challenges. >>So you guys have a deliberate, uh, focus on these pillars. So what infrastructure, >>Security, DevOps, and data and analytics, and then line of business >>Line of business line, like web marketing >>Solutions, business apps, >>Business, this owner type thing. Exactly. >>Yeah, exactly. >>So solutions there. Yeah. More solutions and the other ones are like hardcore. So infrastructure as well, like storage, backup, ransomware of stuff, or, >>Uh, storage, networking. >>Okay. Yeah. The classic >>Database, et cetera. Right. >>And so there's teams on each pillar. >>Yep. So I think what's, what's fascinating for the startup that we cover is that they've got, they truly have support from a build market sell perspective. Right. So you've got someone who's technical to really help them get the technology, figured out someone to help them get the marketing message dialed and spread, and then someone to actually do the co-sell, uh, day to day activities to help them get in front of customers. >>Probably the number one request that we always ask for Amazon is can we waste that sock report? Oh, download it, the console, which we use all the time. Exactly. But security's a big deal. I mean, you know, SREs are evolving, that role of DevOps is taking on dev SecOps. Um, I, I could see a lot of customers having that need for a relationship to move things faster. Do you guys provide like escalation or is that a part of a service or not, not part of a, uh, >>Yeah, >>So the partner development manager can be an escalation point. Absolutely. Think of them as an extension of your business inside of AWS. >>Great. And you guys how's that partner managers, uh, measure >>On those three pillars. Right. Got it. Are we billing, building valuable use cases? So product development go to market, so go to market activities, think blog, posts, webinars, case studies, so on and so forth. And then co-sell not only are we helping these partners win their current opportunities that they are sourcing, but can we also help them source net new deals? Yeah. Right. That's >>Very important. I mean, top asked from the partners is get me in front of customers. Right. Um, not an easy task, but that's a huge goal of ours to help them grow their top >>Line. Right. Yeah. In fact, we had some interviews here on the cube earlier talking about that dynamic of how enterprise customers are buying. And it's interesting, a lot more POCs. I have one partner here that you guys work with, um, on observability, they got a huge POC with capital one mm-hmm <affirmative> and the enterprises are engaging the startups and bringing them in. So the combination of open source software enterprises are leaning into that hard and bringing young growing startups in mm-hmm <affirmative>. Yep. So I could see that as a huge service that you guys can bring people in. >>Right. And they're bringing massively differentiated technology to the table. Mm-hmm <affirmative> the challenge is they just might not have the brand recognition that the big guys have. And so that it's our job is how do you get that great tech in front of the right situations? >>Okay. So my next question is about the show here, and then we'll talk globally. So here in San Francisco sure. You know, Silicon valley bay area, San Francisco bay area, a lot of startups, a lot of VCs, a lot of action. Mm-hmm <affirmative> so probably a big market for you guys. Yeah. So what's exciting here in SF and then outside SF, you guys have a global program, you see any trends that are geography based or is it sure areas more mature? There's certain regions that are better. I mean, I just interviewed a company here that's doing, uh, AWS edge really well in these cases. It's interesting that these, the partners are filling a lot of holes and gaps in the opportunities with AWS. So what's exciting here. And then what's the global perspective. >>Yeah, totally. So obviously a ton of partners, I, from the bay area that we support. Um, but we're seeing a lot of really interesting technology coming out of AMEA specifically. Yeah. Uh, and making a lot of noise here in the United States, which is great. Um, and so, you know, we definitely have that global presence and, and starting to see super differentiated technology come out of those regions. >>Yeah. Especially Tel Aviv. Yeah. >>Amy real quick, before you get in the surge. It's interesting. The VC market in, in Europe is hot. Yeah. They've got a lot of unicorns coming in. We've seen a lot of companies coming in. They're kind of rattling their own, you know, cage right now. Hey, look at us. We'll see if they crash, you know, but we don't see that happening. I mean, people have been projecting a crash now in, in the startup ecosystem for at least a year. It's not crashing. In fact, funding's up. >>Yeah. The pandemic was hard on a lot of startups for sure. Yeah. Um, but what we've seen is many of these startups, they, as quickly as they can grow, they can also pivot as, as, as well. Um, and so I've actually seen many of our startups grow through the pandemic because their use cases are helping customers either save money, become more operationally efficient and provide value to leadership teams that need more visibility into their infrastructure during a pandemic. >>It's an interesting point. I talked to Andy jazzy and Adam Leski both say the same thing during the pandemic necessity, the mother of all invention. Yep. And startups can move fast. So with that, you guys are there to assist if I'm a startup and I gotta pivot cuz remember iterate and pivot, iterate and pivot. So you get your economics, that's the playbook of the ventures and the models. >>Exactly. How >>Do you guys help me do that? Give me an example of walk me through, pretend me I'm a startup. Hey, I am on the cloud. Oh my God. Pandemic. They need video conferencing. Hey cube. Yeah. What do I need? Surge? What, what do I do? >>That's a good question. First thing is just listen. Yeah. I think what we have to do is a really good job of listening to the partner. Um, what are their needs? What is their problem statement and where do they want to go at the end of the day? Um, and oftentimes because we've worked with so many successful startups, they have come out of our program. We have, um, either through intuition or a playbook, determined what is gonna be the best path forward and how do we get these partners to stop focusing on things that will eventually, um, just be a waste of time yeah. And, or not provide, or, you know, bring any fruit to the table, which, you know, essentially revenue. >>Well, we love star rights here in the cube because one, um, they have good stories. They're oil and cutting edge, always pushing the envelope and they're kind of disrupting someone else. Yeah. And so they have an opinion. They don't mind sharing on camera. So love talking to startups. We love working with you guys on our startup showcases startups.com. Check out AWS startups.com and you got the showcases, uh, final. We I'll give you guys the last word. What's the bottom line bumper sticker for AP the global APN program. Summarize the opportunity for startups, what you guys bring to the table and we'll close it out. Totally start >>With you. Yeah. I think the AWS global startup program's here to help companies truly accelerate their business full stop. Right. And that's what we're here for. I love it. >>It's a good way to, it's a good way to put it Dito. >>Yeah. All right, sir. Thanks for coming on. Thanks John. Great to see you love working with you guys. Hey, startups need help. And the growing and huge market opportunities, the shift cloud scale data engineering, security infrastructure, all the markets are exploding in growth because of the digital transformation of the realities here. Open source and cloud all making it happen here in the cube in San Francisco, California. I'm John furrier, your host. Thanks for watching >>John. >>Hello and welcome back to the cubes live coverage here in San Francisco, California for AWS summit, 2022. I'm John for host of the cube. Uh, two days of coverage, AWS summit, 2022 in New York city. Coming up this summer, we'll be there as well at events are back. The cube is back of course, with the cube virtual cube hybrid, the cube.net, check it out a lot of content this year, more than ever, a lot more cloud data cloud native, modern applic is all happening. Got a great guest here. Jeremy Burton, Cub alumni, uh, CEO of observe Inc in the middle of all the cloud scale, big data observability Jeremy. Great to see you. Thanks >>Always great to come and talk to you on the queue, man. It's been been a few years, so, >>Um, well you, you got your hands. You're in the trenches with great startup, uh, good funding, great board, great people involved in the observability hot area, but also you've been a senior executive president of Dell, uh, EMC, uh, 11 years ago you had a, a vision and you actually had an event called cloud meets big data. Um, yeah. And it's here. You predicted it 11 years ago. Um, look around it's cloud meets big data. >>Yeah. I mean the, the cloud thing I think, you know, was, was probably already a thing, but the big data thing I do claim credit for, for, for sort of catching that bus out, um, you know, we, we were on the, the, the bus early and, and I think it was only inevitable. Like, you know, if you could bring the economics and the compute of cloud to big data, you, you could find out things you could never possibly imagine. >>So you're close to a lot of companies that we've been covering deeply. Snowflake obviously are involved, uh, the board level, you know, the founders, you know, the people there cloud, you know, Amazon, you know, what's going on here? Yeah. You're doing a startup as the CEO at the helm, uh, chief of observ, Inc, which is an observability, which is to me in the center of this confluence of data engineering, large scale integrations, um, data as code integrating into applic. I mean, it's a whole nother world developing, like you see with snowflake, it means snowflake is super cloud as we call it. So a whole nother wave is here. What's your, what's this wave we're on what's how would you describe the wave? >>Well, a couple of things, I mean, people are, I think riding more software than, than ever fall. Why? Because they've realized that if, if you don't take your business online and offer a service, then you become largely irrelevant. And so you you've got a whole set of new applications. I think, I think more applications now than any point. Um, not, not just ever, but the mid nineties, I always looked at as the golden age of application development. Now back then people were building for windows. Well, well now they're building for things like AWS is now the platform. Um, so you've got all of that going on. And then at the same time, the, the side effect of these applications is they generate data and lots of data and the, you know, the sort of the transactions, you know, what you bought today or something like that. But then there's what we do, which is all the telemetry data, all the exhaust fumes. And I think people really are realizing that their differentiation is not so much their application. It's their understanding of the data. Can, can I understand who my best customers are, what I sell today. If people came to my website and didn't buy, then I not, where did they drop off all of that they wanna analyze. And, and the answers are all in the data. The question is, can you understand it >>In our last startup showcase, we featured data as code. One of the insights that we got out of that I wanna get your opinion on our reaction to is, is that data used to be put into a data lake and turns into a data swamp or throw into the data warehouse. And then we'll do some query, maybe a report once in a while. And so data, once it was done, unless it was real time, even real time was not good anymore after real time. That was the old way. Now you're seeing more and more, uh, effort to say, let's go look at the data cuz now machine learning is getting better. Not just train once mm-hmm <affirmative> they're iterating. Yeah. This notion of iterating and then pivoting, iterating and pivoting. Yeah, that's a Silicon valley story. That's like how startups work, but now you're seeing data being treated the same way. So now you have another, this data concept that's now yeah. Part of a new way to create more value for the apps. So this whole, this whole new cycle of >>Yeah. >>Data being reused and repurposed and figured out and >>Yeah, yeah. I'm a big fan of, um, years ago. Uh, uh, just an amazing guy, Andy McAfee at the MIT C cell labs I spent time with and he, he had this line, which still sticks to me this day, which is look I'm I'm. He said I'm part of a body, which believes that everything is a matter of data. Like if you, of enough data, you can answer any question. And, and this is going back 10 years when he was saying these kind of things and, and certainly, you know, research is on the forefront. But I, I think, you know, starting to see that mindset of the, the sort of MIT research be mainstream, you know, in enterprises, they they're realizing that yeah, it is about the data. You know, if I can better understand my data better than my competitor than I've got an advantage. And so the question is is, is how, what, what technologies and what skills do I need in my organization to, to allow me to do that. So >>Let's talk about observing you the CEO of, okay. Given you've seen the wave before you're in the front lines of observability, which again is in the center of all this action what's going on with the company. Give a quick minute to explain, observe for the folks who don't know what you guys do. What's the company doing? What's the funding status, what's the product status and what's the customer status. Yeah. >>So, um, we realized, you know, a handful of years ago, let's say five years ago that, um, look, the way people are building applications is different. They they're way more functional. They change every day. Uh, but in some respects they're a lot more complicated. They're distributed. They, you know, microservices architectures and when something goes wrong, um, the old way of troubleshooting and solving problems was not gonna fly because you had SA so much change going into production on a daily basis. It was hard to tell like where the problem was. And so we thought, okay, it's about time. Somebody looks at the exhaust fumes from this application and all the telemetry data and helps people troubleshoot and make sense of the problems that they're seeing. So, I mean, that's observability, it's actually a term that goes back to the 1960s. It was a guy called, uh, Rudolph like, like everything in tech, you know, it's, it's a reinvention of, of something from years gone by. >>But, um, there's a guy called, um, Rudy Coleman in 1960s, kinder term. And, and, and the term was been able to determine the state of a system by looking at its external outputs. And so we've been going on this for, uh, the best part of the all years now. Um, it took us three years just to build the product. I think, I think what people don't appreciate these days often is the barrier to entry in a lot of these markets is quite high. You, you need a lot of functionality to have something that's credible with a customer. Um, so yeah, this last year we, we, we did our first year selling, uh, we've got about 40 customers now. <affirmative> um, we just we've got great investors for the hill ventures. Uh, I mean, Mike SP who was, you know, the, the guy who was the, really, the first guy in it snowflake and the, the initial investor were fortunate enough to, to have Mike on our board. And, um, you know, part of the observed story yeah. Is closely knit with snowflake because all of that time data know we, we still are in there. >>So I want to get, uh, >>Yeah. >>Pivot to that. Mike Pfizer, snowflake, Jeremy Burton, the cube kind of, kind of same thinking this idea of a super cloud or what snowflake became snowflake is massively successful on top of AWS. Mm-hmm <affirmative> and now you're seeing startups and companies build on top of snowflake. Yeah. So that's become an entrepreneurial story that we think that to go big in the cloud, you can have a cloud on a cloud, uh, like as Jerry, Jerry Chan and Greylock calls it castles in the cloud where there are moats in the cloud. So you're close to it. I know you're doing some stuff with snowflake. So a startup, what's your view on building on top of say a snowflake or an AWS, because again, you gotta go where the data is. You need all the data. >>Yeah. So >>What's your take on that? >>I mean, having enough gray hair now, um, you know, again, in tech, I think if you wanna predict the future, look at the past. And, uh, you know, to many years ago, 25 years ago, I was at a, a smaller company called Oracle and an Oracle was the database company. And, uh, their, their ambition was to manage all of the world's transactional data. And they built on a platform or a couple of platforms, one, one windows, and the other main one was Solaris. And so at that time, the operator and system was the platform. And, and then that was the, you know, ecosystem that you would compete on top of. And then there were companies like SAP that built applications on top of Oracle. So then wind the clock forward 25 years gray hairs. <laugh> the platform, isn't the operating system anymore. The platform is AWS, you know, Google cloud. I gotta probably look around if I say that in. Yeah. It's >>Okay. But hyperscale, yeah. CapX built out >>That is the new platform. And then snowflake comes along. Well, their aspiration is to manage all of the, not just human generator data, but machine generated data in the world of cloud. And I think they they've done an amazing job doing for the, I'd say, say the, the big data world, what Oracle did for the relational data world, you know, way back 25 years ago. And then there are folks like us come along and, and of course my ambition would be, look, if, if we can be as successful as an SAP building on top of snow snowflake, uh, as, as they were on top of Oracle, then, then we'd probably be quite happy. >>So you're building on top of snowflake. >>We're building on top of snowflake a hundred percent. And, um, you know, I've had folks say to me, well, aren't you worried about that? Isn't that a risk? It's like, well, that that's a risk. You >>Still on the board. >>Yeah. I'm still on the board. Yeah. That that's a risk I'm prepared to take <laugh> I am long on snowflake you, >>Well, you're in a good spot. Stay on the board, then you'll know what's going on. Okay. No know just doing, but the, this is a real dynamic. It is. It's not a one off it's. >>Well, and I do believe as well that the platform that you see now with AWS, if you look at the revenues of AWS is an order of magnitude more than Microsoft was 25 years ago with windows mm-hmm <affirmative>. And so I believe the opportunity for folks like snowflake and folks like observe it's an order of magnitude more than it was for the Oracle and the SAPs of the old >>World. Yeah. And I think this is really, I think this is something that this next generation of entrepreneurship is the go big scenario is you gotta be on a platform. Yeah. >>It's quite >>Easy or be the platform, but it's hard. There's only like how many seats are at that table left. >>Well, value migrates up over time. So, you know, when the cloud thing got going, there were probably 10, 20, 30, you know, Rackspace and there's 1,000,001 infrastructure, a service platform as a service, my, my old, uh, um, employee EMC, we had pivotal, you know, pivotal was a platform as a service. You don't hear so much about it, these, but initially there's a lot of players and then it consolidates. And then to, to like extract, uh, a real business, you gotta move up, you gotta add value, you gotta build databases, then you gotta build applications. So >>It's interesting. Moving from the data center of the cloud was a dream for starters. Cause then if the provision, the CapEx, now the CapEx is in the cloud. Then you build on top of that, you got snowflake you on top of that, the >>Assumption is almost that compute and storage is free. I know it's not quite free. Yeah. It's >>Almost free, >>But, but you can, you know, as an application vendor, you think, well, what can I do if I assume compute and storage is free, that's the mindset you've gotta get into. >>And I think the platform enablement to value. So if I'm an entrepreneur, I'm gonna get a serious, multiple of value in what I'm paying. Yeah. Most people don't even blanket their Avis pills unless they're like massively huge. Yeah. Then it's a repatriation question or whatever discount question, but for most startups or any growing company, the Amazon bill should be a small factor. >>Yeah. I mean, a lot of people, um, ask me like, look, you're building on snowflake. Um, you, you know, you are, you are, you're gonna be, you're gonna be paying their money. How, how, how, how does that work with your business model? If you're paying them money, you know, do, do you have a viable business? And it's like, well, okay. I, we could build a database as well in observe, but then I've got half the development team working on in that will never be as good as snowflake. And so we made the call early on that. No, no, we, we wanna innovate above the database. Yeah. Right. Snowflake are doing a great job of innovating on the database and, and the same is true of something like Amazon, like, like snowflake could have built their own cloud and their own platform, but they didn't. >>Yeah. And what's interesting is that Dave <inaudible> and I have been pointing this out and he's actually more on snowflake. I I've been looking at data bricks, um, and the same dynamics happening, the proof is the ecosystem. Yeah. I mean, if you look at Snowflake's ecosystem right now and data bricks it's exploding. Right. I mean, the shows are selling out the floor. Space's book. That's the old days at VMware. Yeah. The old days at AWS >>One and for snowflake and, and any platform provider, it's a beautiful thing. You know, we build on snowflake and we pay them money. They don't have to sell to us. Right. And we do a lot of the support. And so the, the economics work out really, really well. If you're a platform provider and you've got a lot of ecosystems. >>Yeah. And then also you get, you get a, um, a trajectory of, uh, economies of scale with the institutional knowledge of snowflake integrations, right. New products. You're scaling that function with the, >>Yeah. I mean, we manage 10 petabytes of data right now. Right. When I, when I, when I arrived at EMC in 2010, we had, we had one petabyte customer. And, and so at observe, we've been only selling the product for a year. We have 10 petabytes of data under management. And so been able to rely on a platform that can manage that is invaluable, >>You know, but Jeremy Greek conversation, thanks for sharing your insights on the industry. Uh, we got a couple minutes left. Um, put a plug in for observe. What do you guys, I know you got some good funding, great partners. I don't know if you can talk about your, your, your POC customers, but you got a lot of high ends folks that are working with you. You getting traction. Yeah. >>Yeah. >>Scales around the corner. Sounds like, are you, is that where you are scale? >>Got, we've got a big announcement coming up in two or weeks. We've got, we've got new funding, um, which is always great. Um, the product is, uh, really, really close. I think, as a startup, you always strive for market fit, you know, which is at which point can you just start hiring salespeople? And the revenue keeps going. We're getting pretty close to that right now. Um, we've got about 40 SaaS companies run on the platform. They're almost all AWS Kubernetes, uh, which is our sweet spot to begin with, but we're starting to get some really interesting, um, enterprise type customers. We're, we're, you know, F five networks we're POC in right now with capital one, we got some interest in news around capital one coming up. I, I can't share too much, uh, but it's gonna be exciting. And, and like I saids hill continued to, to, to stick, >>I think capital one's a big snowflake customer as well. Right. They, >>They were early in one of the things that attracted me to capital one was they were very, very good with snowflake early on. And, and they put snowflake in a position in the bank where they thought that snowflake could be successful. Yeah. And, and today that, that is one of Snowflake's biggest accounts. >>So capital one, very innovative cloud, obviously AIOS customer and very innovative, certainly in the CISO and CIO, um, on another point on where you're at. So you're, Prescale meaning you're about to scale, right? So you got POCs, what's that trick GE look like, can you see around the corner? What's, what's going on? What's on, around the corner. That you're, that you're gonna hit the straight and narrow and, and gas it >>Fast. Yeah. I mean, the, the, the, the key thing for us is we gotta get the product. Right. Um, the nice thing about having a guy like Mike Pfizer on the board is he doesn't obsess about revenue at this stage is questions that the board are always about, like, is the product, right? Is the product right? Is the product right? If you got the product right. And cuz we know when the product's right, we can then scale the sales team and, and the revenue will take care of itself. Yeah. So right now all the attention is on the product. Um, the, this year, the exciting thing is we were, we're adding all the tracing visualizations. So people will be able to the kind of things that back in the day you could do with the new lakes and, and AppDynamics, the last generation of, of APM tools, you're gonna be able to do that within observe. And we've already got the logs and the metrics capability in there. So for us, this year's a big one, cuz we sort of complete the trifecta, you know, the, the logs, >>What's the secret sauce observe. What if you had the, put it into a, a sentence what's the secret sauce? I, >>I, I think, you know, an amazing founding engineering team, uh, number one, I mean, at the end of the day, you have to build an amazing product and you have to solve a problem in a different way. And we've got great long term investors. And, and the biggest thing our investors give is actually it's not just money. It gives us time to get the product, right. Because if we get the product right, then we can get the growth. >>Got it. Final question. Why I got you here? You've been on the enterprise business for a long time. What's the buyer landscape out there. You got people doing POCs on capital one scale. So we know that goes on. What's the appetite at the buyer side for startups and what are their requirements that you're seeing? Uh, obviously we're seeing people go in and dip into the startup pool because new ways to refactor their business restructure. So a lot happening in cloud. What's the criteria. How are enterprises engaging in with startups? >>Yeah. I mean, enterprises, they know they've gotta spend money transforming the business. I mean, this was, I almost feel like my old Dell or EMC self there, but, um, what, what we were saying five years ago is happening. Um, everybody needs to figure out out a way to take their, this to this digital world. Everybody has to do it. So the nice thing from a startup standpoint is they know at times they need to risk or, or take a bet on new technology in order to, to help them do that. So I think you've got buyers that a have money, uh, B prepared to take risks and it's, it's a race against time to, you know, get their, their offerings in this. So a new digital footprint, >>Final, final question. What's the state of AWS. Where do you see them going next? Obviously they're continuing to be successful. How does cloud 3.0, or they always say it's day one, but it's more like day 10. Uh, but what's next for Aw. Where do they go from here? Obviously they're doing well. They're getting bigger and bigger. >>Yeah. They're, they're, it's an amazing story. I mean, you know, we we're, we're on AWS as well. And so I, I think if they keep nurturing the builders in the ecosystem, then that is their superpower. They, they have an early leads. And if you look at where, you know, maybe the likes of Microsoft lost the plot in the, in the late it was, they stopped, uh, really caring about developers and the folks who were building on top of their ecosystem. In fact, they started buying up their ecosystem and competing with people in their ecosystem. And I see with AWS, they, they have an amazing head start and if they did more, you know, if they do more than that, that's, what's gonna keep the jut rolling for many years to come. Yeah, >>They got the silicone and they got the staff act, developing Jeremy Burton inside the cube, great resource for commentary, but also founding with the CEO of a company called observing in the middle of all the action on the board of snowflake as well. Um, great start. Thanks for coming on the cube. >>Always a pleasure. >>Okay. Live from San Francisco to cube. I'm John for your host. Stay with us more coverage from San Francisco, California after the short break. >>Hello. Welcome back to the cubes coverage here live in San Francisco, California. I'm John furrier, host of the cubes cube coverage of AWS summit 2022 here in San Francisco. We're all the developers of the bay area at Silicon valley. And of course, AWS summit in New York city is coming up in the summer. We'll be there as well. SF and NYC cube coverage. Look for us. Of course, reinforcing Boston and re Mars with the whole robotics AI thing, all coming together. Lots of coverage stay with us today. We've got a great guest from Deibel VC. John Skoda, founding partner, entrepreneurial venture is a venture firm. Your next act, welcome to the cube. Good to see you. >>Good to see you, Matt. I feel like it's been forever since we've been able to do something in person. Well, >>I'm glad you're here because we run into each other all the time. We've known each other for over a decade. Um, >><affirmative>, it's been at least 10 years now, >>At least 10 years more. And we don't wanna actually go back as frees back, uh, the old school web 1.0 days. But anyway, we're in web three now. So we'll get to that in >>Second. We, we are, it's a little bit of a throwback to the path though, in my opinion, >><laugh>, it's all the same. It's all distributed computing and software. We ran each other in cube con you're investing in a lot of tech startup founders. Okay. This next level, next gen entrepreneurs have a new makeup and it's software. It's hardcore tech in some cases, not hardcore tech, but using software is take old something old and make it better, new, faster. <laugh>. So tell us about Deibel what's the firm. I know you're the founder, uh, which is cool. What's going on. Explain >>What you're doing. I mean, you remember I'm a recovering entrepreneur, right? So of course I, I, I, >>No, you're never recovering. You're always entrepreneur >>Always, but we are also always recovering. So I, um, started my first company when I was 24. If you remember, before there was Facebook and friends, there was instant messaging. People were using that product at work every day, they were creating a security vulnerability between their network and the outside world. So I plugged that hole and built an instant messaging firewall. It was my first company. The company was called, I am logic and we were required by Symantec. Uh, then spent 12 years investing in the next generation of our companies, uh, early investor in open source companies and cloud companies and spent a really wonderful 12 years, uh, at a firm called NEA. So I, I feel like my whole life I've been either starting enterprise software companies or helping founders start enterprise software companies. And I'll tell you, there's never been a better time than right now to start enter price software company. >>So, uh, the passion for starting a new firm was really a recognition that founders today that are starting in an enterprise software company, they, they tend to be, as you said, a more technical founder, right? Usually it's a software engineer or a builder mm-hmm <affirmative>, uh, they are building products that are serving a slightly different market than what we've traditionally seen in enterprise software. Right? I think traditionally we've seen it buyers or CIOs that have agendas and strategies, which, you know, purchased software that has traditionally bought and sold tops down. But, you know, today I think the most successful enterprise software companies are the ones that are built more bottoms up and have more technical early opts. And generally speaking, they're free to use. They're free to try. They're very commonly community source or open source companies where you have a large technical community that's supporting them. So there's a, there's kind of a new normal now I think in great enterprise software. And it starts with great technical founders with great products and great and emotions. And I think there's no better place to, uh, service those people than in the cloud and uh, in, in your community. >>Well, first of all, congratulations, and by the way, you got a great pedigree and great background, super smart admire of your work and your, and, and your founding, but let's face it. Enterprise is hot because digital transformation is all companies. The is no, I mean, consumer is enterprise. Now everything is what was once a niche. No, I won't say niche category, but you know, not for the faint of heart, you know, investors, >>You know, it's so funny that you say that enterprise is hot because you, and I feel that way now. But remember, like right now, there's also a giant tech in VC conference in Miami <laugh> it's covering cryptocurrencies and FCS and web three. So I think beauty is definitely in the eye of the beholder <laugh> but no, I, I will tell you, >>Ts is one big enterprise, cuz you gotta have imutability you got performance issues. You have, I IOPS issues. Well, and, >>And I think all of us here that are, uh, maybe students of history and have been involved in, open in the cloud would say that we're, you know, much of what we're doing is, uh, the predecessors of the web web three movement. And many of us I think are contributors to the web three movement. >>The hype is definitely that three. >>Yeah. But, but >>You know, for >>Sure. Yeah, no, but now you're taking us further east to Miami. So, uh, you know, look, I think, I, I think, um, what is unquestioned with the case now? And maybe it's, it's more obvious the more time you spend in this world is this is the fastest growing part of enterprise software. And if you include cloud infrastructure and cloud infrastructure spend, you know, it is by many men over, uh, 500 billion in growing, you know, 20 to 30% a year. So it it's a, it's a just incredibly fast, >>Let's getting, let's get into some of the cultural and the, the shifts that are happening, cuz again, you, you have the luxury of being in enterprise when it was hard, it's getting easier and more cooler. I get it and more relevant, but it's also the hype of like the web three, for instance. But you know, uh, um, um, the CEO snowflake, okay. Has wrote a book and Dave Valenti and I were talking about it and uh, Frank Luman has says, there's no playbooks. We always ask the CEOs, what's your playbook. And he's like, there's no playbook, situational awareness, always Trump's playbooks. So in the enterprise playbook, oh, higher direct sales force and SAS kind of crushed the, at now SAS is being redefined, right. So what is SAS? Is snowflake a SAS or is that a platform? So again, new unit economics are emerging, whole new situation, you got web three. So to me there's a cultural shift, the young entrepreneurs, the, uh, user experience, they look at Facebook and say, ah, you know, they own all my data. You know, we know that that cliche, um, they, you know, the product. So as this next gen, the gen Z and the millennials come in and our customers and the founders, they're looking at things a little bit differently and the tech better. >>Yeah. I mean, I mean, I think we can, we can see a lot of commonalities across all successful startups and the overall adoption of technology. Uh, and, and I would tell you, this is all one big giant revolution. I call it the user driven revolution. Right. It's the rise of the user. Yeah. And you might say product like growth is currently the hottest trend in enterprise software. It's actually user like growth, right. They're one in the same. So sometimes people think the product, uh, is what is driving. You >>Just pull the >>Product through. Exactly, exactly. And so that's that I, that I think is really this revolution that you see, and, and it does extend into things like cryptocurrencies and web three and, you know, sort of like the control that is taken back by the user. Um, but you know, many would say that, that the origins of this movement maybe started with open source where users were, are contributors, you know, contributors, we're users and looking back decades and seeing how it, how it fast forward to today. I think that's really the trend that we're all writing and it's enabling these end users. And these end users in our world are developers, data engineers, cybersecurity practitioners, right. They're really the users. And they're really the, the beneficiaries and the most, you know, kind of valued people in >>This. I wanna come back to the data engineers in a second, but I wanna make a comment and get your reaction to, I have a, I'm a GenXer technically, so for not a boomer, but I have some boomer friends who are a little bit older than me who have, you know, experienced the sixties. And I've, I've been staying on the cube for probably about eight years now that we are gonna hit a digital hippie revolution, meaning a rebellion against in the sixties was rebellion against the fifties and the man and, you know, summer of love. That was a cultural differentiation from the other one other group, the predecessors. So we're kind of having that digital moment now where it's like, Hey boomers, Hey people, we're not gonna do that anymore. We hate how you organize shit. >>Right. But isn't this just technology. I mean, isn't it, isn't it like there used to be the old adage, like, you know, you would never get fired for buying IBM, but now it's like, you obviously probably would get fired if you bought IBM. And I mean, it's just like the, the, I think, I think >>It's the main for days, those renegades were breaking into Stanford, starting the home brew club. So what I'm trying to get at is that, do you see the young cultural revolution also, culturally, just, this is my identity NFTs to me speak volumes about my, I wanna associate with NFTs, not single sign on. Well, >>Absolutely. And, and I think like, I think you're hitting on something, which is like this convergence of, of, you know, societal trends with technology trends and how that manifests in our world is yes. I think like there is unquestionably almost a religion around the way in which a product is built. Right. And we can use open source, one example of that religion. Some people will say, look, I'll just never try a product in the cloud if it's not open source. Yeah. I think cloud, native's another example of that, right? It's either it's, you know, it either is cloud native or it's not. And I think a lot of people will look at a product and say, look, you know, you were not designed in the cloud era. Therefore I just won't try you. And sometimes, um, like it or not, it's a religious decision, right? It's, it's something that people just believe to be true almost without, uh, necessarily. I mean >>The decision making, let me ask you this next question. As a VC. Now you look at pitch, well, you've made a VC for many years, but you also have the founder, uh, entrepreneurial mindset, but you can get empathize with the founders. You know, hustle is a big part of the, that first founder check, right? You gotta convince someone to part with their ch their money and the first money in which you do a lot of is about believing in the person. So fing, so you make, it is hard. Now you, the data's there, you either have it cloud native, you either have the adaption or traction. So honesty is a big part of that pitch. You can't fake it. Oh, >>AB absolutely. You know, there used to be this concept of like the persona of an entrepreneur, right. And the persona of the entrepreneur would be, you know, somebody who was a great salesperson or somebody who tell a great story. You, I still think that that's important, right? It still is a human need for people to believe in narratives and stories. But having said that you're right, the proof is in the pudding, right? At some point you click download and you try the product and it does what it says it it's gonna do, or it doesn't, or it either stands up to the load test or it doesn't. And so I, I feel like in this new economy that we live in, it's a shift from maybe the storytellers and the creators to, to the builders, right. The people that know how to build great product. And in some ways the people that can build great product yeah. Stand out from the crowd. And they're the ones that can build communities around their products. And, you know, in some ways can, um, you know, kind of own more of the narrative because their products exactly >>The volume back to the user led growth. >>Exactly. And it's the religion of, I just love your product. Right. And I, I, I, um, Doug song was the founder of du security used to say, Hey, like, you know, the, the really like in today's world of like consumption based software, the user is only gonna give you 90 seconds to figure out whether or not you're a company that's easy to do business with. Right. And so you can say, and do all the things that you want about how easy you are to work with. But if the product isn't easy to install, if it's not easy to try, if it's not, if, if the, you know, it's gotta speak to >>The, speak to the user, but let me ask a question now that the people watching who are maybe entrepreneurial entrepreneur, um, masterclass here is in session. So I have to ask you, do you prefer, um, an entrepreneur to come in and say, look at John. Here's where I'm at. Okay. First of all, storytelling's fine. Whether you're an extrovert or introvert, have your style, sell the story in a way that's authentic, but do you, what do you prefer to say? Here's where I'm at? Look, I have an idea. Here's my traction. I think here's my MVP prototype. I need help. Or do you wanna just see more stats? What's the, what's the preferred way that you like to see entrepreneurs come in and engage, engage? >>There's tons of different styles, man. I think the single most important thing that every founder should know is that we, we don't invest in what things are today. We invest in what we think something will become. Right. And I think that's why we all get up in the morning and try to build something different, right? It's that we see the world a different way. We want it to be a different way, and we wanna work every single moment of the day to try to make that vision a reality. So I think the more that you can show people where you want to be, the more likely somebody is gonna align with your vision and, and want to invest in you and wanna be along for the ride. So I, I wholeheartedly believe in showing off what you got today, because eventually we all get down to like, where are we and what are we gonna do together? But, um, no, I >>Show >>The path. I think the single most important thing for any founder and VC relationship is that they have the same vision, uh, have the same vision. You can, you can get through bumps in the road, you can get through short term spills. You can all sorts of things in the middle of the journey can happen. Yeah. But it doesn't matter as much if you share the same long term vision, >>Don't flake out and, and be fashionable with the latest trends because it's over before you can get there. >>Exactly. I think many people that, that do what we do for a living will say, you know, ultimately the future is relatively easy to predict, but it's the timing that's impossible to predict. So you, you know, you sort of have to balance the, you know, we, we know that the world is going this way and therefore we're gonna invest a lot of money to try to make this a reality. Uh, but sometimes it happens in six months. Sometimes it takes six years is sometimes like 16 years. >>Uh, what's the hottest thing in enterprise that you see the biggest wave that people should pay attention to that you're looking at right now with Desel partners, Tebel dot your site. What's the big wave. What's your big >>Wave. There, there's three big trends that we invest in. And they're the, they're the only things we do day in, day out. One is the explosion and open source software. So I think many people think that all software is unquestionably moving to an open source model in some form or another yeah. Tons of reasons to debate whether or not that is gonna happen and on what timeline happening >>Forever. >>But it is, it is accelerating faster than we've ever seen. So I, I think it's, it's one big, massive wave that we continue to ride. Um, second is the rise of data engineering. Uh, I think data engineering is in and of itself now, a category of software. It's not just that we store data. It's now we move data and we develop applications on data. And, uh, I think data is in and of itself as big of a, a market as any of the other markets that we invest in. Uh, and finally, it's the gift that keeps on giving. I've spent my entire career in it. We still feel that security is a market that is under invested. It is, it continues to be the place where people need to continue to invest and spend more money. Yeah. Uh, and those are the three major trends that we run >>And security, you think we all need a dessert do over, right? I mean, do we need a do over in security or is what's the core problem? I, >>I, I keep using this word underinvested because I think it's the right way to think about the problem. I think if you, I think people generally speaking, look at cyber security as an add-on. Yeah. But if you think about it, the whole economy is moving online. And so in, in some ways like security is core to protecting the digital economy. And so it's, it shouldn't be an afterthought, right? It should be core to what everyone is doing. And that's why I think relative to the trillions of dollars that are at stake, uh, I believe the market size for cybersecurity is around 150 billion. And it still is a fraction of what we're, what >>We're and security even boom is booming now. So you get the convergence of national security, geopolitics, internet digital >>That's right. You mean arguably, right? I mean, arguably again, it's the area of the world that people should be spending more time and more money given what to stake. >>I love your thesis. I gotta, I gotta say, you gotta love your firm. Love. You're doing we're big supporters of your mission. Congratulations on your entrepreneurial venture. And, uh, we'll be, we'll be talking and maybe see a Cub gone. Uh, >>Absolutely. >>Certainly EU maybe even north America's in Detroit this year. >>Huge fan of what you guys are doing here. Thank you so much for having me on >>The show. Guess bell VC Johnson here on the cube. Check him out. Founder for founders here on the cube, more coverage from San Francisco, California. After the short break, stay with us. Everyone. Welcome to the queue here. Live in San Francisco, California for AWS summit, 2022 we're live we're back with the events. Also we're virtual. We got hybrid all kinds of events. This year, of course, 80% summit in New York city is happening this summer. We'll be there with the cube as well. I'm John. Again, John host of the cube got a great guest here. Justin Coby owner and CEO of innovative solutions. Their booth is right behind us. Justin, welcome to the cube. >>Thank you. Thank you for having me. >>So we're just chatting, uh, uh, off camera about some of the work you're doing. You're the owner of and CEO. Yeah. Of innovative. Yeah. So tell us a story. What do you guys do? What's the elevator pitch. >>Yeah. <laugh> so the elevator pitch is we are, uh, a hundred percent focused on small to midsize businesses that are moving into the cloud or have already moved to the cloud and really trying to understand how to best control, cost, security, compliance, all the good stuff, uh, that comes along with it. Um, exclusively focused on AWS and, um, you know, about 110 people, uh, based in Rochester, New York, that's where our headquarters is, but now we have offices down in Austin, Texas up in Toronto, uh, key Canada, as well as Chicago. Um, and obviously in New York, uh, you know, the, the business was never like this, uh, five years ago, um, founded in 1989, made the decision in 2018 to pivot and go all in on the cloud. And, uh, I've been a part of the company for about 18 years, bought the company about five years ago and it's been a great ride. It >>It's interesting. The manages services are interesting with cloud cause a lot of the heavy liftings done by AWS. So we had Matt on your team on earlier talking about some of the edge stuff. Yeah. But you guys are a managed cloud service. You got cloud advisory, you know, the classic service that's needed, but the demands coming from cloud migrations and application modernization and obviously data is a huge part of it. Huge. How is this factoring into what you guys do and your growth cuz you guys are the number one partner on the SMB side for edge. Yeah. For AWS, you got results coming in. Where's the, where's the forcing function. What's the pressure point. What's the demand like? >>Yeah. It's a great question. Every CEO I talk to, that's a small to midsize business. They're trying to understand how to leverage technology. It better to help either drive a revenue target for their own business, uh, help with customer service as so much has gone remote now. And we're all having problems or troubles or issues trying to hire talent. And um, you know, tech ISNT really at the, at the forefront and the center of that. So most customers are coming to us and they're like, listen, we gotta move to the cloud or we move some things to cloud and we want to do that better. And um, there's this big misnomer that when you move to the cloud, you gotta automatically modernize. Yeah. And what we try to help as many customers understand as possible is lifting and shifting, moving the stuff that you maybe currently have OnPrem and a data center to the cloud first is a first step. And then, uh, progressively working through a modernization strateg, always the better approach. And so we spend a lot of time with small to midsize businesses who don't have the technology talent on staff to be able to do >>That. Yeah. They want get set up. But then the dynamic of like latency is huge. We're seeing that edge product is a big part of it. This is not a one-off happening around everywhere. It is. And it's not, it's manufacturing, it's the physical plant or location >>Literally. >>And so, and you're seeing more IOT devices. What's that like right now from a challenge and problem statement standpoint, are the customers, not staff, is the it staff kind of old school? Is it new skills? What's the core problem you guys solve >>In the SMB space? The core issue nine outta 10 times is people get enamored with the latest and greatest. And the reality is not everything that's cloud based. Not all cloud services are the latest and greatest. Some things have been around for quite some time and are hardened solutions. And so, um, what we try to do with technology staff that has traditional on-prem, uh, let's just say skill sets and they're trying to move to a cloud-based workload is we try to help those customers through education and through some practical, let's just call it use case. Um, whether that's a proof of concept that we're doing or whether we're gonna migrate a small workload over, we try to give them the confidence to be able to not, not necessarily go it alone, but to, to, to have the, uh, the Gusto and to really have the, um, the, the opportunity to, to do that in a wise way. Um, and what I find is that most CEOs that I talk to, yeah, they're like, listen, the end of the day, I'm gonna be spending money in one place or another, whether that's OnPrem or in the cloud. I just want to know that I'm doing that in a way that helps me grow as quickly as possible status quo. I think every, every business owner knows that COVID taught us anything that status quo is, uh, is, is no. No. >>Good. How about factoring in the, the agility and speed equation? Does that come up a lot? It >>Does. I think, um, I, there's also this idea that if, uh, if we do a deep dive analysis and we really take a surgical approach to things, um, we're gonna be better off. And the reality is the faster you move with anything cloud based, the better you are. And so there's this assumption that we gotta get it right the first time. Yeah. In the cloud, if you start down your journey in one way and you realize midway that it's not the right, let's just say the right place to go. It's not like buying a piece of iron that you put in the closet and now you own it in the cloud. You can turn those services on and off. It's gives you a much higher density for making decisions and failing >>Forward. Well actually shutting down the abandoning the projects that early and not worrying about it, you got it. I mean, most people don't abandon cause like, oh, I own it. >>Exactly. And >>They get, they get used to it. Like, and then they wait too long. >>That's exactly. Yeah. >>Frog and boiling water as we used to say. So, oh, it's a great analogy. So I mean, this is a dynamic that's interesting. I wanna get more thoughts on it because like I'm a, if I'm a CEO of a company, like, okay, I gotta make my number. Yeah. I gotta keep my people motivated. Yeah. And I gotta move faster. So this is where you, I get the whole thing. And by the way, great service, um, professional services in the cloud right now are so hot because so hot, you can build it and then have option optionality. You got path decisions, you got new services to take advantage of. It's almost too much for customers. It is. I mean, everyone I talked to at reinvent, that's a customer. Well, how many announcements did am jazzy announce or Adam, you know, the 5,000 announcement or whatever. They do huge amounts. Right. Keeping track of it all. Oh, is huge. So what's the, what's the, um, the mission of, of your company. How does, how do you talk to that alignment? Yeah. Not just processes. I can get that like values as companies, cuz they're betting on you and your people. >>They are, they are, >>What's the values. >>Our mission is, is very simple. We want to help every small to midsize business leverage the power of the cloud. Here's the reality. We believe wholeheartedly. This is our vision that every company is going to become a technology company. So we go to market with this idea that every customer's trying to leverage the power of the cloud in some way, shape or form, whether they know it or don't know it. And number two, they're gonna become a tech company in the process of that because everything is so tech-centric. And so when you talk about speed and agility, when you talk about the, the endless options and the endless permutations of solutions that a customer can buy in the cloud, how are you gonna ask a team of one or two people in your, or it department to make all those decisions going it alone or trying to learn it as you go, it only gets you so far working with a partner. >>I'll just give you some perspective. We work with about a thousand small to midsize business customers. More than 50% of those customers are on our managed services. Meaning they know that we have their back Andre or the safety net. So when a customer is saying, all right, I'm gonna spend a couple thousand dollars a month in the cloud. They know that that bill, isn't gonna jump to $10,000 a month going in alone. Who's there to help protect that. Number two, if you have a security posture and let's just say you're high profile and you're gonna potentially be more vulnerable to security attack. If you have a partner, that's all offering you some managed services. Now you, again, you've got that backstop and you've got those services and tooling. We, we offer, um, seven different products, uh, that are part of our managed services that give the customer the tooling, that for them to go out and buy on their own for a customer to go out today and go buy a new Relic solution on their own. It, it would cost 'em a fortune. If >>Training alone would be insane, a factor and the cost. Yes, absolutely. Opportunity cost is huge, >>Huge, absolutely enormous training and development. Something. I think that is often, you know, it's often overlooked technologists. Typically they want to get their skills up. Yeah. They, they love to get the, the stickers and the badges and the pins, um, at innovative in 2018, when, uh, when we made the decision to go all in on the club, I said to the organization, you know, we have this idea that we're gonna pivot and be aligned with AWS in such a way that it's gonna really require us all to get certified. My executive assistant at the time looks at me. She said, even me, I said, yeah, even you, why can't you get certified? Yeah. And so we made, uh, a conscious decision. It wasn't requirement and still isn't today to make sure everybody in the company has the opportunity to become certified. Even the people that are answering the phones at the front desk >>And she could be running the Kubernetes clusters. I love it. It's amazing. >>But I'll tell you what, when that customer calls and they have a real Kubernetes issue, she'll be able to assist and get >>The right people involved. And that's a cultural factor that you guys have. So, so again, this is back to my whole point about SMBs and businesses in general, small en large, it staffs are turning over the gen Z and millennials are in the workforce. They were provisioning top of rack switches. Right. First of all. And so if you're a business, there's also the, I call the build out, um, uh, return factor, ROI piece. At what point in time as an owner or SMB, do I get the ROI? Yeah. I gotta hire a person to manage it. That person's gonna have five zillion job offers. Yep. Uh, maybe who knows? Right. I got cybersecurity issues. Where am I gonna find a cyber person? Yeah. A data compliance. I need a data scientist and a compliance person. Right. Maybe one and the same. Right. Good luck. Trying to find a data scientist. Who's also a compliance person. Yep. And the list goes on. I can just continue. Absolutely. I need an SRE to manage the, the, uh, the sock report and we can pen test. Right. >>Right. >>These are, these are >>Critical issues. This >>Is just like, these are the table stakes. >>Yeah. And, and every, every business owner's thinking about. So that's, >>That's what, at least a million in bloating, if not three or more Just to get that going. Yeah. Then it's like, where's the app. Yeah. So there's no cloud migration. There's no modernization on the app side though. Yeah. No. And nevermind AI and ML. That's >>Right. That's right. So to try to go it alone, to me, it's hard. It it's incredibly difficult. And, and the other thing is, is there's not a lot of partners, so the partner, >>No one's raising their hand boss. I'll >>Do all that >>Exactly. In it department. >>Exactly. >>Like, can we just call up, uh, you know, <laugh> our old vendor. That's >>Right. <laugh> right. Our old vendor. I like it, but that's so true. I mean, when I think about how, if I was a business owner, starting a business to today and I had to build my team, um, and the amount of investment that it would take to get those people skilled up and then the risk factor of those people now having the skills and being so much more in demand and being recruited away, that's a real, that's a real issue. And so how you build your culture around that is, is very important. And it's something that we talk about every, with every one of our small to midsize business. >>So just, I want to get, I want to get your story as CEO. Okay. Take us through your journey. You said you bought the company and your progression to, to being the owner and CEO of innovative award winning guys doing great. Uh, great bet on a good call. Yeah. Things are good. Tell your story. What's your journey? >>It's real simple. I was, uh, was a sophomore at the Rochester Institute of technology in 2003. And, uh, I knew that I, I was going to school for it and I, I knew I wanted to be in tech. I didn't know what I wanted to do, but I knew I didn't wanna code or configure routers and switches. So I had this great opportunity with the local it company that was doing managed services. We didn't call it at that time innovative solutions to come in and, uh, jump on the phone and dial for dollars. I was gonna cold call and introduce other, uh, small to midsize businesses locally in Rochester, New York go to Western New York, um, who innovative was now. We were 19 people at the time. And I came in, I did an internship for six months and I loved it. I learned more in those six months that I probably did in my first couple of years at, uh, at R I T long story short. >>Um, for about seven years, I worked, uh, to really help develop, uh, sales process and methodology for the business so that we could grow and scale. And we grew to about 30 people. And, um, I went to the owners at the time in 2010 and I was like, Hey, I'm growing the value of this business. And who knows where you guys are gonna be another five years? What do you think about making me an owner? And they were like, listen, you got long ways before you're gonna be an owner, but if you stick it out in your patient, we'll, um, we'll work through a succession plan with you. And I said, okay, there were four other individuals at the time that we're gonna also buy the business with >>Me. And they were the owners, no outside capital, >>None zero, well, 2014 comes around. And, uh, the other folks that were gonna buy into the business with me that were also working at innovative for different reasons. They all decided that it wasn't for them. One started a family. The other didn't wanna put capital in. Didn't wanna write a check. Um, the other had a real big problem with having to write a check. If we couldn't make payroll, I'm like, well, that's kind of like if we're owners, we're gonna have to like cover that stuff. <laugh> so >>It's called the pucker factor. >>Exactly. So, uh, I sat down with the CEO in early 2015, and, uh, we made the decision that I was gonna buy the three partners out, um, go through an earn out process, uh, coupled with, uh, an interesting financial strategy that wouldn't strap the business, cuz they care very much. The company still had the opportunity to keep going. So in 2016 I bought the business, um, became the sole owner. And, and at that point we, um, we really focused hard on what do we want this company to be? We had built this company to this point. Yeah. And, uh, and by 2018 we knew that pivoting all going all in on the cloud was important for us and we haven't looked back. >>And at that time, the proof points were coming clearer and clearer 2012 through 15 was the early adopters, the builders, the startups and early enterprises. Yes. The capital ones of the world. Exactly the, uh, and those kinds of big enterprises. The game don't, won't say gamblers, but ones that were very savvy. The innovators, the FinTech folks. Yep. The hardcore glass eating enterprises >>Agreed, agreed to find a small to midsize business, to migrate completely to the cloud as, as infrastructure was considered. That just didn't happen as often. Um, what we were seeing were a lot of our small to midsize business customers, they wanted to leverage cloud based backup, or they wanted to leverage a cloud for disaster recovery because it lent itself. Well, early days, our most common cloud customer though, was the customer that wanted to move messaging and collaboration. The, the Microsoft suite to the cloud and a lot of 'em dipped their toe in the water. But by 2017 we knew infrastructure was around the corner. Yeah. And so, uh, we only had two customers on eight at the time. Um, and we, uh, we, we made the decision to go all in >>Justin. Great to have you on the cube. Thank you. Let's wrap up. Uh, tell me the hottest product that you have. Is it migrations? Is the app modernization? Is it data? What's the hot product and then put a plug in for the company. Awesome. >>So, uh, there's no question. Every customer is looking to migrate workloads and try to figure out how to modernize for the future. We have very interesting, sophisticated yet elegant funding solutions to help customers with the cash flow, uh, constraints that come along with those migrations. So any SMB that's thinking about migrating to the cloud, they should be talking innovative solutions. We know how to do it in a way that allows those customers not to be cash strapped and gives them an opportunity to move forward in a controlled, contained way so that they can modernize. >>So like insurance, basically for them not insurance class in the classic sense, but you help them out on the, on the cash exposure. >>Absolutely. We are known for that and we're known for being creative with those customers, empathetic to where they are in their journey. And >>That's the cloud upside is all about doubling down on the variable wind. That's right. Seeing the value and doubling down on it. Absolutely not praying for it. Yeah. <laugh> all right, Justin. Thanks for coming on. You really appreciate it. Thank >>You very much for having >>Me. Okay. This is the cube coverage here live in San Francisco, California for AWS summit, 2022. I'm John for your host. Thanks for watching with back with more great coverage for two days after this short break >>Live on the floor in San Francisco for 80 west summit, I'm John ferry, host of the cube here for the next two days, getting all the action we're back in person. We're at AWS reinvent a few months ago. Now we're back events are coming back and we're happy to be here with the cube, bringing all the action. Also virtual, we have a hybrid cube, check out the cube.net, Silicon angle.com for all the coverage. After the event. We've got a great guest ticketing off here. Matthew Park, director of solutions, architecture with innovation solutions. The booth is right here. Matthew, welcome to the cube. >>Thank you very much. I'm glad >>To be here. So we're back in person. You're from Tennessee. We were chatting before you came on camera. Um, it's great to have to be back through events. >>It's amazing. This is the first, uh, summit I've been to and what two, three years. >>It's awesome. We'll be at the, uh, New York as well. A lot of developers and a big story this year is as developers look at cloud going distributed computing, you got on premises, you got public cloud, you got the edge. Essentially the cloud operations is running everything dev sec ops, everyone kind of sees that you got containers, you got Kubernetes, you got cloud native. So the, the game is pretty much laid out. Mm. And the edge is with the actions you guys are number one, premier partner at SMB for edge. >>That's right. >>Tell us about what you guys doing at innovative and, uh, what you do. >>That's right. Uh, so I'm the director of solutions architecture. Uh, me and my team are responsible for building out the solutions that are around, especially the edge public cloud out for us edge is anything outside of an AWS availability zone. Uh, we are deploying that in countries that don't have AWS infrastructure in region. They don't have it. Uh, give >>An example, >>Uh, example would be Panama. We have a customer there that, uh, needs to deploy some financial tech data and compute is legally required to be in Panama, but they love AWS and they want to deploy AWS services in region. Uh, so they've taken E EKS anywhere. We've put storage gateway and, uh, snowball, uh, in region inside the country and they're running their FinTech on top of AWS services inside Panama. >>You know, what's interesting, Matthew is that we've been covering Aw since 2013 with the cube about their events. And we watched the progression and jazzy was, uh, was in charge and then became the CEO. Now Adam Slosky is in charge, but the edge has always been that thing they've been trying to, I don't wanna say, trying to avoid, of course, Amazon would listen to customers. They work backwards from the customers. We all know that. Uh, but the real issue was they were they're bread and butters EC two and S three. And then now they got tons of services and the cloud is obviously successful and seeing that, but the edge brings up a whole nother level. >>It does >>Computing. It >>Does. >>That's not central lies in the public cloud. Now they got regions. So what is the issue with the edge what's driving? The behavior. Outpost came out as a reaction to competitive threats and also customer momentum around OT, uh, operational technologies. And it merging. We see with the data at the edge, you got five GM having. So it's pretty obvious, but there was a slow transition. What was the driver for the <affirmative> what's the driver now for edge action for AWS >>Data is the driver for the edge. Data has gravity, right? And it's pulling compute back to where the customer's generating that data and that's happening over and over again. You said it best outpost was a reaction to a competitive situation. Whereas today we have over fit 15 AWS edge services, and those are all reactions to things that customers need inside their data centers on location or in the field like with media companies. >>Outpost is interesting. We always used to riff on the cube, uh, cuz it's basically Amazon in a box, pushed in the data center, uh, running native, all the stuff, but now cloud native operations are kind of become standard. You're starting to see some standard Deepak sings group is doing some amazing work with open source Rauls team on the AI side, obviously, uh, you got SW who's giving the keynote tomorrow. You got the big AI machine learning big part of that edge. Now you can say, okay, outpost, is it relevant today? In other words, did outpost do its job? Cause EKS anywhere seems to be getting a lot of momentum. You see low the zones, the regions are kicking ass for Amazon. This edge piece is evolving. What's your take on EKS anywhere versus say outpost? >>Yeah, I think outpost did its job. It made customers that were looking at outpost really consider, do I wanna invest in this hardware? Do I, do I wanna have, um, this outpost in my data center, do I wanna manage this over the long term? A lot of those customers just transitioned to the public cloud. They went into AWS proper. Some of those customers stayed on prem because they did have use cases that were, uh, not a good fit for outpost. They weren't a good fit. Uh, in the customer's mind for the public AWS cloud inside an availability zone. Now what's happening is as AWS is pushing these services out and saying, we're gonna meet you where you are with 5g. We're gonna meet you where you are with wavelength. We're gonna meet you where you are with EKS anywhere. Uh, I think it has really reduced the amount of times that we have conversations about outposts and it's really increased. We can deploy fast. We don't have to spin up outpost hardware. We can go deploy EKS anywhere in your VMware environment and it's increasing the speed of adoption >>For sure. So you guys are making a lot of good business decisions around managed cloud service. Innovative does that. You have the cloud advisory, the classic professional services for the specific edge piece and, and doing that outside of the availability zones and regions for AWS, um, customers in, in these new areas that you're helping out are they want cloud, like they want to have modernization a modern applications. Obviously they got data machine learning and AI, all part of that. What's the main product or, or, or gap that you're filling for AWS, uh, outside of their available ability zones or their regions that you guys are delivering. What's the key is it. They don't have a footprint. Is it that it's not big enough for them? What's the real gap. What's why, why are you so successful? >>So what customers want when they look towards the cloud is they want to focus on, what's making them money as a business. They wanna focus on their applications. They want focus on their customers. So they look towards AWS cloud and say, AWS, you take the infrastructure. You take, uh, some of the higher layers and we'll focus on our revenue generating business, but there's a gap there between infrastructure and revenue generating business that innovative slides into, uh, we help manage the AWS environment. We help build out these things in local data centers for 32 plus year old company, we have traditional on-premises people that know about deploying hardware that know about deploying VMware to host EKS anywhere. But we also have most of our company totally focused on the AWS cloud. So we're filling that gap in helping deploy these AWS services, manage them over the long term. So our customers can go to just primarily and totally focusing on their revenue generating business. >>So basically you guys are basically building AWS edges, >>Correct? >>For correct companies, correct? Mainly because the, the needs are there, you got data, you got certain products, whether it's, you know, low latency type requirements, right. And then they still work with the regions, right. It's all tied together, right. Is that how it works? Right. >>And, and our customers, even the ones in the edge, they also want us to build out the AWS environment inside the availability zone, because we're always gonna have a failback scenario. If we're gonna deploy FinTech in the Caribbean, we're gonna talk about hurricanes and gonna talk about failing back into the AWS availability zones. So innovative is filling that gap across the board, whether it be inside the AWS cloud or on the AWS edge. >>All right. So I gotta ask you on the, since you're at the edge in these areas, I won't say underserved, but developing areas where now have data, you have applications that are tapping into that, that requirement. It makes total sense. We're seeing across the board. So it's not like it's, it's an outlier it's actually growing. Yeah. There's also the crypto angle. You got the blockchain. Are you seeing any traction at the edge with blockchain? Because a lot of people are looking at the web three in these areas like Panama, you mentioned FinTech in, in the islands. There are a lot of, lot of, lot of web three happening. What's your, what's your view on the web three world right now, relative >>To we, we have some customers actually deploying crypto, especially, um, especially in the Caribbean. I keep bringing the Caribbean up, but it's, it's top of my mind right now we have customers that are deploying crypto. A lot of, uh, countries are choosing crypto underly parts of their central banks. Yeah. Um, so it's, it's up and coming. Uh, I, I have some, you know, personal views that, that crypto is still searching for a use case. Yeah. And, uh, I think it's searching a lot and, and we're there to help customers search for that use case. Uh, but, but crypto, as a, as a tech technology, um, lives really well on the AWS edge. Yeah. Uh, and, and we're having more and more people talk to us about that. Yeah. And ask for assistance in the infrastructure because they're developing new cryptocurrencies every day. Yeah. It's not like they're deploying Ethereum or anything specific. They're actually developing new currencies and, and putting them out there on it's >>Interesting. And I mean, first of all, we've been doing crypto for many, many years. We have our own little, um, you know, projects going on. But if you look talk to all the crypto people that say, look, we do a smart contract, we use the blockchain. It's kind of over a lot of overhead. It's not really their technical already, but it's a cultural shift, but there's underserved use cases around use of money, but they're all using the blockchain, just for this like smart contracts for instance, or certain transactions. And they go into Amazon for the database. Yeah. <laugh> they all don't tell anyone we're using a centralized service, but what happened to decent centralized. >>Yeah. And that's, and that's the conversation performance. >>Yeah. >>And, and it's a cost issue. Yeah. And it's a development issue. Um, so I think more and more as, as some of these, uh, currencies maybe come up, some of the smart contracts get into, uh, they find their use cases. I think we'll start talking about how does that really live on, on AWS and, and what does it look like to build decentralized applications, but with AWS hardware and services. >>Right. So take me through a, a use case of a customer, um, Matthew around the edge. Okay. So I'm a customer, pretend I'm a customer, Hey, you know, I'm, we're in an underserved area. I want to modernize my business. And I got my developers that are totally peaked up on cloud. Um, but we've identified that it's just a lot of overhead latency issues. I need to have a local edge and serve my a and I also want all the benefits of the cloud. So I want the modernization and I wanna migrate to the cloud for all those cloud benefits and the good this of the cloud. What's the answer. Yeah. >>Uh, big thing is, uh, industrial manufacturing, right? That's, that's one of the best use cases, uh, inside industrial manufacturing, we can pull in many of the AWS edge services we can bring in, uh, private 5g, uh, so that all the, uh, equipment inside that, that manufacturing plant can be hooked up. They don't have to pay huge overheads to deploy 5g it's, uh, better than wifi for the industrial space. Um, when we take computing down to that industrial area, uh, because we wanna do pre-procesing on the data. Yeah. We want to gather some analytics. We deploy that with, uh, regular commercially available hardware running VMware, and we deploy EKS anywhere on that. Uh, inside of that manufacturing plant, uh, we can do pre-processing on things coming out of the, uh, the robotics that depending on what we're manufacturing, right. Uh, and then we can take the, those refined analytics and for very low cost with maybe a little bit longer latency transmit those back, um, to the AWS availability zone, the, the standard >>For data lake or whatever, >>To the data lake. Yeah. Data Lakehouse, whatever it might be. Um, and we can do additional data science on that once it gets to the AWS cloud. Uh, but I'll lot of that, uh, just in time business decisions, just in time, manufacturing decisions can all take place on an AWS service or services inside that manufacturing plant. And that's, that's one of the best use cases that we're >>Seeing. And I think, I mean, we've been seeing this on the queue for many, many years, moving data around is very expensive. Yeah. But also compute going of the data that saves that cost yep. On the data transfer also on the benefits of the latency. So I have to ask you, by the way, that's standard best practice now for the folks watching don't move the data unless you have to. Um, but those new things are developing. So I wanna ask you, what new patterns are you seeing emerging once this new architecture's in place? Love that idea, localize everything right at the edge, manufacture, industrial, whatever the use case, retail, whatever it is. Right. But now what does that change in the, in the core cloud? There's a, there's a system element here. Yeah. What's the new pattern. There's >>Actually an organizational element as well, because once you have to start making the decision, do I put this compute at the point of use or do I put this compute in the cloud? Uh, now you start thinking about where business decisions should be taking place. Uh, so not only are you changing your architecture, you're actually changing your organization because you're thinking, you're thinking about a dichotomy you didn't have before. Uh, so now you say, okay, this can take place here. Uh, and maybe, maybe this decision can wait. Yeah. Uh, and then how do I visualize that? By >>The way, it could be a bot tube doing the work for management. Yeah. <laugh> exactly. You got observability going, right. But you gotta change the database architecture in the back. So there's new things developing. You've got more benefit. There >>Are, there are. And, and we have more and more people that, that want to talk less about databases and want to talk more about data lakes because of this. They want to talk more about out. Customers are starting to talk about throwing away data, uh, you know, for the past maybe decade. Yeah. It's been store everything. And one day we will have a data science team that we hire in our organization to do analytics on this decade of data. And well, >>I mean, that's, that's a great point. We don't have time to drill into, maybe we do another session on this, but the one pattern we're seeing of the past year is that throwing away data's bad, even data lakes that so-called turn into data swamps, actually, it's not the case. You look at data, brick, snowflake, and other successes out there. And even time series data, which may seem irrelevant efforts over actually matters when people start retraining their machine learning algorithms. Yep. So as data becomes code, as we call it in our last showcase, we did a whole whole event on this. The data's good in real time and in the lake. Yeah. Because the iteration of the data feeds the machine learning training. Things are getting better with the old data. So it's not throw it away. It's not just business better. Yeah. There's all kinds of new scale. >>There are. And, and we have, uh, many customers that are running pay Toby level. Um, they're, they're essentially data factories on, on, uh, on premises, right? They're, they're creating so much data and they're starting to say, okay, we could analyze this, uh, in the cloud, we could transition it. We could move Aytes of data to the AWS cloud, or we can run, uh, computational workloads on premises. We can really do some analytics on this data transition, uh, those high level and sort of raw analytics back to AWS run 'em through machine learning. Um, and we don't have to transition 10, 12 petabytes of data into AWS. >>So I gotta end the segment on a, on a kind of a, um, fun note. I was told to ask you about your personal background, OnPrem architect, Aus cloud, and skydiving instructor. <laugh> how does that all work together? What tell, what does this mean? Yeah. >>Uh, you >>Jumped out a plane and got a job. You got a customer to jump out >>Kind of. So I was, you jumped out. I was teaching having, uh, before I, before I started in the cloud space, this was 13, 14 years ago. I was a, I still am a sky. I instructor, uh, I was teaching skydiving and I heard out of the corner of my ear, uh, a guy that owned an MSP that was lamenting about, um, you know, storing data and, and how his customers are working. And he can't find an enough people to operate all these workloads. So I walked over and said, Hey, this is, this is what I went to school for. Like, I'd love to, you know, uh, I was living in a tent in the woods, teaching skydiving. I was like, I'd love to not live in a tent in the woods. So, uh, uh, I started and the first day there, uh, we had a, a discussion, uh, EC two had just come out <laugh> and, uh, like, >>This is amazing. >>Yeah. And so we had this discussion, we should start moving customers here. And, uh, and that totally revolutionized that business, um, that, that led to, uh, that that guy actually still owns a skydiving airport. But, um, but through all of that, and through being in on premises, migrated me and myself, my career into the cloud, and now it feels like, uh, almost, almost looking back and saying, now let's take what we learned in the cloud and, and apply those lessons and those services tore >>It's. So it's such a great story, you know, was gonna, you know, you know, the whole, you know, growth mindset pack your own parachute, you know, uh, exactly. You know, the cloud in the early days was pretty much will the shoot open. Yeah. It was pretty much, you had to roll your own cloud at that time. And so, you know, you, you jump on a plane, you gotta make sure that parachute is gonna open. >>And so was Kubernetes by the way, 2015 or so when, uh, when that was coming out, it was, I mean, it was, it was still, and maybe it does still feel like that to some people. Right. But, uh, it was, it was the same kind of feeling that we had in the early days of AWS, the same feeling we have when we >>It's now with you guys, it's more like a tandem jump. Yeah. You know, but, but it's a lot of, lot of this cutting edge stuff, like jumping out of an airplane. Yeah. You got the right equipment. You gotta do the right things. Exactly. >>Right. >>Yeah. Thanks for coming. You really appreciate it. Absolutely great conversation. Thanks for having me. Okay. The cubes here live in San Francisco for eight of us summit. I'm John for host of the cube. Uh, we'll be at a summit in New York coming up in the summer as well. Look up for that. Look up this calendar for all the cube, actually@thecube.net. We'll right back with our next segment after this break. >>Okay. Welcome back everyone to San Francisco live coverage here, we're at the cube a be summit 2022. We're back in person. I'm John fury host of the cube. We'll be at the eighties summit in New York city this summer, check us out then. But right now, two days in San Francisco, getting all the coverage what's going on in the cloud, we got a cube alumni and friend of the cube, my dos car CEO, investor, a Sierra, and also an investor in a bunch of startups, angel investor. Gonna do great to see you. Thanks for coming on the cube. Good to see you. Good to see you. Cool. How are you? Good. >>How hello you. >>So congratulations on all your investments. Uh, you've made a lot of great successes, uh, over the past couple years, uh, and your company raising, uh, some good cash as Sarah. So give us the update. How much cash have you guys raised? What's the status of the company product what's going on? >>First of all, thank you for having me. We're back to be business with you, never after to see you. Uh, so is a company started around four years back. I invested with a few of the investors and now I'm the CEO there. We have raised close to a hundred million there. The investors are people like Norwes Menlo ventures, coastal ventures, Ram Shera, and all those people, all well known guys. And Beckel chime Paul me Mayard web. So whole bunch of operating people and, uh, Silicon valley VCs are involved >>And has it gone? >>It's going well. We are doing really well. We are going almost 300% year over year. Uh, for last three years, the space ISRA is going after is what I call the applying AI for customer service. It operations, it help desk, uh, the same place I used to work at ServiceNow. We are partners with ServiceNow to take, how can we argument for employees and customers, Salesforce, and service now to take you to the next stage? Well, >>I love having you on the cube, Dave and I, Dave LAN as well loves having you on too, because you not only bring the entrepreneurial CEO experience, you're an investor. You're like a, you're like a guest analyst. <laugh> >>You know, who does >>You, >>You >>Get the call fund to talk to you though. You >>Get the commentary, your, your finger in the pulse. Um, so I gotta ask you obviously, AI and machine learning, machine learning AI, or you want to phrase it. Isn't every application. Now, AI first, uh, you're seeing a lot of that going on. You're starting to see companies build the modern applications at the top of the stack. So the cloud scale has hit. We're seeing cloud scale. You predicted that we talked about in the cube many times. Now you have that past layer with a lot more services and cloud native becoming a standard layer. Containerizations growing Docker just raised a hundred million on a $2 billion valuation back from the dead after they pivoted from enterprise services. So open source developers are booming. Um, where's the action. I mean, is there data control plan? Emerging AI needs data. There's a lot of challenges around this. There's a lot of discussions and a lot of companies being funded, observability there's 10 billion observability companies. Data is the key. This is what's your end on this. What's your take. >>Yeah, look, I think I'll give you the few that I see right from my side. Obviously data is very clear. So the things that rumor system of recorded you and me talked about the next layer is called system of intelligence. That's where the AI will play. Like we talk cloud native, it'll be called AI. NA AI enable is a new buzzword and using the AI for customer service. It, you talk about observability. I call it, AIOps applying AOPs for good old it operation management, cloud management. So you'll see the AOPs applied for whole list of, uh, application from observability doing the CMDB, predicting the events insurance. So I see a lot of work clicking for AIOps and AI services. What used to be desk with ServiceNow BMC GLA you see a new ALA emerging as a system of intelligence. Uh, the next would be is applying AI with workflow automation. So that's where you'll see a lot of things called customer workflows, employee workflows. So think of what UI path automation, anywhere ServiceNow are doing, that area will be driven with AI workflows. So you, you see AI going >>Off is RPA. A company is AI, is RPA a feature of something bigger? Or can someone have a company on RPA UI S one will be at their event this summer? Um, is it a product company? I mean, or I mean, RPA is, should be embedded in everything. It's a >>Feature. It is very good point. Very, very good thinking. So one is, it's a category for sure. Like, as we thought, it's a category, it's an area where RPA may change the name. I call it much more about automation, workflow automation, but RPA and automation is a category. Um, it's a company also, but that automation should be embedded in every area. Yeah. Like we call cloud NATO and AI. They it'll become automation data. Yeah. And that's your, thinking's >>Interesting me. I think about the, what you're talking about what's coming to mind is I'm kinda having flashbacks to the old software model of middleware. Remember at middleware, it was very easy to understand it was middleware. It sat between two things and then the middle, and it was software abstraction. Now you have all kinds of workflows, abstractions everywhere. So multiple databases, it's not a monolithic thing. Right? Right. So as you break that down, is this the new modern middleware? Because what you're talking about is data workflows, but they might be siloed. Are they integrated? I mean, these are the challenges. This is crazy. What's the, >>So remember the databases became called polyglot databases. Yeah. I call this one polyglot automation. So you need automation as a layer, as a category, but you also need to put automation in every area like you, you were talking about, it should be part of service. Now it should be part of ISRA. Like every company, every Salesforce. So that's why you see it MuleSoft and sales buying RPA companies. So you'll see all the SaaS companies, cloud companies having an automation as a core. So it's like how you have a database and compute and sales and networking. You'll also have an automation as a layer embedded inside every stack. >>All right. So I wanna shift gears a little bit and get your perspective on what's going on behind us. You can see, uh, behind, as you got the XPO hall got, um, we're back to vis, but you got, you know, AMD, Clum, Dynatrace data, dog, innovative, all the companies out here that we know, we interview them all. They're trying to be suppliers to this growing enterprise market. Right? Okay. But now you also got the entrepreneurial equation. Okay. We're gonna have John Sado on from Deibel later. He's a former NEA guy and we always talk to Jerry, Jen, we know all the, the VCs, what does the startups look like? What does the state of the, in your mind, cause you, I know you invest the entrepreneurial founder situation. Cloud's bigger. Mm-hmm <affirmative> global, right? Data's part of it. You mentioned data's code. Yes. Basically. Data's everything. What's it like for a first an entrepreneur right now who's starting a company. What's the white space. What's the attack plan. How do they get in the market? How do they engineer everything? >>Very good. So I'll give it to, uh, two things that I'm seeing out there. Remember leaders of Amazon created the startups 15 years back. Everybody built on Amazon now, Azure and GCP. The next layer would be people don't just build on Amazon. They're going to build it on top of snow. Flake companies are snowflake becomes a data platform, right? People will build on snowflake, right? So I see my old boss playing ment, try to build companies on snowflake. So you don't build it just on Amazon. You build it on Amazon and snowflake. Snowflake will become your data store. Snowflake will become your data layer, right? So I think that's the next level of companies trying to do that. So if I'm doing observability AI ops, if I'm doing next level of Splunk SIM, I'm gonna build it on snowflake, on Salesforce, on Amazon, on Azure, et cetera. >>It's interesting. You know, Jerry Chan has it put out a thesis a couple months ago called castles in the cloud where your moat is, what you do in the cloud. Not necessarily in the, in the IP. Um, Dave LAN and I had last re invent, coined the term super cloud, right? It's got a lot of traction and a lot of people throwing, throwing mud at us, but we were, our thesis was, is that what Snowflake's doing? What Goldman S Sachs is doing. You're starting to see these clouds on top of clouds. So Amazon's got this huge CapEx advantage. And guys like Charles Fitzgeral out there, who we like was kind of hitting on us saying, Hey, you guys terrible, they didn't get him. Like, yeah, I don't think he gets it, but that's a whole, can't wait to debate him publicly on this. <laugh> cause he's cool. Um, but snowflake is on Amazon. Yes. Now they say they're on Azure now. Cause they've got a bigger market and they're public, but ultimately without a AWS snowflake doesn't exist and, and they're reimagining the data warehouse with the cloud, right? That's the billion dollar opportunity. >>It is. It is. They both are very tight. So imagine what Frank has done at snowflake and Amazon. So if I'm a startup today, I want to build everything on Amazon where possible whatever is, I cannot build. I'll make the pass layer room. The middle layer pass will be snowflake. So I cannot build it on snowflake. I can use them for data layer if I really need to size, I'll build it on force.com Salesforce. Yeah. Right. So I think that's where you'll >>See. So basically the, the, if you're an entrepreneur, the, the north star in terms of the, the outcome is be a super cloud. It >>Is, >>That's the application on another big CapEx ride, the CapEx of AWS or cloud, >>And that reduce your product development, your go to market and you get use the snowflake marketplace to drive your engagement. Yeah. >>Yeah. How are, how is Amazon and the clouds dealing with these big whales, the snowflakes of the world? I mean, I know they got a great relationship, uh, but snowflake now has to run a company they're public. Yeah. So, I mean, I'll say, I think got Redshift. Amazon has got Redshift. Um, but snowflake big customer. The they're probably paying AWS big, >>I >>Think big bills too. >>So John, very good. Cause it's like how Netflix is and Amazon prime, right. Netflix runs on Amazon, but Amazon has Amazon prime that co-option will be there. So Amazon will have Redshift, but Amazon is also partnering with the snowflake to have native snowflake data warehouse as a data layer. So I think depending on the use case you have to use each of the above, I think snowflake is here for a long term. Yeah. Yeah. So if I'm building an application, I want to use snowflake then writing from stats. >>Well, I think that comes back down to entrepreneurial hustle. Do you have a better product? Right. Product value will ultimately determine it as long as the cloud doesn't, you know, foreclose your value. That's right. With some sort of internal hack, but I've think, I think the general question that I have is that I think it's okay to have a super cloud like that because the rising tide is still happening at some point, when does the rising tide stop and the people shopping up their knives, it gets more competitive or is it just an infinite growth cycle? I >>Think it's growth. You call it closed skill you the word cloud scale. So I think look, cloud will continually agree, increase. I think there's as long as there more movement from on, uh, on-prem to the classical data center, I think there's no reason at this point, the rumor, the old lift and shift that's happening in like my business. I see people lift and shifting from the it operations, it helpless. Even the customer service service. Now the ticket data from BMCs CAS like Microfocus, all those workloads are shifted to the cloud, right? So cloud ticketing system is happening. Cloud system of record is happening. So I think this train has still a long way to go made. >>I wanna get your thoughts for the folks watching that are, uh, enterprise buyers are practitioners, not suppliers to the market. Feel free to text me or DMing. Next question is really about the buying side, which is if I'm a customer, what's the current, um, appetite for startup products. Cause you know, the big enterprises now and you know, small, medium, large, and large enterprise, they're all buying new companies cuz a startup can go from zero to relevant very quickly. So that means now enterprises are engaging heavily with startups. What's it like what's is there a change in order of magnitude of the relationship between the startup selling to, or growing startup selling to an enterprise? Um, have you seen changes there? I mean seeing some stuff, but why don't we get your thoughts on that? What it >>Is you, if I remember going back to our 2007 or eight, when I used to talk to you back then when Amazon started very small, right? We are an Amazon summit here. So I think enterprises on the average used to spend nothing with startups. It's almost like 0% or one person today. Most companies are already spending 20, 30% with startups. Like if I look at a C I will line our business, it's gone. Yeah. Can it go more? I think it can double in the next four, five years. Yeah. Spending on the startups. Yeah. >>And check out, uh, AWS startups.com. That's a site that we built for the startup community for buyers and startups. And I want to get your reaction because I, I reference the URL causes like there's like a bunch of companies we've been promoting because the solution that startups have actually are new stuff. Yes. It's bending, it's shifting left for security or using data differently or um, building tools and platforms for data engineering. Right. Which is a new persona that's emerging. So you know, a lot of good resources there. Um, and goes back now to the data question. Now, getting back to your, what you're working on now is what's your thoughts around this new, um, data engineering persona, you mentioned AIOps, we've been seeing AIOps IOPS booming and that's creating a new developer paradigm that's right. Which we call coin data as code data as code is like infrastructure as code, but it's for data, right? It's developing with data, right? Retraining machine learnings, going back to the data lake, getting data to make, to do analysis, to make the machine learning better post event or post action. So this, this data engineers like an SRE for data, it's a new, scalable role we're seeing. Do you see the same thing? Do you agree? Um, do you disagree or can you share? >>I, a lot of thoughts that Fu I see the AI op solutions in the futures should be not looking back. I need to be like we are in San Francisco bay. That means earthquake prediction. Right? I want AOPs to predict when the outages are gonna happen. When there's a performance issue. I don't think most AOPs vendors have not gone there yet. Like I spend a lot of time with data dog, Cisco app dynamic, right? Dynatrace, all this solution will go future towards predict to pro so solution with AOPs. But what you bring up a very good point on the data side. I think like we have a Amazon marketplace and Amazon for startup, there should be data exchange where you want to create for AOPs and AI service that customers give the data, share the data because we thought the data algorithms are useless. I can give the best algorithm, but I gotta train them, modify them, make them better, make them better. Yeah. And I think their whole data exchange is the industry has not thought through something you and me talk many times. Yeah. Yeah. I think the whole, that area is very important. >>You've always been on, um, on the Vanguard of data because, uh, it's been really fun. Yeah. >>Going back to big data days back in 2009, you know that >>Look at, look how much data bricks has grown. >>It is doubled. The key cloud >>Air kinda went private, so good stuff. What are you working on right now? Give a, give a, um, plug for what you're working on. You'll still investing. >>I do still invest, but look, I'm a hundred percent on ISRA right now. I'm the CEO there. Yeah. Okay. So right. ISRA is my number one baby right now. So I'm looking year that growing customers and my customers, or some of them, you like it's zoom auto desk, McAfee, uh, grand <inaudible>. So all the top customers, um, mainly for it help desk customer service. AIOps those are three product lines and going after enterprise and commercial deals. >>And when should someone buy your product? What's what's their need? What category is it? >>I think they look whenever somebody needs to buy the product is if you need AOP solution to predict, keep your lights on, predict ours. One area. If you want to improve employee experience, you are using a slack teams and you want to automate all your workflows. That's another value problem. Third is customer service. You don't want to hire more people to do it. Some of the areas where you want to scale your company, grow your company, eliminate the cost customer service, >>Great stuff, man. Doing great to see you. Thanks for coming on. Congratulations on the success of your company and your investments. Thanks for coming on the cube. Okay. I'm John fur here at the cube live in San Francisco for day one of two days of coverage of a us summit 2022. And we're gonna be at Aus summit in San, uh, in New York in the summer. So look for that on the calendar, of course, go to a us startups.com. That's a site for all the hot startups and of course the cube.net and Silicon angle.com. Thanks for watching. We'll be back more coverage after this short break. >>Okay. Welcome back everyone. This the cubes coverage here in San Francisco, California, a Davis summit, 2022, the beginning of the event season, as it comes back, little bit smaller footprint, a lot of hybrid events going on, but this is actually a physical event, a summit in new York's coming in the summer. We'll be two with the cube on the set. We're getting back in the Groove's psych to be back. We were at reinvent, uh, as well, and we'll see more and more cube, but you're gonna see a lot of virtual cube outta hybrid cube. We wanna get all those conversations, try to get more interviews, more flow going. But right now I'm excited to have Corey Quinn here on the back on the cube chief cloud economist with duck bill groove, he's the founder, uh, and chief content person always got great angles, fun comedy, authoritative Corey. Great to see you. Thank you. >>Thanks. Coming on. Sure is a lot of words to describe is shit posting, which is how I describe what I tend to do. Most days, >>Shit posting is an art form now. And if you look at mark, Andrew's been doing a lot of shit posting lately. All a billionaires are shit posting, but they don't know how to do it. They're >>Doing it right. There's something opportunity there. It's like, here's how to be even more obnoxious and incisive. It's honestly the most terrifying scenario for anyone is if I have that kind of budget to throw at my endeavors, it's like, I get excited with a nonsense I can do with a $20 gift card for an AWS credit compared to, oh well, if I could buy a mid-size island to begin doing this from, oh, then we're having fun. >>This shit posting trend. Interesting. I was watching a thread go on about, saw someone didn't get a job because of their shit posting and the employer didn't get it. And then someone on this side I'll hire the guy cuz I get that's highly intelligent shit posting. So for the audience that doesn't know what shit posting is, what, what is shitposting >>It's more or less talking about the world of enterprise technology, which even that sentence is hard to finish without falling asleep and toppling out of my chair in front of everyone on the livestream, but it's doing it in such a way that brings it to life that says the quiet part. A lot of the audience is thinking, but generally doesn't say either because they're polite or not a Jack ass or more prosaically are worried about getting fired for better or worse. I don't have that particular constraint, >>Which is why people love you. So let's talk about what you, what you think is, uh, worthy and not worthy in the industry right now, obviously, uh, Cuban coming up in Spain, which they're having a physical event, you see the growth of cloud native Amazon's evolving Atos, especially new CEO. Andy move on to be the chief of all. Amazon just saw him the cover of was it time magazine. Um, he's under a lot of stress. Amazon's changed. Invoice has changed. What's working. What's not, what's rising, what's falling. What's hot. What's not, >>It's easy to sit here and criticize almost anything. These folks do. They're they're effectively in a fishbowl, but I have trouble. Imagine the logistics, it takes to wind up handling the catering for a relatively downscale event like this one this year, let alone running a 1.7 million employee company having to balance all the competing challenges and pressures and the rest. I, I just can't fathom what it would be like to look at all of AWS. And it's, it's sprawling immense, the nominates our entire industry and say, okay, this is a good start, but I, I wanna focus on something with a broader remit. What is that? How do you even get into that position? And you can't win once you're there. All you can do is hold onto the tiger and hope you don't get mold. >>Well, there's a lot of force for good conversations. Seeing a lot of that going on, Amazon's trying to a, is trying to portray themselves, you know, the Pathfinder, you know, you're the pioneer, um, force for good. And I get that and I think that's a good angle as cloud goes mainstream. There's still the question of, we had a guy on just earlier, who was a skydiving instructor and we were joking about the early days of cloud. Like that was like skydiving, build a parachute open, you know, and now it's same kind of thing. As you move to edge, things are like reliable in some areas, but still new, new fringe, new areas. That's crazy. Well, >>Since the last time we've spoken, uh, Steve Schmidt is now the CISO for all of Amazon and his backfill replacement. The AWS CISO is CJ. Moses who as a hobby races, a as a semi-pro race car, our driver to my understanding, which either, I don't know what direction to take that in either. This is what he does to relax or ultimately, or ultimately it's. Huh? That, that certainly says something about risk assessment. I'm not entirely sure what, but okay. Either way, it sounds like more exciting. Like they >>Better have a replacement ready in case something goes wrong on the track, highly >>Available >>CSOs. I gotta say one of the things I do like in the recent trend is that the tech companies are getting into the formula one, which I was never a fan of until I watched that Netflix series. But when you look at the formula one, it's pretty cool. Cause it's got some tech angles, I get the whole data instrumentation thing, but the most coolest thing about formula, the one is they have these new rigs out. Yeah. Where you can actually race in e-sports with other people in pure simulation of the race car. You gotta get the latest and video graphics card, but it's basically a tricked out PC with amazing monitors and you have all the equipment of F1 and you're basically simulating racing. Oh, >>It's great too. And I can see the appeal of these tech companies getting it into it because these things are basically rocket shifts. When those cars go, like they're sitting there, we can instrument every last part of what is going on inside that vehicle. And then AWS crops up. And we can bill on every one of those dimensions too. And it's like slow down their hasty pudding one step at a time. But I do see the appeal. >>So I gotta ask you about, uh, what's going on in your world. I know you have a lot of great SA we've been following you in the queue for many, many years. Got a great newsletter. Check out Corey Quinn's newsletter, uh, screaming in the cloud program. Uh, you're on the cutting edge and you've got a great balance between really being snarky and, and, and really being delivering content. That's exciting, uh, for people, uh, with a little bit of an edge, um, how's that going? Uh, what's the blowback, any blowback late leads there been tick? What was, what are some of the things you're hearing from your audience, more Corey, more Corey. And then of course the, the PR team's calling you >>The weird thing about having an audience beyond a certain size is far and away as a landslide. The most common response I get is silence where it's hi, I'm emailing an awful lot of people at last week in AWS every week and okay. They not have heard me. It. That is not actually true. People just generally don't respond to email because who responds to email newsletters. That sounds like something, a lunatic might do same story with response to live streams and podcasts. It's like, I'm gonna call into that am radio show and give them a piece of my mind. People generally don't do that. >>We should do that. Actually. I think sure would call in. Oh, I, I >>Think >>I guarantee if we had that right now, people would call in and Corey, what do you think about X? >>Yeah. It not, everyone understands the full context of what I do. And in fact, increasingly few people do and that's fine. I, I keep forgetting that sometimes people do not see what I'm doing in the same light that I do. And that's fine. Blowback has been largely minimal. Honestly, I am surprised anything by how little I have gotten over the last five years of doing this, but it would be easier to dismiss me if I weren't generally. Right. When, okay, so you launch this new service and it seems pretty crappy to me cuz when I try and build something, it falls over and begs for help. And people might not like hearing that, but it's what customers are finding too. Yeah. I really am the voice of the customer. >>You know, I always joke with Dave Avante about how John Fort's always at, uh, um, reinvent getting the interview with jazzy now, Andy we're there, you're there. And so we have these rituals at the events. It's all cool. Um, one of the rituals I like about your, um, your content is you like to get on the naming product names. Um, and, and, and, and, and kind of goof on that. Now why I like is because I used to work at ETT Packard where they used to name things as like engineers, HP 1 0, 0 5, or we can't, we >>Have a new monitor. How are we gonna name it? Throw the wireless keyboard down the stairs again. And then there you go. Yeah. >>It's and the old joke at HP was if they, if they invented sushi, they'd say, yeah, we can't call sushi. It's cold, dead fish, but that's what it is. And so the joke was cold. Dead fish is a better name than sushi. So you know is fun. So what's the, what are the, how's the Amazon doing in there? Have they changed their naming, uh, strategy, uh, on some of their, their product >>They're going in different directions. When they named Aurora, they decided to explore a new theme of Disney princesses as they go down those paths. And some things are more descriptive. Some people are clearly getting bonus on number of words, they can shove into it. Like the better a service is the longer it's name. Like AWS systems manager, a session manager is a great one. I love the service ridiculous name. They have a systems manager, parameter store with is great. They have secrets manager, which does the same thing. It's two words less, but that one costs money in a way that systems manage through parameter store does not. It's fun. >>What's your, what's your favorite combination of acronyms >>Combination of you >>Got Ks. You got EMR, you got EC two. You got S three SQS. Well, RedShift's not an acronym. You got >>Gas is one of my personal favorites because it's either elastic block store or elastic bean stock, depending entirely on the context of the conversation, >>They still got bean stock or is that still >>Around? Oh, they never turn anything off. They're like the anti Google, Google turns things off while they're still building it. Whereas Amazon is like, wow, we built this thing in 2005 and everyone hates it. But while we certainly can't change it, now it has three customers on it, John. >>Okay. >>Simple BV still haunts our >>Dreams. I, I actually got an email on, I saw one of my, uh, servers, all these C twos were being deprecated and I got an email I'm like, I couldn't figure out. Why can you just like roll it over? Why, why are you telling me just like, gimme something else. Right. Okay. So let me talk about, uh, the other things I want to ask you is that like, okay, so as Amazon gets better in some areas where do they need more work? And you, your opinion, because obviously they're all interested in new stuff and they tend to like put it out there for their end to end customers. But then they've got ecosystem partners who actually have the same product. Yes. And, and this has been well documented. So it's, it's not controversial. It's just that Amazon's got a database Snowflake's got out database service. So, you know, Redshift, snowflake database is out there. So you've got this optician. Yes. How's that going? And what are you hearing about the reaction to any of that stuff? >>Depends on who you ask. They love to basically trot out a bunch of their partners who will say nice things about them. And it very much has heirs of, let's be honest, a hostage video, but okay. Cuz these companies do partner with Amazon and they cannot afford to rock the boat too far. I'm not partnered with anyone. I can say what I want. And they're basically restricted to taking away my birthday at worse so I can live with that. >>All right. So I gotta ask about multi-cloud cause obviously the other cloud shows are coming up. Amazon hated that word. Multi-cloud um, a lot of people are saying, you know, it's not a real good marketing word. Like multicloud sounds like, you know, root canal. Mm-hmm <affirmative> right. So is there a better description for multicloud? >>Multiple single >>Loves that term. Yeah. >>You're building in multiple single points of failure. Do it for the right reasons or don't do it as a default. I believe not doing it is probably the, the right answer. However, and if I were, if I were Amazon, I wouldn't want to talk about multi-cloud either as the industry leader, let's talk about other clouds, bad direction to go in from a market cap perspective. It doesn't end well for you, but regardless of what they want to talk about, or don't want to talk about what they say, what they don't say, I tune all of it out. And I look at what customers are doing and multi-cloud exists in a variety of some brilliant, some brain dead. It depends a lot on context. But my general response is when someone gets on stage from a company and tells me to do a thing that directly benefits their company. I am skeptical at best. Yeah. When customers get on stage and say, this is what we're doing because it solves problems. That's when I shut up and listen. >>Yeah. Cool. Awesome. Corey, I gotta ask you a question cause I know you we've been, you know, fellow journey mean in the, in the cloud journey, going to all the events and then the pandemic hit where now in the third year, who knows what it's gonna end, certainly events are gonna look different. They're gonna be either changing footprint with the virtual piece, new group formations community's gonna emerge. You've got a pretty big community growing and it's growing like crazy. What's the weirdest or coolest thing, or just big changes you've seen with the pan endemic, uh, from your perspective, cuz you've been in the you're in the middle of the whitewater rafting. You've seen the events you circle offline. You saw the online piece come in, you're commentating, you're calling balls and strikes in the industry. You got a great team developing over there. Duck bill group. What's the big aha moment that you saw with the pandemic. Weird, funny, serious, real in the industry and with customers what's >>Accessibility. Reinvent is a great example. When in the before times it's open to anyone who wants to attend, who >>Can pony. >>Hello and welcome back to the live cube coverage here in San Francisco, California, the cube live coverage. Two days, day two of a summit, 2022 Aish summit, New York city coming up in summer. We'll be there as well. Events are back. I'm the host, John fur, the Cub got great guest here. Johnny Dallas with Ze. Um, here is on the queue. We're gonna talk about his background. Uh, little trivia here. He was the youngest engineer ever worked at Amazon at the age. 17 had to get escorted into reinvent in Vegas cause he was underage <laugh> with security, all good stories. Now the CEO of company called Z know DevOps kind of focus, managed service, a lot of cool stuff, Johnny, welcome to the cube. >>Thanks John. Great. >>So tell a story. You were the youngest engineer at AWS. >>I was, yes. So I used to work at a company called Bebo. I got started very young. I started working when I was about 14, um, kind of as a software engineer. And when I, uh, it was about 16. I graduated out of high school early, um, working at this company Bebo, still running all of the DevOps at that company. Um, I went to reinvent in about 2018 to give a talk about some of the DevOps software I wrote at that company. Um, but you know, as many of those things were probably familiar with reinvent happens in a casino and I was 16. So was not able to actually go into the, a casino on my own. Um, so I'd have <inaudible> security as well as casino security escort me in to give my talk. >>Did Andy jazzy, was he aware of >>This? Um, you know, that's a great question. I don't know. <laugh> >>I'll ask him great story. So obviously you started a young age. I mean, it's so cool to see you jump right in. I mean, I mean you never grew up with the old school that I used to grew up in and loading package software, loading it onto the server, deploying it, plugging the cables in, I mean you just rocking and rolling with DevOps as you look back now what's the big generational shift because now you got the Z generation coming in, millennials on the workforce. It's changing like no one's putting and software on servers. Yeah, >>No. I mean the tools keep getting better, right? We, we keep creating more abstractions that make it easier and easier. When I, when I started doing DevOps, I could go straight into E two APIs. I had APIs from the get go and you know, my background was, I was a software engineer. I never went through like the CIS admin stack. I, I never had to, like you said, rack servers, myself. I was immediately able to scale. I was managing, I think 2,500 concurrent servers across every Ables region through software. It was a fundamental shift. >>Did you know what an SRE was at that time? >>Uh, >>You were kind of an SRE on >>Yeah, I was basically our first SRE, um, was familiar with the, with the phrasing, but really thought of myself as a software engineer who knows cloud APIs, not a SRE. All >>Right. So let's talk about what's what's going on now as you look at the landscape today, what's the coolest thing that's going on in your mind in cloud? >>Yeah, I think the, I think the coolest thing is, you know, we're seeing the next layer of those abstraction tools exist and that's what we're doing with Z is we've basically gone and we've, we're building an app platform that deploys onto your cloud. So if you're familiar with something like Carku, um, where you just click a GitHub repo, uh, we actually make it that easy. You click a GI hub repo and it will deploy on ALS using a AWS tools. So, >>Right. So this is Z. This is the company. Yes. How old's the company about >>A year and a half old now. >>All right. So explain what it does. >>Yeah. So we make it really easy for any software engineer to deploy on a AWS. It's not SREs. These are the actual application engineers doing the business logic. They don't really want to think about Yamo. They don't really want to configure everything super deeply. They want to say, run this API on S in the best way possible. We've encoded all the best practices into software and we set it up for you. Yeah. >>So I think the problem you're solving is that there's a lot of want be DevOps engineers. And then they realize, oh shit, I don't wanna do this. Yeah. And some people want to do it. They loved under the hood. Right. People love to have infrastructure, but the average developer needs to actually be as agile on scale. So that seems to be the problem you solve. Right? >>Yeah. We, we, we give way more productivity to each individual engineer, you know? >>All right. So let me ask you a question. So let me just say, I'm a developer. Cool. I build this new app. It's a streaming app or whatever. I'm making it up cube here, but let's just say I deploy it. I need your service. But what happens about when my customers say, Hey, what's your SLA? The CDN went down from this it's flaky. Does Amazon have, so how do you handle all that SLA reporting that Amazon provides? Cuz they do a good job with sock reports all through the console. But as you start getting into DevOps <affirmative> and sell your app, mm-hmm <affirmative> you have customer issues. How do you, how do you view that? Yeah, >>Well, I, I think you make a great point of AWS has all this stuff already. AWS has SLAs. AWS has contract. Aw has a lot of the tools that are expected. Um, so we don't have to reinvent the wheel here. What we do is we help people get to those SLAs more easily. So Hey, this is AWS SLA as a default. Um, Hey, we'll fix you your services. This is what you can expect here. Um, but we can really leverage S's reliability of you. Don't have to trust us. You have to trust ALS and trust that the setup is good there. >>Do you handle all the recovery or mitigation between, uh, identification say downtime for instance? Oh, the server's not 99% downtime. Uh, went down for an hour, say something's going on? And is there a service dashboard? How does it get what's the remedy? Do you have a, how does all that work? >>Yeah, so we have some built in remediation. You know, we, we basically say we're gonna do as much as we can to keep your endpoint up 24 7 mm-hmm <affirmative>. If it's something in our control, we'll do it. If it's a disc failure, that's on us. If you push bad code, we won't put out that new version until it's working. Um, so we do a lot to make sure that your endpoint stay is up, um, and then alert you if there's a problem that we can't fix. So cool. Hey S has some downtime, this thing's going on. You need to do this action. Um, we'll let you know. >>All right. So what do you do for fun? >>Yeah, so, uh, for, for fun, um, a lot of side projects. <laugh> uh, >>What's your side hustle right now. You got going on >>The, uh, it's >>A lot of tools playing tools, serverless. >>Yeah, painless. A lot of serverless stuff. Um, I think there's a lot of really cool WAM stuff as well. Going on right now. Um, I love tools is, is the truest answer is I love building something that I can give to somebody else. And they're suddenly twice as productive because of it. Um, >>It's a good feeling, isn't it? >>Oh yeah. There's >>Nothing like tools were platforms. Mm-hmm <affirmative>, you know, the expression, too many tools in the tool. She becomes, you know, tools for all. And then ultimately tools become platforms. What's your view on that? Because if a good tool works and starts to get traction, you need to either add more tools or start building a platform platform versus tool. What's your, what's your view on a reaction to that kind of concept debate? >>Yeah, it's a good question. Uh, we we've basically started as like a, a platform. First of we've really focused on these, uh, developers who don't wanna get deep into the DevOps. And so we've done all of the pieces of the stacks. We do C I C D management. Uh, we do container orchestration, we do monitoring. Um, and now we're, spliting those up into individual tools so they can be used. Awesome in conjunction more. >>All right. So what are some of the use cases that you see for your service? It's DevOps basically nano service DevOps. So people who want a DevOps team, do clients have a DevOps person and then one person, two people what's the requirements to run >>Z. Yeah. So we we've got teams, um, from no DevOps is kind of when they start and then we've had teams grow up to about, uh, five, 10 men DevOps teams. Um, so, you know, as is more infrastructure people come in because we're in your cloud, you're able to go in and configure it on top you're we can't block you. Uh, you wanna use some new AWS service. You're welcome to use that alongside the stack that we deploy >>For you. How many customers do you have now? >>So we've got about 40 companies that are using us for all of their infrastructure, um, kind of across the board, um, as well as >>What's the pricing model. >>Uh, so our pricing model is we, we charge basically similar to an engineering salary. So we charge a monthly rate. We have plans at 300 bucks a month, a thousand bucks a month, and then enterprise plan for >>The requirement scale. Yeah. So back into the people cost, you must have her discounts, not a fully loaded thing, is it? >>Yeah, there's a discounts kind of asking >>Then you pass the Amazon bill. >>Yeah. So our customers actually pay for the Amazon bill themselves. So >>Have their own >>Account. There's no margin on top. You're linking your, a analyst account in, um, got it. Which is huge because we can, we are now able to help our customers get better deals with Amazon. Um, got it. We're incentivized on their team to drive your costs down. >>And what's your unit main unit of economics software scale. >>Yeah. Um, yeah, so we, we think of things as projects. How many services do you have to deploy as that scales up? Um, awesome. >>All right. You're 20 years old now you not even can't even drink legally. <laugh> what are you gonna do when you're 30? We're gonna be there. >>Well, we're, uh, we're making it better, better, >>Better the old guy on the queue here. <laugh> >>I think, uh, I think we're seeing a big shift of, um, you know, we've got these major clouds. ALS is obviously the biggest cloud and it's constantly coming out with new services, but we're starting to see other clouds have built many of the common services. So Kubernetes is a great example. It exists across all the clouds and we're starting to see new platforms come up on top that allow you to leverage tools for multiple times. At the same time. Many of our customers actually have AWS as their primary cloud and they'll have secondary clouds or they'll pull features from other clouds into AWS, um, through our software. I think that's, I'm very excited by that. And I, uh, expect to be working on that when I'm 30. <laugh> awesome. >>Well, you gonna have a good future. I gotta ask you this question cuz uh, you know, I always, I was a computer science undergrad in the, in the, and um, computer science back then was hardcore, mostly systems OS stuff, uh, database compiler. Um, now there's so much compi, right? Mm-hmm <affirmative> how do you look at the high school college curriculum experience slash folks who are nerding out on computer science? It's not one or two things. You've got a lot of, lot of things. I mean, look at Python, data engineering and emerging as a huge skill. What's it, what's it like for college kids now and high school kids? What, what do you think they should be doing if you had to give advice to your 16 year old self back a few years ago now in college? Um, I mean Python's not a great language, but it's super effective for coding and the datas were really relevant, but it's, you've got other language opportunities you've got tools to build. So you got a whole culture of young builders out there. What should, what should people gravitate to in your opinion and stay away from or >>Stay away from? That's a good question. I, I think that first of all, you're very right of the, the amount of developers is increasing so quickly. Um, and so we see more specialization. That's why we also see, you know, these SREs that are different than typical application engineering. You know, you get more specialization in job roles. Um, I think if, what I'd say to my 16 year old self is do projects, um, the, I learned most of my, what I've learned just on the job or online trying things, playing with different technologies, actually getting stuff out into the world, um, way more useful than what you'll learn in kind of a college classroom. I think classroom's great to, uh, get a basis, but you need to go out and experiment actually try things. >>You know? I think that's great advice. In fact, I would just say from my experience of doing all the hard stuff and cloud is so great for just saying, okay, I'm done, I'm banning the project. Move on. Yeah. Cause you know, it's not gonna work in the old days. You have to build this data center. I bought all this, you know, people hang on to the old, you know, project and try to force it out there. Now you >>Can launch a project now, >>Instant gratification, it ain't working <laugh> or this is shut it down and then move on to something new. >>Yeah, exactly. Instantly you should be able to do that much more quickly. Right. So >>You're saying get those projects and don't be afraid to shut it down. Mm-hmm <affirmative> that? Do you agree with that? >>Yeah. I think it's ex experiment. Uh, you're probably not gonna hit it rich on the first one. It's probably not gonna be that idea is the genius idea. So don't be afraid to get rid of things and just try over and over again. It's it's number of reps >>That'll win. I was commenting online. Elon Musk was gonna buy Twitter, that whole Twitter thing. And someone said, Hey, you know, what's the, I go look at the product group at Twitter's been so messed up because they actually did get it right on the first time. And we can just a great product. They could never change it because people would freak out and the utility of Twitter. I mean, they gotta add some things, the added button and we all know what they need to add, but the product, it was just like this internal dysfunction, the product team, what are we gonna work on? Don't change the product so that you kind of have there's opportunities out there where you might get the lucky strike right outta the gate. Yeah. Right. You don't know. >>It's almost a curse too. It's you're not gonna hit curse Twitter. You're not gonna hit a rich the second time too. So yeah. >><laugh> Johnny Dallas. Thanks for coming on the cube. Really appreciate it. Give a plug for your company. Um, take a minute to explain what you're working on. What you're look looking for. You hiring funding. Customers. Just give a plug, uh, last minute and kind the last word. >>Yeah. So, um, John Dallas from Ze, if you, uh, need any help with your DevOps, if you're a early startup, you don't have DevOps team, um, or you're trying to deploy across clouds, check us out z.com. Um, we are actively hiring. So if you are a software engineer excited about tools and cloud, or you're interested in helping getting this message out there, hit me up. Um, find us on z.co. >>Yeah. LinkedIn Twitter handle GitHub handle. >>Yeah. I'm the only Johnny on a LinkedIn and GitHub and underscore Johnny Dallas underscore on Twitter. All right. Um, >>Johnny Dallas, the youngest engineer working at Amazon, um, now 20 we're on great new project here in the cube. Builders are all young. They're growing into the business. They got cloud at their, at their back it's tailwind. I wish I was 20. Again, this is a I'm John for your host. Thanks for watching. Thanks. >>Welcome >>Back to the cubes. Live coverage of a AWS summit in San Francisco, California events are back, uh, ADAS summit in New York cities. This summer, the cube will be there as well. Check us out there lot. I'm glad we have events back. It's great to have everyone here. I'm John furry host of the cube. Dr. Matt wood is with me cube alumni now VP of business analytics division of AWS. Matt. Great to see you. Thank >>You, John. Great to be here. >>Appreciate it. I always call you Dr. Matt wood, because Andy jazzy always says Dr. Matt, we >>Would introduce you on the he's the one and only the one and >>Only Dr. Matt wood >>In joke. I love it. >>Andy style. And I think you had walkup music too on, you know, >>Too. Yes. We all have our own personalized walk. >>So talk about your new role. I not new role, but you're running up, um, analytics, business or AWS. What does that consist of right now? >>Sure. So I work, I've got what I consider to be the one of the best jobs in the world. Uh, I get to work with our customers and, uh, the teams at AWS, uh, to build the analytics services that millions of our customers use to, um, uh, slice dice, pivot, uh, better understand their day data, um, look at how they can use that data for, um, reporting, looking backwards and also look at how they can use that data looking forward. So predictive analytics and machine learning. So whether it is, you know, slicing and dicing in the lower level of, uh Hado and the big data engines, or whether you're doing ETR with glue or whether you're visualizing the data in quick side or building models in SageMaker. I got my, uh, fingers in a lot of pies. >>You know, one of the benefits of, uh, having cube coverage with AWS since 2013 is watching the progression. You were on the cube that first year we were at reinvent 2013 and look at how machine learning just exploded onto the scene. You were involved in that from day one is still day one, as you guys say mm-hmm <affirmative>, what's the big thing now. I mean, look at, look at just what happened. Machine learning comes in and then a slew of services come in and got SageMaker became a hot seller, right outta the gate. Mm-hmm <affirmative> the database stuff was kicking butt. So all this is now booming. Mm-hmm <affirmative> that was the real generational changeover for <inaudible> what's the perspective. What's your perspective on, yeah, >>I think how that's evolved. No, I think it's a really good point. I, I totally agree. I think for machine machine learning, um, there was sort of a Renaissance in machine learning and the application of machine learning machine learning as a technology has been around for 50 years, let's say, but, uh, to do machine learning, right? You need like a lot of data, the data needs to be high quality. You need a lot of compute to be able to train those models and you have to be able to evaluate what those mean as you apply them to real world problems. And so the cloud really removed a lot of the constraints. Finally, customers had all of the data that they needed. We gave them services to be able to label that data in a high quality way. There's all the compute. You need to be able to train the models <laugh> and so where you go. >>And so the cloud really enabled this Renaissance with machine learning, and we're seeing honestly, a similar Renaissance with, uh, with data, uh, and analytics. You know, if you look back, you know, five, 10 years, um, analytics was something you did in batch, like your data warehouse ran a analysis to do, uh, reconciliation at the end of the month. And then was it? Yeah. And so that's when you needed it, but today, if your Redshift cluster isn't available, uh, Uber drivers don't turn up door dash deliveries, don't get made. It's analytics is now central to virtually every business and it is central to every virtually every business is digital transformation. Yeah. And be able to take that data from a variety of sources here, or to query it with high performance mm-hmm <affirmative> to be able to actually then start to augment that data with real information, which usually comes from technical experts and domain experts to form, you know, wisdom and information from raw data. That's kind of, uh, what most organizations are trying to do when they kind of go through this analytics journey. It's >>Interesting, you know, Dave LAN and I always talk on the cube, but out, you know, the future and, and you look back, the things we were talking about six years ago are actually happening now. Yeah. And it's not a, a, a, you know, hyped up statement to say digital transformation. It actually's happening now. And there's also times where we bang our fist on the table, say, I really think this is so important. And Dave says, John, you're gonna die on that hill <laugh>. >>And >>So I I'm excited that this year, for the first time I didn't die on that hill. I've been saying data you're right. Data as code is the next infrastructure as code mm-hmm <affirmative>. And Dave's like, what do you mean by that? We're talking about like how data gets and it's happening. So we just had an event on our 80 bus startups.com site mm-hmm <affirmative>, um, a showcase with startups and the theme was data as code and interesting new trends emerging really clearly the role of a data engineer, right? Like an SRE, what an SRE did for cloud. You have a new data engineering role because of the developer on, uh, onboarding is massively increasing exponentially, new developers, data science, scientists are growing mm-hmm <affirmative> and the, but the pipelining and managing and engineering as a system. Yeah. Almost like an operating system >>And as a discipline. >>So what's your reaction to that about this data engineer data as code, because if you have horizontally scalable data, you've gotta be open that's hard. <laugh> mm-hmm <affirmative> and you gotta silo the data that needs to be siloed for compliance and reasons. So that's got a very policy around that. So what's your reaction to data as code and data engineering and >>Phenomenon? Yeah, I think it's, it's a really good point. I think, you know, like with any, with any technology, uh, project inside an organization, you know, success with analytics or machine learning is it's kind of 50% technology and then 50% cultural. And, uh, you have often domain experts. Those are, could be physicians or drug experts, or they could be financial experts or whoever they might be got deep domain expertise. And then you've got technical implementation teams and it's kind of a natural often repulsive force. I don't mean that rudely, but they, they just, they don't talk the same language. And so the more complex the domain and the more complex the technology, the stronger that repulsive force, and it can become very difficult for, um, domain experts to work closely with the technical experts, to be able to actually get business decisions made. And so what data engineering does and data engineering is in some cases team, or it can be a role that you play. >>Uh, it's really allowing those two disciplines to speak the same language it provides. You can think of it as plumbing, but I think of it as like a bridge, it's a bridge between like the technical implementation and the domain experts. And that requires like a very disparate range of skills. You've gotta understand about statistics. You've gotta understand about the implementation. You've gotta understand about the, it, you've gotta understand and understand about the domain. And if you could pull all of that together, that data engineering discipline can be incredibly transformative for an organization, cuz it builds the bridge between those two >>Groups. You know, I was advising some, uh, young computer science students at the sophomore junior level, uh, just a couple weeks ago. And I told 'em, I would ask someone at Amazon, this questions I'll ask you since you're, you've been in the middle of of it for years, they were asking me and I was trying to mentor them on. What, how do you become a data engineer from a practical standpoint, uh, courseware projects to work on how to think, um, not just coding Python cause everyone's coding in Python mm-hmm <affirmative> but what else can they do? So I was trying to help them and I didn't really know the answer myself. I was just trying to like kind of help figure it out with them. So what is the answer in your opinion or the thoughts around advice to young students who want to be data engineers? Cuz data scientists is pretty clear in what that is. Yeah. You use tools, you make visualizations, you manage data, you get answers and insights and apply that to the business. That's an application mm-hmm <affirmative>, that's not the, you know, sta standing up a stack or managing the infrastructure. What, so what does that coding look like? What would your advice be to >>Yeah, I think >>Folks getting into a data engineering role. >>Yeah. I think if you, if you believe this, what I said earlier about like 50% technology, 50% culture, like the, the number one technology to learn as a data engineer is the tools in the cloud, which allow you to aggregate data from virtually any source into something which is incrementally more valuable for the organization. That's really what data engineering is all about. It's about taking from multiple sources. Some people call them silos, but silos indicates that the, the storage is kind of fungible or UND differentiated. That that's really not the case. Success requires you to really purpose built well crafted high performance, low cost engines for all of your data. So understanding those tools and understanding how to use 'em, that's probably the most important technical piece. Um, and yeah, Python and programming and statistics goes along with that, I think. And then the most important cultural part, I think is it's just curiosity. >>Like you want to be able to, as a data engineer, you want to have a natural curiosity that drives you to seek the truth inside an organization, seek the truth of a particular problem and to be able to engage, cuz you're probably, you're gonna have some choice as you go through your career about which domain you end up in, like maybe you're really passionate about healthcare. Maybe you're really just passionate about your transportation or media, whatever it might be. And you can allow that to drive a certain amount of curiosity, but within those roles, like the domains are so broad, you kind of gotta allow your curiosity to develop and lead, to ask the right questions and engage in the right way with your teams. So because you can have all the technical skills in the world, but if you're not able to help the team's truths seek through that curiosity, you simply won't be successful. >>We just had a guest on 20 year old, um, engineer, founder, Johnny Dallas, who was 16 when he worked at Amazon youngest engineer at >>Johnny Dallas is a great name by the that's fantastic. It's his real name? >>It sounds like a football player. Rockstar. I should call Johnny. I have Johnny Johnny cube. Uh it's me. Um, so, but he's young and, and he, he was saying, you know, his advice was just do projects. >>Yeah. That's get hands on. >>Yeah. And I was saying, Hey, I came from the old days though, you get to stand stuff up and you hugged onto the assets. Cause you didn't wanna kill the cause you spent all this money and, and he's like, yeah, with cloud, you can shut it down. If you do a project that's not working and you get bad data, no one's adopting it or you don't want like it anymore. You shut it down. Just something >>Else. Totally >>Instantly abandoned it. Move onto something new. >>Yeah. With progression. Totally. And it, the, the blast radius of, um, decisions is just way reduced, gone. Like we talk a lot about like trying to, you know, in the old world trying to find the resources and get the funding. And it's like, right. I wanna try out this kind of random idea that could be a big deal for the organization. I need 50 million in a new data center. Like you're not gonna get anywhere. You, >>You do a proposal working backwards, document >>Kinds, all that, that sort of stuff got hoops. So, so all of that is gone, but we sometimes forget that a big part of that is just the, the prototyping and the experimentation and the limited blast radius in terms of cost. And honestly, the most important thing is time just being able to jump in there, get fingers on keyboards, just try this stuff out. And that's why at AWS, we have part of the reason we have so many services because we want, when you get into AWS, we want the whole toolbox to be available to every developer. And so, as your ideas developed, you may want to jump from, you know, data that you have, that's already in a database to doing realtime data. Yeah. And then you can just, you have the tools there. And when you want to get into real time data, you don't just have kineses, but you have real time analytics and you can run SQL again, that data is like the, the capabilities and the breadth, like really matter when it comes to prototyping and, and >>That's culture too. That's the culture piece, because what was once a dysfunctional behavior, I'm gonna go off the reservation and try something behind my boss's back or cause now as a side hustle or fun project. Yeah. So for fun, you can just code something. Yeah, >>Totally. I remember my first Haddo project, I found almost literally a decommissioned set of servers in the data center that no one was using. They were super old. They're about to be literally turned off. And I managed to convince the team to leave them on for me for like another month. And I installed her DUP on them and like, got them going. It's like, that just seems crazy to me now that I, I had to go and convince anybody not to turn these service off, but what >>It was like for that, when you came up with elastic map produce, because you said this is too hard, we gotta make it >>Easier. Basically. Yes. <laugh> I was installing Haddo version, you know, beta nor 0.9 or whatever it was. It's like, this is really hard. This is really hard. >>We simpler. All right. Good stuff. I love the, the walk down memory lane and also your advice. Great stuff. I think culture's huge. I think. And that's why I like Adam's keynote to reinvent Adam. Lesky talk about path minds and trail blazers because that's a blast radius impact. Mm-hmm <affirmative> when you can actually have innovation organically just come from anywhere. Yeah, that's totally cool. Totally. Let's get into the products. Serverless has been hot mm-hmm <affirmative> uh, we hear a lot about EKS is hot. Uh, containers are booming. Kubernetes is getting adopted. There's still a lot of work to do there. Lambda cloud native developers are booming, serverless Lambda. How does that impact the analytics piece? Can you share the hot, um, products around how that translates? Sure, absolutely. Yeah, the SageMaker >>Yeah, I think it's a, if you look at kind of the evolution and what customers are asking for, they're not, you know, they don't just want low cost. They don't just want this broad set of services. They don't just want, you know, those services to have deep capabilities. They want those services to have as lower operating cost over time as possible. So we kind of really got it down. We got built a lot of muscle, lot of services about getting up and running and experimenting and prototyping and turning things off and turn turning them on and turning them off. And like, that's all great. But actually the, you really only most projects start something once and then stop something once. And maybe there's an hour in between, or maybe there's a year, but the real expense in terms of time and, and complexity is sometimes in that running cost. Yeah. And so, um, we've heard very loudly and clearly from customers that they want, that, that running cost is just undifferentiated to them and they wanna spend more time on their work and in analytics that is, you know, slicing the data, pivoting the data, combining the data, labeling the data, training their models, uh, you know, running inference against their models, uh, and less time doing the operational pieces. >>So is that why the servers focus is there? >>Yeah, absolutely. It, it dramatically reduces the skill required to run these, uh, workloads of any scale. And it dramatically reduces the UND differentiated, heavy lifting, cuz you get to focus more of the time that you would've spent on the operation on the actual work that you wanna get done. And so if you look at something just like Redshift serverless that we launched a reinvent, you know, there's a kind of a, we have a lot of customers that want to run like a, uh, the cluster and they want to get into the, the weeds where there is benefit. We have a lot of customers that say, you know, I there's no benefit for me though. I just wanna do the analytics. So you run the operational piece, you're the experts we've run. You know, we run 60 million instant startups every single day. Like we do this a lot. Exactly. We understand the operation. I >>Want the answers come on. So >>Just give the answers or just let, give me the notebook or just give the inference prediction. So today for example, we announced, um, you know, serverless inference. So now once you've trained your machine learning model, just, uh, run a few, uh, lines of code or you just click a few buttons and then yeah, you got an inference endpoint that you do not have to manage. And whether you're doing one query against that endpoint, you know, per hour or you're doing, you know, 10 million, but we'll just scale it on the back end. You >>Know, I know we got not a lot of time left, but I want, wanna get your reaction to this. One of the things about the data lakes, not being data swamps has been from what I've been reporting and hearing from customers is that they want to retrain their machine learning algorithm. They want, they need that data. They need the, the, the realtime data and they need the time series data, even though the time has passed, they gotta store in the data lake mm-hmm <affirmative>. So now the data lakes main function is being reusing the data to actually retrain. Yeah, >>That's >>Right. It worked properly. So a lot of, lot of postmortems turn into actually business improvements to make the machine learning smarter, faster. You see that same way. Do you see it the same way? Yeah, >>I think it's, I think it's really interesting. No, I think it's really interesting because you know, we talk it's, it's convenient to kind of think of analytics as a very clear progression from like point a point B, but really it's, you are navigating terrain for which you do not have a map and you need a lot of help to navigate that terrain. Yeah. And so, you know, being, having these services in place, not having to run the operations of those services, being able to have those services be secure and well governed, and we added PII detection today, you know, something you can do automatically, uh, to be able to use their, uh, any unstructured data run queries against that unstructured data. So today we added, you know, um, text extract queries. So you can just say, well, uh, you can scan a badge for example, and say, well, what's the name on this badge? And you don't have to identify where it is. We'll do all of that work for you. So there's a often a, it's more like a branch than it is just a, a normal, uh, a to B path, a linear path. Uh, and that includes loops backwards. And sometimes you gotta get the results and use those to make improvements further upstream. And sometimes you've gotta use those. And when you're downstream, you'll be like, ah, I remember that. And you come back and bring it all together. So awesome. It's um, it's, uh, uh, it's a wonderful >>Work for sure. Dr. Matt wood here in the queue. Got just take the last word and give the update. Why you're here. What's the big news happening that you're announcing here at summit in San Francisco, California, and update on the, the business analytics >>Group? Yeah, I think, you know, one of the, we did a lot of announcements in the keynote, uh, encouraged everyone to take a look at that. Uh, this morning was Swami. Uh, one of the ones I'm most excited about, uh, is the opportunity to be able to take, uh, dashboards, visualizations. We're all used to using these things. We see them in our business intelligence tools, uh, all over the place. However, what we've heard from customers is like, yes, I want those analytics. I want their visualization. I want it to be up to date, but you know, I don't actually want to have to go my tools where I'm actually doing my work to another separate tool to be able to look at that information. And so today we announced, uh, one click public embedding for quick side dashboards. So today you can literally, as easily as embedding a YouTube video, you can take a dashboard that you've built inside, quick site cut and paste the HTML, paste it into your application and that's it. That's all you have to do. It takes seconds and >>It gets updated in real time. >>Updated in real time, it's interactive. You can do everything that you would normally do. You can brand it like this is there's no power by quick site button or anything like that. You can change the colors, make it fit in perfectly with your, with your applications. So that's sitting incredibly powerful way of being able to take a, uh, an analytics capability that today sits inside its own little fiefdom and put it just everywhere. It's, uh, very transformative. >>Awesome. And the, the business is going well. You got the serverless and your tailwind for you there. Good stuff, Dr. Matt with thank you. Coming on the cube >>Anytime. Thank >>You. Okay. This is the cubes cover of eight summit, 2022 in San Francisco, California. I'm John host cube. Stay with us with more coverage of day two after this short break.

(dramatic music) >> Live from San Francisco. It's theCUBE, covering IBM Think 2019. Brought to you by IBM. >> Welcome back to theCUBE. We are live at IBM Think 2019. I'm Lisa Martin with Dave Vellante. We're in San Francisco this year at the newly rejuved Moscone Center. Welcoming to theCUBE for the first time, Jozef de Vries, Director of IBM Cloud Databases. Jozef, it's great to have you on the program. >> Thank you very much, great to be here, great to be here. >> So as we were talking before we went live, this is, I was asking what you're excited about for this year's IBM Think. >> Yeah. >> Only the second annual IBM Think. >> Right. >> This big merger of a number of shows. >> Sure, you're right. >> Day minus one, team minus one, >> Yeah. >> everything really kicks off tomorrow. Talk to us about some of the things that you're working on. You've been at IBM for a long time. >> Mmm hmm. >> But cloud managed databases, let's talk value there for the customers. >> Yeah, definitely. Cloud managed databases really, at its core, it's about simplifying adoption of cloud provided services and reducing the capital expense that comes along with developing applications. Fundamentally what we're trying to do is abstract the overhead that is associated with running your own systems. Whether it's the infrastructure management, whether it's the network management, whether it's the configuration and deployment of you databases. Our collection of services really is about streamlining time to value of accessing and building against your databases. So we are really focused on is allowing the developer to focus on their business critical applications, their objectives, and really what they're paid for. They're paid to build applications, not paid to maintain systems. When we talk about the CIO office, the CTO office, they are looking at cost, they're looking at ways to reduce overall expenditures. And what we're able to provide with cloud managed databases is the ability not to have to staff an IT team, not to have to maintain and pay for infrastructure, not have to procure licenses, what have you, everything that goes into standing up the managing those systems yourself, we provide that and we provide the consumption based methods. So you basically pay for what you use, and we have various ways in which you can interact with your databases and the charges that are associated with that. But it really is again about alleviating all of that overhead and that expense that is associated with running systems yourself. >> 15 years ago, you're back to, before you started with IBM, >> Yeah. >> There was obviously IBM DB2, Oracle, SQL Server, >> SQL Server. >> I guess MySQL is around >> Mm hmm. >> back then, LabStack was building out the internet. But databases are pretty boring >> Yeah. >> back then. And then all of a sudden, it exploded. >> Right. >> And the NoSQL movement happened in a huge way. >> Mm hmm. >> Coincided with the big data movement. What happened? >> Yeah, I think as we saw the space of this technology evolve, and a variety of different kind of use cases cropping up. The development community kind of respond to that. And really what we try to do with our portfolio is provide that variety of database technology solutions. To me, not any number of different use cases. And we like to think about it broken down into two categories. Your primary data stores. This is where your applications are writing and reading the data that has been stored. And then particularly to your point, this is where we call the auxiliary data services, for example. These are your in memory caches, your message brokers, your search index, what have you. There is a plethora of different database technologies out there today that plug into any number of different use cases and application developers are attempting to fill. And more often than not, they're using more than one database at a time. And really what we're trying to do at IBM with our cloud managed database offering is provide a variety of those data services and database technologies to meet a variety of those use cases, whether they're mixing and matching, or different kind of applications workloads or what have you. We'd like to provide our customers with the choices that are out there today in the community at large. >> So many choices. >> Yeah. >> Am I hearing that its kind of horses for courses? I mean, you get things like, even niches like Cumulo with fine grain security. >> Yeah. >> Or Couchbase, obviously. >> Mm hmm. This one scales. And then this one is easy to use. You take Mongo, for text, really easy to use >> Yeah exactly. >> Sort of different specialized use cases. How do you squint through, and how does IBM match the right characteristics with the right technology? >> It's really, it's two-pronged. It's about understanding the user base. Understanding and listening to your customers. And really internalizing what are the use cases that they are looking to fulfill? It's also being in tune with the database technology in the market today. It's understanding where there are trends. Understanding where there are new use cases cropping up. And it's about building a deep enough engineering operations team where we can quickly spin up these new offerings. And again provide that technology to our end customers. And it's about working with our customers as well. And understanding the use cases and then sometimes making recommendations on what database technology or combination of databases would be best suited for their objectives. >> I'm curious. One of the things that you mentioned in terms of what the developer's day-to-day job should be, is this almost IBM's approach to aligning with the developer role and enabling it in new ways? >> It is really about, I think, having sympathy in delivering on solutions in regards that is simply for the pains that they had otherwise endured 10, 15 years ago. When the notion of cloud managed anything really wasn't a thing yet. Or was just starting to emerge. IBM in houses runs their own systems for years and years obviously and the folks on my team, they have come from other companies, they know that the pain, what pain is involved in trying to run services. So like I said it's a little bit out of sympathy, it's a bit out of knowing what your users need in a cloud managed service. Whether again it's security, or availability, or redundancy, you name it. It's about coming around to the other side of the table and I sat where you once sat. And we know what you need out of your data services. So trusting us to provide that for you. >> How are the requirements different? Things like recovery and resiliency. Do I need asset compliance in this new world? May be you could. >> Yeah. It's funny, that's a good question in that we don't necessarily deal so much with database specific requirements. Again as I mention we try to provide a variety of different database technologies. And by and large the users are going to know what they need, what combinations that they will need. And we'll work with them if they're navigating their way through it. Really what we see more the requirements these days are around the management characteristics. As you cited, are they highly available? Are they backed up? What's your disaster recovery policy? What security policies do you have in place? what compliance, so on and so forth. It's really about presenting the overall package of that managed solution. Not so much, whether the database is going to be high available verses consistent replication or what have you. I mean that's in there, and it's part of what we engage with our customers about, but also what we'd like to put a lot of emphasis is on providing those recognized database technologies so that there is a community behind and there's opportunity for the users to understand what it is that they need beyond just what we can sell them. It's really about selling the value proposition of again, the management characteristics of the services. >> So who do you see as the competition? Obviously the other big, the two big cloud providers, AWS and Azure. >> Yep. >> You're competing with them. >> Definitely. >> Quality of offerings. May be talk about how you fit. >> And Google's another one. Or Oracle is another emerging one. Even Alibaba is catching up quite a bit. It really feels like a neck-to-neck race in our day after day. The way we try to approach our portfolio is focusing on deep, broad and secure. Deep being that there're a core set of database technologies. We're building the database itself. Db2, Cloudant which is based off of Couchbase. Excuse me, CouchDB. And then broad. Again as I've been mentioning, having a variety of different database technologies. And they're secure across the board. Whether it's secure in how we run the systems, secure on how we certify them through external compliance certifications. Or secure in how we integrate with security based tooling that our users can take advantage of. Regarding our competitors, it really is one week it may be a new big data at scale type of database technology. Another day it may be, or another week it might be deeper integrations into the platform. It might be new open source database technologies. It might be a new proprietary database technology. But we're, it's a constant, like I say, race to who got the most robust portfolio. >> Developers are like teenagers. They're fickle. >> Yeah, that too, that too. We got to be quick in order to respond to those demands. >> In this age of hybrid multi-cloud, where the average company has five plus private cloud, public cloud, through inertia, through acquisition, et cetera. Where's IBM's advantage there as companies are, I think we heard a stat the other day, Dave, that in 2018, 80% of the companies migrated data and apps from public cloud. In terms of this reality that companies live in this multi-cloud, where is IBM's advantage there? And where does your approach to cloud managed services really differentiate IBM's capabilities? >> Really there's, for the last couple of years, a tremendous amount of investment on building on the Kubernetes open source platform. And even in particular to our cloud managed database services, we have been developing and have been recently releasing a number of different databases that run on a platform that we've developed against Kubernetes. It's a platform that allows us to orchestrate deployments, deletions of databases, backups, high availability, platform level integrations, all, a number of different things. What that has allowed us to do when concerning a hybrid type of strategy is it makes our platform more portable. So Kubernetes is something that can run on the cloud. It can run in a private cloud. It can run on premise. And this platform we're developing is something that can be deployed, which we do today for private, public cloud consumption, which can also be packaged up and deploy into a private cloud type environment. And ultimately it's portable and it's leveraging of that Kubernetes technology itself. So we're not hamstringing ourselves to purely public cloud type services, or only private cloud type services. We want to have something that is abstracted enough that again it can move around to these different kind of environments. >> How important is open source and how important is it for you to commit to the different open source projects? There are so many, >> Yeah. >> And you have limited resources. So how do you manage that? >> Open source is really critical both in what we're building and what we're also offering. As we've talked about our users out there, they know what they often want or sometimes we nudge them to the right or to the left, but generally speaking it's around all the open source technologies and whatever may be trending for that current month is often times what we're getting requested for. It could be a Postgres. It could be a RabbitMQ. It could be ElasticSearch. What have you. And really we put a lot of emphasis on embracing the open source community, providing those database technologies to our customers. And then it allows our customers to benefit from the community at large too. We don't become again the sole provider of education and information about that technology. We're able to expose the whole community to our customers and they're able to take advantage of that. >> I hear a lot of complaints sometimes, particularly from folks that might list themselves in a marketplace for one cloud or another, that they feel like the primary cloud vendor might be nudging the customer into their proprietary database. What's IBM's position on that? Is that fair? Is that overblown? >> We obviously have proprietary tech, particularly the Db2. And that's something we're continue investing in. It's what we view as one of our strategic top priority database technologies. We are very active developers in the Couch community as well. I wouldn't consider that proprietary, but again back to the point of-- >> CouchDB. You're as the steward of CouchDB. >> Exactly. >> Right. >> Right, exactly. But again, firm believers in open source. We want to give those opportunities to our customers to avoid those vendor lock-in type situations. We actually have quite a lot of interests from our EU customer base. And by and large EU policies are around anti-trust and what have you. They tend to gravitate towards open source technology because they know it's again portable. They can be used in Postgres by IBM one month and if they no longer are satisfied with that, they can take their Postgres workloads and move them into another cloud provider. Ideally they're coming from the other cloud providers onto IBM. >> Well I should be actually more specific, in fairness, Dynamo's often cited. I supposed Google's Spanner although that's sort of a more of a niche, >> Mm hmm. >> specialized database. If I understand it correctly, Db2, that's a hard core transaction >> Sure. >> system. You're not going to confused that with, I don't think, anyway CouchDB. Although, who knows? May be there are some use cases there. But it sounds like you're not nudging them to your proprietary, certainly Db2 is proprietary. CouchDB is one of many options that you offer. >> Certainly Db2 is one of our core products for our database portfolio. And we do want to push our customers to Db2 where-- >> If it makes sense. >> Exactly, where it makes sense. And where there's demand for it. If it doesn't make sense so there's not demand we will offer up any number of the other databases that we also offer. >> Excellent, here's our last question.As >> Sure. >> As IBM Think the 2nd annual kicks off really tomorrow. For this developer audience that you were talking about a lot in our conversation, what are some of the exciting things that they're going to you? Any sort of obviously not breaking news, but >> Mmm hmm. >> Where would you advise the developer community, who's attending IBM Think to go to learn more about cloud managed databases? And how they can really become far more efficient to do their jobs better. >> Sure. Databases are hard, plain and simple. They are particularly hard to run, and developers who are not necessarily database admins, they're not database operators, that they want to focus on building the applications, are going to want to find solutions that alleviate that overhead of running those systems themselves. So to your question we've got sessions all throughout the week where we're talking about our Cloudant offerings and the future of where we're going with that. We've got a couple of different sessions around our IBM cloud database portfolio. This is a lot of the open source database technology we're running. We have demos in the solution center and Db2's strided all around the conference as well. So there's lots of different sessions focused on talking the value proposition of IBM's cloud managed database portfolio across the board. >> A lot of opportunities for learning. Well, Jozef de Vries, Thank you so much for joining Dave and me on theCube this afternoon. >> Thank you very much, it was great. And for Dave Vallente, I am Lisa Martin. You're watching theCube, live from IBM Think 2019. Day 1 stick around. We'll be right back with our next guest. (upbeat music)

>> Narrator: Live from Munich Germany, it's theCUBE, covering IBM, Fast Track Your Data. Brought to you by IBM. >> We're back. This is Dave Vellante with Jim Kobielus, and this is theCUBE, the leader in live tech coverage. We go out to the events. We extract the signal from the noise. We are here covering special presentation of IBM's Fast Track your Data, and we're in Munich Germany. It's been a day-long session. We started this morning with a panel discussion with five senior level data scientists that Jim and I hosted. Then we did CUBE interviews in the morning. We cut away to the main tent. Kate Silverton did a very choreographed scripted, but very well done, main keynote set of presentations. IBM made a couple of announcements today, and then we finished up theCUBE interviews. Jim and I are here to wrap. We're actually running on IBMgo.com. We're running live. Hilary Mason talking about what she's doing in data science, and also we got a session on GDPR. You got to log in to see those sessions. So go ahead to IBMgo.com, and you'll find those. Hit the schedule and go to the Hilary Mason and GDP our channels, and check that out, but we're going to wrap now. Jim two main announcements today. I hesitate to call them big announcements. I mean they were you know just kind of ... I think the word you used last night was perfunctory. You know I mean they're okay, but they're not game changing. So what did you mean? >> Well first of all, when you look at ... Though IBM is not calling this a signature event, it's essentially a signature event. They do these every June or so. You know in the past several years, the signature events have had like a one track theme, whether it be IBM announcing their investing deeply in Spark, or IBM announcing that they're focusing on investing in R as the core language for data science development. This year at this event in Munich, it's really a three track event, in terms of the broad themes, and I mean they're all important tracks, but none of them is like game-changing. Perhaps IBM doesn't intend them to be it seems like. One of which is obviously Europe. We're holding this in Munich. And a couple of things of importance to European customers, first and foremost GDPR. The deadline next year, in terms of compliance, is approaching. So sound the alarm as it were. And IBM has rolled out compliance or governance tools. Download and the go from the information catalog, governance catalog and so forth. Now announcing the consortium with Hortonworks to build governance on top of Apache Atlas, but also IBM announcing that they've opened up a DSX center in England and a machine-learning hub here in Germany, to help their European clients, in those countries especially, to get deeper down into data science and machine learning, in terms of developing those applicants. That's important for the audience, the regional audience here. The second track, which is also important, and I alluded to it. It's governance. In all of its manifestations you need a master catalog of all the assets for building and maintaining and controlling your data applications and your data science applications. The catalog, the consortium, the various offerings at IBM is announced and discussed in great detail. They've brought in customers and partners like Northern Trust, talk about the importance of governance, not just as a compliance mandate, but also the potential strategy for monetizing your data. That's important. Number three is what I call cloud native data applications and how the state of the art in developing data applications is moving towards containerized and orchestrated environments that involve things like Docker and Kubernetes. The IBM DB2 developer community edition. Been in the market for a few years. The latest version they announced today includes kubernetes support. Includes support for JSON. So it's geared towards new generation of cloud and data apps. What I'm getting at ... Those three core themes are Europe governance and cloud native data application development. Each of them is individually important, but none of them is game changer. And one last thing. Data science and machine learning, is one of the overarching envelope themes of this event. They've had Hilary Mason. A lot of discussion there. My sense I was a little bit disappointed because there wasn't any significant new announcements related to IBM evolving their machine learning portfolio into deep learning or artificial intelligence in an environment where their direct competitors like Microsoft and Google and Amazon are making a huge push in AI, in terms of their investments. There's a bit of a discussion, and Rob Thomas got to it this morning, about DSX. Working with power AI, the IBM platform, I would like to hear more going forward about IBM investments in these areas. So I thought it was an interesting bunch of announcements. I'll backtrack on perfunctory. I'll just say it was good that they had this for a lot of reasons, but like I said, none of these individual announcements is really changing the game. In fact like I said, I think I'm waiting for the fall, to see where IBM goes in terms of doing something that's actually differentiating and innovative. >> Well I think that the event itself is great. You've got a bunch of partners here, a bunch of customers. I mean it's active. IBM knows how to throw a party. They've always have. >> And the sessions are really individually awesome. I mean terms of what you learn. >> The content is very good. I would agree. The two announcements that were sort of you know DB2, sort of what I call community edition. Simpler, easier to download. Even Dave can download DB2. I really don't want to download DB2, but I could, and play with it I guess. You know I'm not database guy, but those of you out there that are, go check it out. And the other one was the sort of unified data governance. They tried to tie it in. I think they actually did a really good job of tying it into GDPR. We're going to hear over the next, you know 11 months, just a ton of GDPR readiness fear, uncertainty and doubt, from the vendor community, kind of like we heard with Y2K. We'll see what kind of impact GDPR has. I mean it looks like it's the real deal Jim. I mean it looks like you know this 4% of turnover penalty. The penalties are much more onerous than any other sort of you know, regulation that we've seen in the past, where you could just sort of fluff it off. Say yeah just pay the fine. I think you're going to see a lot of, well pay the lawyers to delay this thing and battle it. >> And one of our people in theCUBE that we interviewed, said it exactly right. It's like the GDPR is like the inverse of Y2K. In Y2K everybody was freaking out. It was actually nothing when it came down to it. Where nobody on the street is really buzzing. I mean the average person is not buzzing about GDPR, but it's hugely important. And like you said, I mean some serious penalties may be in the works for companies that are not complying, companies not just in Europe, but all around the world who do business with European customers. >> Right okay so now bring it back to sort of machine learning, deep learning. You basically said to Rob Thomas, I see machine learning here. I don't see a lot of the deep learning stuff quite yet. He said stay tuned. You know you were talking about TensorFlow and things like that. >> Yeah they supported that ... >> Explain. >> So Rob indicated that IBM very much, like with power AI and DSX, provides an open framework or toolkit for plugging in your, you the developers, preferred machine learning or deep learning toolkit of an open source nature. And there's a growing range of open source deep learning toolkits beyond you know TensorFlow, including Theano and MXNet and so forth, that IBM is supporting within the overall ESX framework, but also within the power AI framework. In other words they've got those capabilities. They're sort of burying that message under a bushel basket, at least in terms of this event. Also one of the things that ... I said this too Mena Scoyal. Watson data platform, which they launched last fall, very important product. Very important platform for collaboration among data science professionals, in terms of the machine learning development pipeline. I wish there was more about the Watson data platform here, about where they're taking it, what the customers are doing with it. Like I said a couple of times, I see Watson data platform as very much a DevOps tool for the new generation of developers that are building machine learning models directly into their applications. I'd like to see IBM, going forward turn Watson data platform into a true DevOps platform, in terms of continuous integration of machine learning and deep learning another statistical models. Continuous training, continuous deployment, iteration. I believe that's where they're going, or probably she will be going. I'd like to see more. I'm expecting more along those lines going forward. What I just described about DevOps for data science is a big theme that we're focusing on at Wikibon, in terms where the industry is going. >> Yeah, yeah. And I want to come back to that again, and get an update on what you're doing within your team, and talk about the research. Before we do that, I mean one of the things we talked about on theCUBE, in the early days of Hadoop is that the guys are going to make the money in this big data business of the practitioners. They're not going to see, you know these multi-hundred billion dollar valuations come out of the Hadoop world. And so far that prediction has held up well. It's the Airbnbs and the Ubers and the Spotifys and the Facebooks and the Googles, the practitioners who are applying big data, that are crushing it and making all the money. You see Amazon now buying Whole Foods. That in our view is a data play, but who's winning here, in either the vendor or the practitioner community? >> Who's winning are the startups with a hot new idea that's changing, that's disrupting some industry, or set of industries with machine learning, deep learning, big data, etc. For example everybody's, with bated breath, waiting for you know self-driving vehicles. And the ecosystem as it develops somebody's going to clean up. And one or more companies, companies we probably never heard of, leveraging everything we're describing here today, data science and containerized distributed applications that involve you know deep learning for you know image analysis and sensor analyst and so forth. Putting it all together in some new fabric that changes the way we live on this planet, but as you said the platforms themselves, whether they be Hadoop or Spark or TensorFlow, whatever, they're open source. You know and the fact is, by it's very nature, open source based solutions, in terms of profit margins on selling those, inexorably migrate to zero. So you're not going to make any money as a tool vendor, or a platform vendor. You got to make money ... If you're going to make money, you make money, for example from providing an ecosystem, within which innovation can happen. >> Okay we have a few minutes left. Let's talk about the research that you're working on. What's exciting you these days? >> Right, right. So I think a lot of people know I've been around the analyst space for a long long time. I've joined the SiliconANGLE Wikibon team just recently. I used to work for a very large solution provider, and what I do here for Wikibon is I focus on data science as the core of next generation application development. When I say next-generation application development, it's the development of AI, deep learning machine learning, and the deployment of those data-driven statistical assets into all manner of application. And you look at the hot stuff, like chatbots for example. Transforming the experience in e-commerce on mobile devices. Siri and Alexa and so forth. Hugely important. So what we're doing is we're focusing on AI and everything. We're focusing on containerization and building of AI micro-services and the ecosystem of the pipelines and the tools that allow you to do that. DevOps for data science, distributed training, federated training of statistical models, so forth. We are also very much focusing on the whole distributed containerized ecosystem, Docker, Kubernetes and so forth. Where that's going, in terms of changing the state of the art, in terms of application development. Focusing on the API economy. All of those things that you need to wrap around the payload of AI to deliver it into every ... >> So you're focused on that intersection between AI and the related topics and the developer. Who is winning in that developer community? Obviously Amazon's winning. You got Microsoft doing a good job there. Google, Apple, who else? I mean how's IBM doing for example? Maybe name some names. Who do you who impresses you in the developer community? But specifically let's start with IBM. How is IBM doing in that space? >> IBM's doing really well. IBM has been for quite a while, been very good about engaging with new generation of developers, using spark and R and Hadoop and so forth to build applications rapidly and deploy them rapidly into all manner of applications. So IBM has very much reached out to, in the last several years, the Millennials for whom all of this, these new tools, have been their core repertoire from the very start. And I think in many ways, like today like developer edition of the DB2 developer community edition is very much geared to that market. Saying you know to the cloud native application developer, take a second look at DB2. There's a lot in DB2 that you might bring into your next application development initiative, alongside your spark toolkit and so forth. So IBM has startup envy. They're a big old company. Been around more than a hundred years. And they're trying to, very much bootstrap and restart their brand in this new context, in the 21st century. I think they're making a good effort at doing it. In terms of community engagement, they have a really good community engagement program, all around the world, in terms of hackathons and developer days, you know meetups here and there. And they get lots of turnout and very loyal customers and IBM's got to broadest portfolio. >> So you still bleed a little bit of blue. So I got to squeeze it out of you now here. So let me push a little bit on what you're saying. So DB2 is the emphasis here, trying to position DB2 as appealing for developers, but why not some of the other you know acquisitions that they've made? I mean you don't hear that much about Cloudant, Dash TV, and things of that nature. You would think that that would be more appealing to some of the developer communities than DB2. Or am I mistaken? Is it IBM sort of going after the core, trying to evolve that core you know constituency? >> No they've done a lot of strategic acquisitions like Cloudant, and like they've acquired Agrath Databases and brought them into their platform. IBM has every type of database or file system that you might need for web or social or Internet of Things. And so with all of the development challenges, IBM has got a really high-quality, fit-the-purpose, best-of-breed platform, underlying data platform for it. They've got huge amounts of developers energized all around the world working on this platform. DB2, in the last several years they've taken all of their platforms, their legacy ... That's the wrong word. All their existing mature platforms, like DB2 and brought them into the IBM cloud. >> I think legacy is the right word. >> Yeah, yeah. >> These things have been around for 30 years. >> And they're not going away because they're field-proven and ... >> They are evolving. >> And customers have implemented them everywhere. And they're evolving. If you look at how IBM has evolved DB2 in the last several years into ... For example they responded to the challenge from SAP HANA. We brought BLU Acceleration technology in memory technology into DB2 to make it screamingly fast and so forth. IBM has done a really good job of turning around these product groups and the product architecture is making them cloud first. And then reaching out to a new generation of cloud application developers. Like I said today, things like DB2 developer community edition, it's just the next chapter in this ongoing saga of IBM turning itself around. Like I said, each of the individual announcements today is like okay that's interesting. I'm glad to see IBM showing progress. None of them is individually disruptive. I think the last week though, I think Hortonworks was disruptive in the sense that IBM recognized that BigInsights didn't really have a lot of traction in the Hadoop spaces, not as much as they would have wished. Hortonworks very much does, and IBM has cast its lot to work with HDP, but HDP and Hortonworks recognizes they haven't achieved any traction with data scientists, therefore DSX makes sense, as part of the Hortonworks portfolio. Likewise a big sequel makes perfect sense as the sequel front end to the HDP. I think the teaming of IBM and Hortonworks is propitious of further things that they'll be doing in the future, not just governance, but really putting together a broader cloud portfolio for the next generation of data scientists doing work in the cloud. >> Do you think Hortonworks is a legitimate acquisition target for IBM. >> Of course they are. >> Why would IBM ... You know educate us. Why would IBM want to acquire Hortonworks? What does that give IBM? Open source mojo, obviously. >> Yeah mojo. >> What else? >> Strong loyalty with the Hadoop market with developers. >> The developer angle would supercharge the developer angle, and maybe make it more relevant outside of some of those legacy systems. Is that it? >> Yeah, but also remember that Hortonworks came from Yahoo, the team that developed much of what became Hadoop. They've got an excellent team. Strategic team. So in many ways, you can look at Hortonworks as one part aqui-hire if they ever do that and one part really substantial and growing solution portfolio that in many ways is complementary to IBM. Hortonworks is really deep on the governance of Hadoop. IBM has gone there, but I think Hortonworks is even deeper, in terms of their their laser focus. >> Ecosystem expansion, and it actually really wouldn't be that expensive of an acquisition. I mean it's you know north of ... Maybe a billion dollars might get it done. >> Yeah. >> You know so would you pay a billion dollars for Hortonworks? >> Not out of my own pocket. >> No, I mean if you're IBM. You think that would deliver that kind of value? I mean you know how IBM thinks about about acquisitions. They're good at acquisitions. They look at the IRR. They have their formula. They blue-wash the companies and they generally do very well with acquisitions. Do you think Hortonworks would fit profile, that monetization profile? >> I wouldn't say that Hortonworks, in terms of monetization potential, would match say what IBM has achieved by acquiring the Netezza. >> Cognos. >> Or SPSS. I mean SPSS has been an extraordinarily successful ... >> Well the day IBM acquired SPSS they tripled the license fees. As a customer I know, ouch, it worked. It was incredibly successful. >> Well, yeah. Cognos was. Netezza was. And SPSS. Those three acquisitions in the last ten years have been extraordinarily pivotal and successful for IBM to build what they now have, which is really the most comprehensive portfolio of fit-to-purpose data platform. So in other words all those acquisitions prepared IBM to duke it out now with their primary competitors in this new field, which are Microsoft, who's newly resurgent, and Amazon Web Services. In other words, the two Seattle vendors, Seattle has come on strong, in a way that almost Seattle now in big data in the cloud is eclipsing Silicon Valley, in terms of where you know ... It's like the locus of innovation and really of customer adoption in the cloud space. >> Quite amazing. Well Google still hanging in there. >> Oh yeah. >> Alright, Jim. Really a pleasure working with you today. Thanks so much. Really appreciate it. >> Thanks for bringing me on your team. >> And Munich crew, you guys did a great job. Really well done. Chuck, Alex, Patrick wherever he is, and our great makeup lady. Thanks a lot. Everybody back home. We're out. This is Fast Track Your Data. Go to IBMgo.com for all the replays. Youtube.com/SiliconANGLE for all the shows. TheCUBE.net is where we tell you where theCUBE's going to be. Go to wikibon.com for all the research. Thanks for watching everybody. This is Dave Vellante with Jim Kobielus. We're out.

>> Narrator: Live from Las Vegas! It's the Cube covering Interconnect 2017, brought to you by IBM. >> Okay, welcome back everyone. We are live in Las Vegas at IBM Interconnect 2017, IBM's cloud and now data show. I'm John Furrier with my co-host Dave Vellante. This is the Cube. Our next guest is Derek Schoettle, the general manager of Watson Data Platform, and Adam Kocoloski who's the CTO of the Watson Data Platform. Guys, welcome to the Cube. Good to see you again Derek. Great to see you, welcome Adam! >> Thanks, John. >> So, obviously the data was a big part of the theme. You saw Chris Moody from Twitter up there, obviously, they have a ton of data. I like to joke about they have a really active user right now in the President of the United States. >> Daily State of the Union, I think, was the one take away. >> Daily State of the Union. But this is the conversation that's happening in all over IT, and enterprise, and cloud, both public and enterprise, is the data conversation in context to cloud. Super relevant right now, and there's architecturals at play, it's app, it impacts app developers, it impacts architectures. And that's the Holy Grail, the so-called app data layer or cloud data layer. What's your vision, guys, on this? Derek, I'll start with you, your vision on this data opportunity. How does IBM approach it? And what's different from, or could be different from the competitors? >> Yeah, I know, one, it's an exciting time. We were just chatting about before we went live is, there's so much change taking place in and around data, right? It used to be it's the natural currency, it's everything everyone is talking about. The reality is, it's changing business models, right? It introduces a whole new set of discussions when you introduce cloud, self-service and open source. So, when we step back and think about how we can differentiate, how we can make IBM's offer to clients and the broader market interesting, is shift to a platform strategy where it says, we have instead of discreet compossible services that act independent of one another that are not, I'll say, self-aware, shift into a platform where you have common governance, you have common management, and you have really a collaborative by design approach where data is at the epicenter. Data is what starts every conversation whether you're on the app dev side, whether you are a data scientist, someone who's, you know, at the edge of discovery. And cloud's what's enabling that, self-service is what's enabling that and operationalize is what we do. I mean, we spend our days thinking about and then operationalizing feature, function, and then performance for a lot of different workloads. 'Cause it used to be, I think the, I was at Vertica, right? So that was the introduction of volume, variety, and velocity, right? Now, with the introduction of AI and cognitive, it's really about taking any and all and rationalizing it. And any and all meaning sitting within your corporate structure, as well as what's more broadly in the internet, out available within social media, right? That to me is the shift that's taking place. It's all companies are realizing they made a lot of investments, they have a lot of data, and they're not taking advantage of it. And we see that the big shift is... People are saying data scientist, what we think about is the merging of data and science. You think of science as cognitive and AI, right? That's a small population that really understands and can take advantage of. You have a whole big market that's out there in traditional data and analytics. Our platform is about merging those two. It's really about merging those experiences so everyone takes advantage of the benefits of data and science. >> What's the conversations that you are having, Derek, with customers? Because I think that's, there's a lot of bells going off into the CXO or even practitioners when you hear about machine learning, you hear AI, cognitive, autonomous vehicles, sensor networks. Obviously that's, the alarms are going off, like, I'd better get my act together. So, how do they pull that off? How do your customers pull off making that happen? Because now you got to bring in to be cloud ready, you have all these decoupled component parts. >> Yeah. >> John: You got to operate them in the cloud and you got to kind of have an on-prem component that's hybrid. What are the conversations that you are having with customers in how they're pulling this off? >> Yeah so, I'll cover the first piece, and I know Adam is spending certainly this week and a lot of time as well with clients on this topic. You know, the first part of the discussion is do you believe that the cloud can help you? Most folks are saying, "Yes, we believe it can help". Second piece is, how do I take advantage of emerging technologies that are moving at a rate and pace that perhaps my skills, my existing IT architecture, and my business model can't fully kind of, grasp, if not take advantage of? So, what we've introduced is a methodology, a data first method, which literally is a, it sounds simple, but at the end of the day, it is a common, uniform, agile way for us as IBM to engage with partners and clients that literally starts with the discovery workshop that says how does data inform your business? It's not static reporting anymore, it's what is the data that's sitting within your organization? You heard it from James at PlayFab. Data is changing the way people build in games today, thinking about how to enrich games, so on and so forth. Data First Method is what we've introduced, so you'll see going forward, IBM will sell Data First, we will engage Data First. So, any conversation with someone who says, "How do I take advantage of AI, "or machine learning, "or data science experience?". Well, let's step back for a second and talk about data. 'Cause 30 years ago, 20, that's how every conversation started. You get on a whiteboard, you design a schema, you talk about the relationships. That's how it started, and we're kind of cycling back to that, right? We got to put data first. >> So, Adam, the geeks are always arguing speeds, "I got a Hadoop cluster here, "I got this over here.". I mean, there's a lot of variety and diversity in terms of how people can manage either databases, and middleware or what not, right? So, how do you see the data first? How does it play out architecturally? And how does that play out for the solution? >> I think one of the big advantages we have in the world of the cloud platform is this opportunity to, on the one hand, use more a broader variety of compossible services, but also be able to take different parts of the business that were historically a little bit more separated from one another and bring them together. So you look at a Hadoop-flavored data leg on premises. It's a good area to do discovery, a good area to do exploration. But what clients really care about time and time again, a common refrain is the operationalization of the analytics, of the machine learning models. How do I take this insight that my data science team has discovered, and have it really influence a business process or incorporate it into an application? And in the on-premises architecture, that's often times quite a challenge. In the world of the cloud platform and the Watson data platform, we have an opportunity to be a little bit closer to things like the world of kubernetes which are really ideally suited for deploying and scaling microservices and APIs in a cloud-native, fault-tolerant, reliable fashion, right? So, you're seeing us take that menu of composable services in the cloud platform, and treat the data platform as one such composition. An opinionated way to put together this menu of services specifically to help data professionals collaborate, and drive the business forward. >> So, when you guys announced the Watson Data Platform, I think you called it Data Works, then changed the name, about five, maybe six months ago you messaged that 80% of, you know, data professionals' time is spent wrangling data, not enough time doing the fun stuff. And the premise was you coming up with a platform for collaboration that sort of integrates those different roles as well as, as you pointed out just now, allows you to operationalize analytics. Okay, so we're five months in, six months in, what kind of proof points do you have? Have you seen it? I mean, some people were skeptical saying, "Okay, well, it's IBM, "they've put a nice wrapper on this thing, "pulling in some different legacy components, "and you know, nice name." Okay, so, what do you say to that? And what evidence do you have that what you said is going to come true is actually coming true? >> You're going to do tech and I can do customer? >> Yeah, go for customer first. >> Yeah, so what we've seen is if you think about why we ended up at a platform. So, if you roll the tape back to when Cloudant got acquired in 2014, the journey that we were on was everyone was building rich applications, they wanted to be smarter, they wanted to understand what that exhaust was coming off. >> Right. >> Derek: And they wanted to add different ingredients to it. So, instead of a do-it-yourself kit that is a bunch of proprietary interoperability issues that's a ton of expense and inefficiency, and can't take advantage of the cloud, we decided, in very much of then our path towards, let's build a platform that allows you to easily ingest, govern, curate, and then, I'll say present and deploy. So, starting in actually June, and thhis started first with Spark. We made a huge bet on Spark 'cause we believed that to be kind of the operational operating system, if you will, for an analytic fabric. So, it started in Spark. Then, when we announced the Watson Data Platform in October it was, here's how we're going to take our heritage run governance, our heritage run traditional structured, non-structured data repositories, and here's how we're going to take visualization and distribution of data. So, that then next went into how we bring it to market? That's Data First. So, we've been working with large insurance companies, large financial services companies, retailers, gaming companies, and the net that we see is three things. First is, yes everyone agrees the platform is the right place to go. It's where do we get started? How do I take my existing investment and take advantage of this platform? And that, invariably, is I'm going to build a net new application whether it be Watson Conversations, so that runs into Watson Data Platform. We want to ingest data, but we want that data to be resident on-prem, we want it to be native to the cloud, and so we're going to work through the architectural change to adopt that. Another great example is we want to start with just an analytic application because we are already hosting with you a mobile app. Well, we're going to run it into your analytic fabric using dashDB, and dashDB works with Watson Analytics and we're going to build an application that's resident. The really creative and compelling piece here, back to your comment on IBM is, it's really hard to buy things from this company historically. Buying things from IBM is not easy, so we built a platform, we built the methodology to help you understand how to take advantage of it, and now we have a subscription, the Bluemix subscription is which you can come in and draw down those services, be it an object store, be it a sequel data store, be the visualization layer. >> John: Opposability basically. >> Yeah, but in a common governed framework. The big takeaway is, and I'll pass to Adam, governance and security and operationalizing the platform is what we can bring to bear. 'Cause we're bringing Open Source, we're bringing proprietary technologies, but if it's done independent, it doesn't really deliver on the promise of a platform. >> I will say that architecturally, that's incredibly liberating to know that there is this one common mind model. >> It's also highly requested by customers. That's what they want. >> Derek: That's what they want. It's the path to get there that I think is, we're at that intersection right now, it's crossing the chasm. >> John: So, what's liberating? Give us good-- >> Oh, just the fact that you know that if there's a common access control layer under the hood, if there's a common governance layer under the hood, that you don't have to compromise and come up with an alternative proposition for taking some capability, maybe deploying a model to a scoring engine. You can have the one purpose filled scoring engine and know that I can call that in on demand from discovery phase to go to production and I don't have to sort of engage in another separate mind conversation or separate entitlement conversation or a separate enabling conversation. This catalog is allowing it to work together. >> That to me from a team sport perspective is that the steps you have to take. So, think of ETL. ETL really in a modern real time, like getting away from batch and go into real time, that's just flow. So, the skill set and the ownership of the infrastructure associated with that is evolved, especially in cloud where that's just a dynamic where it's going to be a team deciding here's the data I want, here's how I want to enrich it, here's how I want to govern and curate it. >> It's a team sport. I love that. We were just at the Strata Hadoop. We had our big data SV event and the collision between batch and real time, they are not mutually exclusive and some people just made bets on batch and forgot real time. And they have real time people who don't do batch. So, you kind of see that coming together. >> Adam: Conversion. >> So, the question, Adam, for you is that, with the world kind of moving in that direction, how do you rationalize so the customer who's saying, "Hey, I'm cloud native but I also have a hybrid here "and I want to be cloud native purely "on this net new applications". So, there's a conversation happening. I call it the dev ops of data which is like data ops. Hey, I'm a programmer. I just want data as code. I just don't want to get in the weeds of setting up a data warehouse, and prepping an ETL, all that batch stuff that someone else does. I'm writing some software. I want data native to my app, but I don't want to go in and do the wrangling. I don't want to go out. I just want stuff to magically work. How do you tackle that premise? >> I mean, I think the dev ops of data piece is certainly a topic we're going to be hearing a lot more about over the next coming six months, in a year. I think the reason for that is precisely because this earlier topic of operationalization. You've got lots of people building up, budding data science teams and so on. And the first thing they're going to do is be working in the discovery area. They won't be in the world of pushing things to production. When they do, it's going to become more important that the folks who truly understand the details of the algorithm are close enough to the deployed assets, so that they can understand how this model is behaving over time. So that they can understand new data quality issues that might have cropped up and get close to that without obviously sort of breaking the separation duties that are important for a production system. So, I think, that is one part of the data ops conversation that hasn't yet been worked out. It's going to be a real opportunity for folks who-- >> That's an emerging area. You agree, right? >> It's a cultural shift too. I mean that is a re-thinking of, because most companies keep data in steel pipes. They're highly regulated. Their rules, the personalities that own them so to speak. The proposition that we've been on and every client asks for is how do I create a common fabric that gives access to people, that is governed and curated so you can always give a shopping experience. People that work with data do not want to talk about and say this : "How long does it take to stand up a server? "When can I get the data stood up in the staging area "so I can actually access it?" That's over. >> It's interesting, we're doing some Wikibon research on this, and this is the point where people look at value extraction of the data so they tend to, it's kind of like if you're a hammer, everything looks like a nail. So if you're in IT, it's infrastructure. If you are on the business line, it's the apps. So, you're seeing the shift where apps is value creating the value, but the infrastructure is more elastic, more compossible so it's enablement by itself so that's interesting. So, your thoughts on that, guys? Where is that value of the data coming from most, right now? Is it the apps? Is the infrastructure still evolving? The hybrid not-- >> We think there's a value model here. There is certainly elements of the data pipeline that are purely operational, reporting base and things like that, which drive value on their own. But we also recognize that it's new uses of data and new business processes that are primarily driven by applications, driven by conversational interfaces, driven by these sort of emerging paradigms. And one of our goals in the data platform is to ensure that clients can move along that curve more aggressively. >> How are people getting started with the Watson Data Platform? Do they go jumping all in? Is there a community edition, you can try it before you buy it kind of thing? >> Yeah, so you're signing up in Bluemix. You have access to a set of services around the platform. You have a 30-day window where you can try everything included within it, and then at some point you got to commit to a credit card or you got to commit a 12-month term agreement. I think in parallel, we see a lot of other companies that end up blasting in size challenge for IBM. We have a lot of clients. We have got a lot of clients that we are working with today in traditional architects and infrastructure, helping them through a methodology, helping them with the right skills. That is a more traditional, hey, come in and try an analytic workload on the platform. We'll give the skills. We'll help do the enablement and then we're off and running. I think the big difference is whether or not clients are paying for and they are willing to pay for it. 'Cause we are helping them get to this new model. We're helping them get to the platform, and I think the big thing we're working through is how do we get to velocity? I think when you look at these workloads that are happening. The reason they're happening is now data is not just in some dark corner. With AI, the machine learning is always on. So, there's a lot of different ways in which you can unleash that, that then, how do you take advantage of it? And that is a cultural shift. It's re-thinking business models, it's re-thinking how you got skills deployed which is incredibly exciting for us, and I think the market in general. I think back to how AI is cast in many cases as the robots are going to rule the world. There's a lot of good that can come from exposing vast amounts of data to AI and to frameworks where you can get a lot of value out of it. From how to better position products to how to, better design of medicines to fulfillment chains in countries that need help. >> So, guys, in the last minute that we have I want you to take a minute to either together or one of you guys talk about how IBM is helping solve what seems to be the number one question we get on the Cube where I get asked, hey, how do you help me build a hybrid architecture. I have more data-rich workloads coming on board now. Either I have some heavy data rich workloads that are run on-prem, I got more cloud action coming, I got IOT and I'm investing in data science. So, how do you guys specifically help me build a hybrid cloud architecture that's going to fuel and support data-rich workloads and propel my data science operation. >> Yeah, so, I'll take the basics for me. It is the Data First method. It is dashDB, which is an extensible on-prem hybrid in the cloud so that the common analytic fabric. There's Data Connect, which is our ability to move data batch continuous into different end states in the cloud, and then there's data science experience. So data science experience is our offering that brings together community, it brings together content, it brings together various tooling for the data scientist or data engineers. And I think the other piece of this is, we have something called solutions assurance. So we're literally designing patterns that we stand up in our own environments that reflect what we see on Premise and what we see workloads going into the cloud with, and stamping that as hybrid architectures that are repeatable, and we remove risk, the operational risk. But the reality is (mumbles) is, clients have to make sacrifices in getting to the cloud. You have to deprecate, you have to rethink. And that's where some of the smoothing of those rough edges come into the discipline of us saying, here's a supported architecture, here's the destination that you're going to, and we're going to have to work together to get there. Which is the fun part, I mean, that's what we're all in this for, is getting the outcomes. >> I think the key is not to pretend that these environments are completely identical to one another. There are things that the public cloud is uniquely well suited for. So let's make sure that those kinds of use cases are really nailed there, right? And then there are other cases where you're dealing with mainframe systems running critical business processes, and you want to be able to infuse that process with some analytics. So you have to look at the use case. Maybe it's training a machine learning model in the cloud, being able to export that model and run it-- >> So use proven solutions and be prepared to be handling new ones coming onboard. Alright, Derek Schoettle, general manager, and Adam Kocoloski, the CTO, the leaders at IBM Watson Data Group, IMB Watson Platform. This is The Cube, back with more live coverage after this short break.

>> Announcer: Live from New York, it's theCUBE, covering the IBM Machine Learning Launch Event, brought to you by IBM. Now, here are your hosts, Dave Vellante and Stu Miniman. >> Welcome back to New York City, everybody. We're here at the Waldorf Astoria covering the IBM Machine Learning Launch Event, bringing machine learning to the IBM Z. Bryan Smith is here, he's the vice president of R&D and the CTO of Rocket Software, powering the path to digital transformation. Bryan, welcome to theCUBE, thanks for coming on. >> Thanks for having me. >> So, Rocket Software, Waltham, Mass. based, close to where we are, but a lot of people don't know about Rocket, so pretty large company, give us the background. >> It's been around for, this'll be our 27th year. Private company, we've been a partner of IBM's for the last 23 years. Almost all of that is in the mainframe space, or we focused on the mainframe space, I'll say. We have 1,300 employees, we call ourselves Rocketeers. It's spread around the world. We're really an R&D focused company. More than half the company is engineering, and it's spread across the world on every continent and most major countries. >> You're esstenially OEM-ing your tools as it were. Is that right, no direct sales force? >> About half, there are different lenses to look at this, but about half of our go-to-market is through IBM with IBM-labeled, IBM-branded products. We've always been, for the side of products, we've always been the R&D behind the products. The partnership, though, has really grown. It's more than just an R&D partnership now, now we're doing co-marketing, we're even doing some joint selling to serve IBM mainframe customers. The partnership has really grown over these last 23 years from just being the guys who write the code to doing much more. >> Okay, so how do you fit in this announcement. Machine learning on Z, where does Rocket fit? >> Part of the announcement today is a very important piece of technology that we developed. We call it data virtualization. Data virtualization is really enabling customers to open their mainframe to allow the data to be used in ways that it was never designed to be used. You might have these data structures that were designed 10, 20, even 30 years ago that were designed for a very specific application, but today they want to use it in a very different way, and so, the traditional path is to take that data and copy it, to ETL it someplace else they can get some new use or to build some new application. What data virtualization allows you to do is to leave that data in place but access it using APIs that developers want to use today. They want to use JSON access, for example, or they want to use SQL access. But they want to be able to do things like join across IMS, DB2, and VSAM all with a single query using an SQL statement. We can do that relational databases and non-relational databases. It gets us out of this mode of having to copy data into some other data store through this ETL process, access the data in place, we call it moving the applications or the analytics to the data versus moving the data to the analytics or to the applications. >> Okay, so in this specific case, and I have said several times today, as Stu has heard me, two years ago IBM had a big theme around the z13 bringing analytics and transactions together, this sort of extends that. Great, I've got this transaction data that lives behind a firewall somewhere. Why the mainframe, why now? >> Well, I would pull back to where I said where we see more companies and organizations wanting to move applications and analytics closer to the data. The data in many of these large companies, that core business-critical data is on the mainframe, and so, being able to do more real time analytics without having to look at old data is really important. There's this term data gravity. I love the visual that presents in my mind that you have these different masses, these different planets if you will, and the biggest, massivest planet in that solar system really is the data, and so, it's pulling the smaller satellites if you will into this planet or this star by way of gravity because data is, data's a new currency, data is what the companies are running on. We're helping in this announcement with being able to unlock and open up all mainframe data sources, even some non-mainframe data sources, and using things like Spark that's running on the platform, that's running on z/OS to access that data directly without having to write any special programming or any special code to get to all their data. >> And the preferred place to run all that data is on the mainframe obviously if you're a mainframe customer. One of the questions I guess people have is, okay, I get that, it's the transaction data that I'm getting access to, but if I'm bringing transaction and analytic data together a lot of times that analytic data might be in social media, it might be somewhere else not on the mainframe. How do envision customers dealing with that? Do you have tooling them to do that? >> We do, so this data virtualization solution that I'm talking about is one that is mainframe resident, but it can also access other data sources. It can access DB2 on Linux Windows, it can access Informix, it can access Cloudant, it can access Hadoop through IBM's BigInsights. Other feeds like Twitter, like other social media, it can pull that in. The case where you'd want to do that is where you're trying to take that data and integrate it with a massive amount of mainframe data. It's going to be much more highly performant by pulling this other small amount of data into, next to that core business data. >> I get the performance and I get the security of the mainframe, I like those two things, but what about the economics? >> Couple of things. One, IBM when they ported Spark to z/OS, they did it the right way. They leveraged the architecture, it wasn't just a simple port of recompiling a bunch of open source code from Apache, it was rewriting it to be highly performant on the Z architecture, taking advantage of specialty engines. We've done the same with the data virtualization component that goes along with that Spark on z/OS offering that also leverages the architecture. We actually have different binaries that we load depending on which architecture of the machine that we're running on, whether it be a z9, an EC12, or the big granddaddy of a z13. >> Bryan, can you speak the developers? I think about, you're talking about all this mobile and Spark and everything like that. There's got to be certain developers that are like, "Oh my gosh, there's mainframe stuff. "I don't know anything about that." How do you help bridge that gap between where it lives in the tools that they're using? >> The best example is talking about embracing this API economy. And so, developers really don't care where the stuff is at, they just want it to be easy to get to. They don't have to code up some specific interface or language to get to different types of data, right? IBM's done a great job with the z/OS Connect in opening up the mainframe to the API economy with ReSTful interfaces, and so with z/OS Connect combined with Rocket data virtualization, you can come through that z/OS Connect same path using all those same ReSTful interfaces pushing those APIs out to tools like Swagger, which the developers want to use, and not only can you get to the applications through z/OS Connect, but we're a service provider to z/OS Connect allowing them to also get to every piece of data using those same ReSTful APIs. >> If I heard you correctly, the developer doesn't need to even worry about that it's on mainframe or speak mainframe or anything like that, right? >> The goal is that they never do. That they simply see in their tool-set, again like Swagger, that they have data as well as different services that they can invoke using these very straightforward, simple ReSTful APIs. >> Can you speak to the customers you've talked to? You know, there's certain people out in the industry, I've had this conversation for a few years at IBM shows is there's some part of the market that are like, oh, well, the mainframe is this dusty old box sitting in a corner with nothing new, and my experience has been the containers and cool streaming and everything like that, oh well, you know, mainframe did virtualization and Linux and all these things really early, decades ago and is keeping up with a lot of these trends with these new type of technologies. What do you find in the customers that, how much are they driving forward on new technologies, looking for that new technology and being able to leverage the assets that they have? >> You asked a lot of questions there. The types of customers certainly financial and insurance are the big two, but that doesn't mean that we're limited and not going after retail and helping governments and manufacturing customers as well. What I find is talking with them that there's the folks who get it and the folks who don't, and the folks who get it are the ones who are saying, "Well, I want to be able "to embrace these new technologies," and they're taking things like open source, they're looking at Spark, for example, they're looking at Anaconda. Last week, we just announced at the Anaconda Conference, we stepped on stage with Continuum, IBM, and we, Rocket, stood up there talking about this partnership that we formed to create this ecosystem because the development world changes very, very rapidly. For a while, all the rage was JDBC, or all the rage was component broker, and so today it's Spark and Anaconda are really in the forefront of developers' minds. We're constantly moving to keep up with developers because that's where the action's happening. Again, they don't care where the data is housed as long as you can open that up. We've been playing with this concept that came up from some research firm called two-speed IT where you have maybe your core business that has been running for years, and it's designed to really be slow-moving, very high quality, it keeps everything running today, but they want to embrace some of their new technologies, they want to be able to roll out a brand-new app, and they want to be able to update that multiple times a week. And so, this two-speed IT says, you're kind of breaking 'em off into two separate teams. You don't have to take your existing infrastructure team and say, "You must embrace every Agile "and every DevOps type of methodology." What we're seeing customers be successful with is this two-speed IT where you can fracture these two, and now you need to create some nice integration between those two teams, so things like data virtualization really help with that. It opens up and allows the development teams to very quickly access those assets on the mainframe in this case while allowing those developers to very quickly crank out an application where quality is not that important, where being very quick to respond and doing lots of AB testing with customers is really critical. >> Waterfall still has its place. As a company that predominately, or maybe even exclusively is involved in mainframe, I'm struck by, it must've been 2008, 2009, Paul Maritz comes in and he says VMWare our vision is to build the software mainframe. And of course the world said, "Ah, that's, mainframe's dead," we've been hearing that forever. In many respects, I accredit the VMWare, they built sort of a form of software mainframe, but now you hear a lot of talk, Stu, about going back to bare metal. You don't hear that talk on the mainframe. Everything's virtualized, right, so it's kind of interesting to see, and IBM uses the language of private cloud. The mainframe's, we're joking, the original private cloud. My question is you're strategy as a company has been always focused on the mainframe and going forward I presume it's going to continue to do that. What's your outlook for that platform? >> We're not exclusively by the mainframe, by the way. We're not, we have a good mix. >> Okay, it's overstating that, then. It's half and half or whatever. You don't talk about it, 'cause you're a private company. >> Maybe a little more than half is mainframe-focused. >> Dave: Significant. >> It is significant. >> You've got a large of proportion of the company on mainframe, z/OS. >> So we're bullish on the mainframe. We continue to invest more every year. We invest, we increase our investment every year, and so in a software company, your investment is primarily people. We increase that by double digits every year. We have license revenue increases in the double digits every year. I don't know many other mainframe-based software companies that have that. But I think that comes back to the partnership that we have with IBM because we are more than just a technology partner. We work on strategic projects with IBM. IBM will oftentimes stand up and say Rocket is a strategic partner that works with us on hard problem-solving customers issues every day. We're bullish, we're investing more all the time. We're not backing away, we're not decreasing our interest or our bets on the mainframe. If anything, we're increasing them at a faster rate than we have in the past 10 years. >> And this trend of bringing analytics and transactions together is a huge mega-trend, I mean, why not do it on the mainframe? If the economics are there, which you're arguing that in many use cases they are, because of the value component as well, then the future looks pretty reasonable, wouldn't you say? >> I'd say it's very, very bright. At the Anaconda Conference last week, I was coming up with an analogy for these folks. It's just a bunch of data scientists, right, and during most of the breaks and the receptions, they were just asking questions, "Well, what is a mainframe? "I didn't know that we still had 'em, "and what do they do?" So it was fun to educate them on that. But I was trying to show them an analogy with data warehousing where, say that in the mid-'90s it was perfectly acceptable to have a separate data warehouse separate from your transaction system. You would copy all this data over into the data warehouse. That was the model, right, and then slowly it became more important that the analytics or the BI against that data warehouse was looking at more real time data. So then it became more efficiencies and how do we replicate this faster, and how do we get closer to, not looking at week-old data but day-old data? And so, I explained that to them and said the days of being able to do analytics against old data that's copied are going away. ETL, we're also bullish to say that ETL is dead. ETL's future is very bleak. There's no place for it. It had its time, but now it's done because with data virtualization you can access that data in place. I was telling these folks as they're talking about, these data scientists, as they're talking about how they look at their models, their first step is always ETL. And so I told them this story, I said ETL is dead, and they just look at me kind of strange. >> Dave: Now the first step is load. >> Yes, there you go, right, load it in there. But having access from these platforms directly to that data, you don't have to worry about any type of a delay. >> What you described, though, is still common architecture where you've got, let's say, a Z mainframe, it's got an InfiniBand pipe to some exit data warehouse or something like that, and so, IBM's vision was, okay, we can collapse that, we can simplify that, consolidate it. SAP with HANA has a similar vision, we can do that. I'm sure Oracle's got their vision. What gives you confidence in IBM's approach and legs going forward? >> Probably due to the advances that we see in z/OS itself where handling mixed workloads, which it's just been doing for many of the 50 years that it's been around, being able to prioritize different workloads, not only just at the CPU dispatching, but also at the memory usage, also at the IO, all the way down through the channel to the actual device. You don't see other operating systems that have that level of granularity for managing mixed workloads. >> In the security component, that's what to me is unique about this so-called private cloud, and I say, I was using that software mainframe example from VMWare in the past, and it got a good portion of the way there, but it couldn't get that last mile, which is, any workload, any application with the performance and security that you would expect. It's just never quite got there. I don't know if the pendulum is swinging, I don't know if that's the accurate way to say it, but it's certainly stabilized, wouldn't you say? >> There's certainly new eyes being opened every day to saying, wait a minute, I could do something different here. Muscle memory doesn't have to guide me in doing business the way I have been doing it before, and that's this muscle memory I'm talking about of this ETL piece. >> Right, well, and a large number of workloads in mainframe are running Linux, right, you got Anaconda, Spark, all these modern tools. The question you asked about developers was right on. If it's independent or transparent to developers, then who cares, that's the key. That's the key lever this day and age is the developer community. You know it well. >> That's right. Give 'em what they want. They're the customers, they're the infrastructure that's being built. >> Bryan, we'll give you the last word, bumper sticker on the event, Rocket Software, your partnership, whatever you choose. >> We're excited to be here, it's an exciting day to talk about machine learning on z/OS. I say we're bullish on the mainframe, we are, we're especially bullish on z/OS, and that's what this even today is all about. That's where the data is, that's where we need the analytics running, that's where we need the machine learning running, that's where we need to get the developers to access the data live. >> Excellent, Bryan, thanks very much for coming to theCUBE. >> Bryan: Thank you. >> And keep right there, everybody. We'll be back with our next guest. This is theCUBE, we're live from New York City. Be right back. (electronic keyboard music)

>> Voiceover: Live from New York, it's The Cube, covering Big Data New York City 2016. Brought to you by headline sponsors, Cisco, IBM, Nvidia, and our ecosystem sponsors. Now, here are your hosts, Dave Vellante and George Gilbert. >> Welcome back to New York City, everybody. Nenshad Bardoliwalla is here, he's the co-founder and chief product officer at Paxata, a company that, three years ago, I want to say three years ago, came out of stealth on The Cube. >> October 27, 2013. >> Right, and we were at the Warwick Hotel across the street from the Hilton. Yeah, Prakash came on The Cube and came out of stealth. Welcome back. >> Thank you very much. >> Great to see you guys. Taking the world by storm. >> Great to be here, and of course, Prakash sends his apologies. He couldn't be here so he sent his stunt double. (Dave and George laugh) >> Great, so give us the update. What's the latest? >> So there are a lot of great things going on in our space. The thing that we announced here at the show is what we're calling Paxata Connect, OK? We are moving just in the same way that we created the self-service data preparation category, and now there are 50 companies that claim they do self-service data prep. We are moving the industry to the next phase of what we are calling our business information platform. Paxata Connect is one of the first major milestones in getting to that vision of the business information platform. What Paxata Connect allows our customers to do is, number one, to have visual, completely declarative, point-and-click browsing access to a variety of different data sources in the enterprise. For example, we support, we are the only company that we know of that supports connecting to multiple, simultaneous, different Hadoop distributions in one system. So a Paxata customer can connect to MapR, they can connect to Hortonworks, they can connect to Cloudera, and they can federate across all of them, which is a very powerful aspect of the system. >> And part of this involves, when you say declarative, it means you don't have to write a program to retrieve the data. >> Exactly right. Exactly right. >> Is this going into HTFS, into Hive, or? >> Yes it is. In fact, so Hadoop is one part of, this multi-source Hadoop capability is one part of Paxata Connect. The second is, as we've moved into this information platform world, our customers are telling us they want read-write access to more than just Hadoop. Hadoop is obviously a very important part, but we're actually supporting no-sequel data sources like Cloudant, Mongo DB, we're supporting read and write, we're supporting, for the first time, relational databases, we already supported read, but now we actually support write to relational databases. So Paxata is really becoming kind of this fabric, a business-centric information fabric, that allows people to move data from anywhere to any destination, and transform it, profile it, explore it along the way. >> Excellent. Let's get into some of the use cases. >> Yeah, tell us where the banks are. The sense at the conference is that everyone sort of got their data lakes to some extent up and running. Now where are they pushing to go next? >> Sure, that's an excellent question. So we have really focused on the enterprise segment, as you know. So the customers that are working with Paxata from an industry perspective, banking is, of course, a very important one, we were really proud to share the stage yesterday with both Citi and Standard Chartered Bank, two of our flagship banking customers. But Paxata is also heavily used in the United States government, in the intelligence community, I won't say any more about that. It's used heavily in retail and consumer products, it's used heavily in the high-tech space, it's used heavily by data service providers, that is, companies whose entire business is based on data. But to answer your question specifically, what's happening in the data lake world is that a lot of folks, the early adopters, have jumped onto the data lake bandwagon. So they're pouring terabytes and petabytes of data into the data lake. And then the next question the business asks is, OK, now what? Where's the data, right? One of the simplest use cases, but actually one that's very pervasive for our customers, is they say, "Look, we don't even know, "our business people, they don't even know "what's in Hadoop right now." And by the way, I will also say that the data lake is not just Hadoop, but Amazon S3 is also serving as a data lake. The capabilities inside Microsoft's cloud are also serving as a data lake. Even the notion of a data lake is becoming this sort of polymorphic distributed thing. So what they do is, they want to be able to get what we like to say is first eyes on data. We let people with Paxata, especially with the release of Connect, to just point and click their way and to actually explore the data in all of the native systems before they even bring it in to something like Paxata. So they can actually sneak preview thousands of database tables or thousands of compressed data sets inside of Amazon S3, or thousands of data sets inside of Hadoop, and now the business people for the first time can point and click and actually see what is in the data lake in the first place. So step number one is, we have taken the approach so far in the industry of, there have been a lot of IT-driven use cases that have motivated people to go to the data lake approach. But now, we obviously want to show, all of our companies want to show business value, so tools and platforms like Paxata that sit on top of the data lake, that can federate across multiple data lakes and provide business-centric access to that information is the first significant use case pattern we're seeing. >> Just a clarification, could there be two roles where one is for slightly more technical business user exposes views summarizing, so that the ultimate end user doesn't have to see the thousands of tables? >> Absolutely, that's a great question. So when you look at self-service, if somebody wants to roll out a self-service strategy, there are multiple roles in an organization that actually need to intersect with self-service. There is a pattern in organizations where people say, "We want our people to get access to all the data." Of course it's governed, they have to have the right passwords and SSO and all that, but they're the companies who say, yes, the users really need to be able to see all of the data across these different tables. But there's a different role, who also uses Paxata extensively, who are the curators, right? These are the people who say, look, I'm going to provision the raw data, provide the views, provide even some normalization or transformation, and then land that data back into another layer, as people call the data relay, they go from layer zero to layer one to layer two, they're different directory structures, but the point is, there's a natural processing frame that they're going through with their data, and then from the curated data that's created by the data stewards, then the analysts can go pick it up. >> One of the other big challenges that our research is showing, that chief data officers express, is that they get this data in the data lake. So they've got the data sources, you're providing access to it, the other piece is they want to trust that data. There's obviously a governance piece, but then there's a data quality piece, maybe you could talk about that? >> Absolutely. So use case number one is about access. The second reason that people are not so -- So, why are people doing data prep in the first place? They are trying to make information-driven decisions that actually help move their business forward. So if you look at researchers from firms like Forrester, they'll say there are two reasons that slow down the latency of going from raw data to decision. Number one is access to data. That's the use case we just talked about. Number two is the trustworthiness of data. Our approach is very different on that. Once people actually can find the data that they're looking for, the big paradigm shift in the self-service world is that, instead of trying to process data based on transforming the metadata attributes, like I'm going to draw on a work flow diagram, bring in this table, aggregate with this operator, then split it this way, filter it, which is the classic ETL paradigm. The, I don't want to say profound, but maybe the very obvious thing we did was to say, "What if people could actually look at the data in the first place --" >> And sort of program it by example? >> We can tell, that's right. Because our eyes can tell us, our brains help us to say, we can immediately look at a data set, right? You look at an age column, let's say. There are values in the age column of 150 years. Maybe 20 years from now there may be someone who, on Earth, lives to 150 years. But pretty much -- >> Highly unlikely. >> The customers at the banks you work with are not 150 years old, right? So just being able to look at the data, to get to the point that you're asking, quality is about data being fit for a specific purpose. In order for data to be fit for a specific purpose, the person who needs the data needs to make the decision about what is quality data. Both of you may have access to the same transactional data, raw data, that the IT team has landed in the Hadoop cluster. But now you pull it up for one use case, you pull it up for another use case, and because your needs are different, what constitutes quality to you and where you want to make the investment is going to be very different. So by putting the power of that capability into the hands of the person who actually knows what they want, that is how we are actually able to change the paradigm and really compress the latency from "Here's my raw data" to "Here's the decision I want to make on that data." >> Let me ask, it sounds like, having put all of the self-service capabilities together, you've democratized access to this data. Now, what happens in terms of governance, or more importantly, just trust, when the pipeline, you know, has to go beyond where you're working on it, to some of the analytics or some of the basic ingest? To say, "I know this data came from here "and it's going there." >> That's right, how do we verify the fidelity of these data sources? It's a fantastic question. So, in my career, having worked in BI for a couple of decades, I know I look much younger but it actually has been a couple of decades. Remember, the camera adds about 15 pounds, for those of you watching at home. (Dave and George laugh) >> George: But you've lost already. >> Thank you very much. >> So you've lost net 30. (Nenshad laughs) >> Or maybe I'm back to where I'm supposed to be. What I've seen as the two models of governance in the enterprise when it comes to analytics and information management, right? There's model one, which is, we're going to build an enterprise data warehouse, we're going to know all the possible questions people are going to ask in advance, we're going to preprogram the ETL routines, we're going to put something like a MicroStrategy or BusinessObjects, an enterprise-reporting factory tool. Then you spend 10 million dollars on that project, the users come in and for the first time they use the system, and they say, "Oh, I kind of want to change this, this way. "I want to add this calculation." It takes them about five minutes to determine that they can't do it for whatever reason, and what is the first feature they look for in the product in order to move forward? Download to Excel, right? So you invested 15 million dollars to build a download to Excel capability which they already had before. So if you lock things down too much, the point is, the end users will go around you. They've been doing it for 30 years and they'll keep doing it. Then we have model two. Model two is, Excel spreadsheet. Excel Hell, or spreadmarts. There are lots of words for these things. You have a version of the data, you have a version of the data, I have a version of the data. We all started from the same transactional data, yet you're the head of sales, so suddenly your forecast looks really rosy. You're the head of finance, you really don't like what the forecast looks like. And I'm the product guy, so why am I even looking at the forecast in the first place, but somehow I got access to the data, right? These are the two polarities of the enterprise that we've worked with for the last 30 years. We wanted to find sort of a middle path, which is to say, let's give people the freedom and flexibility to be able to do the transformations they need to. If they want to add a column, let them add a column. If they want to change a calculation, let them add a a calculation. But, every single step in the process must be recorded. It must be versioned, it must be auditable. It must be governed in that way. So why the large banks and the intelligence community and the large enterprise customers are attracted to Paxata is because they have the ability to have perfect retraceability for every decision that they make. I can actually sit next to you and say, "This is why the data looks like this. "This is how this value, which started at one million, "became 1.5 million." That covers the Paxata part. But then the answer to the question you asked is, how do you even extend that to a broader ecosystem? I think that's really about some of the metadata interchange initiatives that a lot of the vendors in the Hadoop space, but also in the traditional enterprise space, have had for the last many years. If you look at something like Apache Atlas or Cloudera Navigator, they are systems designed to collect, aggregate, and connect these different metadata steps so you can see in an end-to-end flow, this is the raw data that got ingested into Hadoop. These are the transformations that the end user did in Paxata in order to make it ready for analytics. This is how it's getting consumed in something like Zoom Data, and you actually have the entire life cycle of data now actually manifested as a software asset. >> So those not, in other words, those are not just managing within the perimeter of Hadoop. They are managers of managers. >> That's right, that's right. Because the data is coming from anywhere, and it's going to anywhere. And then you can add another dimension of complexity which is, it's not just one Hadoop cluster. It's 10 Hadoop clusters. And those 10 Hadoop clusters, three of them are in Amazon. Four of them are in Microsoft. Three of them are in Google Cloud platform. How do you know what people are doing with data then? >> How is this all presented to the user? What does the user see? >> Great question. The trick to all of this, of self service, first you have to know very clearly, who is the person you are trying to serve? What are their technical skills and capabilities, and how can you get them productive as fast as possible? When we created this category, our key notion was that we were going to go after analysts. Now, that is a very generic term, right? Because we are all, in some sense, analysts in our day-to-day lives. But in Paxata, a business analyst, in an enterprise organizational context, is somebody that has the ability to use Microsoft Excel, they have to have that skill or they won't be successful with today's Paxata. They have to know what a VLOOKUP is, because a VLOOKUP is a way to actually pull data from a second data source into one. We would all know that as a join or a lookup. And the third thing is, they have to know what a pivot table is and know how a pivot table works. Because the key insight we had is that, of the hundreds of millions of analysts, people who use Excel on a day-to-day basis, a lot of their work is data prep. But Excel, being an amazing generic tool, is actually quite bad for doing data prep. So the person we target, when I go to a customer and they say, "Are we a good candidate to use Paxata?" and we're talking to the actual person who's going to use the software, I say, "Do you know what a VLOOKUP is, yes or no? "Do you know what a pivot table is, yes or no?" If they have that skill, when they come into Paxata, we designed Paxata to be very attractive to those people. So it's completely point-and-click. It's completely visual. It's completely interactive. There's no scripting inside that whole process, because do you think the average Microsoft Excel analyst wants to script, or they want to use a proprietary wrangling language? I'm sorry, but analysts don't want to wrangle. Data scientists, the 1% of the 1%, maybe they like to wrangle, but you don't have that with the broader analyst community, and that is a much larger market opportunity that we have targeted. >> Well, very large, I mean, a lot of people are familiar with those concepts in Excel, and if they're not, they're relatively easy to learn. >> Nenshad: That's right. Excellent. All right, Nenshad, we have to leave it there. Thanks very much for coming on The Cube, appreciate it. >> Thank you very much for having me. >> Congratulations for all the success. >> Thank you. >> All right, keep it right there, everybody. We'll be back with our next guest. This is The Cube, we're live from New York City at Big Data NYC. We'll be right back. (electronic music)