 Okay, we're back live in San Francisco, California for Node Summit, the event where Node.js is front and center. The first Node Summit, it's an inaugural conference. I'm John Furrier, the founder of SiliconANGLE with Alex Williams from SiliconANGLE with our next guest, Glenn Loheed. Welcome to theCUBE. Thank you. So you were going to have some pretty exciting stuff around DevOps. We just launched today our new vertical publication called DevOpsANGLE, where we're going to be doing in-depth coverage of DevOps. And as was pointed out earlier, you've been upon where you come from. So you have an interesting development around automation. And it's a big area, you know, configuration management, automation, making all that stuff work automatically, self-healing networks are out there and you've got all the issues around provisioning and deploying, big hot button. Give us kind of the state of the union around the marketplace and what you're developing. Well, for us, we tend to integrate with the technologies that are in that space. So like the puppet, the chef, the end stratus guys, really our specialty is more in the monitoring side. So really we integrate well with those guys because what we're doing is we're providing the visibility into the server and some of the application services to be able to trigger those automation programs. But one question I have is about your tools and such and looking at IT today. And IT today, you know, is not, the people are not trained really for this new environment as much. Yeah, how, where's the disconnect? Where are you starting to see some, you know, some abilities for, you know, for this new adoption to really take off? Well, I think the thing is, is that where we've seen is that, and for us, the hardest sell for our product is sort of the server admin guys that are over the age of 35. Because they're so used to products like Cacti and Nagios from a monitoring perspective. So it's hard for them to really get over that hump that, oh, there's something new that can automate this stuff for me, right? But we've seen sort of all the younger guys being able to adopt this stuff very quickly and partially because they don't have the sort of decades of experience within that server environment. And as the infrastructure as a service has come forward more and more and more, running a server is really getting easier. So, you know, the ability for those guys to dig into that server isn't as necessary. So that's really where those experience came from from those older guys is that, you know, they actually had to get there. They actually had to go down to the rack and start pulling through this stuff, right? So that's where we, you know, for us that's where we see the opportunity is being able to provide much easier solutions for these guys. So, like you're saying, John, DevOps and OpStep, right? I mean, like the older guys are just trying to, hey, what the heck is this stuff? We've got systems guys, and we heard from Theo Schloss-Nagel who's Ops bringing up the devil's advocate side of it is that, you know, Ops and systems, you can't, they aren't supposed to break. Nope, code breaks, code says bugs and they kind of iterate, you know, developers, developers, developers and iterate, iterate, iterate. But, you know, you're running systems all day long. You know, there's a little conflict there. So, you know, that's where automation really makes sense, right? So how do you make things more reliable in that dynamic environment of configuration and management? Well, I think the thing is that, you know, that's where, you know, companies like us and those guys from like Chef and Puppet and Instratus can really help, right? Is that we can provide all of that opportunity to make those things happen for them, right? Whereas then they can really focus on the application itself. So, let's talk about your product. So tell the folks out there what you guys do and what you make and specifically just tell them what the product is then we can talk about some of the use cases. So, what we do is we're a hosted monitoring service. So we look at the machine level, the OS as well as the application services layers and we pull all that data back, process it, create some derivative metrics, start to visualize it for these individuals and then you can put all of your alerts on it and be able to be monitoring very quickly. And so for us what we do and our specialty really is, is that we have a single line install. So, it's a W get or curl command and what that does is that gets embedded into stuff like Puppet and Chef and Instratus and allows you to be able to spin these things up and then be monitoring and that's really our specialty, be able to be monitoring those instances from within 45 seconds of them being spun out. So that's really where- And who's buying this thing right now? Who's using it? Where are you at in terms of the company? Okay, so we've just sort of launched publicly. We've gotten a bunch of partners with us including Joyant that we're partnering with to push our product out there. The base of our product and a lot of the development came from a bunch of social game developers. So those guys really have that issue where it's like we gotta spin this stuff up and spin it down because we're dealing with sort of that dinner hour crunch on their game. So really they don't need those 50 servers the whole time but during a specific time when people come home and start playing that game- Come up from school. Partially, yes. So they get crunched but they really want to be able to monitor at the same time, be able to be pulling the statistics back off of those servers but using traditional solution stuff that was built in the 90s like Nagios first release was 1999. So those technologies don't work in those environments and so that's really where we see our opportunities to fit in and innovate in that area. So tell me a little bit more about the fit with Puppet and Schaffen and Stratus. Okay. Can you explain that? So simply the thing about Puppet and Schaffen and Stratus those guys are automation. So really what they're looking at is making it really easy for you to deploy your network, be able to manage those things, be able to put updates and push updates through to those guys. So what we do is that we've got the simple one line that can be part of like the recipe with Chef or part of your configuration with Puppet and it's that simple to get monitoring. Whereas before, monitoring was tons of configuration, setting up your processing server, we take care of all of that. Okay. So it's all taken care of and again, who are like the core audience that you're trying to reach right now? I would say for us the easiest cell tends to be on the dev op and not necessarily the op dev. Yeah, I would say so. The thing is is that those guys that are traditional hardcore system in operator type guys, they're a little bit harder sell because they're used to very traditional technologies in this way. We saw a lot of greatness come out of with Amazon. Obviously the whole history of Amazon is pretty significant. So right scale come out with that front end made it easier. And then now as we move into the cloud with other simply front ends like puppet and chef and others are creating that simple environment. What's changed or anything's changed over the past three years in this market? It's been pretty dynamic from what I could see. Not a lot of proven solutions. It's evolving. Can you share with us your vision of, or can you share with us your view of what happened over the past three years in terms of that market change and kind of what's in front of you? Well, I think that's the thing. I think we've seen, you know, several years ago we were still in a phase where your business would grow organically. And so your growth curve would obviously still be in that sort of L shape. But unlike today where we've seen sort of viral and social growth and moving from being able to, you know, gain 1,000 users to being able to gain 10,000, 20,000, 100,000, a million users in a day. You know, these products have had to evolve to deal with those situations. And that's where that sort of automation has come in and those guys have really had to focus on being able to make sure that they can scale and work within that environment. Has the number one issue been provisioning servers and networks or all the above or any one area that's jumping out at you? Or is it? I mean, provisioning is definitely an ongoing sort of concern. And that's where I think we fit in really well is that we can provide the monitoring as they continue to provision. So what's the node JS angle for you guys? So for us, there's sort of two components. We're a user of node. It functions within our system as our internal API. So pulling data from the processing layer into our UI. We also use it for our external API so anybody wants to pull data out of our system. They can do it by a node JS. You know, as it turned out and as it sort of became like this cool little virus within our organization, one of our developers said, oh, you know, we had a feature that people really wanted, which was sort of this network connections, TCP, SSH, HTTP. So he prototyped it very quickly in node and it turned out to be so stable that we just kind of kept it that way. So it's been continually creeping in as we've been using it forward. And then on the second angle is that with our partnership with Joand, we're pulling via their API the detrace data that's being coming out of node JS on the HTTP layer. So we're grabbing that, starting to visualize it and allowing people to put alerts on it. So you're one of the tools that's integrating into detrace, though. I mean, that's definitely one part of what we do, absolutely. Well, that's what they were talking about. They say that there needs to be more tools available around detrace. Yeah, and I think we're gonna continue to keep innovating in that area. I think that there's so much opportunity with the amount of sheer data that detrace can pull out because we tend to look at stuff a little bit more in the 10,000 foot level. If you look at how amazing the stuff that Joand's doing on the detrace side, it's like grain of sand compared to the 10,000 foot level. So sometimes it's really overwhelming to look at, but if you can get the alert at the higher level and then dig in, I think it's really valuable. Right, so I guess if I can see why you're using node JS, it seems like it caught on very quickly, but what are some of the other real reasons why you're using it? Well, the thing was is that we weren't completely sold. And within our API, we actually started AB testing. So we AB tested against PHP, we AB tested against Python within our internal API. And it just turned out that node was actually the most effective data mover for us. So we tested it and it proved itself to be the best solution for us. So for us, that's really why we jumped on it. It was just the best solution. So do you have any funding? Are you funded yet? We've been bootstrapping and doing it ourselves. What's your background? All over the place. Tell us a little more. Come on, share it, tell us. Well, it's mostly on the creative industry side. So I did a bunch of movies and a bunch of television series and a bunch of music videos. Tell us some of your work. You're a natural for the cube then, what do you think of the cube? The lights are very bright. No, like I did a ridiculous amount of filmed entertainment but the thing was is during that whole time, I was always trying to push on the new media side and on the gaming side. And I was one of the guys that helped create this TV show called Electric Playground, which is a show that reviews video games. And it was really interesting because it's actually one of the first television shows to evolve out of a web property. So we started with the web property and then moved into film and television. So I started as a web guy and then moved into filmed entertainment. And then as I sort of moved through film and entertainment, I started moving back into web and gaming. So my last company was a company called Dime Rocker, which we tried to create this really cool platform to deliver 3D games to Facebook. And I think we were just a little bit ahead of the curve on that one. And then during that whole experience, we couldn't get the statistics out of our servers. And so it kind of evolved into me finding a way to be able to pull the metrics out of our servers to be able to monitor them. So thus DevOps, but you know, you began the DevOps journey. Yes. We talk about on theCUBE here, we take all the other events, the big data events where there's no, in the big data world, the discipline is interesting. You have a lot of creative meets math jocks to programmers, all kind of rolled into one. So you have that interesting talents, not just peer developers. It's the new skill set, right? Yeah. Being versatile. Well it was really interesting because it was. I flowed from web to like that creative industry stuff and then back from that creative industry right back into web. From Hollywood to the Valley, to Hollywood to the Valley. But I'm in Vancouver, so it's from Vancouver North. That's a big film hub. That's a big film hub. It's a massive film hub. Yeah. So my final question, Glenn, is what's next? What do you see out in front of your house? So you got to start up your bootstrapping it. You probably generate some cash or financing or that comes in. What's next for you? How do you see this market evolving? What's the vision? Well, I see, you know, I continue to see how the sort of social and viral growth is going to continue to affect how businesses are built. And I think for us, we just want to be able to help those businesses grow and have them focus more on the application and keeping it stable as they grow. And then for us, just being there to support them through the monitoring side. Well, great to chat with you, Glenn. I'm Glenn Loheed here inside theCUBE. We're live at Node Summit, where all the action is happening in the first conference of its kind, inaugural conference around node.js. Real successful framework with JavaScript, doing well, great performance. Thanks so much for coming to theCUBE and we'll be right back in five minutes. Thanks.