>>from around the globe. It's the Cube with digital coverage of next level network experience event brought to you by Info blocks Hi ups to Minuteman and welcome to the Cube's coverage of the info blocks virtual event. Digging into the next level networking experience. I'm here with John Furrier, who is the host of the event. John. We've been talking about next level networking for for a few years now. Everything's multi cloud cloud native SAS adoption, really transforming the way that we have to think about networking. Tell us a little bit about this event. >>So as you know, yeah, again go back years from when member VM Ware bought in a sexual like Okay, you know that's going to change the game software to find networking. And we love that. We were all riffing on program ability. You saw the Dev Ops trajectory hitting networking. We would say that's where the action is on this event really kind of speaks to Info Blocks as a company which is really well known for DNS. I mean, they had cricket. Liu Stuart Bailey, that really kind of the pioneers in DNS and security have constantly been adding innovation to it, but DNS is one of those things where it's kind of like not thought about, but it runs everywhere, runs the web. It is critical infrastructure and, you know D HCP. We all know what that is. We have a home router, and then he got I p address management. These have been traditionally different things for enterprises, and everyone has it. They got to deal with it. And it's really, ultimately the location and how things resolved and connect. So you know, it really becomes a foundational opportunity to figure out where the access is not only a remote access, but security. So we had a great bunch of guests looking at looking at the info blocks. Next level networking, because they bought, had an acquisition, a Cube alumni snap route recently, and this caught our attention because they were doing Cloud Native. And one of the guests we had was Glenn Sullivan. He was the founder of Snap Route. He was the the guy who did all the Siri work for Apple. So this guy knows large scale of those cloud native We had kuna Sunni, who's the runs? Corporate development in all of the products for info blocks. He kind of went into the strategy of how they're taking the I won't say boring DNs, but the critical infrastructure of DNS and how they're extending the functionality with an abstraction layer around D D I, which is DNS DCP and management. And then we had some great guests on there. We had a Craig Sanderson from info blocks. He's on there. You'll hear from him. He talked about the security and then finally a customer who's running a big school district who, with Covert 19 exposes all these challenges around what has been called the borderless enterprise. So really, next level is that, you know, how do you deal with all this stuff? And that's been a big issue. So we're gonna unpack all that in this virtual event. We have four great interviews, and so it's going to be a great program. >>Yeah, John, as you said it to some of those foundational pieces of how network is done, a lot of times runs, you know, under the radar, something you don't need to think about. But all of these changes, as we said, you know my data. My network is now highly distributed, especially I would expect that the impact of the global pandemic and work from home are really causing even more of these challenges and to think about distributed infrastructure even more. So what are some of the themes we should be looking for here? How much of them kind of tie into what we've been talking about the last couple of years in some of these cloud native worlds? >>That's great questions to I'll get into some of the themes of the program, but you brought up the covert 19 again. We've been talking about this in our reporting. You've been doing a ton of interviews following all your your stuff as well as well as all of our team. Covert 19 really exposes the aspect of critical infrastructure, and to me it's like it's the It's the great I o T experiment happening in real time. It's forcing companies saying, Hey, the work. The future of work is about workplace. The location is now home workforce. Are the people emotional? They want ease of use. They want a different experience. They're all not in the office workloads and work flows. All of them have the common word working it so I think over 19 exposes this what I call I o t experiment because everyone is now borderless. It changes the game and really puts the pressure on security network access. And ultimately, you know, the bad guys are out there so you could have someone a teacher at home or a worker at home, and they get some malware attack and they're not sophisticated, zoom or whatever they're using for tools. All that's changed and they're vulnerable. So this brings up a huge networking challenge from whether even VP ends or even relevant or not to everything. So, to me, that is a huge point. You're gonna hear that throughout the commentary that that's kind of teased out. But the real things about innovation around the cloud you're gonna hear info blocks and they're experts talk about what they're doing and how they see cloud scale and cloud native integrating into an older paradigm like DNS. And to me, that's the That's the evolution of this DD I concept. That's an abstraction layer that creates innovation opportunities but also takes away a lot of the complexities around managing all the DNS things out there and again, that's the access of the network. It's a it's a place of truth is really kind of low level, but it's really foundational. So to me, that's the main theme. And customers want ease of use into it, whether they're at home or not, and replacing the old ways to putting a box out there. That's the way it was, DNs DNs. People would manage it all. Now they want to have it provisioned, managed a manage service cloud Native Cloud operations because it's only gonna get has to get that way. >>Yeah, it's interesting, John. You know, we watched the whole wave of software defined impact networking. I think of a company like Info blocks. They've been around for decades. They're dominant in the space is that they play in. Traditionally, it would have been an appliance that you thought of for their environment you talked about. They now have the snapper out acquisition as part of what they're doing. So it just what should we be looking for? What are they really the main point? That Info Box wants to bring people together for this next level networking experience? >>Well, Glenn Sullivan was one of my favorite discussions, and he's been on. He's a cube alumni and he's so smart. He came again from Apple. He knows that he knows what large scale looks like. Snap route was really early and was one of those technologies that just, you know, it has the core DNs built in kubernetes built in. They were doing some pretty aggressive, I would call it for lack of a better word kubernetes on bare metal. They were doing stuff, but really super cool kubernetes you combine that with DNS and info blocks actually has the core DNs that's actually in every kubernetes of in the CN CF. So everything that comes out of the CN CF from a core DNS standpoint is info blocks. So yeah, they're definitely relevant in the whole CNC of Cloud Native foundation, effort around cloud native. And as that scales just micro services, you're gonna have to have this new abstraction layer and also be compatible with automation. So that's, um, we didn't go into the weeds on that, but that was essentially the head room for all the different conversations roles of cloud native and open source technologies enabling borderless enterprises because you got to have the operation side and you got to have the program ability. So you start to get into the true dev ops that we used to riff on all the time. You know, move fast, break stuff to don't break anything. Right? So ops, ops and Dev have to come together. This is where the winners and losers of networking will be determined. You gotta provide the enablement for developers, but you gotta provide the stability of an operational checklist. >>Yeah, John, I guess the last question I want to ask you before we get to the guests, You know, that operational change, You know, we saw for so many years it was, Oh, all the networking people, they're going to have to learn to code up weight. Dev ops is actually gonna spreading the information around. And maybe I won't need a particular networking team. But we understand when things go wrong, you've gotta have somebody with the expertise that could be able to dig in. What are you know, who should be listening to this? What are some of those organizational implications for what you're talking about with info blocks? >>That's a great point. I mean, the biggest challenge that I see in all this entire digital transformation as it starts to get down into the cloud native world is, most people are asking the wrong questions. They don't even know what they're talking about When it comes down to trying to compare an apple to an orange, they're really kind of disconnected on language. You got server people in networking. We know that they have different languages, and working together is key. When you think about something like DNS, that's a technical. That's an operator that's an I t person, that someone who's running critical infrastructure. But when you start to think about the security aspect of it, it's a CSO conversation. So what I'm seeing come out of this that's critical, is when you start to get into this cloud native world. You have more stakeholders in the value proposition of all this and with covert 19. As I pointed out, you know you got hacks and you got security. So when you talk with security, that's up and down the organization. That's the CSO down to the teams themselves. We have about automation horizontally scaling with Dev ops. That's multiple teams, so you have an integration kind of stakeholders. You know DNS servers, all networking. All these people have to kind of come together. So the people who should watch this are the people who are concerned about scaling the modern enterprise, which is borderless, which is code word for multiple access points and multiple connection points. R i o t um, how do you make that work? And that's the real challenge. So it's kind of like an I t a person who wants to figure out where the puck will be so they could be there when it's there and skate to where the puck is, as we say, and and the CSO of the senior people have to understand that DNS cannot be overlooked because whether it's a managed service. So So Cloudflare had a huge out into the DNS. Setting DNS takes down everything. So it's ah, it's the most fertile ground and the most targeted ground for attacks, and that is well understood. So getting the right questions in place foundational we had to set up the modern enterprise, and then that's going to be a construct for the cloud native architecture and ultimately the developer environment. So yeah, it's a topic that's kind of nerdy with DNS, But it has implications across digital transformation. >>Jonah expecting lots of conversations around security and automation how they tie into all of the modern and modernization themes. Absolutely some pieces that shouldn't be left behind. All right, John Ferrier, Thanks so much for helping us kick off. Really interested. Make sure to stick with us off to listen to all the guest interviews here that John has done the info blocks. Next level networking experience. Instrument, man. And thank you for watching the Cube. Yeah, yeah, yeah, yeah, yeah, yeah.

>> 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.

>> So welcome to the special. Keep conversation here in Palo Alto, California John, for a host of the Cube. We're here with two co founders. Adam Casella was the CTO and Glenn Sullivan's cofounder. Snap Route Hot Start up, guys. Welcome to this Cube conversation. Thank you. Thank you. So left on the founders in because you get the down and dirty, but you guys are launching. Interesting product is for Cloud Cloud Native Super sighting. But first, take a man to explain what is snap brought. What do you guys do? What's the main core goal of the company? >> Right? So your your audience and you familiar with white Box now working disaggregated networking, where you're buying your hardware and your software from different companies. There's a lot of different Network OS is out there, but there's nobody doing what we're doing for the now ergo es, which is a cloud native approach to that where it's a fully containerized, fully micro serviced network OS running on these white box, which is >> test your background. How did you guys start this company? Where'd you come from? What was the epiphany? Was the motivation? >> Sure. So our heritage is from operations running at some of the largest Edison is in the world. We came from Apple. Ah, and running the networks there. And the issues and problems that we saw doing that is what led us to found stabbed. >> And what are some of the things that apples you guys notice on a huge scale? Yep. I mean, Apple. You know, a huge market share most probable company. I think it's now the largest cat. Microsoft was there for a while, but and apples, the gold standard, get from privacy to scale. What were some of the things that you saw, that what was the authority? >> So, I mean, there was a couple of things going on there, one we were driving driving too, doing white box for more control. So we wanted to have a better sense of what we could do with the network operating system on those devices. And we found very quickly that the operating systems that were out there, whether they be from a traditional manufacturer Ah, we and the planes or from someone from a disaggregated marketplace were basically using the same architecture. And this was this old, monolithic single binary item that goes in the pleasant device, and you know that worked in, you know, back in the day when you know applications didn't move, they were static there, One particular location. But as we were seeing, and one things that we were really pushing on is being able to dynamically have move workloads from one location to another quickly to meet demand. The network was not able to keep up with that, and we believe that it really came down to the architecture that was there. Not being flexible enough and not allowing our control to be able to put in the principles would actually allow us to allow that that application time to service be faster. >> You know, one of these on personally fascinated, you know, seeing startups out there and living in this cloud error and watching those like Facebook and Apple, literally build the new kind of scale in real time. It's like you have, you know, changing the airplane engine out of thirty five thousand feet. As the expression goes, you have to be modern. I mean, there's money on the line that's so much scale, and when you see an inefficiency, you've got to move on it Yeah, this is like, what, you guys did it. Apple. What were some of the things that yet you observed was that the box is Was it the software? A CZ? You wanted to be more agile. What was the the problem that you saw? >> So it it's really in fragility, right? It's it's basically, this Network OS is as they were, our design in a way so that you don't touch him right. If you look at the code releases and how often they, you know, fixed security vulnerabilities or you know they have patches or even knew regular versions right there. The cycle isn't weekly. It's not daily like you see in some C I C. Environments, right? You might have a six month or a twelve month or an eighteen month cycle for doing this sort of a new release for for, you know, whatever issue new features or or fixes, right. And the problem that we would see is we would be we would be trying to test a version in the lab, right? We would be qualifying code and say there's a security vulnerability. You know, something like heart bleed, right? That comes out the guys on the server side, they push a new patch using, you know, answerable Scheffer puppet and, you know, two days later, everything's good, even two hours later in some environments. But we had to wait for the new release to come from one of the traditional vendors we had to put in our lab, and we get this sort of kitchen sink of every other fix. There'd be enhancements to be GP that we didn't ask for. There'd be enhancements to, you know, Spanish or that we didn't ask for. Even if they patched it, you'd still get this sort of all in one update. And by the time you're done qualifying, there might be another security vulnerability. So you got to start over. So you'd be in this constant cycle of months of qualified, you know, qualifying the image because you you'd be testing everything that's in the image. And not just that. The update. And that's really the key difference between what we're >> going to work involves shapes you eventually chasing your tail. Exactly. One thing comes in and opens up a lot of consequences, but that's what systems over >> all about this consequences, right? This is right systems are challenging. And what it does is it is it creates this culture and no from the network folks, right? Because the network folks are basically, like, not in my backyard. You want to add this new thing? No. Because they're judged by up time. They're judged by how long the network is up and how long the applications available. They're not judged by how quickly they can put a new feature out or how how quickly they can roll an update. Their They're literally judged in most organizations by up time. How many nines are they giving? So if I'm judged by up time and somebody wants to add something new, my first answer as a network person has anybody really is gonna be No, no, no, don't touch anything. It's it's fragile >> because they're jerks or anything. They just know the risk associate with what could come from the consequence exactly touching something. So, yes, it's hard right now to yes, Okay, so I gotta ask you guys a question. How come the networking industry hasn't solved this problem? >> Well, there's a There's a few different reasons I feel it is, and that's because we've had very tightly coupled, very tightly controlled systems that have been deployed his appliances without allowing operators to go ahead and add their innovations onto those items. So if you look at the way thie compute world is kind of moved along in the past fifteen, you know, fifty, thirty years, you mean, really a revolution started to athletics, right? From their particular perspective, you have Lennox. You can open up the system, you get people constructing open source items everyone knows just end. A story that makes the most is the most successful, monolithic, you know, piece of code base that's ever existed, right? It took fifteen years later for anyone in the network industry to even run the linens on a switch. I mean, that's that's pretty, you know, huge in my mind, right? That's that's that's called like Yeah, and so and even when they've got it on the particular switch to running older versions of Colonel, they're running different things. They don't you know, back Porter versions of code that don't work with the most modern applications that are out there, and they really have it in their tight, little walled garden that you can't adjust things with and >> that was their operational mode at the time. I mean, networks were still stable. They weren't that complicated. And hence the lag and many felt had been left >> behind. Theocracy. Inefficiencies that may have function when you have dozens of devices doesn't function when you have hundreds and thousands of devices. And so when you look at, like even from the way they they presented their operating system from a config standpoint, it is a flat config file that's loaded from filing booted. That's the same paradigm people of file for forty years. Why do we still think that hotel today compute has left that behind? They're going the programmatic AP diversions with you know whether it be you know, Cooper netease war with Doctor, where they have everything built into one ephemeral container that gets deployed. Why it hasn't been working in the same thing. And I really believe it's for that close ecosystem that hasn't allowed. People look to put their innovations onto their Yeah, it's >> almost as a demarcation point in time. You think about history and him and how we got here, where it's like, Okay, we got perimeters. We got firewalls and switches top Iraq stuff. So you got scale. It's bolted down, it's secure. And incomes Cloud comes I ot So there's almost a point, You know, it almost picked. The year was a two thousand eight doesn't through two thousand twelve. You started to see that philosophy. So the question I've asked for you is that what was the tipping point? So because, you know, the fire being lit under the butts of networking guys finally hit and someone saying, Well, they don't evolve to be like the mainframe guys. I was like, not really, because mainframes is just different from client server. Networks aren't going away there around. What's the tip was the tipping point. What made the network industry stand up? >> So yeah, what it is, is it's it's being able to buy infrastructure with a credit card, Right? Because as soon as I've got a problem as an application owner was a developer, I say, Hey, I've got this thing that I've got a release, right and I go to the network came and said, I've got this new thing and I get any sort of pushback. Now you look a cloud, right? Eight of us is our Google, like all the different options out there. Fine. I don't need these guys anymore. When the grab credit card slide it, boom. Now I can buy my infrastructure. That's that's really the shift. That's what's pushing folks away from using those kind of classic network infrastructure is because they could do something else, right? >> So cloud clearly driving it, think >> I would. I would say so. Yeah, absolutely. All >> right, So the path of solve these problems, you guys have an interesting solution. What's the path? What's the solution that you guys are bringing to market? Sure. >> So the way I had kind of view, the way the landscape is set up is really if you look at you know where this innovation has happened in the compute side in the last little bit Weatherby Cloud, whether it be, you know, some of the club native items would come out there. They've all come for the operators. I haven't been a vendor to sitting there and going to play. They've kind of mirth, morph himself into vendors. But they didn't originate as vendors, right to go and supply these systems. And so what I see from the solution to that is sort of enabling operators and people who are running networks to be ableto controller their own destiny to manage how their networks are deployed right. And this boils down from our perspective to a micro services containerized network operating system that is not be spoke, not proprietary, but is using the ecosystem has been built from this P people on the computes side specifically the cloud native universe in a cloud native world and applying those perimeters and shims onto network >> learned, learned from the cloud, Right? Like don't try to make something better. Look at the reasons why folks are going to the cloud Look at the AP structures looking. He's of launching instances. Look, att the infrastructure you build with a few clicks and say, What can I learn from that environment to Moto? Mimic that in my private environment? >> Yeah, and this is why we kinda looked at cu burnett. He's is a really big piece of our infrastructure and using the company as a p I as the main interface in tor device. So that you, Khun, you know multi different reasons, is expandable. You could do, you know, a bunch of different custom options to expand that a P i But it allows people who are either in. Deva loves to look at that and go. I understand how this works. I know how these shims function and started getting in the realization that networking is not that much different than what the computer world is. >> So you guys embraced integration, his deployment, CCD pipeline, all that good stuff. And Cooper netease even saw Apple at sea Ncf conference that they have a booth there. No one would talk, but certainly communities is getting part that cloud native. What's the important solution that you guys are building to solve to solve from the problems that you're going after with now the cloud needed because Dev ops ethos is trickling down, helping down the stack. Certainly we know what cloud is, so it's So what is specifically the problem that you solved >> So a couple things that air So obviously you have your, you know, application time of service. The faster you can double your application, the faster you can get up and running the factory. People using out it is, you know, you get more money, you save money, right? Um, you have security. No one wants to be in that that, you know, that box of having a security voluntarily happened on there, but they >> were non compliance, >> Yes, or non compliance with particular thing with a P i. P. I C P C high socks and all in all things that come along with that. And finally it's the operational efficiency of day two operations. We've gotten pretty good as industry as deploying Day one operations and walking away. We don't do anything. No, no, no. We can't change the network anymore. It's really that next day when you have to to things like apply those applications or have a new application, it gets moved. Containers are ephemeral. The average container last two to three days. Viens last twenty three days. Monolithic caps last for years. That air that are not in those things that are just compute bare metal piece. So when we start moving to a location or a journey of having a two to three day ephemeral app that can be removed or moved, replace different location. The network needs to be able to react to that, and it needs to be able to take that and ensure that that not only up time but availability is there for that, >> and it's not management tools that are going to fix it, right? This is this is sort of our core argument is that you look at all of the different solutions that have come out for the last seven, eight, nine years in the networking in the open networking space. This trying to solve this from management perspective with, you know, different esti n profiling different, different solutions for solving this management. Day two operations issues, right. And our core argument is that the management layers on top aren't what needs to change. That can change. If you adopt communities, you get that kind of along with it. But you need to change the way the network OS itself is built so that it's not so brittle so that it's not so fragile breaking into micro services, breaking the containers so that you can put it into a CCD pipeline. You try to take a monolithic network OS and put it in your C. C I. C D Pipeline. You're going to be pushing a rock up. Help. >> It's funny. We've had Scott McNealy on the Cube founder Sun Microsystems and we said, You know, he has from one time. Hey, you know what about the cloud he goes? I should I had network is the computer was his philosophies. I should should we call the cloud? So if the network is the computer kind of concept thie operating environment management's not aki sub system of the network. It's a component, but the operating system has subsystems. So I like this idea of a network, operates system talk about what you guys do with your work operating system and what is day to mean. What is actually that means >> sure. So when you take your services and you divide them up into containers and, you know, call the micro services, basically taking a single service, putting container and having a bunch of dependency that might be associate with that, what you end up doing is having your ability to, uh, you know, replace or update that particular container independently of the other components on the system. If an issue happens, or if you want to get a new feature functionally for that, the other thing you could do is you, Khun Slim, down what you're running. So you don't have to run these two hundred plus features, which is the average amount you see and just a top Iraq device. And you only use maybe ten to twenty percent of those. Why do I have all these extra features that I have to qualify that may introduce a bug into my particular environment. I want to run the very specific items that I know I need to give my application, uh, up and running and the ability to go ahead and pull in the cloud native environment and tools to do that allows you to get the efficiencies that they've learned from not only the cloud way, but also even doing some on Prem communities. You know, private cloud items to get those efficiencies on their forwarding, your network running your applications. >> It's learning from the hyper sailors to write like this. This is Well, I mean, we had this when we were running networks, right? You put every protocol on the board on a white board, and then you'd start crossing them off and you start arguing in a room full of people saying, Why do I need this feature? Why do I need this other feature and it's like you have to justify it. And we know this is happening up the road at, you know, places like Facebook because, like Google, right, we know that they're that they're saying, Hey, the fewer features I have running the simple or my environment is the easier it is to troubleshoot, the less that can go wrong and the less security vulnerabilities. I have these air all. It's all goodness to run less right. So if you give people the ability to actually do that, they have a substantially better network. Yeah, >> what's unique about what you guys doing? How would you describe the difference between what you're doing and what people mean she might be looking at? >> So if you look at what you know other folks, that you know that we're going to see that look at collaborative Riku Burnett ys everything they do is a bolt on until his old architecture that's been around for twenty five years. So it's like a marriage between these two items. It's how you go ahead and have this plug in that interacts with that. Forget all that you're going to get up in the same spot with another thing you're adding on to another thing you're adding on to another thing. Hearing onto it seized these abstraction layers on top of distraction layers were taking the approach where it is native to the non core operating system. You know, Cooper, Daddy's Docker, Micro Services and containers. They're native to the system. We're not anything on. We're not bolting anything on there. That's how it is. Architect designed to be run. >> And that's key, right? The thing that we were really walking away from from our operational experience, we know that the decisions being made at that, you know, CEO Seo level and even in the you know, director of infrastructure level are going to be We're looking to build an on Prem solution, Mr Customers saying I need it to be orchestrated by an open, nonproprietary platform that gets rid of all of the platforms that are currently out there by the traditional network. Oh, yeah, Bs right. If you start out saying my orchestration platform has to be shared from compute storage network and it has to be open and has to be not proprietary, that pretty much leaves communities is you're really only choice and combinations important. It's hugely important to us, right? We knew that when we broke everything into, you know, containerized Micro Services. You need something to orchestrate those. So what we've done is we said, Hey, we're going to use this Cuban eighties tool. We're going to embed it on the device itself, and we're going to run it natively so that it can be the control point for all the different containers that are running on the system. >> That's awesome, guys. Great Chef will go forward to chatting more final question. What words of wisdom you have for other folks out there, Because there are a lot of worlds colliding as we look at the convergence of a cloud architect, which, by the way, is not a well defined position >> where you >> have infrastructure, folks who have gone through machinations of roles. Network engineer this that the other thing programmable networks air out there. You seeing this thing really time data? I oh, ti's. Also, you're all coming together yet. So what, you gotta re evaluating? What's your advice to folks out there? Who who are either evaluating running POC is rethinking their architecture. >> So the first thing that you know I think this is pretty common from folks that to hear is that evolve, or you're not going to be relevant anymore. You need to actually embrace these other items you can't ignore. Cloud. You can't pretend like I have a network. These applications will never move because eventually they will and you're going to be out of a job. And so we need you to start looking at some of the items that are out there from the cloud native universe to couldn't see Cooper nineties universe and realizing that networking is not a special Silent is completely different from, you know, dev ops every items they need to be working together. And we need to get these two groups and to communicate to each other, to actually move the ball forward for getting applications out there faster for customers. >> Don't let the thing I would say to infrastructure, folks, especially those that are going to cloud strategy is don't let the Ivy and the Moss grow on your own prime solution yesterday. Right? Go into your multi cloud strategy with I'm gonna have some stuff in eight of us and have some stuff deserve. I'm not stuff some stuff and Google. I might have some stuff overseas because the data sovereignty. But I'm also gonna have things that are on prep. Look at your on from environment and make it better to reflect what you could do in the cloud. Because once you're developers get using the AP structures in the cloud. They're going to want something very similar on Prem. And if they don't have it than your own, Prem is going to rot. And and you're going to have some part of your business that has to be on Prem and you're going to give it a level of service that isn't as good as the cloud, and nobody wants to be in that situation. >> Glenn, Adam Thanks so much for sharing. Congratulations on the launch of Snap Out every year and thanks for coming and sharing conversation. >> Thanks. Great. >> I'm John for here in Palo Alto. The Cube Studios for Cube Conversation with Snapper Out. Launching. I'm shot for you. Thanks for watching

>> Hello everyone. Welcome to this CUBE conversation. I'm John Furrier host like you here in our Palo Alto studio here in Palo Alto. Here with Dominic Wilde, known as Dom, CEO of SnapRoute, a hot new startup. A great venture. Backers don. Welcome to skip conversation. So love having to start ups. And so talk about Snape route the company because you're doing something interesting that we've been covering your pretty aggressively the convergence between Dev Ops and Networking. We've known you for many, many years. You were a former Hewlett Packard than you woodpecker enterprise running the networking group over there. You know, networking. And you're an operator. Snap rows. Interesting, because, um, great names back behind it. Big venture backers. Lightspeed Norwest, among others. Yes. Take a minute. Explain what? A SnapRoute. >> So SnapRoute was founded to really address one of the big, big problems we see in infrastructure, which is that, you know, essentially the network gets in the way of the deployment the rapid and angel deployment of applications. And so in the modern environment that we're in, you know, the business environment, highly competitive environment of disruption, continuous disruption going on in our industry, every company out there is constantly looking over their shoulder is, you know, making sure that they're moving fast enough there innovating fast enough that they don't want to be disrupted. They don't want to be overrun by, you know, a new upstart. And in order to do that, you know the application is is actually the work product that you really want to deploy, that you you want to roll out, and you want to be able to do that on a continuous basis. You want to be really agile about how you do it. And, quite frankly, when it comes to infrastructure, networking has been fifteen years behind the rest of the infrastructure and enabling that it's, ah, it's a big roadblock. It's obviously, you know, some of the innovations and developments and networking of lag behind other areas on what we snap Brown set out to do was to say, You know, look, if we're if we're going to bring networking forward and we're going to try and solve some of these problems, how do we do that? In a way, architecturally, that will enable networking to become not just a part of Ah, you know a cloud native infrastructure but actually enable those those organizations to drive forward. And so what we did was we took all of our sort of devops principles and Dev ups tools, and we built a network operating system from the ground up using devops principles, devops architectures and devops tools. And so what we're delivering is a cloud native network operating system that is built entirely on containers and is delivered is a micro services architecture on the big...one of the big value propositions that we deliver is what we call see a CD for networking, which is your continuous integration. Continuous deployment is obviously, you know, Big devops principal there. But doing that for networking, allowing a network to be constantly up enabling network Teo adapt to immutable infrastructure principles. You know we're just replacing pieces that need to be replaced. Different pieces of the operating system can be replaced If there's a security vulnerability, for instance, or if there's ah, bugger and you feature needed so you know we can innovate quicker. We can enable the network to be more reliable, allow it to be more agile, more responsive to the needs of the organization on all of this, fundamentally means that your Operation shins model now becomes ah, lot more unified. A lot more simple. You. Now, we now enable the net ox teams to become a sort of more native part of the conversation with devils. Reduce the tension there, eliminate any conflicts and everything. And we do that through this. You know, this innovative offices. >> Classically, the infrastructure is code ethos. >> Yeah, exactly right. I mean, it's you know, a lot of people have been talking about infrastructure is code for a long, long time. But what we really do, I mean, if if you deploy our network operating system you employ onto the bare metal switching, then you really enable Dev ops to hang have, you know, I take control and to drive the network in the way they want using their native tool chains. So, you know, Cuba Netease, for instance, ears. You know that the big growing dev ops orchestration to all of the moment. In fact, we think it's more than of the moment. You know, I've never seen in the industry that sort of, you know, this kind of momentum behind on open source initiative like there is behind Cuba. Netease. And we've taken communities and baked it natively into the operating system. Such that now our network operating system that runs on a physical switch can be a native part off that communities and develops tool >> Dom, I want to get to the marketplace, dynamics. Kind of what's different. Why now? But I think what's interesting about SnapRoute you're the chief of is that it's a venture back with big names? Yeah. Lightspeed, Norwest, among others. It's a signal of a wave that we've been covering people are interested in. How do you make developers deploy faster, more agility at scale, on premises and in clouds. But I want you to before we get there, want to talk about the origin story of company? Yeah. Why does it exist? How did it come to bear you mentioned? Operation is a big part of cloud to cloud is about operating model so much a company. Yes. This is the big trend. That's the big way. But how did it all get started? What's the SnapRoute story? >> Yeah, it's an interesting story. Our founders were actually operators at at Apple back in the day, and they were responsible for building out some of Apple's biggest. You know, data centers for their sort of customer facing services, like, you know, like loud iTunes, all those good things and you know they would. They were tasked with, sort of, you know, sort of modernizing the operational model with with those data centers and, you know, and then they, like many other operators, do you know, had a sense of community and worked with their peers. You know, another big organizations, even you know, other hyper scale organizations and wanted to learn from what they did on DH. What they recognised was that, you know, cos like, you know, Google and Facebook and Microsoft is urine things. They had done some incredible things and some incredible innovations around infrastructure and particularly in networking, that enabled them to Dr Thie infrastructure from A from a Devil ops perspective and make it more native. But those words that if you know, fairly tailored for there, if you know, for their organizations and so what they saw was the opportunity to say, Well, you know, there's there's many other organizations who are delivering, you know, infrastructure is a service or SAS, or you know, who are just very large enterprises who are acting as these new cloud service providers. And they would have a need to, you know, to also have, you know, tools and capabilities, particularly in the network, to enable the network to be more responsive, more to the devil apps like. And so, you know, they they they founded SnapRoute on that principle that, you know, here's the problem that we know we can solve. It's been solved, you know, some degree, but it's an architectural problem, and it's not about taking, You know, all of the, you know, the last twenty five years of networking knowledge and just incrementally doing a sort of, you know, dot upgrade and, you know, trying to sort of say, Hey, we're just add on some AP eyes and things. You really needed to start from the ground up and rethink this entirely from an architectural perspective and design the network operating system as on with Dev ups, tools and principles. So they started the company, you know, been around just very late two thousand fifteen early two thousand sixteen. >> And how much money have you read >> The last around. We are Siri's, eh? We took in twenty five million. >> And who were the venture? >> It was Lightspeed Ventures on DH Norwest. And we also had some strategic investment from Microsoft Ventures and from teams >> from great name blue chips. What was their interest? What was their thesis? Well, and you mentioned the problem. What was the core problem that you're solving that they were attracted to? Why would that why was the thirst with such big name VCs? >> Yeah, I mean, I think it was, you know, a zip said, I think it's the the opportunity to change the operational more. And I think one of the big things that was very different about our company is and, you know, we like to say, you know, we're building for effort. Operators, by operators, you know, I've found is, as I said, well, more operators from Apple, they have lived and breathed what it is to be woken up at three. A. M. On Christmas Eve toe. You know, some outage and have to, you know, try and figure that out and fight your way through a legacy kind of network and figure out what's going on. So you know, so they empathize with what that means and having that DNA and our company is incredibly meaningful in terms of how we build that you know the product on how we engage with customers. We're not just a bunch of vendors who you know we're coming from, you know, previous spender backgrounds. Although I do, you know, I bring to the table the ability to, you know, to deliver a package and you know, So there's just a cloud scale its clouds, Gail. It's it's but it's It's enabling a bridge if you like. If you look at what the hyper scales have done, what they're achieving and the operational models they have, where a if you like a bridge to enable that capability for a much broader set of operators and C. S. P s and as a service companies and dry forward a an aggressive Angela innovation agenda for companies, >> businesses. You know, we always discussing the Cuban. Everyone who watches the Kiev knows I'm always ranting about how cloud providers make their market share numbers, and lot of people include sass, right? I think everyone will be in the SAS business, so I kind of look at the SAS numbers on, say, it's really infrastructures service platform to service Amazon, Google, Microsoft and then, you know, Ali Baba in China. Others. Then you got IBM or one of it's kind of in the big kind of cluster there top. That is a whole nother set of business requirements that sass driven this cloud based. Yeah, this seems to be a really growing market. Is that what you're targeting? And the question is, how do you relate Visa? Visa Cooper? Netease trend? Because communities and these abstraction layers, you're starting to hear things like service mesh, policy based state Full application states up. Is that you trying to that trend explain. >> We're very complimentary, Teo. Those trends, we're, you know, we're not looking to replace any of that, really. And and my big philosophy is, if you're not simplifying something, then you're not really adding back here, you know, what you're doing is complicating matters or adding another layer on top. So so yeah, I mean, we are of value to those companies who are looking at hybrid approaches or have some on prime asset. Our operating system will land on a physical, bare metal switch So you know what? What we do is when you look at it, you know, service most is your message measures and all the other, You know, technologies you talked about with very, very complimentary to those approaches because we're delivering the on underlying network infrastructure on network fabric. Whatever you'd like to call it, that can be managed natively with class native tools, squeezing the alliteration there. But but, you know, it means that you don't need toe add overlays. We don't need to sort of say, Hey, look, the network is this static, archaic thing that's really fragile. And And I mean, if we touch it, it's going to break. So let's just leave it alone and let's let's put some kind of overlay over the top of it on do you know, run over the top? What we're saying is you can collapse that down. Now what you can say, what you can do is you can say, Well, let's make the network dynamic responsive. Let's build a network operating system out of micro services so you can replace parts of it. You can, you know, fix bugs. You can fix security vulnerabilities and you can do all that on the fly without having to schedule outage windows, which is, you know, for a cloud native company or a sass or infrastructure service company. I mean, that's your business. You can't take outage windows. Your business depends on being available all the time. And so we were really changing that fundamentals of a principle of networking and saying, You know, networking is now dynamic, you know, in a very, very native way, but it also integrates very closely with Dev ops. Operational model >> is a lot of innovation that network. We're seeing that clearly around the industry. No doubt everyone sees late and see that comes into multi Cloud was saying that the trend moving the data to the compute coyote again that's a network issue network is now an innovation opportunity. So I gotta ask you, where do you guys see that happening? And I want to ask you specifically talking about the cloud architects out in the marketplace in these enterprises who were trying to figure out about the architecture of clowns. So they know on premises there, moving that into a cloud operations. We see Amazon, they see Google and Microsoft has clouds that might want to engage with have cloud native presence in a hybrid and multi cloud fashion for those cloud architects. What are the things that you like to see them doing? More of that relates to your value problems. In other words, if they're using containers or they're using micro services, is this good or bad? What? What you should enterprise to be working on that ties into your value proposition. >> So I think about this the other way around, actually, if I can kind of turn that turn that question. But on his head, I think what you know, enterprises, you know, organization C, S. P s. I think what they should be doing is focusing on their business and what their business needs. They shouldn't be looking at their infrastructure architecture and saying, you know, okay, how can we, you know, build all these pieces? And then you know what can the business and do on top of that infrastructure? You wanna look at it the other way around? I need to deploy applications rapidly. I need to innovate those applications. I need to, you know, upgrade, change whatever you need to do with those applications. And I need an infrastructure that can be responsive. I need an infrastructure that can be hybrid. I need infrastructure that can be, you know, orchestrated in the hybrid manner on DH. Therefore, I want to go and look for the building blocks out there of those those architectural and infrastructure building blocks out there that can service that application in the most appropriate way to enable the velocity of my business and the innovation from my business. Because at the end of the day, I mean, you know, when we talk to customers, the most important thing T customers, you know, is the velocity of their business. It is keeping ahead in the highly competitive environment and staying so far ahead that you're not going to be disrupted. And, you know, if any element of your infrastructure is holding you back and even you know, you know the most mild way it's a problem. It's something you should address. And we now have the capability to do that for, you know, for many, many years. In fact, you know, I would claim up to today without snap route that you know, you you do not have the ability to remove the network problem. The network is always going to be a boat anchor on your business. It introduces extra cycles. It introduces big security, of underplaying >> the problems of the network and the consequences that prior to snap her out that you guys saw. >> So I take the security issue right? I mean, everybody is very concerned about security today. One of the biggest attack vectors in the security world world today is the infrastructure. It's it's it's so vulnerable. A lot of infrastructure is is built on sort of proprietary software and operating systems. You know, it's very complex. There's a lot of, you know, operations, operational, moves out and change it. So there's there's a lot of opportunity for mistakes to be made. There's a lot of opportunity for, you know, for vulnerabilities to be exposed. And so what you want to do is you want to reduce the threat surface of, you know, your your infrastructure. So one of the things that we can do it SnapRoute that was never possible before is when you look at a traditional network operating system. Andreas, A traditional. I mean, any operating system is out there, other you know, Other >> than our own. >> It's basically a monolithic Lennox blob. It is one blob of code that contains all of the features. And it could be, you know, architect in in a way that it Sze chopped up nicely. But if you're not using certain features, they're still there. And that increases the threat surface with our sat proud plant native network operating system. Because it is a micro services are key picture. If you are not using certain services or features, you can destroy and remove the containers that contain those features and reduce the threat surface of the operating system. And then beyond that, if you do become aware ofthe vulnerability or a threat that you know is somewhere in there, you can replace it in seconds on the fly without taking the infrastructure. Damn, without having to completely replace that whole blob of software causing, you know, an outage window. So that's just one example of, you know, the things we can do. But even when it comes to simple things, like, you know, adding in new services or things because we're containerized service is a ll boot together. It's no, eh? You know it doesn't. It doesn't have a one after the other. It it's all in parallel. So you know this this operating system comes up faster. It's more reliable. It eliminates the risk factors, the security, you know, the issues that you have. It provides native automation capabilities. It natively integrates with, You know, your Dev Ops tool chain. It brings networking into the cloud. Native >> really, really isn't in frustrations. Code is an operating system, so it sounds like your solution is a cloud native operating system. That's correct. That's pretty much the solution. That's it. How do customers engage with you guys? And what do you say? That cloud architect this is Don't tell me what to do. What's the playbook, right? How you guys advice? Because I see this is a new solution. Talk about the solution and your recommendation to architects as they start thinking about building that elastic in that flexible environment. >> Yeah. I mean, I think you know, Ah, big recommendation is, you know, is to embrace, you know, that all the all of the cloud native principles and most of the companies that were talking to, you know, definitely doing that and moving very quickly. But, you know, my recommendation. You know, engaging with us is you should be looking for the network to in naval, your your goals and your you know your applications rather than limiting. I mean, that's that's the big difference that, you know, the people who really see the value in what we do recognize that, you know, the network should be Andi is an asset. It should be enabling new innovation, new capabilities in the business rather than looking at the network as necessary evil where we you know, where we have to get over its limitations or it's holding us back. And so, you know, for any organization that is, you know, is looking at deploying, you know, new switching infrastructure in any way, shape or form. I think, you know, you should be looking at Well, how am I going to integrate this into a dev ops? You know, world, how may going to integrate this into a cloud native world. So as my business moves forward, I'm actually servicing the application in enabling a faster time to service for the application for the business. At the end of the day, that's that's everybody's going, >> you know, we've been seeing in reporting this consistently, and it's even more mainstream now that cloud computing has opened up the aperture of the value and the economics and also the technical innovation around application developers coding faster having the kind of resource is. But it also created a CZ creating a renaissance and networking. So the value of networking and application development that collision is coming together very quickly. So the intersection you guys play. So I'm sure this will resonate well with customers Will as they try to figure out the role the network because against security number one analytics all the things that go into what Sadiq they care about share data, shared coat all this is kind of coming together. So if someone hears this story, they'll go, OK, love this snap around store. I gotta I gotta dig in. How do they engage you? What do you guys sell to them? What's the pitch? Give the quick plug for the company real >> quick. Engaging with us is, you know, is a simple issue. No, come to www snapper out dot com. And you know, you know contacts are up there. You know, we were currently obviously we're a small company. We sell direct, more engaged with, you know, our first customers and deploying our product, you know, right now, and it's going very, very well, and, you know, it's a PSE faras. You know how you know what and when to engage us. I would say you can engage us at any stage and and value whether or not your architect ing a whole new network deploying a new data center. Obviously. Which is, you know, it is an ideal is built from the ground up, but we add value to the >> data center preexisting data saying that wants >> the modernizing data centers. I mean, very want >> to modernize my data center, my candidate. >> So one of the biggest challenges in an existing data center in when one of the biggest areas of tension is at the top of rack switch the top of racks, which is where you connect in your you know, your your application assets, your servers are connected. You're connecting into the into the, you know, first leap into the network. One of the challenges there is. You know, Dev ops engineers, They want Teo, you know, deploy containers. They want to deploy virtual machines they wantto and stuff move stuff, change stuff and they need network engineers to help them to do that. For a network engineer, the least interesting part of the infrastructure is the top Arax. Which it is a constant barrage day in, day, out of request. Hey, can I have a villain? Can have an i p address. Can we move this? And it's not interesting. It just chews up time we alleviate that tension. What we enable you to do is network engineer can you know, deploy the network, get it up and running, and then control what needs to be controlled natively from their box from debits tool chains and allow the devil ups engineers to take control as infrastructure. So the >> Taelon is taking the stress out of the top of racks. Wedge, take the drama out of this. >> Take that arm around the network. Right. >> So okay, you have the soul from a customer. What am I buying? What do you guys offering? Is that a professional services package? Is it software? Is it a sad solution? Itself is the product. >> It is software, you know. We are. We're selling a network operating system. It lands on, you know, bare metal. He liked white box switching. Ah, nde. We offer that as both perpetual licenses or as a subscription. We also office, um, you know, the value and services around that as well. You know, Andre, right now that is, you know, that is our approach to market. You know, we may expand that, you know, two other services in the future, but that is what we're selling right now. It is a network operating >> system down. Thanks for coming and sharing this story of SnapRoute. Final question for you is you've been in this century. While we've had many conversations we'd love to talk about gear, speeds and feeds. I'll see softwares eating. The world was seeing that we're seeing cloud create massive amounts. Opportunity. You're in a big wave, right? What is this wave look like for the next couple of years? How do you see this? Playing out as Cloud continues to go global and you start to Seymour networking becoming much more innovative. Part of the equation with Mohr developers coming onboard. Faster, more scale. How do you see? It's all playing out in the industry. >> Yeah. So I think the next sort of, you know, big wave of things is really around the operational. But I mean, we've we've we've concentrated for many years in the networking industry on speeds and feeds. And then it was, you know, it's all about protocols and you know how protocol stacks of building stuff. That's all noise. It's really about How do you engage with the network? How do you how do you operate your network to service your business? Quite frankly, you know, you should not even know the network is there. If we're doing a really good job of network, you shouldn't even know about it. And that's where we need to get to is an industry. And you know that's that's my belief is where, where we can take >> it. Low latent. See programmable networks. Great stuff. SnapRoute Dominic. While no one is dominant industry friend of the Cube also keep alumni CEO of Snapper Out. Hot new start up with some big backers. Interesting signal. Programmable networks software Cloud Global all kind of big Party innovation equation. Here in Silicon Valley, I'm showing for with cube conversations. Thanks for watching