>>Hey everyone, and welcome back to Las Vegas. Viva Las Vegas, baby. This is the Cube live at AWS Reinvent 2022 with tens of thousands of people. Lisa Martin here with Dave Valante. Dave, we've had some great conversations. This is day one of four days of wall to wall coverage on the cube. We've been talking data. Every company is a data company. Data protection, data resiliency, absolutely table stakes for organizations to, >>And I think ecosystem is the other big theme. And that really came to life last year. You know, we came out of the pandemic and it was like, wow, we are entering a new era. People no longer was the ecosystem worried about it, AWS competing with them. They were more worried about innovating and building on top of AWS and building their own value. And that's really, I think, the theme of the 2020s within the ecosystem. >>And we're gonna be talking about building on top of aws. Two guests join us, two alumni join us. Stephen Manley is here, the CTO of Druva. Welcome back. Jason crat as well is here. CIO and CTO of Summit Carbon Solutions. Guys, great to have you back on the program. >>Thank you. >>Let's start with you giving the audience an understanding of the company. What do you guys do? What do you deliver value for customers? All that good >>Stuff. Yeah, no, for sure. So Summit Carbon is the world's largest carbon capture and sequestration company capturing close to 15 million tons of carbon every year. So it doesn't go into the atmosphere. >>Wow, fantastic. Steven, the, the risk landscape today is crazy, right? There's, there's been massive changes. We've talked about this many times. What are some of the things, you know, ransomware is a, is, I know as you say, this is a, it's not a, if it's gonna happen, it's when it's how frequent, it's what's gonna be the damage. What are some of the challenges and concerns that you're hearing from customers out there today? >>Yeah, you know, it really comes down to three things. And, and everybody is, is terrified of ransomware and justifiably so. So, so the first thing that comes up is, how do I keep up? Because I have so much data in so many places, and the threats are evolving so quickly. I don't have enough money, I don't have enough people, I don't have enough skilled resources to be able to keep up. The second thing, and this ties in with what Dave said, is, is ecosystem. You know, it used to be that your, your backup was siloed, right? They'd sit in the basement and, and you wouldn't see, see them. But now they're saying, I've gotta work with my security team. So rather than hoping the security team stays away from me, how do I integrate with them? How do I tie together? And then the third one, which is on everybody's mind, is when that attack happens, and like you said, it's win and, and the bell rings and they come to me and they say, all right, it's time for you to recover. It's time for, for all this investment we've put in. Am I gonna be ready? Am I going to be able to execute? Because a ransom or recovery is so different than any other recovery they've ever done. So it's those three things that really are top of mind for >>How, so what is the, what are the key differences, if you could summarize? I mean, I >>Know it's so, so the first one is you can't trust the environment you're restoring into. Even with a disaster, it would finish and you'd say, okay, I'm gonna get my data center set up again and I'm gonna get things working. You know, when I try to recover, I don't know if everything's clean yet. I'm trying to recover while I'm still going through incident response. So that's one big difference. A second big difference is I'm not sure if the thing I'm recovering is good, I've gotta scan it. I've gotta make sure what's inside it is, is, is alright. And then the third thing is what we're seeing is the targets are usually not necessarily the crown jewels because those tend to be more protected. And so they're running into this, I need to recover a massive amount of what we might call tier two, tier three apps that I wasn't ready for because I've always been prepared for that tier one disaster. And so, so those three things they go, it's stuff I'm not prepared or covering. It's a flow. I'm not used to having to check things and I'm not sure where I'm gonna recover too when the, when the time comes. >>Yeah, just go ahead. Yeah, that's right. I mean, I think for me, the biggest concern is the blind spots of where did I actually back it up or not. You know, what did I get it? Cuz you, we always protect our e r p, we always protect these sort of classes of tiers of systems, but then it's like, oh, that user's email box didn't get it. Oh, that, you know, that one drive didn't get it. You know, or, or, or whatever it is. You know, the infrastructure behind it all. I forgot to back that up. That to me the blind spots are the scariest part of a ransomware attack. >>And, and if you think about it, some of the most high profile attacks, you know, on the, on the colonial pipeline, they didn't go after the core assets. They went after billing. That's right. But billing brought everything down so they're smart enough to say, right, I'm not gonna take the, the castle head on. Is there is they're that. Exactly. >>And so how do you, I get, I mean you can air gap and do things like that in terms of protecting the, the, the data, the corrupt data. How do you protect the corrupt environment? Like that's, that's a really challenging issue. Is >>It? I don't know. I mean, I'll, I'll you can go second here. I think that what's interesting to me about is that's what cloud's for. You can build as many environments as you want. You only pay for what you use, right? And so you have an opportunity to just reconstruct it. That's why things, everything is code matters. That's why having a cloud partner like Druva matters. So you can just go restore wherever you need to in a totally clean environment. >>So the answer is you gotta do it in the cloud. Yeah. What if it's on prem? >>So if it's on prem, what we see people do is, and, and, and this is where testing and, and where cloud can still be an asset, is you can look and say a lot of those assets I'm running in the data center, I could still recover in the cloud. And so you can go through DR testing and you can start to define what's in your on-prem so that you could make it, you know, so you can make it cloud recoverable. Now, a lot of the people that do that then say, well actually why am I even running this on prem anymore in the first place? I should just move this to the cloud now. But, but, but there are people in that interim step. But, but, but it's really important because you, you're gonna need a clean environment to play in. And it's so hard to have a clean environment set up in a data center cuz it basically means I'm not touching this, I'm just paying for something to sit idle. Whereas cloud, I can spin that up, right? Get a, a cloud foundation suite and, and just again, infrastructures code, spin things up, test it, spin it down. It doesn't cost me money on a daily basis. >>Jason, talk a little bit about how you are using Druva. Why Druva and give us a kind of a landscape of your IT environment with Druva. >>Yeah. You know, so when we first started, you know, we did have a competitor solution and, and, and it was only backing up, you know, we were a startup. It was only backing up our email. And so as you pointed out, the ecosystem really matters because we grew out of email pretty quick as a startup. And we had to have real use cases to protect and the legacy product just wouldn't support us. And so our whole direction, or my direction to my team is back it up wherever it is, you know, go get it. And so we needed somebody in the field, literally in the middle of Nebraska or Iowa to have their laptop backed up. We needed our infrastructure, our data center backed up and we needed our, our SaaS solutions backed up. We needed it all. And so we needed a partner like Druva to help us go get it wherever it's at. >>Talk about the value in, with Druva being cloud native. >>Yeah. To us it's a big deal, right? There's all sorts of products you could go by to go just do endpoint laptop protection or just do SAS backups. For us, the value is in learning one tool and mastering it and then taking it to wherever the data is. To me, we see a lot of value for that because we can have one team focus on one product, get good at it, and drive the value. >>That consolidation theme is big right now, you know, the economic headwinds and so forth. What was the catalyst for you? Was it, is that something you started, you know, years ago? Just it's good practice to do that? What's, >>Well, no, I mean luckily I'm in a very good position as a startup to do define it, you know, but I've been in those legacy organizations where we've got a lot of tech debt and then how do you consolidate your portfolio so that you can gain more value, right? Cause you only get one budget a year, right? And so I'm lucky in, in the learnings I've had in other enterprises to deal with this head on right now as we grow, don't add tech debt, put it in right. Today. >>Talk to us a little bit about the SaaS applications that you're backing up. You know, we, we talk a lot with customers, the shared, the shared responsibility model that a lot of customers aren't aware of. Where are you using that competing solution to protect SaaS applications before driven and talk about Yeah. The, the value in that going, the data protection is our responsibility and not the SA vendor. >>No, absolutely. I mean, and it is funny to go to, you know, it's like Office 365 applications and go to our, our CFO and a leadership and be like, no, we really gotta back it up to a third party. And they're like, but why? >>It's >>In the cloud, right? And so there's a lot of instruction I have to provide to my peers and, and, and my users to help them understand why these things matter. And, and, and it works out really well because we can show value really quick when anything happens. And now we get, I mean, even in SharePoint, people will come to us to restore things when they're fully empowered to do it. But my team's faster. And so we can just get it done for them. And so it's an extra from me, it's an extra SLA or never service level I can provide to my internal customers that, that gives them more faith and trust in my organization. >>How, how are the SEC op teams and the data protection teams, the backup teams, how are they coming together? Is is, is data protection backup just morphing into security? Is it more of an adjacency? What's that dynamic like? >>So I'd say right now, and, and I'll be curious to hear Jason's organization, but certainly what we see broadly is, you know, the, the teams are starting to work together, but I wouldn't say they're merging, right? Because, you know, you think of it in a couple of ways. The first is you've got a production environment and that needs to be secured. And then you've got a protection environment. And that protection environment also has to be secured. So the first conversation for a lot of backup teams is, alright, I need to actually work with the security team to make sure that, that my, my my backup environment, it's air gapped, it's encrypted, it's secured. Then I think the, the then I think you start to see people come together, especially as they go through, say, tabletop exercises for ransomware recovery, where it's, alright, where, where can the backup team add value here? >>Because certainly recovery, that's the basics. But as there log information you can provide, are there detection pieces that you can offer? So, so I think, you know, you start to see a partnership, but, but the reality is, you know, the, the two are still separate, right? Because, you know, my job as a a protection resiliency company is I wanna make sure that when you need your data, it's gonna be there for you. And I certainly want to, to to follow best secure practices and I wanna offer value to the security team, but there's a whole lot of the security ecosystem that I want to plug into. I'm not trying to replace them again. I want to be part of that broader ecosystem. >>So how, how do you guys approach it? Yeah, >>That's interesting. Yeah. So in my organization, we, we are one team and, and not to be too cheesy or you know, whatever, but as Amazon would say, security is job one. And so we treat it as if this is it. And so we never push something into production until we are ready. And ready to us means it's got a security package on it, it's backed up, the users have tested it, we are ready to go. It's not that we're ready just be to provide the service or the thing. It's that we are actually ready to productionize this. And so it's ready for production data and that slows us down in some cases. But that's where DevOps and this idea of just merging everything together into a central, how do we get this done together, has worked out really well for us. So, >>So it's really the DevOps team's responsibility. It's not a separate data protection function. >>Nope. Nope. We have specialists of course, right? Yeah, yeah. Because you need the extra level, the CISSPs and those people Yeah, yeah. To really know what they're doing, but they're just part of the team. Yeah. >>Talk about some of the business outcomes that you're achieving with Druva so far. >>Yeah. The business outcomes for me are, you know, I meet my SLAs that's promising. I can communicate that I feel more secure in the cloud and, and all of my workloads because I can restore it. And, and that to me helps everybody in my organization sleep well, sleep better. We are, we transport a lot of the carbon in a pipeline like Colonial. And so to us, we are, we are potential victims of, of a pipe, a non pipeline group, right? Attacking us, but it's carbon, you know, we're trying to get it outta atmosphere. And so by protecting it, no matter where it is, as long as we've got internet access, we can back it up. That provides tons of value to my team because we have hundreds of people in the field working for us every day who collect data and generate it. >>What would you say to a customer who's maybe on the fence looking at different technologies, why dva? >>You know, I think, you know, do the research in my mind, it'll win if you just do the research, right? I mean, there might be vendors that'll buy you nice dinners or whatever, and those are, those are nice things, but the, the reality is you have to protect your data no matter where it is. If it's in a SaaS application, if it's in a cloud provider, if it's infrastructure, wherever it is, you need it. And if you just go look at the facts, there it is, right? And so I, I'd say be objective. Look at the facts, it'll prove itself. >>Look at the data. There you go. Steven Druva recently announced a data resiliency guarantee with a big whopping financial sum. Talk to us a little bit about that, the value in it for your customers and for prospects, >>Right? So, so basically there's, there's really two parts to this guarantee. The first is, you know, across five different SLAs, and I'll talk about those, you know, if we violate those, the customers can get a payout of up to 10 million, right? So again, putting, putting our money where our mouth is in a pretty large amount. But, but for me, the exciting part, and this is, this is where Jason went, is it's about the SLAs, right? You know, one of Drew's goals is to say, look, we do the job for you, we do the service for you so you can offer that service to your company. And so the SLAs aren't just about ransomware, some of them certainly are, you know, that, that you're going to be able to recover your data in the event of a ransomware attack, that your data won't get exfiltrated as part of a ransomware attack. >>But also things like backup success rates, because as much as recovery matters a lot more than backup, you do need a backup if you're gonna be able to get that recovery done. There's also an SLA to say that, you know, if 10 years down the road you need to recover your data, it's still recoverable, right? So, so that kind of durability piece. And then of course the availability of the service because what's the point of a service if it's not there for you when you need it? And so, so having that breadth of coverage, I think really reflects who Druva is, which is we're doing this job for you, right? We want to make this this service available so you can focus on offering other value inside your business. And >>The insurance underwriters, if they threw holy water on >>That, they, they, they were okay with it. The legal people blessed it, you know, it, you know, the CEO signed off on it, the board of directors. So, you know, it, and it, it's all there in print, it's all there on the web. If you wanna look, you know, make sure, one of the things we wanted to be very clear on is that this isn't just a marketing gimmick that we're, we're putting, that we're putting substance behind it because a lot of these were already in our contracts anyway, because as a SAS vendor, you're signing up for service level agreements anyway. >>Yeah. But most of the service level agreements and SaaS vendors are crap. They're like, you know, hey, you know, if something bad happens, you know, we'll, we'll give you a credit, >>Right? >>For, you know, for when you were down. I mean, it's not, you never get into business impact. I mean, even aws, sorry, I mean, it's true. We're a customer. I read define print, I know what I'm signing up for. But, so that's, >>We read it a lot and we will not, we don't really care about the credits at all. We care about is it their force? Is it a partner? We trust, we fight that every day in our SLAs with our vendors >>In the end, right? I mean this, we are the last line of defense. We are the thing that keeps the business up and running. So if your business, you know, can't get to his data and can't operate, me coming to you and saying, Dave, I've got some credits for you after you, you know, after you declare bankruptcy, it'll be great. Yeah, that's not a win. >>It's no value, >>Not helpful. The goal's gotta be, your business is up and running cuz that's when we're both successful. So, so, so, you know, we view this as we're in it together, right? We wanna make sure your business succeeds. Again, it's not about slight of hand, it's not about, you know, just, just putting fine print in the contract. It's about standing up and delivering. Because if you can't do that, why are we here? Right? The number one thing we hear from our customers is Dr. Just works. And that's the thing I think I'm most proud of is Druva just works. >>So, speaking of Juva, just working, if there's a billboard in Santa Clara near the new offices about Druva, what's, what's the bumper sticker? What's the tagline? >>I, I, I think, I think that's it. I think Druva just works. Keeps your data safe. Simple as that. Safe and secure. Druva works to keep your data safe and secure. >>Saved me. >>Yeah. >>Truva just works. Guys, thanks so much for joining. David, me on the program. Great to have you back on the cube. Thank you. Talking about how you're working together, what Druva is doing to really putting, its its best foot forward. We appreciate your insights and your time. Thank >>You. Thanks guys. It's great to see you guys. Likewise >>The show for our guests and Dave Ante. I'm Lisa Martin, you're watching the Cube, the leader in enterprise and emerging tech coverage.

(upbeat music) >> Live on the floor in San Francisco for AWS Summit. I'm John Furrier, host of theCUBE. Here for the next two days getting all the action back in person. We're at AWS re:Invent, a few months ago. Now we're back, events are coming back and we're happy to be here with theCUBE. Bring all the action, also virtual, we have a hybrid cube. Check out theCUBE.net, siliconangle.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 theCUBE. >> 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. It's great that be back to events. >> It's amazing, this is the first summit I've been to in what two, three years. >> It's awesome, we'll be at the 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, 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, and the edge is with the action is. You guys are number one premier partner at SMB for edge. >> That's right. >> Tell us about what you guys doing at innovative and what you do. >> That's right, so I'm the director of solutions architecture. 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. We are deploying that in countries that don't have AWS infrastructure in region. They don't have it-- >> Give an example. >> Example would be Panama. We have a customer there that 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. So they've taken EKS anywhere. We've put storage gateway and snowball 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 AWS since 2013 with theCUBE about their events, and we watched the progression. Andy Jassy was in charge and became the CEO. Now Adam Slepsky is in charge, but the edge has always been that thing they've been trying to avoid. I don't want to say trying to avoid. Of course Amazon listens to customers, they work backwards from the customers, we all know that. But the real issue is they're bread and butters, EC2 and S3. And then now they got tons of services, and the cloud is obviously successful, and we're seeing that. But the edge brings up a whole nother level. >> It does. >> Computing. >> It does. >> That's not set 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, operational technologies and IT merging. We see with the data at the edge, you got 5G, 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 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 used to rip on theCUBE 'cause it's basically Amazon in a box pushed in the data center, running native, all this stuff. But now cloud native operations are becoming the standard. You're starting to see some standard, Deepak Singh's group is doing some amazing work with opensource, Raul's team on the AI side. Obviously you got Swam 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 want to invest in this hardware? Do I want to have 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 not a good fit for Outposts, they weren't a good fit 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 going to meet you where you are with 5G. We're going to meet you where you are with wavelength. We're going to meet you where you are with EKS anywhere. 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. >> All right so you guys are making a lot of good business decisions around managed cloud service. Innovative as that, you have the cloud advisory, the classic professional services for the specific edge piece and doing that outside of the availability zone and regions for AWS. Customers in these new areas that you're helping out are, they want cloud, they want to have modernization, modern applications. Obviously they got data machine learning and AI all part of that. What's the main product or gap that you're filling for AWS 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, 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 to focus 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 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, 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? >> Matthew: Correct. >> For companies. >> Matthew: Correct. >> Mainly because the needs are there, you got data, you got certain products, whether it's low latency type requirements, and then they still work with the regions, it's all tied together, is that how it works? >> 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 going to have a failback scenario. If we're going to deploy FinTech in the Caribbean we're going to talk about hurricanes. And we're going to 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 got to ask you on the, since you're at the edge in these areas, now, I won't say underserved but developing areas where you now have data and you have applications that are tapping into that requirement. It makes total sense, we're seeing that across the board. So it's not like it's an outlier, it's actually growing. >> Matthew: 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. And you mentioned FinTech in the islands, there are a lot of web three happening. What's your view on the web three world right now relative? >> We have some customers actually deploying crypto especially in the Caribbean. I keep bringing the Caribbean up, but it's top of my mind right now, we have customers that are deploying crypto. A lot of countries are choosing crypto to underlie parts of their central banks. So it's up and coming. I have some personal views that crypto is still searching for a use case. And I think it's searching a lot and we're there to help customers search for that use case. But crypto as a to technology lives really well on the AWS edge. And we're having more and more people talk to us about that. And ask for assistance in the infrastructure because they're developing new cryptocurrencies every day. It's not like they're deploying Ethereum or anything specific. They're actually developing new currencies 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 projects going on. But if you go talk to all the crypto people they say, look we do a smart concept. We use the blockchain. It's a lot of overhead. It's not really very 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 smart contracts, for instance, or certain transactions. And they go into Amazon for the database. They all, don't tell anyone we're using a centralized service. Well, what happened if decentralized? >> Yeah, and that's a conversation. >> It's a performance issue. >> Yeah and it's a cost issue and it's a development issue. So I think more and more as some of these currencies maybe come up, some of the smart contracts get into, they find their use cases. I think we'll start talking about how does that really live on AWS and what does it look like to build decentralized applications but with AWS hardware and services. >> All right so take me through a use case of a customer, Matthew, around the edge. So I'm a customer, pretend I'm a customer. Hey, 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 app. And I also want all the benefits of the cloud. So I want the modernization and I want to migrate to the cloud for all those cloud benefits and the goodness of the cloud. What's the answer? >> Yeah big thing is industrial manufacturing. That's one of the best use cases. Inside industrial manufacturing we can pull in many of the AWS edge services, we can bring in private 5G so that all the equipment inside that manufacturing plant can be hooked up. They don't have to pay huge overheads to deploy 5G. It's better than wifi for the industrial space. When we take computing down to that industrial area because we want to do pre-processing on the data. We want to gather some analytics. We deploy that with regular commercially available hardware, running VMware, and we deploy EKS anywhere on that. Inside of that manufacturing plant, we can do pre-processing 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 to the AWS availability zone, the standard-- >> John: For data lake, or whatever. >> To the data lake, yeah data lake house, whatever it might be. And we can do additional data science on that once it gets to the AWS cloud. But a lot of that 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 one of the best use cases that we're seeing. >> And I think, I mean, we've been seeing this on theCUBE for many, many years, moving data around is very expensive. But also compute, going to the data that saves that cost on the data transfer but 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, but there's new things are developing. So I want to ask you what new 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. But now what does that change in the core cloud? There's a system element here, 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? Now you start thinking about where business decisions should be taking place. So not only are you changing your architecture you're actually changing your organization because you're thinking about a dichotomy you didn't have before. So now you say, okay, this can take place here. And maybe this decision can wait. And then how do I visualize that? >> By the way, it could be a bot too, doing the work for management. >> Yeah, exactly. >> You got observability going right. But you got to change the database architecture in the backs. There's new things developing. You've got more benefit. >> There are, there are. And we have more and more people 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. For the past maybe decade, 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. >> I mean, this is 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 come of the past year is that throwing away data's bad. Even data lakes that so-called turn into data swamps. Actually is not the case. You look at Databrick, 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. >> Matthew: Yep. >> So as data becomes code, as we call it in our last showcase, we did, a whole event on this. The data's good in real time and in the lake. 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 benefits. There's all kinds of new scale. >> There are. And we have many customers that are running petabyte level. They're essentially data factories on premises, right? They're creating so much data and they're starting to say, okay we could analyze this in the cloud. We could transition it. We could move petabytes of data to the AWS cloud or we can run computational workloads on premises. We can really do some analytics on this data, transition those high level and sort of raw analytics back to AWS, run 'em through machine learning. And we don't have to transition 10, 12 petabytes of data into AWS. >> So I got to end the segment on a kind of a fun note. I was told to ask you about your personal background on premise architect, AWS cloud, and skydiving instructor. How does that all work together? What does this mean? 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 skydiving before I started in the cloud space, this was 13, 14 years ago. I was a, I still am a skydiving instructor. I was teaching skydiving. And I heard out of the corner of my ear a guy that owned an MSP that was lamenting about 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 what I went to school for. I'd love to, 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 I started and the first day there we had a discussion, EC2 had just come out and-- >> This is amazing. >> Yeah and so we had this discussion, we should start moving customers here. And that totally revolutionized that business, that led to, that guy actually still owns skydiving airport. 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 almost looking back and saying, now let's take what we learned in the cloud and apply those lessons in those services to on premises. >> It's such a great story, is going to, the whole growth mindset, pack your own parachute. >> Matthew: Exactly. >> The cloud in the early days was pretty much will the chute open? >> Matthew: Yeah. >> It was pretty much you had to roll your own cloud at that time. And so, you jump out a plane you got to make sure that parachute is going to open. >> And so was Kubernetes by the way, 2015 or so when that was coming out, it was, I mean, it was still, maybe it does still feel like that to some people. But it was the same kind of feeling that we had in the early days of AWS, the same feeling we have when-- >> It's pretty much now with you guys, it's more like a tandem jump. But a lot of this cutting edge stuff is like jumping out of an airplane. You got the right equipment. You got to do the right things. >> Exactly. >> John: Matthew, thanks for coming on theCUBE. Really appreciate it. Absolutely great conversation. >> Thanks for having me, thank you. >> Okay theCUBE's here live in San Francisco for AWS Summit. I'm John Furrier, host of theCUBE. We'll be at AWS Summit in New York coming up in the summer as well. Look up for that. Look at this calendar for all theCUBE action at theCUBE.net. We'll be right back with our next segment after this break. (upbeat music)

>>Everyone. Welcome to the cube here. Live in San Francisco, California for AWS summit, 2022. We're live we're back with events. Also we're a virtual, we got hybrid all kinds of events this year, of course, summit in New York city happening this summer. We'll be there with the cube as well. I'm John, again, John host of the queue. Got a great guest here, Justin Colby, 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 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 elevator pitch is we are, 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, 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. 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 yeah, 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 demand 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, it's a small to midsize 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 cut customers are coming to us and they're 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, uh, progressively working through a modernization strategy is always the better approach. And so we spent 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 it's 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, I O T devices, what's that like right now from a channel engine 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 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 tell, yeah, they're like, listen, at 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 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 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. 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, 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, 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. 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 Jessey announce or 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 product. I can get that like values as companies, cuz they're betting on you and your people. >>They are, they are what's >>What's 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, the 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 out, how are you gonna ask a team of one or two people in your it department to make all of 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 manage 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 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 would cost them a fortune. If >>The 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. They, they love to get the, the stickers and the badges and the pins, um, at innovative in 28 team. 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. 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 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 and large, it staffs are turning over the gen Z and millennials are in the workforce. They were a provisioning top of rack switches. Right? First of all. And so if you're a business is also the, I call the buildout, 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 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 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 like >>Critical issues. This is >>Just like, these are the table stakes. >>Yeah. And, and every, every business owner's thinking about this. So >>That's, that's what at least a million in loading, 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. No. And then remind AI and ML. That's >>Right. That's right. So to try to 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. An it department. >>Exactly. >>Like, can we just call up, uh, you know, our old vendor that's right, >>Right. Our old vendor. I like it. >><laugh> 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 the, at is, is very important. And it's something that we talk about every, with every one of our small to mid-size >>Business. 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 a good tell your, 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 opportu 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 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, 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 a 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> well, 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 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 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 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 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 that a lot of 'em dipped their toe in the water. But by 2017 we knew interest structure was around the corner. Yeah. 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 the 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 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 migration. 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 classic 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 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 tour 22. I'm John for your host. Thanks for watching. We're back with more great coverage for two days after this short break.

>> From Seattle Washington, it's theCUBE, covering AWS Imagine, nonprofit. Brought to you by Amazon Web Services. >> Hey welcome back everybody, Jeff Frick here with theCUBE. We're actually on the waterfront in Seattle at the AWS Imagine nonprofit event. We were here a couple weeks ago for the AWS Imagine education event. This is really about nonprofits and solving big, big problems. So Dave Levy and team have you know dedicated to some of these big problems. And one of the big problems in the world is human trafficking, and problems that people are encountering and all kinds of nasty situations all over the world. And we're really excited to have someone who's tackling that problem, and really trying to bring a voice to those people that wouldn't otherwise have a voice. And she's Hend Alhinnawai, she's the CEO of Humanitarian Tracker. Hend, good to see you. >> Thank you Jeff, good to be here. >> Absolutely. So before we jump into it, impressions on this event? >> Wonderful event bringing together technologists, people in nonprofits, really creating synergies for people to collaborate and talk to each other and network and learn how they can advance their organizations. >> Such important work. >> Yes. >> So give us kind of the background on what you're up to, what Humanitarian Tracker's all about. >> So Humanitarian Tracker's a nonprofit forum. It was created to connect and empower citizens using innovation and technology, but specifically for humanitarian events. We were among the first to combine crowdsourced reports with data mining and artificial intelligence and apply them to humanitarian disasters, conflicts, human rights violations, disease outbreak. All the way to tracking the UN's Sustainable Development Goals. Really giving a holistic view of what's happening. >> It's interesting, you know, it's probably like the middle eastern spring, I can't remember the exact term that people use, where it was kind of the first use of regular people using their mobile phones to kind of grab a ground swell of action. You're not looking at the politics specifically, you're looking more at humanitarian disasters. But pretty amazing kind of what a connected phone represents to anyone anywhere in the world now to communicate what's happening to them. To share that story. We really didn't have anything like that before. To get that personal event on the ground. >> No it's really a new way of consuming, creating and consuming information. So the cell phone has really given people on the ground a chance to tell their own story. But it's not enough. If you have an event that happens to you. Something happens to you. And you record it, it stops there. But the unique thing with Humanitarian Tracker is it gives people that forum to show the world and tell them what's happening to and around them. >> Right, but it's not just about the individual. And what you guys are doing is using cutting edge technology, obviously you're here as part of the AWS event. In terms of machine-learning and big data to grab a large number of these reported events and distill it into more of an overarching view of what is actually happening on the ground. How did you do that, where did you get that vision, how are you executing that? >> Well, we're all about empowering the citizen. And in our line of work we deal with a lot of data, a lot of information, most of it is unstructured, most of it is crowdsourced. So we use machine-learning to help us extract important details. Information on time. Event location, what is happening. And at the same time we really cared that this reporter, stays anonymous for their own safety. We, privacy and security is utmost importance to us. So that's always our focus. So in that space, we de-identify them. We take out any information that could be identifiable, that could lead to their arrest, or could lead to someone identifying that it was them that reported. >> And how do you get this information to the people that are suffering this activity ground? How do they know about you, how do they know that you are anonymizing their information so there's not going to be repercussions if they report. You know, how do, kind of I guess your go-to-market, to steal a business terms, in making sure that people know this tool's available for help? >> It depends on the situation. For example in the conflict situation, we rolled it out, and we kept it low key for awhile. Because we didn't want government attacks, we didn't want people to be arrested, or to be tried. So we rolled it out. And it was word of mouth that spreads. And people started submitting supports. Actually the first project we did with conflict, we weren't sure if we were going to get one report, zero reports. The first week we got nothing. And then slowly as people learned about it they started submitting their reports. And we see our job as really elevating the otherwise marginalized voice. So you submit a report to us, we then take it. We verify it. We make it public. And that, we welcome, we encourage, we want people to consume it. Whether you're a student, whether you're a journalist, whether you're a government, whether you work in a nonprofit, the UN. It's been used to address human rights violations, it's been used to identify humanitarian hotspots. The data's phenomenal, and what you get from it. It's not just collecting data. We're not just about collecting the data. We want to make sure it's meaningful, and we want to derive insights. So we want to know what is the data actually telling us? >> Right, right. So just to be clear for people that don't know, so you're making that data available, you're cleansing the data, you're running some AI on it to try to get a bigger picture, and anyone with a login, any kind of journalist can now access that data in support of whatever issue or topic or story they're chasing? >> That's it Jeff. >> That's phenomenal. And just kind of size and scope. You've been at this I think you said since 2011. You know kind of how many active, activities, crisis, I don't know, what the definition is of a bucket of these problems. Are you tracking historically at a given point in time? Give us some kind of basic sizing type of dimensions. >> It really ranges, because it could, when we were tracking conflict for example, we were really focused on one area, and the surrounding countries. Because you had refugee population, you had displacement, you had all sorts of issues. But it could be anywhere from five projects, it just depends. And we want to make sure that each project we're taking on we're giving it our full attention, full scope. And I like to run the organization like a two-team pizza team. And so I don't take on more than I could handle. >> Right, right. So then how did it morph from the conflict to the Global Sustainability Goal? So we've worked with Western Digital, they're doing a lot of work, ASP's doing a lot of work on kind of these global sustainability goals. How did you get involved in that, and how did the two kind of dovetail together? >> So the elasticity of the cloud has helped our operation scale tremendously. And in 2016 we were selected as a top 10 global innovation, that could be applied to the Sustainable Development Goals, and-- >> So they found you, the UN find you, or did you get nominated? How did that happen? >> We were nominated, and from over 1,000 solutions we were chosen. >> Congratulations. >> Thank you. And we were showcased at the Solutions Summit which is hosted at the United Nations. And just based on that experience of meeting people that were doing really cool things in their respective communities, we launched the Global Action Mosaic. Because we wanted to create one place where people that are doing projects in their communities could submit it, and have it showcased. And the goals are not only to crowdsource the SGD's, but to also be a part of the effort to track what's happening. Who's doing what where, make it easy for people to search say, Jeff you decided to get involved in a project with education. You can go onto our Global Action Mosaic, search projects on education in your community or in other parts of the world and then get involved in it. So it's really creating a centralized place where people can get information on the global goals. >> Awesome. So that's pretty much the Global Action Mosaic. It's pretty much focused on the UN global goals versus your core efforts around the Humanitarian Tracker. >> Yes. >> That's great. So we're here at AWS. Have you always been on AWS? Is this something new? How does being on kind of the AWS infrastructure help you do your mission better? >> We are, we've been partners in running AWS since we actually started. >> Since the beginning. >> Yes we have Yusheheedi as one of our partners, development partners, AWS. And because one of the core, one of the most important things to us is privacy and security, we want to make sure that whatever data is being handled and received is stored securely. >> Right, right. >> And that information transmitted, handled is also being done so in a secure way. Like I mentioned, the elasticity of the cloud has helped us scale our mission tremendously. It's affordable, we've been able to us it, we've learned their machine-learning stock to de-identify some of the data that comes in. So we're firm believers that AWS is essential to how we run our operation. >> Because do the individual conflicts kind of grow and shrink over time? Do you see it's really a collection of kind of firing up hotspots and then turning down versus one long, sustained, relatively flat, from kind of a utilization and capacity point of view? >> Yeah, no it definitely, it flares up and you'll have like a year, months, weeks sometimes where it's just focused on one area. But one of the things we focus on, it's not just. So what is the data actually telling us? So say you're focusing on point A. But just down the street in location B there is a dire humanitarian emergency that needs to be addressed. The crowdsourced reports, combined with the data mining and the AI, helps us identify those hotspots. So everybody could be focused here, but there could be an emergency down the street that needs to be addressed as well. It just depends. >> And do you have your own data scientists or do you, do other people take your data and run it through their own processes to try to find some of these insights? >> We have both. >> You have both. >> Yeah. >> So what's been the biggest surprise when you anonymize and aggregate the data around some of these hotspots? Is there a particular pattern that you see over and over? Is there some insight, that now that you've seen so much of it, from kind of the (muffled speaking) that you can share and reflect on? >> I think it' very unique to each project to do. But there is one thing that I strongly support, that I don't see enough of, and that's the sharing of data within the organizations. And so, for example just getting to that culture where sharing your data between organizations is encouraged and actually done. Could help create a, create a pool of knowledge. So, for example we worked with 13 different organizations that were all tackling humanitarian events. The same one, in Syria. And the 13 did not share data and did not talk to each other. And so we found that for example, they were all focused on one area. When just a few miles down, there was a need that wasn't being addressed. But because they don't share information, they had no idea. >> Right. >> It was only when we were able to take a look at it, kind of from the, from an overarching view, looking all their data, we were able to say you know, it would be helpful, it would actually, you could save on resources, and less time, and less effort, and you guys are tackling a small funding pool to begin with. If you shared information and tackled different things, instead of focusing on one area, because you don't know what the other guys doing. >> And were they using crowdsource data, is there source data, or were they just trying to collect their own from the field? >> They were collecting their own. >> So I assume that the depth, and the richness, and the broadness of data is nothing like you're collecting. >> Well you get a different kind of, you get different kind of information when the individuals actually telling you what's happening versus you asking a very direct question like, "Are you healthy? Yes or No?". Whereas you give them the chance, they might tell you that they haven't eaten, and their diabetic and you know, give you other pieces of information. Where they're living, are they refugees? Are they healthy? Are they not healthy? Do they go to school? Do their kids go to school? How many kids they have? Are they a female-run household? All this information could help guide development in the proper way. >> Right, right. All right. So give you the final word, how should people get involved if they want to help? >> You can go to humanitariantracker.org if you want to volunteer with us. And if you're doing a project that is related to the UN's Sustainable Development Goals, I would like you to go to globalactionmosaic.org, and map it there, and be part of our community. >> So Hend, thank you for taking a few minutes to share your story, and for all the good work that you're doing out there. >> Thank you Jeff it was a pleasure. >> All right, she's Hend, I'm Jeff, you're watching theCUBE, we're at AWS Imagine nonprofit. Thanks for watching we'll see you next time. (techno music)