>>mhm >>Hello and welcome to this cube conversation here in Palo alto California, I'm john for a year host of the cube, we're here with a great guest Jt gear, Ceo and founder and ops Hot Startup. Jt Welcome to the cube conversation. >>Hey, that sound, thanks for having me. It sounds like we know each other, we used to run into each other at meat out. So yeah, >>it's fun to talk to you because I know you're, you know, scratching the devops it from the beginning before devops was devops before infrastructure of code was infrastructure as code. All that's played out. So it's really a great ride. I know you had a good time doing it a lot of action though. If you look at devops it's kind of like this new, I won't say devops two point because it kind of cliche but you're starting to see the mature ization of companies besides the early adopters and the people who are hardcore adopting and they realize this is amazing and then they? Re platform in the cloud and they go great, let's do more and next thing, you know, they have an operations issue and they got a really kind of stabilize and then also not break anything. So this is kind of the wheelhouse of what you guys are doing in ops reminds me of no ops, no operations, you know, we don't want to have a lot of extra stuff. This is a big thing. Take a but take them in to explain the company, you're what you guys stand for and what you're all about. >>Yeah, so you know, our main focus is more on the operation side, so, you know the reason why you move to cloud or the reason why you have devops practices, you want to go fast. Um but you know when you're building cloud infrastructure, you have to make trade offs right? You have to maybe some environment, maybe you have to optimize for S L A. And maybe another workload, you have to optimize for um you know, maybe costs, right? So what we're on a mission to do is to make sure that companies are able to make the right trade offs, right? We help companies to make sure all their workload, every single resource in the cloud is aligned with the business needs, you know, so we do a lot of cool things by like, you know, bringing accountability mapping and we're close to different genes. But yeah, the end goal is, can we make sure that every single resource on data Bs is aligned with the business needs >>and they're also adding stuff. Every reinvent zillion more services get announced. So a lot, a lot of stuff going on, I gotta ask you while I got you here, what is the definition of cloud apps these days, from your standpoint and why is it important? A lot of folks are looking at this and they want to have stable operations. They love the cloud really can't deny the cloud value at all. But cloud ops has become a big topic. What is cloud apps and why is it important. >>Right? I mean, first of all, Like you just mentioned, right? Like Amazon keeps on launching more services. It's over 200. So the environment is very complex, Right? And then mm complexity within the services is uh pretty uh you really need to be the main expert for example, know everything about do So, you know, our question to us is, let's say if you find a critical issue, uh let's say you want to uh you know, enable multi AZ on your RDS for example. Uh and it's critical because you know, you're running a uh high availability workloads on AWS. How do you follow up on that right to us. Operation is how do you build a cloud backlog? How do you prioritize, how do you come together as a team to actually remediate those issues? No one is tackling that job, everyone's surfaces like, hey, here's 1000 things that are wrong with your environment. No one is focused on like how do you go from these issues to prioritization to backlog to actually coming together as a team. You know, I've been fixing some of those issues. That's that's what operation means is >>I know it's totally hard because sometimes I don't even know what's going on. I gotta ask you why, why is it harder now? Why are people, I mean I get the impression that people like looking the other way? I hope it goes the problem kind of goes away. What are the challenges? What's the big blocker from getting at the root cause or trying to solve these problems? What's the big thing that's holding people back? >>Yeah, I mean, when I first got into, you know, I t you know, I was working in data center and every time we needed a server, you know, we have to ask for approvals, right? And you finally got a server, but nowadays anyone could provision resources. And normally you have different people within the team's provisioning resources and you can have hundreds of different teams who are provisioning resources. So the complexity uh and the speed that we are, you know, provisioning resources across multiple people, it just continues to go higher and higher. So that's why uh you know, on the surface it might look that hey, this, you know, maybe the biggest instance uh is, you know, aligned with the business needs, you know, looking at the changes, it's hard to know, are those aligned with the business? They're not? So that's that's that's where the complexity and player. >>So the question I get a lot from people we talk about devops and cloud, cloud apps or cloud management or whatever kind of buzz words out there, it kind of comes down to cloud apps and cloud management seems to be the category, people focus on. How is cloud ops different then? Say the traditional cloud management and what impact does it have for customers and why should they care and what do they need an option. >>Right. So one of the things we do uh and and we do think that cloud operation is sort of an evolution from cloud management. We make sure that Every single resource 1st, first of all blondes and workload. So and you know, workload could be a group of microservices uh and then uh you know every single workload has owners like define owners who are responsible for making sure they managed budget that they're responsible for security that normally doesn't exist. Right? Cloud is this black box, you know where multiple people are provisioning resources, you know, everyone tries to sort of build sort of a structure to kind of see like what are these resources for? What are these resources for as part of onboarding to end up? So what we do, we actually, you know, analyze all your metadata. We create like 56 workloads and then we say here is a bucket where there's there, this is totally unassigned, right? And then we actually walked them through assigning different roles and also we walk them through to kinda looking under this unallocated resources and assign resources for those as well. So once you're done, every single resource has clear definition, right? Is this a compliant? Uh you know hip hop workload, what are the run books, what is this for? John I don't know if he heard that before. Sometimes there are workloads running and how people don't know, I don't even know who is the owner, right? So after you're done with an office and after you're managing and uh, you know, uh, managing your workload on and off, you have full visibility and clear understanding of what are the. It's funny, it's >>funny you mentioned the workloads being kind of either not knowing the owners, but also we see people um, with the workloads sometimes it's like throwing a switch and leaving the hose on the water on. And next thing you know, they get the bill. They're like, oh my God, what happened? Why did I leave? What, what is this? So there's a lot of things that you could miss. This brings up the point you just said and what you said earlier aligning resources across the cloud uh and and having accountability. And then you, you mentioned at the top of this interview that aligning with the business needs. I find that fastest. I would like to take him in to explain because it sounds really hard. I get how you can align the resources and do some things, identify what's going on, accountability kind of map that that's, that's good tech. How does that, how do you get that to the alignment on the business side. >>Yeah. I mean we start by, first of all, like I said, you know, we use machine learning to play these workloads? And then we asked basic questions about the workload. You know, what is this workload for? Uh Do you need to meet with any kind of compliance is for this workload? Uh What is your S. O. A. For this workload? You know, depending on that. We we make recommendations. Uh So we kind of ask those questions and we also walk them through where they create roles. Like we asked who was responsible for creating budgets or managing security for this workload and guess what also the you know the bucket where resources are allocated for. We ask for you know, owners for that as well like in this bucket who's the owner for who's going to monitor the budget and things like that. So you know we asked, you know, we start by just asking the question, having teams complete that sort of information and also you know, why do you a little bit more information on how this aligns with the business needs? You know, >>talk about the complexity side of it. I love that conversation around the number of services. You said 200 services depending how you count what you call services in the thousands of so many different things uh knobs to turn on amazon uh web services. So why are people um focused on the complexity and the partnering side? Because you know, it's the clouds at E. P. I. Based system. So you're dealing with a lot of different diverse resources. So you have complexity and diversity. Can you talk me through how that works? Because that's that seems to be a tough beast to tame the difference between the complexity of services and also working with other people. >>Yeah for sure like this this normal to have um you know maybe thousands of lambda functions in their application. We're working with a customer where within last month there were nine million containers that launched and got terminated right there, pretty much leveraging, auto scaling and things like that. So these environments are like very complex. You know, there's a lot of moving pieces even, you know, depending on the type of services they're using. So again what we do, you know we when we look at tags and we look at other variables like environments and we look at who's provisioning resources, those resources and we try to group them together and that way there's accountability uh you know if the cost goes up for one workload were able to show that team like your cost is going up uh And also we can show uh unallocated bucket that hey within last week Your cost is you know, $4,000 higher in the unallocated bucket. Where would you like to move this these resources to just like an ongoing game. You >>know, you know jt I was talking with my friend jerry Chen is that Greylock partners is a V. C. Has been on the cube many times a couple of years ago. We're talking about how you can build a business within the cloud, in the shadows of the clouds, what he called it, but I called it more the enabling side and and that's happened now, you're seeing the massive growth. I'm also talking to some C X O C IOS or CSOs and they're like trying to figure out which companies that are evolving and growing to be to buy from, get to get the technology. Uh and they always say to me john I'm looking for game changing kind of impact. I'm looking for the efficiency and you know, enablement, the classic kind of criteria. So how would you guys position yourself to those buyers out there that might want to look at you guys as a solution and ups what game changing aspect of what you do is out there, how would you talk to that that C I O or C. So or buyer um out in the end the enterprise and the thieves ran his piece. What would you say to them? >>Yeah, I think the biggest uh advantage and I think right now it's a necessity, you hear these stories where, you know, people provision resources, they don't even know which project is it for. It's just very hard to govern the cloud environment, but I believe we're the only tool. Mhm where you want to compromise on the speed, right? The whole reason um cloud but they want to innovate faster. No one wants to follow that. Right? But I think what's important. We need to make sure everything is aligned with the business value. Uh, we allow people to do that. You know, we, we, we can both fast at the same time. You can have some sort of guard rails. So there are proper ownership. There's accountability. People are collaborating and people are also rightsizing terminating resources, they're not using. It's like, you know, I think if companies are looking for a tool that's gonna drive better accountability on how people build and collaborate on cloud, I think reply the best solution. >>So people are evolving with the cloud and you mentioned terminating services. That's a huge deal in cloud. Native things are being spun up and turned off all the time. So you need to have good law, You have a good visibility, observe ability is one of the hottest buzzwords out there. We see a zillion companies saying, hey, we're observe ability, which is to me is just monitoring stuff. They can sure you're tracking everything. So when you have all this and you start to operationalize this next gen, next level cloud scale, cost optimization and visibility is huge. Um, what is the, what is the secret sauce uh, for that you guys offer? Because the change management is a big 12 teams are changing too cost team accountability. All this is kind of, it's not just speeds and feeds, there's, it's kind of intersection of both. What's your take on that reaction to that? >>Yeah, I think it's the Delta. Right? So change management, What you're really looking for is not a, like a fire hose, you're looking for. What changed what the root cause who did it, what happened? Right. Because it's totally normal for someone to provision maybe thousands or even millions containers. But how many of those got shut down? What is the delta and uh, you know, if there is a, there is an anomaly, what is the root cause? Right? Uh, how we fix it. So you know the way we've changed managers, change management is a lot different. We really get to the root cause analysis and we really help companies to make, really show what changed and how they can take action to a media. But if there were issues, >>I want to put a little plug in for you guys. I noticed you guys have a really strong net promoter score. You have happy customers also get partners. A lot of enablement there. You kind of got a lot of things going on. Um, explain what you guys are all about. How did you get here? What's the day in the life of a customer that you're serving? Why then why are the scores so high? Um, take us through a use case of someone getting that value. >>Yeah. So I, I come from like a consulting background, john so you know, I was migrating companies to read the Bs when the institute was in beta and then I, you know, founded a consulting company over 100 employees. Really successful interview. S premier partner called in clouds. And so Enos was born there because because you know it was, it was born out a consulting company, there are a lot of other partners who are leveraging the tools to help their customers and it goes back to our point earlier, john like amazon has to wonder services, right? We are noticing customers are open to work with partners and uh you know with different partners that really helped them to make sure they're making the right decisions when they are building on cloud. So a lot of the partners, a lot of the consulting companies are leveraging uh and hopes to deliver value to their customers as far as uh you know how we actually operate. You know, we pay attention to uh you know what, what customers are looking for, what, where are the next sort of challenges uh you know, customers are facing in a cloud environment world like super obsessed, you know, like we're trying to figure out how do we make sure every single resource is aligned with the business value without slowing companies down so that really drives us, we're constantly welcome customers to stay true to the admission >>and that's the ethos of devops moving fast. The old quote Mark Zuckerberg used to have move fast, break stuff and then he revised it to move move fast and make it stable, which is essentially operational thing. Right, so you're starting to see that maturity, I noticed that you guys also have a really cool pricing model, very easy to get in and you have a high end too. So talk us through about how to engage with you guys, how do people get involved? Just click and just jump in there, buying software buying services, take a minute to explain how people can, can work with you. >>Yeah, it's just, it's just signing up on our site, you know, our pricing is tier model, uh you know, once you sign up, if you do need help with, you know, remediating high risk issues we can bring in partners, we have a strong partner ecosystem. Uh we could definitely help you do interviews to the right partners but it's as simple as just signing up and just taking me out. First thing I guess. >>Jt great chatting with you have been there from early days of devops, born in the field, getting, getting close to the customers and you mentioned ec two and beta, they just celebrate their 15th birthday and I remember one of my starts that didn't actually get off the off the blocks, they didn't even have custom domains at that time was still the long remember the long you are else >>everything was ephemeral like when you restart server, everything will go away a cool >>time. And I just remember saying to myself man, every entrepreneur is going to use this service who would ever go out and buy and host the server. So you were there from the beginning and it's been great to see the success. Thanks for coming on the cube >>all That's >>okay. Jt thanks so much as a cube conversation here in Palo alto. I'm john for your host. Thanks for watching. Mhm.