 Okay, we're back here live in Las Vegas for SiliconANGLE's exclusive coverage of Amazon Web Services re-invent conference. Amazon is continuing to roll down the path of dominance in the public cloud and just absolutely extending their lead light years ahead of the competition in our opinion based on what we're seeing here today and it's just continuing innovation. And now moving into the enterprise. But they've had a lock on the startup market going back to when I originally was with those guys launching it back in the early 2000s. But the developer community loves Amazon because it's fast, it's low cost, and we're here to feature a startup here. We've got Jonathan Chu, Collaldes, co-founder and CEO, and Jordan Potter, co-founder and chief operating officer. Guys, welcome to the cube, SiliconANGLE's cube. It's good to be here. So startups are great. I mean startups are bootstrapping. You guys won an award at the TechCrunch conference. Disrupt. Are you mad? Did you win an award? You launched there. We launched there. You launched there. But you guys are a great example of, you know, how Amazon kicks ass so much with the way they can just get people up and running fast. So let's just go into it. Talk about first to company you guys do. You guys target engineers, test and dev, QA. Talk about the solution. Then let's talk about how you guys are wired into the cloud and how that worked for your customers. Yeah, so quality is a cloud automation testing solution that helps companies run their automation tests extraordinarily quickly. And the goal here is to maximize engineering efficiency especially in the valley, right? Engineers are very expensive and also they are the core of your company and they get work done really quickly. So the faster they get out code. It's the core labor. I mean, with clouds basically almost free at this point. I mean, Amazon is going to drop prices. That's the core asset. Exactly. It's people, open source is free. You know, software is free so the cloud is a little bit expensive. But yeah, continue ahead. So if you can make your engineers much more effective that's actual dollars in the bank, right? Yeah. So talk about what the product is just give a quick overview of what the product is the value proposition and why someone would contact you guys. Sure. So there's a few things that we focus on at quality. One is increasing your test suite time by 10, 20, 100 times depending on the parallelization level you're comfortable with. And this actually wasn't possible until services like Amazon EC2 where now computation is so ubiquitous and so cheap you can actually just throw computation in the problem and take, you know with one of our customers 80 minutes worth of tests down to six minutes which is extraordinary. And the big thing that we want was we can actually verify code before it goes into the code base. So no bad code can go in. So for another customer we took their 40 build breaks a month down to zero, which is huge. So you guys basically accelerate the identification of bugs basically and can get code tested. How do you do it? What's the secret sauce? What's the secret sauce for yours? Everyone's got the secret sauce. Is it machine learning? Is it math? Is it algorithms? Is it just process? What's the, you know to tell the exact thing or something. It gives a taste of it. Very, very great distributed systems and also operating systems knowledge that makes things shard really well and run really quickly and also utilizing AWS and EC2 very effectively and helping manage that particular cloud. Okay, so name some of the customers you guys work on. I know you guys can say a few names and then we'll go into some of the use cases around you know, how someone would use you guys. Yeah, so the largest name we can actually say is one Kings Lane. We do have a very large file sharing customer as well as a, I guess you would say a sharing economy customer that we also support and some of the big wins we've had for them, one of them had their testing times taken from 80 minutes to six, which for them translates into roughly a 10 or 15% productivity increase which is like 20 engineers, right? So the old days, I'm all, you guys are young guns. I'm like the old guy close to 50 in the late 40s but back in my day, you'd have to lay out some serious gear to do test dev, right? So now with virtualization in cloud, a lot of coolness can happen there. So describe some of the coolness that you guys do. Is it parallel machines you guys using virtualization? What are some of the coolness that allows you guys to do this at scale? Because remember, people want to stale possibly for use cases that might be at certain scales and you can't get gear for that. So talk about how you guys boot that up. John, you want to handle this? You want to try that? I would say all of the above. For one company in particular, the biggest customer of ours, the file sharing one that we shouldn't actually name but I think you know who it is. For them, we're actually managing 200 large EC2 instances on Amazon simultaneously, which is just a lot of computation, which I think there's a lot of secret sauces involving quality, but in all honesty, 80% of the solution is just throwing computation hardware at the problem. So I think of all things, that's something very exciting that we're doing. So you're managing the, say that number again, how many instances? 200 right now and it will be going up very, very quickly. So do you guys run spot instances to spin up compute for them? You guys, these are actually reserved instances, but that actually allows us to dynamically scale. So at the max, it goes up to 200 instances and when they're not using them, it automatically scales back down. Yes, definitely catering to the Amazon philosophy of you have competition when you need it and you pay for it by the hour. You guys taking advantage of auto scaling on that? So quality actually manages the scaling for you, depending on what you need from your test runs. So as of right now, we're doing it manually, but now we're becoming more and more comfortable with Amidon AWS software. And so with that, we're exploring other services as well. Yeah, we actually don't have a need for auto scaling because we know exactly when you need a certain number of machines and exactly when you don't need them anymore. So we have it as perfect as it can get. So it's not a big feature for you guys, you guys can do that manually. Okay, so talk about some of the use cases where you've been successful and some of the ones you think are going to be the bread and butter for your business. Because obviously I can envision the scale of being pretty significant for you guys. But right now, where are people using you? Why would someone come to you? What's the use cases of the engineering teams? And what are they doing? Engineering teams that really care about their efficiency have some kind of agile process, but also have large testing times, tend to find lots and lots of value from us. And we've also noticed that teams that have grown very quickly, a lot of times have the test suites that are large, but could find tons of value from quality since they haven't actually done much work around them themselves. Give me a number of like, size of the teams you guys work with. Engineering teams. Yeah, so most of our customers are between 30 and 200 engineers. That's not including like QA or other roles, just plain engineers. And most of them have actually been around, they're most relatively recent companies. So most of them have been around since at least 2007 or 2006. What are they saying about the service? They're like, they love you guys. They say, hey, we can't live without you. Asking for the norm or an Amazon like products. It just works. Most of them are saying, finally, I think developers have gotten a lot of attention and a lot of spotlights. We're getting new frameworks, new libraries. We're building this phenomenal community. But I think tools have not kept up with the fast pace of developer community. And so a lot of people are saying, finally, something actually exists that works for me that's pleasant to use and simple to maintain. It's actually a joy, right? We got a standing ovation when we actually, so one of the companies switched their entire engineering of a hundred people over onto the service and we got a standing ovation when they actually presented it. It's like, you guys are using this now. First of all, we love to hear stories of that. We work with companies like ServiceNow and Splunk and their customer bases are so loyal to them like when they launch a new product because when you think about Splunk and State ServiceNow, Splunk in particular is much more notable in the big data world. They took essentially data waste log files and basically took that pain away from slogging through log files. I mean, it doesn't look good on paper. Oh yeah, yeah. But what it does for the customer. So you guys seem a little bit like that where you're solving some pain today for customers at the same time, possibly enabling. So I want to ask you, what is that enablement for the engineering teams? Okay, you take the pain away through the automation like Splunk, they're in customers because they were free to do other stuff. It ended up becoming a huge platform. They ended up going public. So what is your next step? When you take that pain away, you start automating, you start automating some of the test. What's that next enablement? What do you guys, what's your vision? The ultimate vision for us is to make engineers as effective as possible. So I always like to say when I was in college, right, at Carnegie Mellon, I wrote an operating system in a matter of weeks and you can't do that in industry. You just can't because there's so much process in place. There's deployment. You have to go check for bugs. If you can make engineers as effective as that, then you can make the entire world could move forward. Maybe two times, three times faster than it currently is. Technology could advance that much faster. Now, I don't really think it's possible to ever get to how it was in college, but you can definitely make tremendous gains. And for us, our vision is just to make engineers so much more effective that all they have to think about is coding and that's it. All right, so that's good. So I'll ask about the operating system after the interview because I wrote one in the 80s, but that was different. It was on a Vax, but that's a whole other story. I want to ask you though specifically, what vision around the code? Because that vision is definitely awesome, right? But let's talk about what tech will you add next? I mean, in your mind, if you knock this down right now and you get that automation going, you save a lot of time for the engineers, obviously there's going to be creativity. So there's got clearly a more of a feel good benefit, but specifically, what tech are you eyeing? Like, okay, when we're done with this, we're going to bolt on some other tech on top of it. You have any thoughts on that? What do you see? There's no really right answer on this one, but it's more of the vision. That's fair. What's next? I think we should be careful about leaking too much secret sauce, obviously. But I think the next, we'll be open about the next big step for us. We're very excited about continuous deployments. Since we have so much technology for like managing these virtual machines, provisioning them to be like your production environment, so on and so forth. You can read a lot more about on qualitycode.com. But beside all that, with all the technology, it's not too far-fetched to think the next thing for quality is actually managing your continuous deployment. So talk about the size of the company. Will you guys add, obviously, tech crunch disruptors, kind of a startup, early stage startup, you guys funded, you have VC funding, you boost drafts, what's the head count, what's the plan? So we're currently seven people and we've been funded, VC funded, since day one. From who? Which VCs? So FF Angel, it was the first ones in. Index, Felices, the web investment network, and Ray Tonsing. Awesome. Well guys, congratulations. I think you're on something really cool. Like I said, I totally agree that, I've always said the silicon angle and the stuff we're doing with the Q, it's all about the people. And we had the chief security officer on from Amazon and he talked about security paradigms. We're coming back down, everything's about the people. And in these days, with the connected web, making value for people, freeing them up, automating away the hassles, that's the future. So congratulations, big, big fan of your work. We're here live at Amazon. We'll be right back with our next guest after this short break. Hot start up here inside the Q, venture backed, funded, seven people, what's the growth rate? What do you guys want to get to next year? Any hiring engineers? We are definitely hiring engineers. Where's your headquarters? San Francisco? San Francisco, right next to the Caltrin station in Selma. And you went to Carnegie Mellon, where'd you go to school? Stanford. Stanford, okay, not bad schools. They have decent computer science programs there. I've heard of that one before. Okay, we'll be right back after this short break. Got some alums from Carnegie Mellon, Stanford, great programs. This is the new generation right here. This is what it's all about at Amazon. This is a generational philosophy, DevOps, Amazon, innovation. We'll be right back at this short break.