>> Presenter: theCUBE presents UiPath FORWARD5 brought to you by UiPath. >> Back to theCUBE's coverage of UiPath FORWARD5, 2022. This is theCUBE's 4th UiPath FORWARD. They're mining automation gold here at the conference and in the customer base and we're creating Cube Gold, Dave Vellante and Dave Nicholson. Cheryln Chin is here. She's the vice president of Global Alliances at UIPATH. Sameer Bohra, who's the director of Information Technology at Deloitte. Good to see you guys. >> Great. >> Thank you. >> Now normally we would be talking about, how Deloitte's out, doing its thing with its customers, but this is actually a case study on Deloitte's use of automation and UiPath, so that's cool. You not only partner with the GSIs you actually sell to them as well. Okay. What's that all about? What's your relationship like? Why don't you start there? >> Absolutely. So we're thrilled to be here. Thanks for having us. And really appreciate Sameer being here with us. Deloitte was an early adopter of UiPath not just as a partner, driving innovations and investing in getting skilled and building the capability. They were the first to become the US and certified partner network investing in thousands and thousands of skilling up their consultants and resources to help us address our customer needs together. But it's not just about being a great partner it's being a customer with what they've done and built their own business around UiPath and the automations. We've got an amazing story to tell you about today that we'd love to share. >> All right, Sameer, let's hear it. What's the story? What was the catalyst to bring in automation, UiPath? Where are you applying it? Where'd you start? >> Fantastic, well first of all, thanks for having me here. >> You're welcome. >> I'll start this journey with the predictions that we were making at some point. So, Deloitte, as a company, we are in the business of predicting the technology trends. We have been tracking automation as a trend for quite some time, and we have been following how this industries going to come along. And we then started placing our bets not just on the technology, but on the vendor as well in this case. Right around 2017, 18 is when we started kind of implementing automation with UiPath for our internal purposes. And as it happens, different constituents in our member firms started doing it at the same time without kind of consulting with each other. But the surprising thing is that we all ended up with the same results. We all ended up with UiPath. We all ended up using the same technology set and it was good that we all made the same choice because we would then all get along with it together. So we started our journey kind of disintegrated in a way and then we came along quickly all together. We then have COEs in each of our member firms, or at least the big member firms. And around January last year is when we signed an enterprise license agreement with UiPath that really brought some of our mature COEs together. And now we are kind of utilizing the product quite well. We are exploring the benefits of that ELA brings to us. So that has been our journey so far. Just in terms of some numbers, we are more than 400 millionaires saved for our member firm. We have hundreds of processes that we have automated. I'm kind of losing count of that already. And we have a good 70, 80 member team members across our three mature COEs that are constantly automating day in and day out. So there's a lot in terms of the history and there's a lot that we are looking forward to. >> Can you paint a picture of sort of where you're applying these automations in your business and maybe double click on that a little bit? >> Absolutely. So when we started our journey, there were some candidates right off the bat there were some of our enabling areas where we were looking at for instance, finance our talent which we also called as HR. Those were some of our preliminary areas that we started doing automations for. But another surprising thing is that our first automation use cases were actually contingent solutions that we built to help some of the other big deployments that were happening in the firm. And in absence of any good solution, we said, "Let's bring in RP and let's bridge the gap." And that basically opened the door for us to use automation at a bigger scale. So it's enabling area, talent, finance, business operations. Those are the prominent areas, marketing, chief culture, those are the areas that we are applying it. And then our services on the other hand are using automation as well because we need our services people to be armed with the valuable time to be able to invest on our clients rather than, being stuck in repetitive mundane tasks. So we are pretty much applying it all over the board now. >> So as director of IT at Deloitte, I'm curious about how this process works for you. You've heard the term drinking one's own champagne. >> Yeah. >> When you are looking... >> 'or jog fooding, but okay. >> I was trying to be polite, right? One throat to choke one bat to pat, back to pat. Are you immediately and at all times under a microscope when you're deploying something internally because someone else in Deloitte is thinking, "Okay, let's see how this works for us. Because if it works well, if we gain expertise, we can turn this into a line of business to help our clients." Is that something that starts day one? Or do people come to you six months into a project and say, "Hey, I hear you have something going on. That's cool." What's that look like? >> Very interesting question. The way I would like to describe it is we have a symbiotic relationship between our internal COE and our client facing teams that are out in the market selling automation along with UiPath. And the way that symbiotic relationship work for us is when we are doing anything interesting in terms of an automation use case, and we have many that I can talk about, we do have this constant connect with our client facing folks where we tell them about the use case. We tell them about the problem that we are solving and the way in which we are solving that problem. And in many cases, it generates interest. And then we get into conversations where we see, okay is it an asset that we can build out of it? Or is it simply a client use case that we could burn and implement and apply somewhere? So that's one side of the symbolic relationship. The other side is what our client service folks are seeing in the market. So when they see it, they come to us and they tell us, "Look, we see such and such client doing this and we did it for them. We should think about doing this in Deloitte and for ourselves." And then we say, "Fantastic, let's do it." So it's both ways. >> Dave: Both ways. And the fact that it is both ways. There is not that sense of pressure or you know that I'm under a microscope. It's all one big family. >> How do you measure success? >> It's a pretty interesting question again, success is subjective, right? When it comes to automation the typical metrics that people use to define and describe success is how many hours you have saved or how many hours, at least the way we use it how many hours you have reinvested, right? So we started with that as our measure and for some time that was really our measure of success. But lately we are seeing a change in that we are now shifting more over to other matrix like cost avoidance. So for instance, your firm is growing at a certain pace. Do all your enabling areas need to grow at that pace? Maybe not. Maybe we can avoid that cost and maybe we bring in more automation to support that. So cost avoidance is kind of emerging as a bigger matrix for us now, especially given that all low hanging automation fruits have been plucked. That's a big one we are looking at. I think the other matrix which is a bit difficult to measure directly is the employee satisfaction. There's somewhere I read that if you want happy clients you need to have happy employees first, right? And one way of making your employees happy is to give them the task that they really value that they really like to do. Now, again, being a professional services firm are ours are people's, our is our currency, right? So we want to give them as much of their valuable time back so they can invest it in their client facing activities as opposed to, you know doing mundane and ones. So those are some of the matrix and measures we are looking at. >> So I'd like to dig into that a little bit. If I could Sameer. So, aren't hours saved sort of related to cost avoidance? Is that an input to the cost avoidance calculation, if you will? >> So yeah, so yes and no. And the reason I say that is because yes, if you do the math, yes, it makes sense, >> 'not that it's direct. I understand it's not a direct relationship but it's somewhere related. Is it not? >> It is related in the sense that our saved is an immediate measure of automation, right? So if me as a practitioner, if I can hand over a task to the bar, which can take off five hours out of my week, that's an hour saved right away. But cost avoidance is more like, "Hey, I have these 10 engagements that are coming up. Do I need to amp up to meet boost end engagement or I simply amp up my automation, right?" So that's more around the cost avoidance piece. >> Okay. So there's an algorithm there. >> Yeah. >> Which makes sense. Do you find, so in other words, when you save hours at some point it's going to translate it to headcount avoidance. Okay, are you finding that when you run a project if you can automate that project, that the proportion of savings is greater on that automation of the project than it is for those sort of hours saved? I'm just sort of curious as to what the balance looks like. Is it like overwhelmingly speeding up the project? Is the real benefit there? I'm just kind of curious. >> There's absolutely a benefit there. With automation, you can obviously speed up your projects, you can do more with the staff and the team that you have. So that's definitely something that helps us a lot both internally and I believe on the client facing side as well. >> Okay. And just put my CFO hat on. Let's, so are those internal resources or are there sort of out of pocket expenses? In other words, it's the hard dollars that I don't spend or is it resources that I can deploy on another project or both? Or both. >> For the most part it's the resources right? >> So it's okay. >> Yeah, it's the resources that you can now have them do more value work with more clients as opposed to have them do many task at one place. >> Okay, I'm going to just keep going. So that's a productivity measure in my mind anyway, so I just like to keep peeling the onion on the metrics. So I would at some point, so the two things the cost avoidance and the employee satisfaction I would ultimately as the CFO want to see that show up in terms of productivity increases and decreases in turnover. And you probably don't have enough experience yet to measure that. But ultimately, isn't that where you want to go? >> I think that's essentially where it's going and I think that's the way it'll probably go for pretty much everyone who is in this journey of automation at your CFO will eventually want to look at, okay what after this investment, where is it leading us? So that's definitely the direction we are also heading. >> Yeah and so productivity revenue per employee, is that a good starting point? Maybe you get more sophisticated than that, but... >> Yeah, that's probably a good starting point. >> UiPath revenue employees about 250,000, which is pretty average for software companies. Now, maybe it's because they're investing more, but at some point I'd like to see that tick to 350,000 anyway. >> Yeah. >> I Digress. >> And we are on that journey where we are essentially looking to arm everyone with a bot right? There's a philosophy and UiPath around a bot for everyone. We are pretty close to getting to that stage where everybody should be able to leverage the technology. We shouldn't be limited to a certain business unit or certain pockets within a business unit. >> I want a bot. I do, I want a bot, I'm getting a bot. >> I wish I have a bot. >> I would, yeah, I want to a bot and I want to give that bot a very clever name. That's like you're thinking of naming bots. So are your activities evaluated in completely independently as sort of your own P and L or do you get credit for some of that symbiotic relationship that's developed? Because I can imagine a situation where you deploy something intelligent automation and you get a yield that translates into a practice for your firm that brings in a bunch of revenue with a bunch of satisfied customers. Do you get credit for that? Or is it like, no, no, no, no. I wouldn't >> I would love to get credit for that. But again, it's all in the family. It's all one big family. At this time we are simply focused on bringing the right use cases forward for our client facing folks and the other way around. So we haven't got into that stage as left. >> But you need to deliver standalone value. You're evaluated that way. >> And this COE. That's what we are evaluated upon. The matrix that I talked about earlier around cost avoidance, number of our saved employee satisfaction. Those are some of area that we are being rated upon. And that's across all our COEs. >> Oh, surely congratulations on landing Deloitte as a customer and of course a partner. And I'm sure there's big things in the future. We'll give you the last word, bring it home. >> You know, the takeaway here is we are leveraging partners like this who are going way beyond just automating processes for the sake of process and our save the using this to build their business make their consultants more productive and really driving profitability for the business. So really the automation flywheel going beyond that's really trying to fuel digital transformation by taking this, they make it go faster, more profitable, more agile, and they become an amazing customer and an amazing good market partner. >> Yeah, you guys take this pretty seriously behind us there's this, I don't know what you call it but this clouds floating above it. If you walk through there, there's some really inspiring commentary. And so I encourage you to do that if you're here at the show. All right, thanks guys, appreciate it. >> Thank you. >> Thank you. >> You're welcome. All keep it right there Dave Vellante and Dave Nicholson will be back at FORWARD5 UiPath customer event from Las Vegas. We're live right back. (soft music)

>> Narrator: Live from San Juan, Puerto Rico It's theCUBE, covering Blockchain Unbound Brought to you by Blockchain Industries (upbeat music) >> Hey, welcome back everybody, we're live in Puerto Rico for the cryptocurrency, global blockchain, decentralized internet, Cube coverage in Puerto Rico part of Blockchain Unbound. I'm John Furrier, host of theCUBE here, also co-founder of SiliconANGLE Media Inc. And, we're here with a first Cube ever, father/son Cube segment where we're going to kind of break down a summary of the show but mainly get the take from a 22 year old. Here with me is my son Alex Furrier who's been doing the schedule and greeting all the guests. Alec has been also demoing our platform that we haven't formally announced but also Not that we have to but it's out there. theCUBE platform, all the back-end data Because it really is getting everyone here excited So, Alec, welcome to theCUBE. >> Thanks, great to be on, finally, after all these years (John chuckles) to be on, it's an honor. >> Well, thanks for all the hard work you did on the schedule but you're a young gun, you're 22 years old. This is an exciting crypto world for your generation. What's your reaction to the commentary you've heard, the stories you've heard, what's the young perspective on cryptocurrency, blockchain, what's the view? >> Totally, it's a totally crazy culture, right? So, there's a very big influx of young talent and talented minds at that, right? And, this is really changing the revolution landscape. It's accelerating the tech. These ideas are being freely shared whereas before there was bottlenecks in the collaboration aspect of the technological field, right? >> You're a gamer, I know that so you're the young eco-system You don't care about data lakes and data centers and cloud computing. What is your generation look at this as an opportunity? What's exciting about it? What's the perspective? >> Well, there's multiple perspectives. The main two I say, there's multiple perspectives. Main two, is one, there's a shit ton of way to make money. And you know, is there a scam? Is there a risk for my business? You know, blockchain is involved. And there's a little bit of that mumbo jumbo going along. But then, there's also the other side that are really into it and really applying the tech and know that this is the best way to collaborate with peers >> What's the coolest thing you've seen? >> The coolest thing I've seen is probably Hashgraph which is actually not on the blockchain and competitors of the blockchain. And that's actually increasing speeds and pretty much making the tech, the back-end infrastructure better. >> So, you dropped out of UCSB, you're going to maybe go back to school but you're also working as a product manager for our crypto project for SiliconANGLE Media, theCUBE, Cube Network, you were giving demos. What is, what are we doing? How would you explain what we're doing? And, what was some of the reactions to the demo that you were giving? >> All great reactions so far. People are very excited what we're building which is a reputation centrality metric. And, what this does, is allows us to track, what users are talking about, and where they're talking about it. And actually, rank their reputation leaderboard rankings by topic, by frequency, by impact down reverb in the entire network. And that allows us to appropriate connections between two people who have different social, culture and professional topics that they talk about. And allow them to create more value for the entire platform, for the community and more importantly, themselves. >> What is, what does that mean, what problem are we solving? >> So, we're solving the Facebook ad word problem of the old generation which is you as a user do not own your data. Right? >> Yep. >> So now, what we have is this user base struggling to find the monetary value in their social media platforms. But now, we are actually offering a way for them to reverse the paradigm and get paid for interacting with others, creating with others and contributing to the community through all of their social media outlets. >> What was the biggest thing that people reacted to at the demos, the variety of tools we showed them. What was the number one, couple of things that they reacted to, what jumped out at you? >> So, I would say what jumped out is, how blown away these people are. They really are, you know, elevated in their mindset when they think about these concepts. Because it expands their mind and when they realize that I can go and expand someone else's mind and their mind will essentially contribute to the entire community. And everyone's going to grow from one initial idea. >> What are you working on, the project? Please share with the folks, what've you been working on, what specific things that you do and you're managing. What's unique about the technology? Share some color commentary on the project. >> Yeah so right now we have a couple of projects going, and, for now, I'll just talk about the platform side of things which is the more futuristic vision. Specifically, we're creating trending communities so we could actually auto generate stories based on Twitter API data, right? And also, our own platform has even more complex metrics which we'll be rewarding people for, so people will get rewards for using our platform more than the Twitter. But we could still have native content versus in-network content being weighed differently. And so, what we're doing is routing metrics of weighted value with a contextual layer on top through natural language processing and machine learning. >> So, are some people saying "Oh, you're like Steam?" How do you respond to that? >> We're not like Steam. Steam is extremely powerhousey and it's momentum and it doesn't actually do topic weighing Right, so, and we also value attention of the crowd so what we're working on is, what do people influence with their reputation? Whereas Steam, it's like, where do people contribute? How much do they contribute? And so, what we want to do is, we say hey, you know if I get uploads on Reddit that should be weighed in the network somewhere else, right? Instead of having a overall karma, we should have one integrated karmic aspect of a topicality so that if my karma, I'm using karma as an analogy cause Reddit has the up votes karma, down votes karma. >> So what about blockchain, why are we So, how would you explain to someone Okay, you're theCUBE what is the blockchain? What is crypto mean for us? >> So, blockchain, we're using it to add a layer of trust and security to our network. So we want transparency within our network and that means we have to have a ledger for every single engagement, interaction like we tweet on the network, right? >> And the crypto, the token, does what? >> Crypto token will pretty much be able to be cashed out thru Ethereum, right, ERC20 but it would also have a weighted role in our two sided marketplace, bounty ask buy. And, that'll be the main medium of where people identify and exchange their reputation. >> How would you describe out platform to a user out there if they say, what do you like, or what are you disrupting, what aren't you like, what are you guys doing, what you disrupting? And why would I want to use your platform? >> Yeah, so I think we're disrupting, you know, multiple companies, right? And, the one I really associate with is a professional Steamit meets Brave Browser, BAT token versus Steam, right? So, BAT is attention only and attention is valuable. I'm here with you, you have a 20 minute interview with me. That's your attention, that's valuable but it's much more valuable than someone else who isn't interviewing, let's just say, someone who is less fortunate. But, that's also a real time aspect. So there's a time variable, there's a network variable and there's a topicality variable, you know the social graph, you got the interest graph, and then the value graph on top. >> So Alec, so if you had to describe what we do in one sentence, what would it be? Putting you on the spot. >> In one sentence, I would say we would call it, a decentralized media platform with rewards for the user base, based on reputation. >> Alright, my son Alec Furrier is also involved in our crypto project, part of theCUBE network coming soon, house of theCUBE is here, the crypto conference, and what better way to align with the crypto community then demoing our token enabled platform. Congratulations to you, Narendra, Kent, Jeff and the team doing a great job with theCUBE network. Cube alumni are all going to get coins, right? Not yet decided but great work Alec, thanks for sharing. It's theCUBE here, Puerto Rico. I'm John Furrier, my son Alec. Thanks for watching. (upbeat music)

>> Hey welcome back everybody Jeff Frick here with theCUBE. We're at Node Summit 2015 in Downtown San Francisco Mission Bay Conference Center. About 800 people talking about nodes, Node JS. The crazy growth in this application development platform and we're excited to have our next guest to talk about security. Which I don't think we've talked about yet. He's Guy Podjarny, I'm sorry. >> Podjarny Correct. >> Welcome, he's a CEO of Snyk, not spelled like Snyk. (laughing) You'll see it on the lower third. >> It's amazing how often we that question. How do you pronounce Snyk? >> Well I know, obviously people that have never had this start up and tried to go through a URL search. >> Indeed. >> Just don't know what's it's all about. >> It's sort of Google dominance. It's short for so now you know. So now you know. >> Oh, so now you know. Okay perfect, super. First off welcome, great to see you. >> Thank you. Thanks for having me. >> You said this is your second year at the conference. Just kind of share your general impressions of what's going on here. >> Sure, well I think Node Summit is an awesome conference. I think this year's event is bigger, better organized. I don't know if it's bigger people wise but definitely feels that way. It sort of feels more structured. It's nice to see in the audience as well. Just an increased amount of larger organizations that are around and talking about their challenges and a little bit a lot earlier in the conference but a little bit of more experienced conversations. So conversations about hey, we've used node and we've encountered these issues versus we're about to use it. We're thinking of using it so definitely can see the enterprise adoption kind of growing up. That's my primary impression so far. >> Yeah and it's it in 'cause you're a start up but Microsoft is here, Google's here, Intel is here, IBM is here so a lot of the big players. Who've demonstrated in other open source communities that they have completely embraced open source as a method and way to get actually more than the software is getting closer to development community. >> Yeah, agreed and I think another adjacent trend that's happening is ServerList and ServerList has grown ridiculously, by massive amounts in these last while. And Node JS is sort of the de facto default language for ServerList. LAM just started with it and AWS and many of the other platforms only support it. I think that contribution also brings the giants a little bit more in here. The Cloud giants but also I think again just sort of boost the Node JS. As though the Node JS echo system needed a boost. They get another amplifier. Just raise enterprise awareness and general usage. >> Okay, so what's the Snyk all about? Gives us, some people aren't familiar with the company. >> Cool, so Snyk deals with open source security and specifically in Node JS, the world of MPMs. MPM is amazing and it allows us to build on the shoulders of giants and all the others in the community. But there are some inherent security risks with just pulling code off the internet and running it in your application. >> Jeff: Right, right. >> What we do at Snyk is we help you find known security flaws, known vulnerabilities in MPM packages, and do that in a natural fashion as part of your continuous development process, and then fix those efficiently and monitor for them over time. That's basically. >> That's your focus is really keeping track of all these other packages that people are using to their development. Precisely and we're helping you just use open source code and stay secure. The word node is our flag ship and it's where we started and build and now we support a bunch of other systems as well. >> It's interesting, Monica from Intel said that in some of their work they found that some of these applications. The actual developers only contributing 2% of the code 'cause they're pulling in all this other stuff. >> Precisely, I have this example I use in a bunch of my talks that shows ServerList example that has 19 lines of codes. Copies some file from URL and puts it on S3. That's 19 lines of codes which is awesome. Uses two packages which in turn use 19 packages which bring in 190,000 lines of code. >> Wow. >> That's a massive-- >> So what is that step function again? Start from the beginning. >> 19 to 190,000. >> It starts at two? >> 19 lines of code use two MPM packages. They use 19 packages because every package uses other packages as well, and combined those 19 packages bring in 190,000 lines of code. >> Wow, that's amazing. That's an extreme example but you see that pattern. You see this again and again that the majority of your code in your applications especially node is not first party it's third party code. >> Jeff: Right. >> And that means most of your security risks. Most of your vulnerabilities, they come from there so there is a lot of challenges around managing dependencies. I know it's called dependency help for a reason but specifically security is still not sufficiently taken care of. It's still overlooked and we need to make sure that it's not just addressed by security people. But it's addressed a part of the development process by developers. >> How do you keep up? Both with the number as the proliferation grows as well as the revisions and versions inside of any particular package? You kind of chasing a multi headed beast there. >> It's definitely tough. First of all the short answer is automation. Any scale solution has to start with automation. I've got a security research team in Israel that has a vulnerability pipeline that feeds in from activity in the open source world. Some developer opens an issue and gets helps that say SQL injection in some package and that disappears into the ether. So we try to surface those, get it to our security analysts, determine if it's a real vulnerability curated in our database, and then just build that database with your own research but a lot of it is around tapping into community. And then subsequently when you consume this if you want to be able to apply security correctly as you develop your applications Node JS or otherwise. It has to come to you. The security tool has to be a seamless integration with how you currently work. If you impose another step, another two steps, another three steps on the developers. They're just not going to use it. That's a lot of our emphasis is scale on the consumption and the tracking of the database and simplicity and ease of use on the developer on the user side. >> And do you help with just like flagging. Flagging is a problem or is there an alternative. I mean I would imagine with all these interdependencies, you find one rotten apple kind of have a huge impact. It's a huge scale of impact right. >> Absolutely so we do really what our moniker is that we don't find vulnerabilities, we fix them and our goal is to fix vulnerabilities. So we actually, first of all in the flow we have single click, open a fixed PR. We figure out what changes we need to do. What upgrades you need to make the vulnerability go away. Literally click a button to fix it. Put on one bat for everything and then what we also do. We build patches, sort of a little known fact is in the world of operation systems RedHat and Canonical. They build a lot of fixes or they back port a lot open source fixes, and they put them into their repository. You can just say on updates or upgrade and just get those fixes. You don't even know which vulnerabilities you're fixing. You're just getting the fixes so we build patches for our MPM packages as well to allow you to patch vulnerabilities you can not upgrade away. A lot of it is around fix. Make fix easy. >> Right and then the other part as you said is baking security in the development all the way through which we hear over and over and over. >> Build it in and bolt it in. >> The cast in method doesn't work anymore. You've got to have it throughout the application so you said you're speaking on a panel tomorrow. And I wondered if you can just highlight some of the topics for tomorrow for the folks that aren't going to be here and see the panel. When you look at ServerList security. Say that three times fast. What are some of the real special challenges that people need to be thinking about? >> Sure, so you know I actually have two talks tomorrow. One is a panel on Node JS security as a whole and that's sort of a broader panel. We have a few other colleagues in there and we talk about the evolution of Node JS security that includes the platform itself which is increasingly well handled by the foundation. Definitely some improvements there over the years and some of it is around best practices like the ones that was just discussed which is understanding known pitfalls and Node JS sort of security mistakes that you might do as well as handling the MPM echo system. The other talk that I have later in the day is around ServerList security. ServerList security is interesting because a lot of the promise of ServerList is function as a service is that a lot of the concerns. A lot of the earlier or lower levels get abstracted away from you. You don't need to manage servers. You don't need to manage operation systems and with those auto security concerns go away. Which in turns focuses the attackers and should focus you on the application. As attackers are not just going to give up because they can't hack the operating system that the pros are managing. They would look at the next low hanging fruit and that would be the application. Platform as a service and function as a service really increase the importance of dealing with application security as a whole. So my talk is a lot about that but also deals with other security concerns that you might of course any new methodology introduces its own concerns so talk a little bit about how to address those. ServerList like Node JS is an opportunity to build security into the culture and into our methodologies from the early day so trying to help us get that right. >> Alright, as you look forward, the next 12 months. I won't say more than 12 months, 6 months, 9 months, 12 months. What are some of your priorities at Snyk? What are you working on if we get together a year from now, what will we be talking about? I think, so two primary ones. One is continuing the emphasis on fix. Making fixing trivial in the Node JS environments as well as others. I think we've done well there but there is more work to be done. It needs to be as seamless as possible. The other aspect is indeed in this sort of past and fast world and platform and function as a service. Where increasingly there is this awareness as we work with different platforms to the blind spot that they have to open source libraries. They fix your NGX vulnerabilities but not your express vulnerabilities. I sometimes refer to MPM packages or open source packages as sprinkles of infrastructure that are just scattered through your application. And today, all of these Cloud platforms are blind to it so I expect us at Snyk to be helping past and fast users dealing with that security concerns efficiently. >> Alright, well I look forwards to the conversation. >> Thanks. >> Thanks for stopping by. >> Thank you. >> He's Guy Podjarny. He is from Snyk. The CEO of Snyk. I'm Jeff Frick, you're watching theCUBE. (uptempo techno music)