>> Everyone. Welcome to a special cube conversation. We're here in Palo Alto, California Cube Studios. I'm John, four year host of the Q. We hear Atomic Wild, the CEO of Snapper out. Tom. Great to see you. You doing? I'm great. Thanks. You guys. You're launching Snapper. Snapper out. What is the company? What do you guys launching? Tell us. >> Well, quite simply stated were delivering a new class of network operating system for the cloud native era. Andrea Lee. What that does, is it. It delivers on the promise of time to service for applications. Always on security assurance and compliance. Andi greater operational efficiency, which is really one of the things that's been plaguing organizations tonight. >> How long is the company been around? This is the first public launch. A solution? Talk about the history real quick. >> So the company was founded in two thousand fifteen by some former operators from Apple. They built and ran Apple. Sort of biggest public facing data centers from the networking perspective on DH. You know, we've been working diligently on this. This is a new class of operating system that was really inspired by, you know, that their time building out those data centers on def. You, you kind of look back. NETWORKINGS not really had any major disruptive innovation in the last twenty five, thirty years. Ah, but back into the two thousand six, with the advent of a Ws and the and the new sort of big, hyper scaler tze, those guys started to realize that the network was something that was kind of getting in the way of their operational efficiency, of being able to automate and drive the network at scale on DSO. Our founders, you know, went through that whole sort of discovery process and things when when they were Apple on DH, you know, and the hyper scales drove the advent of this kind of white box disaggregated networking, separating the software operating system from the hardware and the reason behind that was really around game great gaining greater control because it's a legacy. Networking vendors were not delivering what was needed, and they needed to get more control on DSO. Are found us. You really saw the opportunity to say, Look, we think that there's a way of solving what an operator really needs and what an organization needs and one of the big challenges. There is howto networking operations. Teams collaborate with dev up stings because the devil teams are responsible for, you know, time to service for the application. And that's, you know, that's really the value of the organization. And so, you know, they set out to solve that problem to say, Well, hell, can we build a network operating system on what they realised was that you know what Deb Ops had done is embrace. It's a cloud. Native principles container ization, virtual ization, my crack services on DH. So what we've done is we've built from the ground up a newly architected network operating system that is a fully containerized micro services architecture that embeds coup Panetti's on DH allows the networking for this first time to be brought natively into the de bop store chain. Sonett ops teams can still sort of control and deploy the network and define policy and things. But now they don't have to worry about that is, you know, sort of annoying day today, tasks where, you know the Devil apps engineer is tryingto get an application on the network and, you know, they have to just do sort of some, you know, pretty trivial movies that changes things. And so, you know, in in doing that, what we also figured out was we could solve, you know, problems not just around the operational efficiencies and the time to service, but also a lot of security >> issues as well. So a lot of development going public with the product you mentioned. Cooper Netease, top of cloud. >> What are the >> big shifts in the industry that you guys air riding on because you have tail winds get cloud? Yeah, What is the way that you're on? Can you take a minute to explain some of the big shifts in the industry that's going, guys? >> Yeah, well, I I think there's several things. I think one of the biggest is that, you know, every single organization out there is looking nervously over its shoulder because we live in an age of very, very rapid disruption. It's kind of you know what call the Amazon affect. You know, those big, established companies who've been around for many, many years, who are being disrupted by, you know, Jason, you know, cos we're in adjacent spaces or new start ups coming in so everybody near realizes they need to use technology to their advantage, and they have to disrupt themselves Before, you know, they're they're disrupted. So? So that's one of the big drivers and And so time to service speed, efficiency are all sort of paramount. When you were in, you know, any C suite, you know, discussion, those air. Those are things that come up a ll the time from a technology perspective. We're seeing things, things changing significantly and how we use technology. And, you know, So everything is mobile. Ah, you know, we have the advent of I O t coming in, and so, you know, lots of services and moving to the edge. And so the data centers that were traditionally completely centralized and they'll sort of starting to distribute a little bit of well, eh? So you have this, you know, idea of sort of age data centers in H compute. So there's there's a lot of things, you know, changing and happening. And there's a lot of opportunity for us to deliver, you know, some strong value in this. >> So they obviously the cloud native trend you mentioned is big. That's driving the application market. De bobs you mentioned earlier huge we've seen years now in years of evidence of growth yet on dev ups. Okay, so now it's coming down into the network how? How our company's solving challenges for application developers that are in a devil's world because that seems to be the growth. And the sooner the pressure's coming from is that more requirements coming from the applications to the network. How are companies solving this problem? >> So, you know, So I think from the computer and storage side, things have moved along, you know, pretty, pretty, pretty swiftly eso, you know, as an application engineer. What? What you want is you want the infrastructure to service. You just You just want it to do what the application needs. Unfortunately, you know, traditionally, infrastructures has has been the other way around. You know, you deploy the infrastructure and you say, Okay, well, this is what the application could do within the constraints of the infrastructure and networking has, you know, just continued that idea. And so what you want to do is you want to take this idea of you we've talked before about infrastructure as code, you know. How do you make it? So is when an application engineer rights and application, he can actually regard the infrastructure as almost like a code library. And that's something that a lot of legacy vendors have talked about marketed to for some time. But the reality is-- >> It makes a lot of sense. >> Yeah, it does. It makes a ton of sense. But the reality is that all they could do was offer up some, you know, proprietary APIs and and programmatic interfaces. And the big challenge was the actual architecture of a network operating system was not designed in a way to actually enable that that infrastructure to react in the proper way by developing this containerized microservices architecture on by embedding communities and putting native DevOps tool chains you know inside the operating system. We actually can deliver on the promise of infrastructure as code. >> and this is what everyone wants. I gotta ask you, if everyone wants this and we hearing all around the Cuban all the events we go to clearly a requirement becoming table stakes. But what? What's been preventing people from doing this? >> Well, it's it's the architecture. I mean, if you look at, I call them Legacy Network architectures, but network architecture. Yeah, network operating system itself. The actual you know, the operating system that exists on the physical switch. That is where the problem starts, because that is designed as one big >> blob off >> coat. So all of the features Aaron there, they're all in the same place. They all sort of interact with each other, and it gives you reliability problems that give you innovation problems, because every time you change something, it has a knock on effect. If there's a bug and you have to fix that bug, you have to replace the entire blob. If you replace the entire blob, you have to down the switch or, you know, do some kind of complex patching. If there's a security vulnerability, you have to either differ like actually fixing their on DH, become non complaint or you have to down the switch. And you know we live in an age, As I said, where everything is on all the time, everything is mobile, you know, everybody wants their services right here right now. And the very you know, the very existence of a business depends on being able to deliver those applications all the time. So you can't bring network's down. So when when we've taken this micro services approach and we've containerized the actual infrastructure, you know, on the protocols and everything else, everything existed in its own container. Now, if there's a security vulnerability, we can replace just that container. If you're not using certain services on the operating system, you could kill those containers. And in the process, you reduce the threat surface off the the operating system in the switch. Where is in a legacy world with this monolithic blob, you can just you can turn off the features, but the code still there, the threat surfaces huge, and you're still vulnerable. So what's the >> solution to this and snap route? Fix this. What's the operational benefits? How do you guys play into fixing? The problems have been holding everyone back. >> Well, I think you know collaboration, I think is, you know, is one of the big benefits. You know, Quite frankly, I think there's, you know, there's there's been sort of tension in organizations. I think unfairly network operating operations teams have been, you know, treated as you know, holding things back or non responsive, whatever, anything that's completely unfair because actually, the problem is with the the vendor community. We haven't been delivering the tools that enable them to, you know, deliver the services they need. And so with you know, with our approach with this cloud native approach, we're actually able, sort of, you know, bring the net net tops world. You know, closer to Deb. Ops allow this Khun collaboration to happen on give you you know that the benefit ofthe I Abel sort of coordinated approach to delivering the application and the application is the value that the business delivers on. Biff, you know, if your application stops working, I mean, you know this in your personal life, right? You know, we use our phones and our devices. You try, use an application and it and it's not working. You're going to go and find a competitive. You're just going to go and say, Oh, well, you know, you saw download something else from the APP store on DH. So, you know, availability is a huge thing for businesses today on the network has been one of the most vulnerable pieces in terms of availability. Not because not necessarily because people are attacking it, but because it's so complex. And brittle that any time you change anything, things fall to pieces. And that's why people don't want to touch the network. And that is why we had the rise of the whole Sgn movement. The ESPN movement was on approach That said, we need to make the network more dynamic. And so, rather than addressing the actual operating system, put overlays over the top, create overlays and allow Deb ops teams to do what they need to do to deploy applications over the top of your fairly done plumbing. What we're saying is, look, we're going to simplify and claps. Thatyou don't need translation layers, and a PR is You don't need overlays. You don't need all of that stuff. We're now re architect in the operating system itself. So you, Khun Natively, address that and you know and directly, you know, control the policy that you need to deploy an application. >> Don, This is about modern infrastructure. It's what cloud is modernizing all parts of the value changing how people by consume, deploy, provide valued application known as you guys are part of that. How do people engage with snap route? So I say, Okay, this is the direction. I'm going. I'm going. I'm in cloud native and doing Cooper Netease. I got containing amusing microspheres betting my company's future on this direction. And a lot of people are. Yep. How doe I engage with you guys. And how do you fit into the equation? >> Right? So s so first of all, you know, initial engagement, you know, website linked in Facebook. You know, we're on all of those things. Weigh, You know, we're in customer trials right now. Invaders right now, you know, where was the launching the product? So you know where we'll be shipping off of your first commercial deployments. But as faras, you know how and where are the good? You know, the good opportunities to to deploy us on. Obviously, there are, you know, sort of new. Come, we're high growth companies who, you know, we're talking to who, you know, kind of wanna build off us as a base to start with. But if you already have ah, large investment in disorder deployed legacy equipment we can fit in quite nicely on. And we can still add a ton of value because one of the big problem areas, he's actually the top of rack, Switch the double racks, which is actually where Dev ops and Net ops come together. It's the first place where compute on the application touched the network on DH. This is where usually Annette, ops engineer, spends a lot of time doing, you know, fairly said of your trivial tasks to help applications, you get onto the network and you know, it's a big >> waste of conversion. You see, you think you're playing at the top Iraq switch, >> that is, that is a good place for for somebody to start to get a tremendous amount of value out of our product. You don't need to replace the entire network. You don't have to have us into end. You don't have to have us in the corps if you deploy us at the top of Rex, which so, you know, take a white box device. You know, deploy our operating system on top is very, very simple to do. The network engineer Khun very simply get that device up and running a little token. Figure itself. And then the Dev ops engineers can, you know, come in and say How would employ an application And I didn't need the network to do the following things, and the device will configure itself in that way. >> This is really two worlds coming together. Network operations and developer operations coming together. Yeah. How do you see that? Coming together and meshing together? Obviously, the top of Rex, which you mentioned? A key area where you get your kogel work. But as those cultural communities come together, you know, network operations and depth there, they're seeing benefits with each other. How are those worlds colliding? What's the benefit? What's it going to look like? And what's the opportunity? >> Yeah, well, I you know, I mean, first of all, I think that there's this misconception that these two over there, you know, these two types of organizations don't want to collaborate anything. That's a complete miss misconception. I mean, everybody wants to do the right thing they wanted, You know, their business is to grow ondas. I said earlier. I mean, I think the problem is that, you know, the vendor community is not delivered, as you know, a set of tools and products and capabilities that enable this collaboration. Andi, you know, that's what we're bringing to the table. But I do think you know that there's this This sort of, you know, this cross pollination, this this this ability to you don't have to learn each other's area of expertise. You don't suddenly have to become a networking expert. You know, the dead box engineer doesn't become a networking expert. Vice versa. But there is this, you know, there's there's this point of view, no collaboration and harmony that we can create where there was a lot of tension on DH, you know, and, you know, in fact, there was, you know, a lot of problems that way. Consider harmonize that and allow these organizations to just, you know, move forward with what really counts, which is growing the business. >> Tom, thanks for coming in. I appreciate your time. Original launch. Final question for you. Taking me displaying your background. Your previous roles in networking. We first met when you were at a PHP that he's being. Then why you attracted to snap Prada's as an opportunity on what's. >> Yeah, so, you know, I'm I've been in networking for over thirty years on and help me on DH. You know, network in security. Various roles, mostly in sort of product Rolls product management. You know, pride to snap her out. I was the general manager of the data center networking group HP on DH. You know, I got to do some, you know, fabulous things at HP. We have, you know, quite a ruber. And in other things there which have been hugely successful. So it was a lot of fun. But I came to the point with my career there, where I realized, you know, I I done, you know, many of the things that I wanted to do, and also, you know, most of the opportunities that were there in transforming and transitioning that company. And I wanted to get back to my start up roots on DH. You know, the, you know, long conversation. >> No data centers, these apple guys. >> Yeah, Andi, you know, And so I started talking Teo to snap Brown on, you know, they were asking my advice and things. And the one of the things that attracted me, as you say was it's a company built by operators for operators. You know, it's I, You know, I've never had the opportunity to be in a company founded by operators who just intrinsically know what the customer problem is on B because they've lived it. And And I think you really do have to live it to truly understand on DH. So, you know, that was a huge plus for me. I was really attracted, Teo, that Adam and Glenn, our founders, you know, really interesting great guys. But also there's this inflection point. There's this inflection point in the marking and market and everything to do with, you know, start ups and successful startups is not just having the right innovative technology, which I truly believe we do but having the right overthere innovative technology at the right time. And the timing here is perfect. I mean, child native, you know, Cuba netease, the movement behind Cuba. Netease is just a force unto itself. You know, Dev Ops is, you know, is really moving forward. There's a huge sort of groundswell within the networking team community to, you know, to modernize and to, you know, toe toe. Contribute more to the success of business s So we have a massive >> opportunity. And And the trend of programmable networks Infrastructure is code is happening now. He wanted rubber is hitting the road now? >> Yeah, absolutely. You know it's, you know, we'll go through the usual adoption curves of, you know, early adopters and mass market etcetera. And so, you know, there's a There's a journey ahead of us, but but yeah. No, I mean, you know, people are doing this right now. >> Well, congratulations on your launch net, right? We'll be watching you. Really innovative. Moving right to the core of the devices with an operating system. No abstraction. Layers with Cooper Netease. Interesting architecture. Looking forward to following it. Dominic Wild CEO Snapper out here inside the Cube studios and fellow Also, I'm John Ferrier. Thanks for watching.