>>Hello, fabulous cloud community and welcome to Las Vegas. We are the Cube and we will be broadcasting live from the AWS Reinvent Show floor for the next four days. This is our first opening segment. I am joined by the infamous John Furrier. John, it is your 10th year being here at Reinvent. How does >>It feel? It's been a great to see you. It feels great. I mean, just getting ready for the next four days. It's, this is the marathon of all tech shows. It's, it's busy, it's crowd, it's loud and the content and the people here are really kind of changing the game and the stories are always plentiful and deep and just it's, it really is one of those shows you kind of get intoxicated on the show floor and in the event and after hours people are partying. I mean it is like the big show and 10 years been amazing run People getting bigger. You're seeing the changing ecosystem Next Gen Cloud and you got the Classics Classic still kind of doing its thing. So getting a lot data, a lot of data stories. And our guests here are gonna talk more about that. This is the year the cloud kind of goes next gen and you start to see the success Gen One cloud players go on the next level. It's gonna be really fun. Fun week. >>Yes, I'm absolutely thrilled and you can certainly feel the excitement. The show floor doors just opened, people pouring in the drinks are getting stacked behind us. As you mentioned, it is gonna be a marathon and very exciting. On that note, fantastic interview to kick us off here. We're starting the day with Stripe. Please welcome nor and Brian, how are you both doing today? Excited to be here. >>Really happy to be here. Nice to meet you guys. Yeah, >>Definitely excited to be here. Nice to meet you. >>Yeah, you know, you were mentioning you could feel the temperature and the energy in here. It is hot, it's a hot show. We're a hot crew. Let's just be honest about that. No shame in that. No shame in that game. But I wanna, I wanna open us up. You know, Stripe serving 2 million customers according to the internet. AWS with 1 million customers of their own, both leading companies in your industries. What, just in case there's someone in the audience who hasn't heard of Stripe, what is Stripe and how can companies use it along with AWS nor, why don't you start us off? >>Yeah, so Stripe started back in 2010 originally as a payments company that helped businesses accept and process their payments online. So that was something that traditionally had been really tedious, kind of difficult for web developers to set up. And what Stripe did was actually introduce a couple of lines of code that developers could really easily integrate into their websites and start accepting those payments online. So payments is super core to who Stripe is as a company. It's something that we still focus on a lot today, but we actually like to think of ourselves now as more than just a payments company but rather financial infrastructure for the internet. And that's just because we have expanded into so many different tools and technologies that are beyond payments and actually help businesses with just about anything that they might need to do when it comes to the finances of running an online company. So what I mean by that, couple examples being setting up online marketplaces to accept multi-party payments, running subscriptions and recurring payments, collecting sales tax accurately and compliantly revenue recognition and data and analytics. Importantly on all of those things, which is what Brian and I focus on at Stripe. So yeah, since since 2010 Stripes really grown to serve millions of customers, as you said, from your small startups to your large multinational companies, be able to not only run their payments but also run complex financial operations online. >>Interesting. Even the Cube, the customer of Stripe, it's so easy to integrate. You guys got your roots there, but now as you guys got bigger, I mean you guys have massive traction and people are doing more, you guys are gonna talk here on the data pipeline in front you, the engineering manager. What has it grown to, I mean, what are some of the challenges and opportunities your customers are facing as they look at that data pipeline that you guys are talking about here at Reinvent? >>Yeah, so Stripe Data Pipeline really helps our customers get their data out of Stripe and into, you know, their data warehouse into Amazon Redshift. And that has been something that for our customers it's super important. They have a lot of other data sets that they want to join our Stripe data with to kind of get to more complex, more enriched insights. And Stripe data pipeline is just a really seamless way to do that. It lets you, without any engineering, without any coding, with pretty minimal setup, just connect your Stripe account to your Amazon Redshift data warehouse, really secure. It's encrypted, you know, it's scalable, it's gonna meet all of the needs of kind of a big enterprise and it gets you all of your Stripe data. So anything in our api, a lot of our reports are just like there for you to take and this just overcomes a big hurdle. I mean this is something that would take, you know, multiple engineers months to build if you wanted to do this in house. Yeah, we give it to you, you know, with a couple clicks. So it's kind of a, a step change for getting data out of Stripe into your data work. >>Yeah, the topic of this chat is getting more data outta your data from Stripe with the pipelining, this is kind of an interesting point, I want to get your thoughts. You guys are in the, in the front lines with customers, you know, stripes started out with their roots line of code, get up and running, payment gateway, whatever you wanna call it. Developers just want to get cash on the door. Thank you very much. Now you're kind of turning in growing up and continue to grow. Are you guys like a financial cloud? I mean, would you categorize yourself as a, cuz you're on top of aws? >>Yeah, financial infrastructure of the internet was a, was a claim I definitely wanna touch on from your, earlier today it was >>Powerful. You guys are super financial cloud basically. >>Yeah, super cloud basically the way that AWS kind of is the superstar in cloud computing. That's how we feel at Stripe that we want to put forth as financial infrastructure for the internet. So yeah, a lot of similarities. Actually it's funny, we're, we're really glad to be at aws. I think this is the first time that we've participated in a conference like this. But just to be able to participate and you know, be around AWS where we have a lot of synergies both as companies. Stripe is a customer of AWS and you know, for AWS users they can easily process payments through Stripe. So a lot of synergies there. And yeah, at a company level as well, we find ourselves really aligned with AWS in terms of the goals that we have for our users, helping them scale, expand globally, all of those good things. >>Let's dig in there a little bit more. Sounds like a wonderful collaboration. We love to hear of technology partnerships like that. Brian, talk to us a little bit about the challenges that the data pipeline solves from Stripe for Redshift users. >>Yeah, for sure. So Stripe Data Pipeline uses Amazon RedShift's built in data sharing capabilities, which gives you kind of an instant view into your Stripe data. If you weren't using Stripe data pipeline, you would have to, you know, ingest the state out of our api, kind of pull yourself manually. And yeah, I think that's just like a big part of it really is just the simplicity with what you can pull the data. >>Yeah, absolutely. And I mean the, the complexity of data and the volume of it is only gonna get bigger. So tools like that that can make things a lot easier are what we're all looking for. >>What's the machine learning angle? Cause I know there's lots of big topic here this year. More machine learning, more ai, a lot more solutions on top of the basic building blocks and the primitives at adds, you guys fit right into that. Cause developers doing more, they're either building their own or rolling out solutions. How do you guys see you guys connecting into that with the pipeline? Because, you know, data pipelining people like, they like that's, it feels like a heavy lift. What's the challenge there? Because when people roll their own or try to get in, it's, it's, it could be a lot of muck as they say. Yeah. What's the, what's the real pain point that you guys solve? >>So in terms of, you know, AI and machine learning, what Stripe Data Pipeline is gonna give you is it gives you a lot of signals around your payments that you can incorporate into your models. We actually have a number of customers that use Stripe radar data, so our fraud product and they integrate it with their in-house data that they get from other sources, have a really good understanding of fraud within their whole business. So it's kind of a way to get that data without having to like go through the process of ingesting it. So like, yeah, your, your team doesn't have to think about the ingestion piece. They can just think about, you know, building models, enriching the data, getting insights on top >>And Adam, so let's, we call it etl, the nasty three letter word in my interview with them. And that's what we're getting to where data is actually connecting via APIs and pipelines. Yes. Seamlessly into other data. So the data mashup, it feels like we're back into in the old mashup days now you've got data mashing up together. This integration's now a big practice, it's a becoming an industry standard. What are some of the patterns and matches that you see around how people are integrating their data? Because we all know machine learning works better when there's more data available and people want to connect their data and integrate it without the hassle. What's the, what's some of the use cases that >>Yeah, totally. So as Brian mentioned, there's a ton of use case for engineering teams and being able to get that data reported over efficiently and correctly and that's, you know, something exactly like you touched on that we're seeing nowadays is like simply having access to the data isn't enough. It's all about consolidating it correctly and accurately and effectively so that you can draw the best insights from that. So yeah, we're seeing a lot of use cases for teams across companies, including, a big example is finance teams. We had one of our largest users actually report that they were able to close their books faster than ever from integrating all of their Stripe revenue data for their business with their, the rest of their data in their data warehouse, which was traditionally something that would've taken them days, weeks, you know, having to do the manual aspect. But they were able to, to >>Simplify that, Savannah, you know, we were talking at the last event we were at Supercomputing where it's more speeds and feeds as people get more compute power, right? They can do more at the application level with developers. And one of the things we've been noticing I'd love to get your reaction to is as you guys have customers, millions of customers, are you seeing customers doing more with Stripe that's not just customers where they're more of an ecosystem partner of Stripe as people see that Stripe is not just a, a >>More comprehensive solution. >>Yeah. What's going on with the customer base? I can see the developers embedding it in, but once you get Stripe, you're like a, you're the plumbing, you're the financial bloodline if you will for the all the applications. Are your customers turning into partners, ecosystem partners? How do you see that? >>Yeah, so we definitely, that's what we're hoping to do. We're really hoping to be everything that a user needs when they wanna run an online business, be able to come in and maybe initially they're just using payments or they're just using billing to set up subscriptions but down the line, like as they grow, as they might go public, we wanna be able to scale with them and be able to offer them all of the products that they need to do. So Data Pipeline being a really important one for, you know, if you're a smaller company you might not be needing to leverage all of this big data and making important product decisions that you know, might come down to the very details, but as you scale, it's really something that we've seen a lot of our larger users benefit from. >>Oh and people don't wanna have to factor in too many different variables. There's enough complexity scaling a business, especially if you're headed towards IPO or something like that. Anyway, I love that the Stripe data pipeline is a no code solution as well. So people can do more faster. I wanna talk about it cuz it struck me right away on our lineup that we have engineering and product marketing on the stage with us. Now for those who haven't worked in a very high growth, massive company before, these teams can have a tiny bit of tension only because both teams want a lot of great things for the end user and their community. Tell me a little bit about the culture at Stripe and what it's like collaborating on the data pipeline. >>Yeah, I mean I, I can kick it off, you know, from, from the standpoint like we're on the same team, like we want to grow Stripe data pipeline, that is the goal. So whatever it takes to kind of get that job done is what we're gonna do. And I think that is something that is just really core to all of Stripe is like high collaboration, high trust, you know, this is something where we can all win if we work together. You don't need to, you know, compete with like products for like resourcing or to get your stuff done. It's like no, what's the, what's the, the team goal here, right? Like we're looking for team wins, not, you know, individual wins. >>Awesome. Yeah. And at the end of the day we have the same goal of connecting the product and the user in a way that makes sense and delivering the best product to that target user. So it's, it's really, it's a great collaboration and as Brian mentioned, the culture at Stripe really aligns with that as >>Well. So you got the engineering teams that get value outta that you guys are dealing with, that's your customer. But the security angle really becomes a big, I think catalyst cuz not just engineering, they gotta build stuff in so they're always building, but the security angle's interesting cuz now you got that data feeding security teams, this is becoming very secure security ops oriented. >>Yeah, you know, we are really, really tight partners with our internal security folks. They review everything that we do. We have a really robust security team. But I think, you know, kind of tying back to the Amazon side, like Amazon, Redshift is a very secure product and the way that we share data is really secure. You know, the, the sharing mechanism only works between encrypted clusters. So your data is encrypted at rest, encrypted and transit and excuse me, >>You're allowed to breathe. You also swallow the audience as well as your team at Stripe and all of us here at the Cube would like your survival. First and foremost, the knowledge we'll get to the people. >>Yeah, for sure. Where else was I gonna go? Yeah, so the other thing like you kind of mentioned, you know, there are these ETLs out there, but they, you know that that requires you to trust your data to a third party. So that's another thing here where like your data is only going from stripe to your cluster. There's no one in the middle, no one else has seen what you're doing, there's no other security risks. So security's a big focus and it kind of runs through the whole process both on our side and Amazon side. >>What's the most important story for Stripe at this event? You guys hear? How would you say, how would you say, and if you're on the elevator, what's going on with Stripe? Why now? What's so important at Reinvent for Stripe? >>Yeah, I mean I'm gonna use this as an opportunity to plug data pipelines. That's what we focus on. We're here representing the product, which is the easiest way for any user of aws, a user of Amazon, Redshift and a user of Stripe be able to connect the dots and get their data in the best way possible so that they can draw important business insights from that. >>Right? >>Yeah, I think, you know, I would double what North said, really grow Stripe data pipeline, get it to more customers, get more value for our customers by connecting them with their data and with reporting. I think that's, you know, my goal here is to talk to folks, kind of understand what they want to see out of their data and get them onto Stripe data pipeline. >>And you know, former Mike Mikela, former eight executive now over there at Stripe leading the charge, he knows a lot about Amazon here at aws. The theme tomorrow, Adams Leslie keynote, it's gonna be a lot about data, data integration, data end to end Lifeing, you see more, we call it data as code where engineering infrastructure as code was cloud was starting to see a big trend towards data as code where it's more of an engineering opportunity and solution insights. This data as code is kinda like the next evolution. What do you guys think about that? >>Yeah, definitely there is a ton that you can get out of your data if it's in the right place and you can analyze it in the correct ways. You know, you look at Redshift and you can pull data from Redshift into a ton of other products to like, you know, visualize it to get machine learning insights and you need the data there to be able to do this. So again, Stripe Data Pipeline is a great way to take your data and integrate it into the larger data picture that you're building within your company. >>I love that you are supporting businesses of all sizes and millions of them. No. And Brian, thank you so much for being here and telling us more about the financial infrastructure of the internet. That is Stripe, John Furrier. Thanks as always for your questions and your commentary. And thank you to all of you for tuning in to the Cubes coverage of AWS Reinvent Live here from Las Vegas, Nevada. I'm Savannah Peterson and we look forward to seeing you all week.

(upbeat music) >> Hey everyone. Welcome back to Las Vegas. The Cube is live. I can't say that enough. We are alive at AWS re:Invent 2021. Lisa Martin with Dave Nicholson. Hey Dave. >> Hey Lisa. >> Having a good day so far. >> So far, so good. >> We have an alumni back with us. We have about a hundred segments on the cube at AWS remit. We've got one of our original alumni back with us. Zaki Bajwa joins us the global head of partner solution engineers at Stripe. Zaki welcome back. >> Thank you, Lisa, thank you, Dave. Pleasure to be here. >> Lisa: Isn't it great to be back in person? >> Love it. Love it. Can't do a whiteboard virtually, you can, it's not the same. >> It's not the same and all those conversations I'm sure that you've had with partners and with customers the last couple of days that you just can't replicate that over zoom. >> Zaki: Exactly. >> So just for anyone who doesn't understand, AWS has a massive ecosystem of partners. So we'll get to talk about Stripe and AWS, but for anyone that doesn't know what Stripe is, give us the lowdown. You guys started 10 years ago. Talk to us about Stripe, the business strategy, what it's like today. >> Yeah, sure. So you guys know Stripe started 10 years ago by two brothers, John and Patrick Collison. And they've really focused on the developer and helping the developers accelerate digital commerce. Why? Cause the status quo at the time was one where a developer needed to, you know, build banking relationships with issuing banks, merchant banks, card networks, payment networks, tax liabilities, data compliance, and all of these manual processes that they had to deal with. So what Stripe aspires to do is build a complete commerce platform. Leveraging our integrated suite of products that is really allowing us to build what we call the global payments and treasury network. So if you think about the global payment and treasury network or what we call the G P T N it's meant to not only help abstract all of that complexity from a global payment infrastructure point of view, but also help move money in a simple and borderless and a programmable way just like we do in the internet. So that's the core essence of Stripe is to build this global payment treasury network to allow for money movement to happen in a simple and borderless manner. >> Simple and borderless two key things there. How has the business strategy evolved in the last 10 years and specifically in the last 20, 22 months? >> Yeah. Great question. So as you can imagine with COVID, you know, David you can order a cup of coffee or a brand new car, and that whole direct to consumer model has accelerated in COVID right. We've accelerated ourselves going to upwards of 6,000 employees. We've been able to answer or manage upwards of 170 billion API requests in the last 12 months alone. Right we deliver upwards of five nines from a availability performance point of view. That means 13 seconds of downtime or less a month. And we're doing this originally starting off for the developer David as you talked about allowing developers to deliver, you know, what I call process payments, accept payments and reconcile payments. But the evolution that you're talking about Lisa has really led to three key areas of focus that our users are requesting from us. And Stripe's first operating principle is really that user first mentality similar to the Amazons where we listen to our users and they're really asking for three key areas of focus. Number one is all around modernizing their digital commerce. So this is big enterprises coming to us and saying, whether I'm a uni lever or a Ford, how do you help me with a direct to consumer a e-commerce type platform? Number one. Secondly, is companies like Deliveroo and Lyft creating what we call marketplaces. Also think about Twitter and clubhouse, more solopreneurs entrepreneurs kind of marketplaces. Third is all around SaaS business models. So think about slack and Atlassian. That are customer vivers and accelerating the journey with us around digitizing digital commerce. So that's the first area of evolution. The second area is all around what we call embedded FinTech. So we know just like Amazon helped accelerate infrastructure as a service, platform as a service and function as a service. We're helping accelerate FinTech as a service. So we believe every company in every industry aspires to add more and more FinTech capabilities in their core services that they offer to their customers. So think about a Shopify or a Lyft they're adding more FinTech capabilities, leveraging Stripe APIs that they offer to their consumers. Likewise, when you think about a Monzo bank or a and 26, what we call Neo banks. They're creating more banking as a service component so a second area of evolution is all around FinTech as a service or embedded FinTech. And the third area of focus again, listen to our users is all around users are saying. Hey, Stripe, you have our financial data. How do you help us more with business operations and automating and optimizing our business operations? So this is revenue management, revenue reconciliation, financial reporting, all of the business processes, you and I know, code to cash, order to cash, pay to procure. Help us automate, optimize, and not just optimize, but help us create net new business models. So these are the three key areas of evolution that we've seen modernizing digital commerce, embedded FinTech, and then certainly last but not least business operations and automating that. >> And your target audience is the developers. Or are you having conversations now that are more, I mean, this is like transformative to industries and disruptive. Are you having conversations higher up in the chain? >> Great, great question. And this is the parallel with Amazon, just like Amazon started with developers, AWS. And then what up to the C-suite, if you will, we're seeing the same exact thing. Obviously our DNA is developer first making it intuitive, natural easy for developers to build on Stripe. But we're seeing more and more C-suite leaders come to us and saying, help us evolve our business model, help us modernize and digitize net new business models to get new revenue streams. So those parallel work streams are both developer mindset and C-suite led is certainly a big evolution for us. And we're looking to learn from our Amazon friends as to the success that they've had there. >> Do you have any examples of projects that developers have proposed that were at first glance, completely outlandish? Something that, you know, is there any sort of corner of the chart use case where Stripe didn't think of it, some developer came up with the idea, maybe it can't be done yet. If you have an example of that, that would be very interesting. >> Yeah, I'll give you two examples. So as I said, we're definitely a user first entity. That's our operating principle. We always think about the user. So let me go to developers and say, what are you struggling with? What are you thinking about? What are the next set of things you need from us? And a simple comment around tax started to come up and do you know in the U S there's 11,000 tax jurisdictions that you and you're selling something online have to abide to these different jurisdictions. So one of the things that we then evolved into is created a Stripe tax product, which initially users or developers were really struggling with and working on. So we created a Stripe tax product. We've done an acquisition called tax jar that helps us accelerate that journey for tax. The other one is this notion of low code that we see in the marketplace right now, where developers saying. Hey, give me more embeddables on top of the primitives that you've created on top of the APIs. So we went leveraging what our customers have already done, created things like a checkout capability, which is a simple redirect highly customized for conversion, which you can just integrate to one API. You have a full checkout capability. You can embed that into your platform, which didn't exist before and needed you to really integrate into different APIs. So all of these capabilities are what developers have really focused on and built that we've done leverage and Excel on. >> Yeah, I think between Lisa and myself, we've paid taxes in about 7,000 of those >> Lisa: Yeah, probably. >> Not 11,000 jurisdictions, but all the various sales taxes and everything else. So we're sort of familiar with it. >> I think so, so here we are, you know, on the floor at re-invent. Great, as we said to be back in person, the 10th annual, but with, as each year goes by AWS has a ecosystem of partners gets bigger and bigger. The flywheel gets, I don't know, I think faster and faster, the number of announcements that came out yesterday and today talk to us about some of the common traits that Stripe and AWS share. >> Yeah. So I've mentioned a few of them. One is certainly the user first mentality where we're listening to users. That tax example is a perfect one of how do we decide new features, new capability based on user first, Amazon does that better than anyone else. Second is that developer mindset focus on the developer. Those will be the core persona we target give you an example, Lyft, we all know Lyft. They wanted to create instant payouts for their drivers. So their developers came to us and say, our developers don't want to get paid. I'm sorry. Our drivers don't want to get paid in a week or two weeks. So we work with their developers who create a instant payout mechanism. Now in six months, over 40% of their drivers are using Stripe instant payout powered by Stripe. And that's a developer first mindset again, back to AWS. And then the third is really around the go to market. And the market opportunity is very similar. You talked about the developer persona and the C-suite very similar to Amazon. But also we're not just catering to enterprise and strategic big customers. We are just so much focused on startups, SMB, mid-market, digital native, just like Amazon is. And I would say the last parallel, which is probably the most important one is innovation. I come from enterprise software where we looked at monthly, quarterly, biannual, annual release cycles. Well, as Stripe, all of that goes out the door just like Amazon. We may have a hundred to a thousand APIs in motion at any time in alpha beta production. And just like Amazon we're iterating and releasing new innovations consistently. So I would say that's probably the most important one that we have with Amazon. >> So a lot of synergies there like deep integrated trusted partner synergies it sounds like. >> Agreed, definitely and then we're seeing this. I was going more as we are going more up market. We're seeing a demand for end to end solutions that require integrations with a CRM vendor for customer 360 with our accounting vendor for pivotal procure order to cash, billing accounting with a e-commerce company like Adobe Magento to do better econ. So more end to end solutions with these tech partners, we're working with our GSI to help deliver those end to end solutions. And certainly, but not least the dev agencies who are still sort of our core constituents that help us keep relevant with those developers. >> You mentioned this at the outset, but some things bear repeating. Can you go into a little more detail on the difference between me wanting to start up a business and take credit cards as payment 10 years ago? Let's say versus today, how much of the friction have you removed from that system? >> It is literally an hour to two hour process versus weeks and months before. >> But what are those steps? Like who would I, you mentioned this, again you mentioned this already, but the go through that, go through that again who would I have to reach out to, to make this happen? And we were talking, you know, relationships with banks, et cetera, et cetera. >> Yeah. So it starts at initiating and registering that company. So imagine you going and having to register a company today, you can do that with a Stripe Atlas product in a matter of hours, get your EIN number, get your tax jurisdictions on your registration as a Delaware entity within the U S you can be anywhere at globally and go do that within a matter of one hour. That's number one, you start there. From there, then it's a matter of embedding payment embeddables within your e-commerce platform, marketplace platform, et cetera. As you've heard us talk about seven lines of code to get payments going, you can quickly onboard accept payments, process payments, reconcile payments all within an hour. And that's just the start. But now you get into more complex use cases around marketplaces and multi-party connection. Multi-party payouts, different commission rates, different subscription models. Think about a flat tier model, a metered tier model, all of these different things that we've abstracted and allow you to just use one to three different integrations to help accelerate and use that in your digital commerce platform. So all of these different workflows have is what we've automated through our APIs. >> Dave: That's unbelievable. >> Yeah. >> It really is. >> It is unbelievable, the amount of automation and innovation that's gone on in such a short time period. What are some of the things as we kind of wrap up here that we can look forward to from stripe from a roadmap perspective, technology wise, partner wise? >> Yes. I mean, we have a slew of data you can imagine billions of billions of transactional data. And you guys know what we do with data is we're looking at fraud prevention. We're looking at, we have a product called radar that looks at fraud, we're doing acceptance, adaptive acceptance to do more AIML learned data and authorization. We're also looking at how do we feed a lot of this financial data into the right mechanisms to allow you to then create new business models on top of this, whether it's cross sell upsell to new user business capture. As well as you know, one of the things I did not talk about, which coming from a farming background is this notion of Stripe climate. Where we have upwards of 2000 companies across 37 countries that are leveraging our Stripe climate product to give back to tech advanced companies that are helping in carbon offset. And super exciting times there from an ESG environmental social governance point of view. So all of those combined is what excites us about the future at Stripe. >> Wow. The future seems unlimited. Lots going on. >> Super excited. Zaki, thank you so much for joining Dave and me talking about what's going on with Stripe. All the innovation that's going on. The synergies with AWS and what's coming down the pipe. We appreciate your insights and your time. >> Thank you, Lisa, thank you, David. Appreciated All right. For Dave Nicholson, I'm Lisa Martin. You're watching the Cube. The global leader in live tech coverage. (lighthearted piano music)

>>Welcome everybody to the cubes live coverage of AWS reinvent 2021. We're here in the main hall. Yes, this is a physical event. It's a hybrid event, probably the industry's most important hybrid event in the year. We're super excited to be here. Of course, last year during the lockdown, reinvent was purely virtual. This year. They go in hybrid 20 plus thousand people. I hear the whisper numbers like 25, 20 7,000 hundreds of thousands of people online. The cubes here, two sets, we've got two remote studios, super excited. I'd like to introduce my co-host David Nicholson. He'll be here all week with us. Uh, John furrier is also here, Lisa Martin for the cubes wall-to-wall coverage. And we're so psyched to start off this session with Kenneth Chestnut. Who's the head of technology partnerships at Stripe. Stripe's an amazing company, Ken. Great to see you. Thanks for coming on. >>Thanks for having me, Dave and David. I greatly appreciate it. How about this? >>Right. Finally live event. We've done a few. We probably done four or five this year, but >>It's good to be back in person. It is. Yeah, absolutely. It's >>A Stripe. I mean, wow. Can a powering the new economy. Tell us a little bit more for those people who may not be familiar with Stripe. They probably use it without even knowing it when they sign it away. Yeah. So tell us about the >>Well, uh, Stripe was founded in 2010 by two brothers, Patrick and John Colson. And really it was from their first business and realizing how hard it was to actually charge for things on online. Um, you had to acquire a relationship with, uh, with a gateway provider to accept payments. You had to acquire a relationship with a, with a acquiring bank. Um, and you had to do that for each and every country that you wanted to service. Uh, so the same way that AWS reduced the barrier in terms of not having to procure, spend millions of dollars on storage, computers, networking, uh, effectively, what we we've done at Stripe is reduce the barriers around economic infrastructure, accepting payments online, >>Use that undifferentiated heavy lifting for payments. So describe Ken, what it was like kind of pre Stripe. You would literally have to install servers, get storage and put, put software on there, get a database. And then what if you had any money left over, you can actually do some business, but, but describe the sort of what the experience is like with Stripe. >>Sure. So, uh, the R R with, with Stripe, we literally talk about seven lines of code. So we, we allow any developer to, um, uh, provide a set of APIs for any developer to accept payments on online. And we do the undifferentiated heavy lifting in terms of accepting payments, accepting those payments, processing them revenue, reporting, and reconciliation, um, all ensuring compliance and security. Um, so it's like you said, uh, taking care of the undifferentiated heavy lifting are around accepting payments online in the enabling >>The enabler. There is the cloud. I mean, it was 2009, 2010. You guys were founded, the cloud was only like three years old. Right. And so you had to really sort of take a chance on leveraging the cloud or maybe early on you just installed it yourself and said, this isn't going to scale. So maybe tell us how you sort of leverage the cloud. >>Sure. Um, so we're a long time, uh, AWS, uh, customer and user, um, uh, back in the early days of, of Stripe in the early days of, of AWS. And we've just grown, uh, with, with AWS and the ecosystem. And it's interesting because a lot of, uh, a lot of the companies that have been built on, on AWS and grown to be successful, they're also Stripe customers as well. So they use Stripe for their economic infrastructure. >>We use Stripe, we run our company on AWS and we use Stripe. It it's true. The integration took like minutes. It was so simple. Hey it, test it, make sure it scales. But so what, what's the stack look like? What is there, is there such thing as a payment stack? What's the technology stuff? >>Sure. So we initially started with payments and being able to accept payments, uh, on online. Uh we've we brought in out our, our, our Stripe product portfolio now to effectively provide economic, uh, infrastructure for the internet. So that could be accepting payments. Uh, it could be setting up marketplaces. So companies like Lyft and Deliveroo, uh, use Stripe to power their marketplaces with their, with their drivers and, and, um, uh, delivers, um, uh, we provide, uh, a product called radar that, uh, that, um, prevents fraud, uh, around, around the globe. Um, based upon the data that we're seeing from our, from our customers, um, we have, uh, issuing and treasury so that companies can provide their users or their merchants with banking services. So loans, uh, issuing credit cards. So we we've really broadened out the product portfolio of Stripe to provide sort of economic infrastructure for the internet. So >>We talked about strike being in the cloud from an infrastructure perspective and how that enables certain things, but that in and of itself, doesn't change the dynamics around sovereignty and governance from country to country. Sure. Uh, I imagine that the global nature of AWS sort of dovetails with your strategy, but how, how do you address that? It's one thing to tell me in Northern California, you can process payments for me, but now globally go across 150 countries. How do you make that work? Yeah, >>Uh, absolutely. So we, we establish relationships, uh, within, within each company country that we operate in we're in about 47, uh, countries, uh, today, um, and that's rapidly expanding so that companies can, can process or accept payments and do, uh, financial transactions within, within, within those countries. So we're in 47 countries today. We, we accept a multitude of different payment, uh, different currencies, different payment types. So the U S is very, uh, credit card focused. But if you go to other, other parts of the globe, it could be a debit cards. It could be, um, uh, wallets, uh, uh, Google pay, Ali pay, uh, others. So really it's, uh, providing sort of the payment methods that users prefer in, in the different countries, uh, and meeting and meeting those users where, where they are. >>Are you out of the box compliant? What integration is required to do that? Uh, what about things like data sovereignty, is that taken care of by the cloud provider or you guys, and where, w w where does, where does AWS end and you guys pick up? Yes, >>We're, we're PCI compliant. Um, we, we leverage AWS as our, as our infrastructure, um, to grow, grow and scale. So, um, one of the things that we're, we're proud of is, uh, through, throughout 2020 and 2021, we've, we've had 11 nines of, uh, of, of, uh, or five nines of uptime, um, even through, um, uh, black Friday and cyber Monday. So providing AWS provides that, that infrastructure, which we built on top of to provide, uh, you know, five nines of uptime for our, for our users. >>You describe in more detail, Kenya, your ecosystem. I mean, you're responsible for tech partnerships. What does that ecosystem, how I paint a picture of it? >>Sure. So, um, uh, a number of users want to be able to use Stripe with, with their other, uh, it infrastructure and, and their business processes. So a customer may start, uh, with a salesperson may start with a quote or order, uh, in, in Salesforce, want to automate the invoicing and billing and payment of that with, with Stripe and then, uh, reconcile re revenue and an ERP solution like SAP or Oracle or NetSuite or into it, um, in the case of, of small, medium businesses. So really, um, what we're focused on is building out that, that ecosystem to allow, uh, um, our, our customers to streamline their business processes, um, and, and integrate Stripe into their existing it infrastructure and, and business processes. >>You mentioned a lot of different services, but broadly speaking, if I think about payments, correct me if I'm wrong, but you were one of the early, uh, sort of software companies, if I can call you that, um, platforms, whatever, but to really focus on a usage based pricing, but how do I, how do I engage with you? What's, what's the pricing model. Maybe you could describe that a little. >>Sure. So the pricing model is very, very transparent. Uh, it's on, it's on the website. So, uh, we, we take a, um, a percentage of each transaction. So literally you can, you can set up a, a Stripe account it's self-service, um, uh, we, we take a 2.9% plus 30 cents on every, uh, Tran transaction. Um, we don't, you don't start getting, um, uh, charged until, uh, you start accepting payments from your, from your customers or from your users. >>Um, can you give us a sense of the business scope, maybe any metrics you can share, customers, whatever. >>Sure. So there's a couple of things we can share publicly, just in terms of the size of the business. I think since, uh, since 2020, uh, more than 2 million businesses have launched on, on Stripe. Uh, so, uh, 2 million in, in, in, in 2020, um, we've, uh, uh, in the past 12 months, we've, uh, uh, uh, processed over 173 billion, uh, API calls. Uh, we do we process about, um, uh, hundreds of billions of, of, of, uh, payment volume, uh, every, every year. Um, if you look at sort of the macros of the business, the business is growing faster than the broader e-commerce space. So the amount of payment volume that we did in this past year is more than the entire industry did when Patrick and John founded the company. And in 2010, just to give you a, uh, an idea of the, the, the size of the business and sort of the pace of the business >>You're growing as e-commerce grows, but you're also stealing share from other sort of traditional payment systems. Okay. So that's a nice flywheel effect. And of course, Stripe's a private company they've raised well over a billion dollars of Peter teal, and it wasn't original founders, so are funders. So, you know, that's, he's talking scale. I want to go back to something you said about radar. Sure. So there's tech in your stack fraud detection, right. So some of >>That in machine learning, right. >>So, and so you guys, I mean, are you a technology company, are you a F a FinTech company? What are you? >>We're a software company. We provide software and we provide technology for developers, uh, to make online businesses and make, uh, uh, commerce, uh, more seamless and more frictionless >>Cloud-first API first. I mean, maybe describe how that is different maybe than, you know, the technical debt that's been built up over, you know, decades with traditional payment systems. >>Yes, it's very similar to the early, earlier days of AWS where a lot of tech forward companies leveraged Stripe, um, to, um, whether it be large enterprises to transform their businesses and move online, or, or, uh, uh, startups and developers that want to, uh, start a new business online and, and do that, uh, as quickly and seamlessly as possible. So it's, it's quite the gamut from large enterprises that are digitally transforming themselves companies like Marske and, and NASDAQ and others, as well as, uh, um, startups and developers that have started their businesses and born on born on Stripe. So >>When you talk about a startup, how small of an entity makes sense, uh, when you think of, if you look at, from an economic perspective, lowering the friction associated with transactions can lift up a large part of the world with sort of, you know, w with very, very small businesses. Is that something that this is all about? >>Yeah, absolutely. So, like I said, you know, two, 2 million business have sub launched on, on, on Stripe, uh, in, in the past year. And, and those businesses vary, but it could be literally a, a developer or a, uh, uh, a small, uh, SMB that wants to be able to accept payments on online. And it can just set up a Stripe account and start accepting payments. >>Yeah. So this is not a one hit wonder, um, lay out the vision for Stripe, right? I mean, you're, you're a platform, uh, you're, you're becoming a fundamental ingredient of the digital economy sounds pre pandemic. That was all a bunch of buzzwords, but today we all know how important that is, but what lay out the vision for us can, >>Yeah, it really are. The mission of Stripe is to grow the GDP of the internet. Um, and, and so what that means is, uh, more and more our, our, our basic belief is more and more and more businesses, uh, will, will, uh, go, go online, uh, with, uh, with the pandemic that that was, uh, accelerated. But I think that the general trend of businesses moving online, uh, will continue to accelerate, and we want to provide, uh, economic infrastructure to support those businesses. Um, you know, um, uh, uh, Andreessen talked about sort of software, software eating the world well fit. Our belief has FinTech is eating software. So in, in the fullness of time, I think the opportunity is for, uh, any, any company to be a financial services company. And we want to empower any company that wants to, or any user that wants to be a financial services company to, to provide the economic infrastructure for them to do so. >>And, and, you know, I mean your data company in that sense, you're moving bits around, you know, and those datas, I like to say data's eating software, you know, cause really you gotta have your data act together. Absolutely. And that's an evolving, I mean, you guys started to, to 2010, I would imagine your data strategy has evolved quite dramatically. Yeah. >>It's a great, it's a great call out Dave. Uh, one of our other products is a product called Sigma. So Sigma allows, uh, merchants or our customers to query payment and transaction data. So they want to be able to understand who, who, who are their customers, what are the payment methods that those customers prefer in different countries, in different regions? Um, so we're, we're starting to have some interesting use cases, um, working with, with AWS and other partners when you can start combining payment and transaction data in Stripe with other data to understand customer segmentation, customer 360 lifetime value of a customer customer acquisition costs, being able to close the books faster in your ERP, because you can apply that payment and transaction data to your general ledger to, to close the books faster at the end of the month or at the end of the, at the end of the year. So, uh, yeah, we we're, um, uh, as, as more and more companies are using Stripe, um, they want to be able to take advantage of that data and combine it with other, other sources of data to drive business. >>Yeah. You mentioned some of those key metrics that are, that are so important to companies today. I'll give you the last word re-invent this hall is packed, um, a little bit surprising, frankly, you know, but, uh, but exciting. Uh, what are you looking forward to this? >>Yeah, I'm just looking forward to meeting people in person again, it's, uh, it's great to be here and, and, you know, uh, uh, we have a strong relationship with AWS. We have lots of partners in, in, in common here, uh, as well, both consulting partners and technology partners. So really looking forward to meeting with partners and customers, and especially as we, as we plan for next year and, uh, launching our, our, our partner program beginning of next year. Uh, there's a lot of, uh, uh, groundwork and things to learn from, from here. As we, as we, we, we, we launch our, our, our partner business formula next >>I'll bet. Looking forward to that, Ken, thanks so much for coming to the cure. You so much. It was great to have a chat at the time. All right. And we want to thank our sponsors, uh, AWS, of course, and also AMD who's making the editorial segments that we bring you this week possible for Dave Nicholson. I'm Dave Volante. You're watching the cube at AWS reinvent 2021. Keep it right there, right back.

(gentle music) >> Good morning from Las Vegas. It's theCUBE live at AWS Reinvent 2022 with tons of thousands of people today. Really kicks off the event. Big keynote that I think is probably just wrapping up. Lisa Martin here with Dave Vellante. Dave, this is going to be an action packed week on theCUBE no doubt. We talked with so many different companies. Every company's a software company these days but we're also seeing a lot of companies leaving software that can help them operate more efficiently in the background. >> Yeah, well some things haven't changed at Reinvent. A lot of people here, you know, back to 2019 highs and I think we exceeded those two hour keynotes. Peter DeSantis last night talking about new Graviton instances and then Adam Selipsky doing the typical two hour keynote. But what was different he was a lot more poetic than we used to hear from Andy Jassy, right? He was talking about the universe as an analogy for data. >> I loved that. >> Talked about ocean exploration as for the security piece and then exploring into the Antarctic for, you know, better chips, you know? So yeah, I think he did a good job there. I think a lot of people might not love it but I thought it was very well done. >> I thought so too. We're having kicking off a great day of live content for you all day today. We've got Eleanor Dorfman joining us, the sales leader at Retool. Eleanor, welcome to theCUBE. It's great to have you. >> Thank you so much for having me. >> So let's talk a little bit about Retool. I was looking on your LinkedIn page. I love the tagline, build custom internal tools best. >> Eleanor: Yep. >> Talk to us a little bit about the company you recently raised, series C two. Give us the backstory. >> Yeah, so the company was founded in 2017 by two co-founders who are best friends from college. They actually set out to build a FinTech company, a payments company. And as they were building that, they needed to build a ton of custom operations software that goes with that. If you're going to be managing people's money, you need to be able to do refunds. You need to be able to look up accounts, you need to be able to detect fraud, you need to do know your customer operations. And as they were building the sort of operations software that supports the business, they realized that there were patterns to all of it and that the same components were used at and again. And had the insight that that was actually probably a better direction to go in than recreating Venmo, which was I think the original idea. And that actually this is a problem every company has because every company needs operations engineering and operations software to run their business. And so they pivoted and started building Retool which is a platform for building custom operations software or internal tools. >> Dave: Good pivot. >> In hindsight, actually probably in the moment as well, was a good pivot. >> But you know, when you talk about some of those things, refunds, fraud, you know, KYC, you know, you think of operations software, you think of it as just internal, but all those things are customer facing. >> Eleanor: Yep. >> Right so, are we seeing as sort of this new era? Is that a trend that you guys, your founders saw that hey, these internal operations can be pointed at customers to support what, a better customer service, maybe even generate revenue, subscriptions? >> I think it's a direction we're actually heading now but we're just starting to scratch the surface of that. The focus for the last five years has very much been on this operations software and sort of changing the economics of developing it and making it easy and fast to productize workflows that were previously being done in spreadsheets or hacky workarounds and make it easier for companies to prioritize those so they can run their business more efficiently. >> And where are you having your customer conversations these days? Thinking of operations software in the background, but to Dave's point, it ends up being part of the customer experience. So where are you having your customer conversations, target audience, who's that persona? >> Mainly developers. So we're working almost exclusively with developer teams who have backlogs and backlogs of internal tools requests to build that sales teams are building manual forecasts. Support teams are in 19 different tools. Their supply chain teams are using seven different spreadsheets to do demand forecasting or freight forwarding or things like that. But they've never been able to be prioritized to the top of the list because customer facing software, revenue generating software, always takes prioritization. And in this economic environment, which is challenging for many companies right now, it's important to be able to do more with less and maximize the productivity especially of high value employees like engineers and developers. >> So what would you say the biggest business outcomes are? If the developer is really the focus, productivity is the- >> Productivity. It's for both, I would say. Developer productivity and being able to maximize your sort of R and D and maximize the productivity of your engineers and take away some of the very boring parts of the job. But, so I would say developer productivity, but then also the tools and the software that they're building are very powerful for end users. So I would say efficiency and productivity across your business. >> Across the business. >> I mean historically, you know, operations is where we focused IT and code. How much of the code out there is dedicated to sort of operations versus that customer facing? >> So I think it would actually be, it's kind of surprising. We have run a few surveys on this sort of, we call them the state of engineering time, and focusing on what developers are spending their time on. And a third of all code that is being written today is actually for this internal operations software. >> Interesting. And do you guys have news at the show? Are you announcing anything interesting or? >> Yeah, so our focus historically, you sort of gave away with one of your early questions, but our focus has always been on this operations, this building web applications on building UIs on top of databases and APIs and doing that incredibly fast and being able to do it all in one place and integrate with as any data source that you need. We abstract away access authentication deployment and you build applications for your internal teams. But recently, we've launched two new products. We're actually supporting more external use cases and more customer facing use cases as well as automating CRON jobs, ETL jobs alerting with the new retail workflows product. So we're expanding the scope of operations software from web applications to also internal operations like CRON jobs and ETL jobs. >> Explain that. Explain the scourge of CRON jobs to the audience. >> Yeah, so operations software businesses run on operations software. It's interesting, zooming out, it's actually something you said earlier as well. Every company has become a software company. So when you think about software, you tend to think about here. Very cool software that people are selling. And software that you use as a consumer. But Coca-Cola for example, has hundreds of software engineers that are building tools to make the business run for forecasting, for demand gen, for their warehouse distribution and monitoring inventory. And there's two types of that. There's the applications that they build and then the operations that have to run behind that. Maybe a workflow that is detecting how many bottles of Coca-Cola are in every warehouse and sending a notification to the right person when they're out or when they, a refill is very strong, but you know when you need a refill. So it does that, it takes those tasks, those jobs that run in the background and enables you to customize them and build them very rapidly in a code first way. >> So some of the notes that you guys provided say that there's over 500 million software apps that are going to be built in the next few years alone. That's tremendous. How much of that is operation software? >> I mean I think at least a third of that, if not more. To the point where every company is being forced to maximize their resources today and operational efficiency is the way to do that. And so it can become a competitive advantage when you can take the things that humans are doing in spreadsheets with 19 open tabs and automate that. That saves hours a day. That's a significant, significant driver of efficiency and productivity for a business >> It does, and there's direct correlation to the customer experience. The use experience. >> Almost certainly. When you think about building support tooling, I was web chat, chatting on the with Gogo wifi support on my flight over here and they asked for my order number and I sent it and they looked up my account and that's a custom piece of software they were using to look up the account, create a new account for me, and restore my second wifi purchase. And so when you think about it, you're actually, even just as a consumer, interacting with this custom software on the day time. And that's because that's what companies use to have a good customer experience and have an efficient business. >> And what's the relationship with AWS? You guys started, I think you said 2017, so you obviously started in the cloud, but I'm particularly interested in from a seller perspective, what that's like. Working with Amazon, how's that affected your business? >> Yeah, I mean so we're built on AWS, so we're customers and big fans. And obviously like from a selling perspective, we have a ton of integrations with AWS so we're able to integrate directly into all the different AWS products that people are using for databases, for data warehouses, for deployment configurations, for monitoring, for security, for observability, we can basically fit into your existing AWS stack in order to make it as seamless integration with your software so that building in Retool is just as seamless as building it on your own, just much, much faster. >> So in your world, I know you wanted to but, in your world is it more analytics? is it more transactional, sort of? Is it both? >> It's all of the above. And I think what's, over Thanksgiving, I was asked a lot to explain what Retool did with people who were like, we just got our first iPhone. And so I tried to explain with an example because I have yet to stumble on the perfect metaphor. But the example I typically use is DoorDash is a customer of ours. And for about three years, and three years ago, they had a problem. They had no way of turning off delivery in certain zip codes during storms. Which as someone who has had orders canceled during a storm, it's an incredibly frustrating experience. And the way it worked is that they had operation team members manually submitting requests to engineers to say there's a storm in this zip code and an engineer would run a manual task. This didn't scale with Doordash as they were opening in new countries all over the world that have very different weather patterns. And so they looked, they had one, they were sort of confronted with a choice. They could buy a piece of software out of the box. There is not a startup that does this yet. They could build it by hand, which would mean scoping the requirements designing a UI, building authentication, building access controls, putting it into a, putting it into a sprint, assigning an engineer. This would've taken months and months. And then it would take just as long to iterate on it or they could use Retool. So they used Retool, they built this app, it saved, I think they were saying up to two years of engineering time for this one application because of how quickly it was. And since then they've built, I think 50 or 60 more automating away other tasks like that that were one out of spreadsheets or in Jira or in Slack notifications or an email saying, "Hey, could you please do this thing? There's a storm." And so now they use us for dozens and dozens of operations like that. >> A lot of automation and of course a lot of customer delight on the other end of the spectrum as you were talking about. It is frustrating when you don't get that order but it's also the company needs to be able to have the the tools in place to automate to be able to react quickly. >> Eleanor: Exactly. >> Because the consumers are, as we know, quite demanding. I wanted to ask you, I mentioned the tagline in the beginning, build custom internal tools fast. You just gave us a great example of DoorDash. Huge business outcomes they're achieving but how fast are we talking? How fast can the average developer build these internal tools? >> Well, we've been doing a fun thing at our booth where we ask people what a problem is and build a tool for them while we're there. So for something lightweight, you can build it in 10 minutes. For something a little more complex, it can take up to a few weeks depending on what the requirements are. But we all have people who will be on a call with us introducing them to our software for the first time and they'll start telling us about their problems and in the background we'll be building it and then at the end we're like, is this what you meant? And they're like, we'd like to add that to our cart. And obviously, it's a platform so you can't do that. But we've been able to build applications on a call before while people are telling us what they need. >> So fast is fast. >> I would say very fast, yeah. >> Now how do you price? >> Right now, we have a couple different plans. We actually have a motion where you can sign up on our website and get started. So we have a free plan, we've got plans for startups, and then we've got plans all the way up to the enterprise. >> Right. And that's a subscription pricing kind of thing? >> Subscription model, yes. >> So I get a subscription to the platform and then what? Is there also a consumption component? >> Exactly. So there's a consumption component as well. So there's access to the platform and then you can build as many applications as you need. Or build as many workflows. >> When you're having customer conversations with prospects, what do you define as Retool's superpowers? You're the sales leader. What are some of those key superpowers that you think really differentiate Retool? >> I do think, well, the sales team first and foremost, but that's not a fair answer. I would say that people are a bit differentiator though. We have a lot of very talented people who are have a ton of domain expertise and care a ton about the customer outcomes, which I do actually think is a little more rare than it should be. But we're one of the only products out there that's built with a developer first mindset, a varied code first mindset, built to integrate with your software development life cycle but also built with the security and robustness that enterprise companies require. So it's able to take an enterprise grade software with a developer first approach while still having a ton of agility and nimbleness which is what people are really craving as the earth keeps moving around them. So I would say that's something that really sets us apart from the field. >> And then talk about some of the what developers are saying, some of the feedback, some of the responses, and maybe even, I know we're just on day one of the show, but any feedback from the booth so far? >> We've had a few people swing by our booth and show us their Retool apps, which is incredibly cool. That's my absolute favorite thing is encountering a Retool application in the wild which happens a lot more than I would've thought, which I shouldn't say, but is incredibly rewarding. But people love it. It's the reason I joined is I'd never heard someone have a product that customers talked about the way they talk about Retool because Retool enables them to do things. For some folks who use it, it enables them to do something they previously couldn't do. So it gives them super powers in their job and to triple their impact. And then for others, it just makes things so fast. And it's a very delightful experience. It's very much built by developers, for developers. And so it's built with a developer's first mindset. And so I think it's quite fun to build in Retool. Even I can build and Retool, though not well. And then it's extremely impactful and people are able to really impact their business and delight their coworkers which I think can be really meaningful. >> Absolutely. Delighting the coworkers directly relates to delighting the customers. >> Eleanor: Exactly. >> Those customer experience, employee experience, they're like this. >> Eleanor: Exactly. >> They go hand in hand and the employee experience has to be outstanding to be able to delight those customers, to reduce churn, to increase revenue- >> Eleanor: Exactly. >> And for brand reputation. >> And it also, I think there is something as someone who is customer facing, when my coworkers and developers I work with build tools that enable me to do my job better and feel better about my own performance and my ability to impact the customer experience, it's just this incredibly virtuous cycle. >> So Retool.com is where folks can go to learn more and also try that subscription that you said was free for up to five users. >> Yes, exactly. >> All right. I guess my last question, well couple questions for you. What are some of the things that excited you that you heard from Adam Selipsky this morning? Anything from the keynote that stood out in terms of- >> Dave: Did you listen to the keynote? >> I did not. I had customer calls this morning. >> Okay, so they're bringing- >> East coast time, east coast time. >> One of the things that will excite you I think is they're connecting, making it easier to connect their databases. >> Eleanor: That would very much exciting. >> Aurora and Redshift, right? Okay. And they're making it easier to share data. I dunno if it goes across regions, but they're doing better integration. >> Amazing. >> Right? And you guys are integrating with those tools, right? Those data platforms. So that to me was a big thing for you guys. >> It is also and what a big thing Retool does is you can build a UI layer for your application on top of every single data source. And you hear, it's funny, you hear people talk about the 360 degree review of the customer so much. This is another, it's not our primary value proposition, but it is certainly another way to get there is if you have data from their desk tickets from in Redshift, you have data from Stripe, from their payments, you have data from Twilio from their text messages, you have data from DataDog where they're having your observability where you can notice analytics issues. You can actually just use Retool to build an app that sits on top of that so that you can give your support team, your sales team, your account management team, customer service team, all of the data that they need on their customers. And then you can build workflows so that you can do automated customer engagement reports. I did a Slack every week that shows what our top customers are doing with the product and that's built using all of our automation software as well. >> The integration is so important, as you just articulated, because every, you know, we say every company's a software company these days. Every company's a data company. But also, the data democratization that needs to happen to be able for lines of business so that data moves out of certain locked in functions and enables lines of business to use it. To get that visibility that you were just talking about is really going to be a competitive advantage for those that survive and thrive and grow in this market. >> It's able to, I think it's first it's visibility, but then it's action. And I think that's what Retool does very uniquely as well is it can take and unite the data from all the places, takes it out of the black box, puts it in front of the teams, and then enables them to act on it safely and securely. So not only can you see who might be fraudulent, you can flag them as fraud. Not only can you see who's actually in danger, you can click a button and send them an email and set up a meeting. You can set up an approval workflow to bring in an exec for engagement. You can update a password for someone in one place where you can see that they're having issues and not have to go somewhere else to update the password. So I think that's the key is that Retool can unlock the data visibility and then the action that you need to serve your customers. >> That's a great point. It's all about the actions, the insights that those actions can be acted upon. Last question for you. If you had a billboard that you could put any message that you want on Retool, what would it say? What's the big aha? This is why Retool is so great. >> I mean, I think the big thing about Retool is it's changing the economics of software development. It takes something that previously would've been below the line and that wouldn't get prioritized because it wasn't customer facing and makes it possible. And so I would say one of two billboards if I could be a little bit greedy, one would be Retool changed the economics of software development and one would be build operations software at the speed of thought. >> I love that. You're granted two billboards. >> Eleanor: Thank you. >> Those are both outstanding. Eleanor, it's been such a pleasure having you on the program. Thank you for talking to us about Retool. >> Eleanor: Thank you. >> Operations software and the massive impact that automating it can make for developers, businesses alike, all the way to the top line. We appreciate your insights. >> Thank you so much. >> For our guests and Dave Vellante, I'm Lisa Martin. You're watching theCUBE, the leader in live, emerging, and enterprise tech coverage. (gentle music)

>>Welcome back everyone to the cubes coverage here in Seattle, Washington for AWS's marketplace seller conference. The big news here is that the Amazon partner network and marketplace coming together and reorganizing into one organization, the AIST partner organization, APO bringing together the best of the partnership and the marketplace to sell through. It's a sellers company. This is the second year, but technically with COVID, I call it a year and a half. This is the cube. I'm John for your host. Got a great guest, Leah for sale vice president of business development at four square. Leah, thanks for coming on the cube. Look great. Yeah. >>Hey, thanks. Thanks for having me here. >>So four square, everyone, and that has internet history knows you. You check in you'd become the mayor of a place right back in the day, all fun. It was a great app and I think it was competitor go sold the Facebook, but that was the beginning of location data. Now you got Uber apps, you got all apps, location, everywhere. Data is big here in the marketplace. They sell data, they got a data exchange, Chris head of marketplaces. Like we have all these things we're gonna bring 'em together, make it simpler. So you're on the data side. I'm assuming you're selling data and you're participating at the data exchange. What is Foursquare doing right now? Yeah, >>Exactly. So we are part of the data exchange. And you mentioned checking in. So we, we are really proud of our roots, the, the four square app, and that's kind of the basis still of our business. We have a hundred million data points, which are actually places of interest across the world 200 countries. And we are we're in the business of understanding whereplace are and how people move through those places over time. And >>What's the value proposition for that data. You're selling the data. >>We are selling the data and we're selling it. You can think about use cases. Like how can I improve the engagement with my app through location data? So for example, next door, as a customer of ours, everyone knows next door. When a new business comes online, they wanna make sure that business is a real business. So they use our places to ensure that the address of that business is accurate. >>So how did you, how do you guys get your data? Because if you don't have the first party app, you probably had critical mass of data. Yeah. But then do other people use your data and then re contribute back in kinda like, well, Stripe is for financial. You guys are plugging in yeah. To >>Apps. A great question. So we still do have our consumer apps. We're still proud of those. It's still a basis of our company really. Okay. So, but we take that data. So our first party data, we also, for all the web, we have some partners integrate our SDK. And so we're pulling in all that data from various sources and then scrubbing it and making sure we have the most unique. >>So you guys still have a business where the app's working. Yep. Okay. But also let's just say, I wanna have a cube app. Yeah. And I want to do a check in button. Yep. So rather than build checking in, could I OEM you could four square is that you >>Could, and we could help you understand where people are checking in. So we know someone's here at the Hilton and Bellevue, we know exactly where that place is. You building the Cub app. You could say, I'm gonna check in here and we are verified. We know that that's the >>Right place. So that's a good for developer if they're building an app. >>Absolutely. So we have an SDK that any developer can integrate. >>Great. Okay. So what's the relationship with the marketplace? Take us through how Foursquare works with AWS marketplace. >>Sure. So we are primarily integrated with ADX, which is sort of a piece of marketplace it's for data specifically, we have both of our main products, which are places that POI database and visits, which is how people move through those places over time. So we're able to say these are the top chains in the country. Here's how people move throughout those. And both those products are listed on ADX. >>So if I'm in Palo Alto and I go to Joe in the juice yeah. You know that I kind of hang in one spot or is it privacy there? I mean, how do you know like what goes on? Well, >>We know somebody does that. We don't >>Know that you do that. So >>We ensure, you know, we're very privacy centric and privacy focused. We're not gonna, we don't tell anybody at you >>Yourself it's pattern data. It is. >>Okay. So it's normalized data, right? Over time groups of people, >>How they, how are people using the data to improve processes, user experience? What are some of the use cases? >>So that example, nextdoor, that's really a use case that we see a lot and that's improving their application. So that nextdoor app to ensure that the ACC, the data's accurate and that as you, as a user, you know, that that business is real. Cuz it's verified by four wear. Another one is you can use our data to make business decisions around where you're gonna place your next loca. You know, your next QSR. So young brands is a customer of ours. Those are, those guys are pizza hut KFC. They work with us to figure out where they should put their next KFC. Yeah. >>I mean retail location, location, location. Yeah. >>Right. Yeah. People are still, even though e-commerce right. People still go into stores >>And still are. Yeah. There's, there's, there's probably lot, a lot of math involved in knowing demographics patterns. Volume. >>Yeah. Some of our key customers are really data scientists. Like the think about cus with businesses that have true data science companies. They're really looking at that. >>Yeah. I mean in, and out's on the exit for a reason. Right. They want in and out. Yeah. So they wanna put it inland. >>Right. And we can actually tell you where that customer from in and out where they go next. Right. So then, you know, oh, they go to this park or they go somewhere and we can help you place your next in and out based on that visitation. >>Yeah. And so it's real science involved. So take us through the customers. You said data scientists, >>Mostly data scientists is kind of a key customer data science at a large corporation, like a QSR that's >>Somebody. Okay. So how is the procurement process on the marketplace? What does the buyer get? >>So what we see the real value is, is because they're already a customer of Amazon. That procurement is really easy, right? All the fulfillment goes through Amazon, through ADX. And what you're buying is either at API. So you can, that API can make real time calls or you're buying a flat file, like an actual database of those hundred points of interest. >>And then they integrate into their tool set. Right. They can do it. So it's pretty data friendly in terms of format. >>You can kind of do whatever you want with it. We're gonna give you that as long as you're smart enough to figure out what to do. Do we have a >>Lot of, so what's your experience with AWS marketplace? I mean, obviously we, we see a lot of changes. They had a reorg partner network merging with marketplace. You've been more on the data exchange, Chris kind of called that out. It's yeah. It's kind of a new thing. And, and he was hinting at a lot of confusion, but simplifying things. Yeah. What's your take of the current AWS marketplace >>Religions? I actually think ADX because our experience has primarily been ADX. I think they've done a really good job. They've really focused on the data and they understand how CU, how, you know, people like us sell our data. It hasn't been super confusing. We've had a lot of support. I think that's what Amazon gives you. You have to put a lot of effort into it, but they're also, they also give you a lot of support. >>Yeah. And, and I think data exchange is pretty significant to the strategic. It is >>Mission. It is. We feel that. Yeah. You know, we feel like they really value us as a partner. >>What's the big thing you're seeing out there right now in data, because like you're seeing a lot more data exchanges going on. There's always been data exchange, but you're seeing a lot more exchanges between companies. So let's just take partners. You're seeing a lot more people handle front end of a, a supply chain and you got more data exchanges. What's the future of data exchanges. If you had to kind of, you know, guess given your history in, in the industry. Yeah. What's the next around the corner trend? >>I think. Well, I think there's a, has to be consolidation. I know everyone's building one, but there's probably too many. I know from our experience, we can't support all of them. We're not a huge company. We can't support Amazon and X and Y and Z. Like it's just too many. So we kind of put all of our eggs in a couple baskets. So I think there'll be consolidation. I think there has to be just some innovation on what data products are, you know, for us, we have these two, it's an API and a flat file. I think as exchanges think about, you know, expanding what are the other types of data products that can help us build? >>Yeah. I mean, one of the things that's, you know, we see, we cover a lot of on the cube is edge. You know, you got, yeah. Amazon putting out new products in regions, you got new wavelength out there, you got regions, you got city level connectivity, data coming from cars. So a lot more IOT data. How do you guys see that folding into your vision of data acquisition and data usage, leverage, reuse, durability. These >>Are, yeah. I mean, we're, we are keeping an eye on all of that. You know, I think we haven't quite figured out how we wanna allocate resources against it, but you know, it's definitely, it's a really interesting space to be in. Like, I don't think data's going anywhere and I think it's really just gonna grow and how people use it's >>Gonna expand. Okay. So if I'm a customer, I go to the marketplace, I wanna buy four square data. What's the pitch. >>We can help you improve your business decisions or your applications through location data. We know where places are and how people move through the world over time. So we can tell you we're, we're sure that this is the Hilton in Bellevue. We know that, that we know how many people are moving through here and that's really the pitch. >>And they use that for whatever their needs are, business improvement, user experience. Yeah. >>Those are really the primary. I mean, we also have some financial use cases. So hedge funds, maybe they're thinking about yeah. How they wanna invest their money. They're gonna look at visits over time to understand what people are doing. Right. The pandemic made that super important. >>Yeah. That's awesome. Well, this is great. Great success story. Congratulations. And thanks for sharing on the cube. Really appreciate you coming on. Thank you. My final question is more about kind of the future. I wanna get your thoughts because your season pro, when you have the confluence of physical and digital coming together. Yeah. You know, I was just talking with a friend about FedEx's earnings, comparing that to say, AWS has a fleet of delivery too. Right? Amazon, Amazon nots. So, but physical world only products location matters. But then what about the person when they're walking around the real world? What happens when they get to the metaverses or, you know, they get to digital, they tend an event. Yeah. How do you see that crossroad? Cuz you have foot in both camps. We do, you got the app and you got the physical world it's gonna come together. Is there thoughts around, you can take your course care hat off and put your industry hat on. Yeah. You wanna answer that? Not officially on behalf of Foursquare, but I'm just curious, this is a, this is the confluence of like the blending of physical and digital. >>Yeah. I know. Wow. I admittedly haven't thought a whole lot about that. I think it would be really weird if I could track myself over time and the metaverse I mean, I think, yeah, as you said, it's >>It's, by the way, I'm not Bo on the metaverse when it's blocked diagrams, when you have gaming platforms that are like the best visual experience possible, right? >>Yeah. I mean, I think it, I think we'll see, I don't, I don't know that I have a >>Prediction, well hybrid we've seeing a lot of hybrid events. Like this event is still intimate VIP, but next year I guarantee it's gonna be larger, much larger and it's gonna be physical and face to face, but, but digital right as well. Yeah. Not people experiencing the, both that first party, physical, digital hybrid. Yeah. And it's interesting something that we track a lot >>Of. Yeah, for sure. Yeah. I think we'll have a, well, I think we'll, there's something there for us. I think that those there's a play there as we watch kind >>Of things change. All right, Leah, thank you for coming on the Q appreciate so much it all right. With four Graham, John fur a year checking in with four square here on the cube here at the Amazon web services marketplace seller conference. Second year back from the pandemic in person, more coverage after this break.

(gentle upbeat music) >> Okay, welcome back everyone to theCUBE's live coverage here in Boston, Massachusetts for AWS RE:INFORCE 22. I'm John Furrier, your host with Dave Vellante co-host of theCUBE, and Shreyans Metah, CTO and founder of Cequence Security. CUBE alumni, great to see you. Thanks for coming on theCUBE. >> Yeah. Thanks for having me here. >> So when we chatted you were part of the startup showcase. You guys are doing great. Congratulations on your business success. I mean, you guys got a good product in hot market. >> Yeah. >> You're here before we get into it. I want to get your perspective on the keynote and the talk tracks here and the show. But for the folks that don't know you guys, explain what you guys, take a minute to explain what you guys do and, and key product. >> Yeah, so we are the unified API protection place, but I mean a lot of people don't know what unified API protection is but before I get into that, just just talking about Cequence, we've been around since 2014. But we are protecting close to 6 billion API transactions every day. We are protecting close to 2 billion customer accounts, more than 2 trillion dollars in customer assets and a hundred million plus sort of, data points that we look at across customer base. That's that's who we are. >> I mean, of course we all know APIs is, is the basis of cloud computing and you got successful companies like Stripe, for instance, you know, you put API and you got a financial gateway, billions of transactions. What's the learnings. And now we're in a mode now where single point of failure is a problem. You got more automation you got more reasoning coming a lot more computer science next gen ML, AI there too. More connections, no perimeter. Right? More and more use cases, more in the cloud. >> Yeah. So what, what we are seeing today is, I mean from six years ago to now, when we started, right? Like the monolith apps are breaking down into microservices, right? What effectively, what that means is like every of the every such microservices talking APIs, right? So what used to be a few million web applications have now become billions of APIs that are communicating with each other. I mean, if you look at the, I mean, you spoke about IOT earlier, I call, I call like a Tesla is an application on four wheels that is communicating to its cloud over APIs. So everything is API yesterday. 80% traffic on internet is APIs. >> Now that's dated transit right there. (laughing) Couldn't resist. >> Yeah. >> Fully encrypted too. >> Yeah. >> Yeah, well hopefully. >> Maybe, maybe, maybe. (laughing) We dunno yet, but seriously everything is talking to an API. >> Yeah. >> Every application. >> Yeah. And, and there is no single choke point, right? Like you spoke about it. Like everybody is hosting their application in the cloud environments of their choice, AWS being one of them. But it's not the only one. Right? The, the, your APIs are hosted behind a CDN. Your APIs are hosted on behind an API gateway behind a load balancer in guest controllers. There is no single. >> So what's the problem? What's the problem now that you're solving? Because one was probably I can imagine connecting people, connecting the APIs. Now you've got more operational data. >> Yeah. >> Potential security hacks? More surface area? What's the what's what are you facing? >> Well, I can speak about some of the, our, some of the well known sort of exploits that have been well published, right. Everybody gets exploited, but I mean some of the well knowns. Now, if you, if you heard about Expedian last year there was a third party API that was exposing your your credit scores without proper authentication. Like Facebook had Ebola vulnerability sometime ago, where people could actually edit somebody else's videos online. Peloton again, a well known one. So like everybody is exposed, right. But that is the, the end results. All right? But it all starts with people don't even know where their APIs are and then you have to secure it all the way. So, I mean, ultimately APIs are prone to business logic attacks, fraud, and that's what, what you need to go ahead and protect. >> So is that the first question is, okay, what APIs do I need to protect? I got to take a API portfolio inventory. Is that? >> Yeah, so I think starting point is where. Where are my APIs? Right, so we spoke about there's no single choke point. Right, so APIs could be in, in your cloud environment APIs could be behind your cloud front, like we have here at RE:INFORCE today. So APIs could be behind your AKS, Ingrid controllers API gateways. And it's not limited to AWS alone, right. So, so knowing the unknown is, is the number one problem. >> So how do I find him? I asked Fred, Hey, where are our API? No, you must have some automated tooling to help me. >> Yeah, so, I, Cequence provides an option without any integration, what we call it, the API spider. Whereas like we give you visibility into your entire API attack surface without any integration into any of these services. Where are your APIs? What's your API attack surface about? And then sort of more details around that as well. But that is the number one. Is that agent list or is that an agent? >> There's no agent. So that means you can just sign up on our portal and then, then, then fire it away. And within a few minutes to an hour, we'll give you complete visibility into where your API is. >> So is it a full audit or is it more of a discovery? >> Or both? >> So, so number one, it's it's discovery, but we are also uncovering some of the potential vulnerabilities through zero knowledge. Right? So. (laughing) So, we've seen a ton of lock for J exposed server still. Like recently, there was an article that lock four J is going to be endemic. That is going to be here. >> Long time. >> (laughs) For, for a very long time. >> Where's your mask on that one? That's the Covid of security. >> Yeah. Absolutely absolutely. So, you need to know where your assets are what are they exposing? So, so that is the first step effectively discovering your attack surface. Yeah. >> I'm sure it's a efficiency issue too, with developers. The, having the spider allows you to at least see what's connecting out there versus having a meeting and going through code reviews. >> Yeah. Right? Is that's another big part of it? >> So, it is actually the last step, but you have, you actually go through a journey. So, so effectively, once you're discovering your assets you actually need to catalog it. Right. So, so I know where they're hosted but what are developers actually rolling out? Right. So they are updating your, the API endpoints on a daily basis, if not hourly basis. They have the CACD pipelines. >> It's DevOps. (laughing) >> Welcome to DevOps. It's actually why we'll do it. >> Yeah, and people have actually in the past created manual ways to catalog their APIs. And that doesn't really work in this new world. >> Humans are terrible at manual catalogization. >> Exactly. So, cataloging is really the next step for them. >> So you have tools for that that automate that using math, presumably. >> Exactly. And then we can, we can integrate with all these different choke points that we spoke about. There's no single choke points. So in any cloud or any on-prem environment where we actually integrate and give you that catalog of your APIs, that becomes your second step really. >> Yeah. >> Okay, so. >> What's the third step? There's the third step and then compliance. >> Compliance is the next one. So basically catalog >> There's four steps. >> Actually, six. So I'll go. >> Discovery, catalog, then compliance. >> Yeah. Compliance is the next one. So compliance is all about, okay, I've cataloged them but what are they really exposing? Right. So there could be PII information. There could be credit card, information, health information. So, I will treat every API differently based on the information that they're actually exposing. >> So that gives you a risk assessment essentially. >> Exactly. So you can, you can then start looking into, okay. I might have a few thousand API endpoints, like, where do I prioritize? So based on the risk exposure associated with it then I can start my journey of protecting so. >> That that's the remediation that's fixing it. >> Okay. Keep going. So that's, what's four. >> Four. That was that one, fixing. >> Yeah. >> Four is the risk assessment? >> So number four is detecting abuse. >> Okay. >> So now that I know my APIs and each API is exposing different business logic. So based on the business you are in, you might have login endpoints, you might have new account creation endpoint. You might have things around shopping, right? So pricing information, all exposed through APIs. So every business has a business logic that they end up exposing. And then the bad guys are abusing them. In terms of scraping pricing information it could be competitors scraping pricing. They will, we are doing account take. So detecting abuse is the first step, right? The fifth one is about preventing that because just getting visibility into abuse is not enough. I should be able to, to detect and prevent, natively on the platform. Because if you send signals to third party platforms like your labs, it's already too late and it's too course grain to be able to act on it. And the last step is around what you actually spoke about developers, right? Like, can I shift security towards the left, but it's not about shifting left. Just about shifting left. You obviously you want to bring in security to your CICD pipelines, to your developers, so that you have a full spectrum of API securities. >> Sure enough. Dave and I were talking earlier about like how cloud operations needs to look the same. >> Yeah. >> On cloud premise and edge. >> Yes. Absolutely. >> Edge is a wild card. Cause it's growing really fast. It's changing. How do you do that? Cuz this APIs will be everywhere. >> Yeah. >> How are you guys going to reign that in? What's the customers journey with you as they need to architect, not just deploy but how do you engage with the customer who says, "I have my environment. I'm not going to be to have somebody on premise and edge. I'll use some other clouds too. But I got to have an operating environment." >> Yeah. "That's pure cloud." >> So, we need, like you said, right, we live in a heterogeneous environment, right? Like effectively you have different, you have your edge in your CDN, your API gateways. So you need a unified view because every gateway will have a different protection place and you can't deal with 5 or 15 different tools across your various different environments. So you, what we provide is a unified view, number one and the unified way to protect those applications. So think of it like you have a data plane that is sprinkled around wherever your edges and gateways and risk controllers are and you have a central brains to actually manage it, in one place in a unified way. >> I have a computer science or computer architecture question for you guys. So Steven Schmidt again said single controls or binary states will fail. Obviously he's talking from a security standpoint but I remember the days where you wanted a single point of control for recovery, you talked about microservices. So what's the philosophy today from a recovery standpoint not necessarily security, but recovery like something goes wrong? >> Yeah. >> If I don't have a single point of control, how do I ensure consistency? So do I, do I recover at the microservice level? What's the philosophy today? >> Yeah. So the philosophy really is, and it's very much driven by your developers and how you want to roll out applications. So number one is applications will be more rapidly developed and rolled out than in the past. What that means is you have to empower your developers to use any cloud and serverless environments of their choice and it will be distributed. So there's not going to be a single choke point. What you want is an ability to integrate into that life cycle and centrally manage that. So there's not going to be a single choke point but there is going to be a single control plane to manage them off, right. >> Okay. >> So you want that unified, unified visibility and protection in place to be able to protect these. >> So there's your single point of control? What about the company? You're in series C you've raised, I think, over a hundred million dollars, right? So are you, where are you at? Are you scaling now? Are you hiring sales people or you still trying to sort of be careful about that? Can you help us understand where you're at? >> Yeah. So we are absolutely scaling. So, we've built a product that is getting, that is deployed already in all these different verticals like ranging from finance, to detail, to social, to telecom. Anybody who has exposure to the outside world, right. So product that can scale up to those demands, right? I mean, it's not easy to scale up to 6 billion requests a day. So we've built a solid platform. We've rolled out new products to complete the vision. In terms of the API spider, I spoke about earlier. >> The unified, >> The unified API protection covers three aspects or all aspects of API life cycle. We are scaling our teams from go to market motion. We brought in recently our chief marketing officer our chief revenue officer as well. >> So putting all the new, the new pieces in place. >> Yeah. >> So you guys are like API observability on steroids. In a way, right? >> Yeah, absolutely. >> Cause you're doing the observability. >> Yes. >> You're getting the data analysis for risk. You're having opportunities and recommendations around how to manage the stealthy attacks. >> From a full protection perspective. >> You're the API store. >> Yeah. >> So you guys are what we call best of breed. This is a trend we're seeing, pick something that you're best in breed in. >> Absolutely. >> And nail it. So you're not like an observability platform for everything. >> No. >> You guys pick the focus. >> Specifically, APS. And, so basically your, you can have your existing tools in place. You will have your CDN, you will have your graphs in place. So, but for API protection, you need something specialized and that stuff. >> Explain why I can't just rely on CDN infrastructure, for this. >> So, CDNs are, are good for content delivery. They do your basic TLS, and things like that. But APIs are all about your applications and business that you're exposing. >> Okay, so you, >> You have no context around that. >> So, yeah, cause this is, this is a super cloud vision that we're seeing of structural change in the industry, a new thing that's happening in real time. Companies like yours are be keeping a focus and nailing it. And now the customer's can assemble these services and company. >> Yeah. - Capabilities, that's happening. And it's happening like right now, structural change has happened. That's called the cloud. >> Yes. >> Cloud scale. Now this new change, best of brief, what are the gaps? Because I'm a customer. I got you for APIs, done. You take the complexity away at scale. I trust you. Where are the other gaps in my architecture? What's new? Cause I want to run cloud operations across all environments and across clouds when appropriate. >> Yeah. >> So I need to have a full op where are the other gaps? Where are the other best of breed components that need to be developed? >> So it's about layered, the layers that you built. Right? So, what's the thing is you're bringing in different cloud environments. That is your infrastructure, right? You, you, you either rely on the cloud provider for your security around that for roll outs and operations. Right? So then is going to be the next layer, which is about, is it serverless? Is it Kubernetes? What about it? So you'll think about like a service mesh type environment. Ultimately it's all about applications, right? That's, then you're going to roll out those applications. And that's where we actually come in. Wherever you're rolling out your applications. We come in baked into that environment, and for giving you that visibility and control, protection around that. >> Wow, great. First of all, APIs is the, is what cloud is based on. So can't go wrong there. It's not a, not a headwind for you guys. >> Absolutely. >> Great. What's a give a quick plug for the company. What are you guys looking to do hire? Get customers who's uh, when, what, what's the pitch? >> So like I started earlier, Cequence is around unified API protection, protecting around the full life cycle of your APIs, ranging from discovery all the way to, to testing. So, helping you throughout the, the life cycle of APIs, wherever those APIs are in any cloud environment. On-prem or in the cloud in your serverless environments. That's what Cequence is about. >> And you're doing billions of transactions. >> We're doing 6 billion requests every day. (laughing) >> Which is uh, which is, >> A lot. >> Unheard for a lot of companies here on the floor today. >> Sure is. Thanks for coming on theCUBE, sure appreciate it. >> Yeah. >> Good, congratulations to your success. >> Thank you. >> Cequence Security here on theCUBE at RE:INFORCE. I'm chatting with Dave Vellante, more coverage after this short break. (upbeat, gentle music)

(upbeat music) >> Man: We're good. >> Hey everyone. Welcome back to theCube's live coverage of AWS Summit NYC. We're in New York City, been here all day. Lisa Martin, John Furrier, talking with AWS partners ecosystem folks, customers, AWS folks, you name it. Next up, one of our alumni, rejoins us. Please welcome Anshu Sharma the co-founder and CEO of Skyflow. Anshu great to have you back on theCube. >> Likewise, I'm excited to be back. >> So I love how you guys founded this company. Your inspiration was the zero trust data privacy vault pioneered by two of our favorites, Apple and Netflix. You started with a simple question. What if privacy had an API? So you built a data privacy vault delivered as an API. Talk to us, and it's only in the last three and a half years. Talk to us about a data privacy vault and what's so unique about it. >> Sure. I think if you think about all the key challenges we are seeing in our personal lives when we are dealing with technology companies a lot of anxiety is around what happens to my data, right? If you want to go to a pharmacy they want to know not just your health ID number but they want to know your social security number your credit card number, your phone number and all of that information is actually useful because they need to be able to engage with you. And it's true for hospitals, health systems. It's true for your bank. It's true for pretty much anybody you do business with even an event like this. But then question that keeps coming up is where does this data go? And how is it protected? And the state of the art here has always been to keep kind of, keep it protected when it's in storage but almost all the breaches, all the hacks happen not because you've steal somebody's disc, but because someone enters through an API or a portal. So the question we asked was we've been building different shapes of containers for different types of data. You don't store your logs in a data warehouse. You don't store your analytical data in a regular RDBMS. Similarly, you don't store your passwords and usernames you store them in identity systems. So if PI is so special why isn't it a container that's used for storing PII? So that's how the idea of Pii.World came up. >> So you guys just got a recent funding, a series B financing which means for the folks out there that don't know the inside baseball, must people do, means you're doing well. It's hard to get that round of funding means you're up and growing to the right. What's the differentiator? Why are you guys so successful? Why the investment growth, what's the momentum driver? >> So I think in some ways we took one of the most complex problems, data privacy, like half the people can't even describe like, does data privacy mean like I have to be GDPR compliant or does it actually mean I'm protecting the data? So you have multiple stakeholders in any company. If you're a pharma company, you may have a chief privacy officer, a data officer, this officer, that officer, and all of these people were talking and the answer was buy more tools. So if you look around behind our back, there's probably dozens of companies out there. One protecting data in an API call another protecting data in a database, another one data warehouse. But as a CEO, CTO, I want to know what happens to my social security number from a customer end to end. So we said, if you can radically simplify the whole thing and the key insight was you can simplify it by actually isolating and protecting this data. And this architecture evolved on its own at companies like Apple and other places, but it takes dozens of engineers for those companies to build it out. So we like, well, the pattern will makes sense. It logically kind is just common sense. So instead of selling dozens of tools, we can just give you a very simple product, which is like one API call, you know, protect this data... >> So like Stripe is for a plugin for a financial transaction you plug it into the app, similar dynamic here, right? >> Exactly. So it's Stripe for payments, Twilio for Telephony. We have API for everything, but if you have social security numbers or pan numbers you still are like relying on DIY. So I think what differentiated us and attracted the investors was, if this works, >> It's huge. every company needs it. >> Well, that's the integration has become the key thing. I got to ask you because you mentioned GDPR and all the complexities around the laws and the different regulations. That could be a real blocker in a wet blanket for innovation. >> Anshu: Yes. >> And with the market we're seeing here at, at your Summit New York, small event. 10,000 people, more people here than were at Snowflake Summit as an example. And they're the hottest company in data. So this small little New York event is proven that that world is growing. So why should this wet blanket, these rules slow it down? How do you balance it? 'Cause that's a concern. If you checking all the boxes you're never actually building anything. >> So, you know, we just ran into a couple of customers who still are struggling with moving from the data center to AWS Cloud. Now the fact that here means they want to but something is holding them back. I also met the AI team of Amazon. They're doing some amazing work and they're like, the biggest hindrance for them is making customers feel safe when they do the machine learning. Because now you're opening up the data sets to more people. And in all of those cases your innovation basically stops because CSO is like, look you can't put PII in the cloud unprotected. And with the vault architecture we call it privacy by architecture. So there's a term called privacy by design. I'm like what the, is privacy by design, right? >> John: It's an architecture. (John laughing) >> But if you are an architecture and a developer like me I was like, I know what architecture is. I don't know what privacy by design is. >> So you guys are basically have that architecture by design which means foundational based services. So you're providing that as a service. So other people don't have to build the complex. >> Anshu: Exactly. >> You know that you will be Apple's backend team to build that privacy with you you get all that benefit. >> Exactly. And traditionally, people have had to make compromises. If you encrypt the data and secure it, then you can't use it. Using a proprietary polymorphic encryption technology you can actually have your cake and eat it to. So what that means for customers is, if you want to protect data in Snowflake or REDshare, use Skyflow with it. We have integrations to databases, to data lakes, all the common workflow tools. >> Can you give us a customer example that you think really articulates the value of what Skyflow is delivering? >> Well, I'll give you two examples. One in the FinTech space, one in the health space. So in the FinTech space this is a company called Nomi Health. They're a large payments processor for the health insurance market. And funnily enough, their CTO actually came from Goldman Sachs. He actually built apple card. (John laughing) Right? That if we all have in our phones. And he saw our product and he's like, for my new company, I'm going to just use you guys because I don't want to go hire 20 engineers. So for them, we had a HIPAA compliant environment a PCI compliant environment, SOC 2 compliant environment. And he can sleep better at night because he doesn't have to worry what is my engineer in Poland or Ukraine doing right now? I have a vault. I have rules set up. I can audit it. Everything is logged. Similarly for Science 37, they run clinical trials globally. They wanted to solve data residency. So for them the problem was, how do I run one common global instance? When the rules say you have to break everything up and that's very expensive. >> And so I love this. I'm a customer. For them a customer. I love it. You had me at hello, API integration. I love it. How much does it cost? What's it going to cost me? How do I need to think about my operationalizing? 'Cause I know with an API, I can do that. Am I paying by the usage, by the drink? How do I figure out? >> So we have programs for startups where it's really really inexpensive. We get them credits. And then for enterprises, we basically have a platform fee. And then based on the amount of data PII, we charge them. We don't nickel and dime the customers. We don't like the usage based model because, you don't know how many times you're going to hit an API. So we usually just based on the number of customer records that you have and you can hit them as many time as you want. There's no API limits. >> So unlimited record based. >> Exactly. that's your variable. >> Exactly. We think about you buying odd zero, for example, for authentication you pay them by the number of active users you have. So something similar. >> So you run on AWS, but you just announced a couple of new GTM partners, MuleSoft and plan. Can you talk to us about, start with MuleSoft? What are you doing and why? And the same with VLA? >> Sure. I mean, MuleSoft was very interesting customers who were adopting our products at, you know, we are buying this product for our new applications but what about our legacy code? We can't go in there and add APIs there. So the simplest way to do integration in the legacy world is to use an integration broker. So that's where MuleSoft integration came out and we announced that. It's a logical place for you to swap out real social security numbers with, you know, fake ones. And then we also announced a partnership with SnowFlake, same thing. I think every workload as it's moving to the cloud needs some kind of data protection with it. So I think going forward we are going to be announcing even more partnerships. So you can imagine all the places you're storing PII today whether it's in a call center solution or analytics solution, there's a PII story there. >> Talk about the integration aspect because I love the momentum. I get everything makes secure the customers all these environments, integrations are super important to plug into. And then how do I essentially operate you on my side? Do I import the records? How do you connect to my environment in my databases? >> So it's really, really easy when you encrypt the data and use Skyflow wall, we create what is called a format preserving token, which is essentially replacing a social security number with something that looks like an SSN but it's not. So that there's no schema changes involved. You just have to do that one time swap over and then in terms of integrations, most of these integrations are prebuilt. So Snowflake integration is prebuilt. MuleSoft integration is prebuilt. We're going to announce some new ones. So the goal is for off the table in platforms like Snowflake and MuleSoft, we prebuilt all the integrations. You can build your own. It takes about like a day. And then in terms of data import basically it's the same standard process that you would use with any other data store. >> Got to ask you about data breaches. Obviously the numbers in 2021 were huge. We're seeing so much change in the cyber security landscape ransomware becoming a household word, a matter of when but not if... How does Skyflow help organizations protect themselves or reduce the number of breaches so that they are not the next headline? >> You know, the funny thing about breaches is again and again, we see people doing the same mistakes, right? So Equifax had a breach four years ago where a customer portal, you know, no customer support rep should have access to a 100 million people's data. Like is that customer agent really accessing 100 million? But because we've been using legacy security tools they either give you access or don't give you access. And that's not how it's going to work. Because if I'm going to engage with the pharmacy and airline they need to be able to use my data in multiple different places. So you need to have fine grain controls around it. So I think the reason we keep getting breaches is cybersecurity industry is selling, 10s of billions of dollars worth of tools in the name of security but they cannot be applied at a fine grain level enough. I can't say things like for my call center agent that's living in Phoenix, Arizona they can only verify last four digits, but the same call center worker in Philippines can't even see that. So how do you get all that granular control in place? Is really why we keep seeing data breaches. So the Equifax breach, the Shopify breach the Twitter breaches, they're all the same. Like again and again, it's either an inside person or an external person who's gotten in. And once you're in and this is the whole idea of zero trust as you know. Once you're in, you can access all the data. Zero trust means that you don't assume that you actually isolate PII separately. >> A lot of the cybersecurity issues as you were talking about, are people based. Somebody clicking on something or gaining access. And I always talk to security experts about how do you control for the people aspect besides training, awareness, education. Is Skyflow a facilitator of that in a way that we haven't seen before? >> Yeah. So I think what ends up happening is, people even after they have breaches, they will lock down the system that had the breach, but then they have the same data sitting in a partner database, maybe a customer database maybe a billing system. So by centralizing and isolating PII in one system you can then post roles based access control rules. You can put limitations around it. But if you try to do that across hundreds of DS bases, you're just not going to be able to do it because it's basically just literally impossible, so... >> My final question for you is on, for me is you're here at AWS Summits, 10,000 people like I said. More people here than some big events and we're just in New York city. Okay. You actually work with AWS. What's next for you guys as you got the fresh funding, you guys looking for more talent, what's your next mountain you're going to climb? Tell us what's next for the company. Share your vision, put a plug in for the company. >> Well, it's actually very simple. Today we actually announced that we have a new chief revenue officer who's joining us. Tammy, she's joined us from LaunchDarkly which is it grew from like, you know, single digits to like over nine digits in revenue. And the reason she's joining Skyflow is because she sees the same inflection point hitting us. And for us that means more marketing, more sales, more growth in more geographies and more partnerships. And we think there's never been a better time to solve privacy. Literally everything that we deal with even things like rove evade issues eventually ties back into a issue around privacy. >> Lisa: Yes. >> AWS gets the model API, you know, come on, right? That's their model. >> Exactly. So I think if you look at the largest best companies that have been built in the last 20 years they took something that should have been simple but was not. There used to be Avayas of the world, selling Telephony intel, Twilio came and said, look an API. And we are trying to do the same to the entire security compliance and privacy industry is to narrow the problem down and solve it once. >> (indistinct) have it. We're going to get theCube API. (Lisa laughing) That's what we're going to do. All right. >> Thank you so much. >> Awesome. Anshu, thank you for joining us, talking to us about what's new at Skyflow. It sounds like you got that big funding investment. Probably lots of strategic innovation about to happen. So you'll have to come back in a few months and maybe at next reinvent in six months and tell us what's new, what's going on. >> Last theCube interview was very well received. People really like the kind of questions you guys asked. So I love this show and I think... >> It's great when you're a star like you, you got good market, great team, smart. I mean, look at this. I mean, what slow down are we talking about here? >> Yeah. I don't see... >> There is no slow down on the enterprise. >> Privacy's hot and it's incredibly important and we're only going to be seeing more and more of it. >> You can talk to any CIO, CSO, CTO or the board and they will tell you there is no limit to the budget they have for solving the core privacy issues. We love that. >> John: So you want to move on to building? >> Lisa: Obviously that must make you smile. >> John: You solved a big problem. >> Thank you. >> Awesome. Anshu, thank you again. Congrats on the momentum and we'll see you next time and hear more on the evolution of Skyflow. Thank you for your time. >> Thank you. >> For John furrier, I'm Lisa Martin. You're watching theCube live from New York City at AWS Summit NYC 22. We'll be right back with our next guest. So stick around. (upbeat music)

>>Hello, everyone. Welcome to the cubes presentation of the 80 startup showcase marketing technology, emerging cloud scale customer experiences. This is season two, episode three of the ongoing series covering the exciting startups from the, a AWS ecosystem to talk about all the top trends and also featuring the key customers. I'm your host, John ER, today we're joined by Louis Fernando, Denise vice president of peak pay social and John Kim, the CEO of Sandberg to learn about the future of what's going on in fostering deeper customer relationships. Gentlemen, thanks for joining us in the cube showcase, >>Excited to be here. >>So John talk about Sendbird real quick set the table for us. What you guys do, you got a customer here to highlight some of the key things you're doing with customers, the value proposition what's Sendbird and what's the showcase about, >>Yeah, I'm really excited to be here. Uh, I'm John founder, C of Sandberg. So Sandberg is the worst leading conversations platform for mobile applications. We can power user to user conversations in mobile applications, as well as the brand to user conversations such as marketing sales and support. So, uh, today we power over quarter billion users on a monthly basis. Uh, we have, you know, through over 300 employees across seven different countries around the world, we work with some of the world's leading, uh, uh, customers such as big pay that we are going to showcase today, along with other, uh, wonderful customers like DoorDash, Reddit, <inaudible> sports and so forth. We have collectively raised over 200 million in funding. Um, so that's kind of where we are today. >>Well, it's always great to have, uh, one great success. Uh, good funding, more important is the customers. And I love showcases where the customers do the talking, because that means you've got some success stories. Louise, talk about, um, are you happy customer? What's it like working with Sandberg? Give us the, give us the scoop. >>So sandbar is being a great partner with us. So pick pay is a Brazilian payment app. We're at a FinTech here with more than 30 million active users using everyday pick pay to pay everything. So the, the, the majority of the payments are between peers, between people. So sandbar is, is helping us to improve a lot this journey to make it more pleasant between every everyone who are using big, big. So we are here, let's talk and it's a >>Pleasure. Yeah, it's awesome. Well, I great to have you guys on great, great relationship. And one of the things we've been talking about on the cube, if the folks watching that know our audience, no we've been banging the, the drum hard on this new world and this new patterns of user expectations and building relationships in this new digital world is not about the old way, the old MarTech way. There are new new use cases, new expectations by the consumers, John, that are, that are bringing up new opportunities, but also expectations. It's not about, I mean, I mean, if someone's using discord, for example, cuz they're gamers, they're done discord. If they want to communicate with, with slack, they, I do slack, SMS, kind of old hat. You got WhatsApp, you've got all these now peer to peer organic connections, multiple channels. This is all the new world. What's your vision on this new relationship building digital communication world. >>Yeah. So I, I think you brought a really good point there. One of the most frequently used applications in the world today are messaging applications across any countries, any region, any culture, if you look at the most frequently used and most longest used applications are usually some form of a, a messaging application. Now the end users or the customers in the world are so used to using, uh, uh, such a, you know, frictionless ver very responsive, modern experience on those messaging applications. What we want to help with the business around the world, the 99.9% of the business around the world don't have those really te knowledge or user experience expertise in messaging. So we want to help our businesses, help our customers be able to harness the power of modern messaging capabilities and then be able to embed it in their own business so that they can retain their users on their platform, engage with them in the con context that their, uh, what their business is about so that they can not only, uh, control or provide a better user experience, but also be able to, uh, understand their users better, uh, understand what they're doing on their businesses, be able to own and, uh, control the data in a more secure and safe way. >>So really it's uh, we're like the Robin hood of the world trying to keep superpower yeah. Back to the businesses. >>Yeah. Deal from the rich idea, the messaging scale. Bring that to everybody else. I love that. Uh, and you got kind of this double int Robin hood kind of new for the new generation finance. This is about taking the advantage of scalable platforms, monopolies, right. And giving the entrepreneur an opportunity to have that same capability feature, rich Louise PPE. You guys used Sendbird together. You have to level up, you gotta compete with those big monopolies to pride, scalable conversations. Okay. How did you engage this? What was your success path look? What was it look like? >>Yeah. When we look to this majority, the bigger chat apps that we have nowadays in the market, we are looking to them and then Brazilians are using for their daily course, but Brazilians are paying every day millions and millions of payments. And these chat apps are not, uh, able to, to, to deal with these payments. So what we are doing here is that, uh, providing a solution where every conversation that are going to happen before, during, or after a payment between the, the people, they would, uh, uh, have a nice platform that could afford all, all of their emotions and discussions that they have to do before or after the payment. So we are putting together the chat platform and we with the payment platform. So that's, that's what we are doing now. >>Okay. So just so I get this right. You're using Sandberg essentially integrated your mobile payment experience. Okay. Which is your app you're Sandberg to bring that scalability into the, into the social app application into the app itself. Is that right? >>Yes. Perfect. Integrated with the payment journey. So everybody who is going to pay, they need to find the one, the, the one they want to pay and then they can chat and conclude the payment through the platform. Yeah. I >>Mean, why not have it right there at point of, uh, transaction. Right. Um, why did you, um, decide to, um, to use conversations in your mobile wallet? Just curious. >>So it's important to say that we were born social. We born in 2012. So when our main main product was peer to peer payments, so everybody were sending money to a friend requesting or charging their family. So a service provider. And once we, we started as a social platform in that period. In that moment, we are just focusing in likes comments and like public interactions and the word become more private. And as soon we under understood this situation, we decided to move from a public feed to a private, to a private interaction. So that's, uh, that then the, the conversational space was the solution for that moving from a public interaction to a private interaction. So between the peers, which are involved in the, the transaction. So that's why we are providing the chat solution integrated with payments. >>That's a great call. John, just give some context here, again, for the folks watching this is now expected, this integrated experience. What's your, how would you talk to folks out there? I mean, first of all, I, I, I see it clearly, you've got an app, you gotta have all this integration and you need it scaling to reach features. Talk about your view on that. Is that the, is that what's happening here? What's, what's the real dynamic here. What's the, the big trend. >>Yeah. One thing that's, uh, super interesting about, uh, uh, like messaging experience in general, if you think about any kind of conversations that's happening, uh, digitally between human beings, more and more conversations, just like what Louis mentioned earlier are happening between in a private setting, even on applications, whether it be slack or other forms of communication, uh, more hap uh, more conversations happen through either one-on-one conversations or in a private small group settings. And because people feel more secure, uh, safe to have, uh, more intimate conversations. So even when you're making transactions is more, you know, there's a higher trust and, uh, people tend to engage, uh, far better on platforms through these kind of private conversations. That's where we kind of come in, whether it be, you want to set a one-on-one conversations or with a group conversation. And then ultimately if you want to take it public in a large group setting, you can also support, you know, thousands, if not, you know, hundreds of thousands of people, uh, engaging a public forum as well. So all of those capabilities can be implemented using something Ember, but again, the world is, uh, right now the businesses and how the user are, are interacting with this with each other is all happening through digital conversations. And we're seeing more and more of that happening, uh, throughout the life cycle of our company. >>Yeah, just as a sidebar, I was just talking to a venture in San Francisco the other day, and we're talking about the future of security and SAS and cloud scale. And, you know, the conversation went to more of, is it SAS? Is it platform as a service Louis? I wanna get your thoughts because, you know, you're seeing more and more needs for customization, low code, no code. You're seeing these trends. You gotta built in security. So, you know, the different, the old SAS model was softwares a service, but now that's everything in the cloud is softwares a service. So, but you need to have that platform kind of vibe for scale customization, maybe some developer integration, cuz apps are becoming the, the touchpoint. So can you walk us through what your vision was when you decided to integrate, chat into your app and how did you see that chat, changing the customer experience for payments and across your user journey? Cause, I mean, it's obvious now looking at it, but it might not have been for some. What was your, what was your vision? And when you had to do that, >>When you looked to Brazilian reality, we can see those in, uh, payment apps. All of them are focused on the transactional moment. And as soon as we started to think, how could be, how could our journey be better, more pleased than the others and make people want to be here and to use and to open our app every day is just about making the interaction with the peers easier, even with a merchant or even with my friend. So the main point that our first step was just to connect all, all the users between themselves to payments. The second step we are providing now is using the chat platform, the send bird platform as a platform for peak pay. So we are going to provide more best information. We're going to provide a better customer experience through the support and everything. So, um, this, this, this interaction or this connection, this partnership with Sandberg are going to unlock a new level of service for our users. And at the same time, a much more pleasant or a more pleasant journey for them while they are using the, the app for a, a simple payment, or if they are going to look for a group objective or maybe a crowdfund in the future or a group to decide, or just to pay something. So we are then locking a new level of interaction between the peers between the people and the users that are, that are involved into this, this payment or this simple transaction, we are making it more conversational. >>Yeah. You're making the application more valuable. We're gonna get to that in the next segment about, you know, the future of apps one and done, you see a lot of sports apps, oh, this big tournament, you know, and then you use it and then you never use it again until next year. You know, you have very time specific apps, but now you guys are smart to kind of build this in, but I gotta ask you a question because a lot of developers and companies out there always have this buy versus build decision. Why did you decide to use Sendbird versus building it in house? It's always kind of like the big trade off. >>Yeah. First of all, it will take a long, long time for us to achieve a major platform as Sandberg. And we are not a chat platform. So we are going to use this social interaction to improve the payment platform that we have. So when we look to the market and we found Sandberg, then we thought, okay, this guys, they are a real platform. And through the conversations, we are seeing that they are roadmap working in synergy with our roadmap. And then we can, we could start to deliver value to our, to our users in a fastest way. Could you imagine it spending 2, 3, 4 years to develop something like sand? And even when we achieve this point, probably our solution will be, would be weaker than, than Sandberg. So it was like no brainer to do that. Yeah. Because we want to improve the payment journey, not to do a chat, only a chat platform. So that's why we are working together to prove it's >>Really, you start to see these plugins, these, you know, look at Stripe for payments, for instance, right. And here in the success they've had, you know, people want to plug in for services. So John, I gotta ask you about, um, about the, the complexity that goes into it. The trust required that they have for you, you have to do this heavy lifting, you gotta provide the confidence that your service is gonna have to scale the compliance. Talk about that. What do you guys do under the covers that make this easy again, great business model, heavy lifting done by you. Seamless integration provide that value. That's why business is good, but there's a lot going on share what's happening under the, under the covers. >>Yeah. Um, before going to like the technical, like intricacy of what we do just to provide a little bit of background context on why we even started this business is we, uh, this is my second startup. My first company was a gaming company. We had built like chat three, four times just for our own game. So we were basically, we felt like we were reinventing the wheel. And then we actually went on a buyer's journey when we were building a social application, uh, uh, for, for, uh, uh, building our own community. We tried to actually be a buyer to see if we can actually find a solution. We want to use turns out that there weren't a lot of like sophisticated, you know, top notch, modern, uh, uh, chat experience that we can build using some other third party solutions. So we had to build all of that ourselves, which became the foundation for se today. >>And what we realized is that for most companies like using a building, the most sophisticated chat is probably not going to be their highest priority in case a pick pay will be, you know, financial transactions and all the other business that can be built on and hosted by platform like pick pay. But, you know, building the most topnotch chat experience would be a priority for a company like let's say WhatsApp or, or telegram, but it will probably not be the priority for, you know, major gaming companies, food delivery companies, finance companies, chat is not the highest priority. That's kind of where we come in, cuz chat is the highest priority for us. And we also have a privilege of working with some of the other, uh, world industry, uh, industry leaders. So by, uh, having this collective experience, working with the industry leaders, we get, uh, uh, technological superiority, being able to, uh, scale to, you know, hundreds of millions of users on a monthly basis. Also the security and the compliances by working with some of the largest commercial banks on some of the largest FinTech applications across the globe. So we have, you know, security, compliances, all the industry, best practices that are built in and all the new topnotch user experience that we are, uh, building with other customers can be also be, uh, utilized by a customer like pick pay. So you get this collective almost like evolutionary benefit. Yeah. By, uh, working with a company like us, >>You get a lot of economies of scale. Could you mind just sharing the URL for the company? So folks watching can go get, do a deep dive. Cause I'm you guys got a lot of, lot of, um, certifications under the covers, a lot of things you guys do. So you mind just sharing URL real quick. >>Yeah. So our company, uh, you can find everything about our company on sandberg.com like carrot pigeon. So, uh, you're sending a bird to send a message. So, uh, yeah. send.com >>All so let's get it to the application, cuz this is really interesting cuz Chad is table stakes now, but things are evolving beyond Chad. You gotta integrate that user experience. It's data. Now you gotta have scale. I mean, you know, people who wanna roll their own chat will find out there's a lot of client side and backend scale issues. Right. You can have a tsunami river like on Twitch, you know, you chat. I mean that, could you got client side issues, data scale. <laugh> right. You got backend. Um, Louis, talk about that dynamic because you know, as you start to scale, you want to rely on that. Talk about this dynamic, how apps now are integrating all these new features. So is it, are apps gonna go like more multifunctional? Do you see apps one and done? What's the, how do you guys see this app world playing out and where does, does the Sendbird fit in? And >>Just, just let me know better John, about the performance or about the, just, just let me >>Oh, slow with performance. Uh, performance is huge, right? You gotta have no one wants to have lag on, on chat. >>Okay. So, um, big pay when we look to the payments have millions, thousands of, of, of payments happen happening every second. So what we are doing now is moving all the payments through a conversation. So it always happened inside the conversation. So since from the first moment, um, every second counts to convert this client. And since from the first moment we never saw in, on Sandberg, any issue about that. And even when we have a question or something that we need to improve the team we're working together. So that that's, those are the points that are making us to work together and to make things going pretty fast. When we look to the users who are going to use chat, they are, their intention is three times better than the users who are not using payments through the chat. They are average. Average spent is three times higher too. >>So they, they are making more connections. They are chatting with their friends. They are friends are here. So the network effect is stronger. So if they're going to pay and they need to wait one more second, two seconds to conclude the payment, probably they will not go into choose paying through the, again, they will use only the wallet, only the code, only the Alliance of the user. So that's is so important for us to perform really, really fast. And then this is what we are finding. And this is what is happening with the integration with Sandberg. >>And what's interesting is, is that the by build chat with conversation, we just had a minute ago kind of plays in here. You get the benefits of Sandberg, but now your transactional fidelity is in the chat <laugh> that you don't build that you rely on them on. So again, that's an interesting dynamic. This is the future of apps, John, this is where it matters. The engagement. This is what you talk about is the new, the new digital experience who would've thought that five, 10 years ago. I mean, chat was just like, Hey, what's going around direct message. Now it's integral part of the app. What's your reading. >>Yeah. I mean, we're seeing that across, uh, uh, to Lewis's point, not just transactions, but like marketing messages are now being sent through chat. So the marketing is no longer just about like giving discount calls, but you can actually reengage with the brand. Uh, also support is becoming more real time through chat. So you're actually building a relationship. The support agents have a better context about the previous conversations and the transactions, the sales conversations, even like building, uh, building alerts, notification, all those things are now, uh, happening through conversations. And that's a better way for customers to engage with the brand cuz you actually, you're actually building a better relationship and also, uh, being able to trust the brand more because there is a channel for you to communicate and, and, and be seen and be heard, uh, by the brand. So we do believe that that's the future of the business and how more and more, uh, brands will be building relationships with their customers. >>Yeah. I love, I love your business model. I think it's really critical. And I think that stickiness is a real, uh, call out point there and the brand, the co-branding and the branding capability, but also really quickly in the last minute we have John and Luis, if you don't mind talking about security, I mean, I can't go a day now without getting an SMS scam, uh, text, uh, you seeing it now on WhatsApp. I mean, I don't even use telegram anymore. I mean, come on. So like, like this is now a problem. The old way has been infiltrated with spam and security issues. Security has to be there. The trust and security real quick, John, we'll start with you and we all Louis go, go ahead. >>No, no. Just, just to, to say how important is that we are not only a chatting platform. We are a payment platform, so we have money now, the transaction. So here in Brazil, we have all this safe, the, the, the layers, the security layers that we have in, on our app. And then we have the security layers provided from Sandburg. So, and when we look to the features, Sandberg are providing to us a lot of features that help users to feel safer like per refined profiles, like announcements, where it's a profile from peak pay, where the users can recognize. So this is peak pay talking with me. It's not a user trying to pass, trying to use big Bay's name to talk with me. So these issues is something that we are really, really, we really care about here because we are not only a chat platform. As I said before, we are a payment platform. We are a FinTech, we're at a digital bank. So we need to take care a lot and we don't have any complaint about it because Sandberg understood it. And then they, they, they are providing since the first moment with the perfect solutions and the user interface to make it simpler for the users to recognize that we speak, pay who is chatting with them, not a user with, with bad, bad intentions. >>Great, great insight, Louis. Thanks for sharing that, John really appreciate you guys coming on. Great showcase. Real final word. John will give you the final word folks watching out there. How do they engage with Sendbird? I want to integrate, I want to use your chat service. What do I do? Do I have to connect in as it managed service is the line of code. What do I do to get Sendbird? >>Yeah. So if you're a developer building a mobile application, simply come visit our website, we have a open documentation and SDK you can download and simply plug into your application. You can have a chat experience up and running matter of minutes, if not ours using our UI kit. So we want to make it as easy as possible for all the builders in the world to be able to harness the superpower of digital conversations. >>All right, great. Congratulations, John, on your success and all the growth and Louis, thanks for coming in, sharing the customer perspective and great insight. Thanks for coming on the showcase. Really appreciate it. Thanks for your time. >>Yeah. Thank you for having me. >>Okay. The a of us startup showcase season two, episode three here I'm John for your host. Thanks for watching.

>> Announcer: "theCUBE" presents "Kubecon and Cloudnativecon Europe, 2022" brought to you by Red Hat, the Cloud Native Computing Foundation and its ecosystem partners. >> Welcome to Valencia, Spain and "Kubecon + Cloudnativecon Europe, 2022." I'm Keith Townsend, and we're continuing the conversations with amazing people doing amazing things. I think we've moved beyond a certain phase of the hype cycle when it comes to Kubernetes. And we're going to go a little bit in detail with that today, and on all the sessions, I have today with me, Taylor Dolezal. New head of CNCF Ecosystem. So, first off, what does that mean new head of? You're the head of CNCF Ecosystem? What is the CNCF Ecosystem? >> Yeah. Yeah. It's really the end user ecosystem. So, the CNCF is comprised of really three pillars. And there's the governing board, they oversee the budget and fun things, make sure everything's signed and proper. Then there's the Technical Oversight Committee, TOC. And they really help decide the technical direction of the organization through deliberation and talking about which projects get invited and accepted. Projects get donated, and the TOC votes on who's going to make it in, based on all this criteria. And then, lastly, is the end user ecosystem, that encompasses a whole bunch of different working groups, special interest groups. And that's been really interesting to kind of get a deeper sense into, as of late. So, there are groups like the developer experience group, and the user research group. And those have very specific focuses that kind of go across all industries. But what we've seen lately, is that there are really deep wants to create, whether it be financial services user group, and things like that, because end users are having trouble with going to all of the different meetings. If you're a company, a vendor member company that's selling authentication software, or something in networking, makes sense to have a SIG network, SIG off, and those kinds of things. But when it comes down to like Boeing that just joined, does that make sense for them to jump into all those meetings? Or does it make sense to have some other kind of thing that is representative of them, so that they can attend that one thing, it's specific to their industry? They can get that download and kind of come up to speed, or find the best practices as quickly as possible in a nice synthesized way. >> So, you're 10 weeks into this role. You're coming from a customer environment. So, talk to me a little bit about the customer side of it? When you're looking at something, it's odd to call CNCF massive. But it is, 7.1 million members, and the number of contributing projects, et cetera. Talk to me about the view from the outside versus the view now that you're inside? >> Yeah, so honestly, it's been fun to kind of... For me, it's really mirrored the open-source journey. I've gone to Kubecon before, gotten to enjoy all of the booths, and trying to understand what's going on, and then worked for HashiCorp before coming to the CNCF. And so, get that vendor member kind of experience working the booth itself. So, kind of getting deeper and deeper into the stack of the conference itself. And I keep saying, vendor member and end user members, the difference between those, is end users are not organizations that sell cloud native services. Those are the groups that are kind of more consuming, the Airbnbs, the Boeings, the Mercedes, these people that use these technologies and want to kind of give that feedback back to these projects. But yeah, very incredibly massive and just sprawling when it comes to working in all those contexts. >> So, I have so many questions around, like the differences between having you as an end user and in inter-operating with vendors and the CNCF itself. So, let's start from the end user lens. When you're an end user and you're out discovering open-source and cloud native products, what's that journey like? How do you go from saying, okay, I'm primarily focused on vendor solutions, to let me look at this cloud native stack? >> Yeah, so really with that, there's been, I think that a lot of people have started to work with me and ask for, "Can we have recommended architectures? Can we have blueprints for how to do these things?" When the CNCF doesn't want to take that position, we don't want to kind of be the king maker and be like, this is the only way forward. We want to be inclusive, we want to pull in these projects, and kind of give everyone the same boot strap and jump... I missing the word of it, just ability to kind of like springboard off of that. Create a nice base for everybody to get started with, and then, see what works out, learn from one another. I think that when it comes to Kubernetes, and Prometheus, and some other projects, being able to share best practices between those groups of what works best as well. So, within all of the separations of the CNCF, I think that's something I've found really fun, is kind of like seeing how the projects relate to those verticals and those groups as well. Is how you run a project, might actually have a really good play inside of an organization like, "I like that idea. Let's try that out with our team." >> So, like this idea of springboarding. You know, is when an entrepreneur says, "You know what? I'm going to quit my job and springboard off into doing something new." There's a lot of uncertainty, but for enterprise, that can be really scary. Like we're used to our big vendors, HashiCorp, VMware, Cisco kind of guiding us and telling us like, what's next? What is that experience like, springboarding off into something as massive as cloud native? >> So, I think it's really, it's a great question. So, I think that's why the CNCF works so well, is the fact that it's a safe place for all these companies to come together, even companies of competing products. you know, having that common vision of, we want to make production boring again, we don't want to have so much sprawl and have to take in so much knowledge at once. Can we kind of work together to create all these things to get rid of our adminis trivia or maintenance tasks? I think that when it comes to open-source in general, there's a fantastic book it's called "Working in Public," it's by Stripe Press. I recommend it all over the place. It's orange, so you'll recognize it. Yeah, it's easy to see. But it's really good 'cause it talks about the maintainer journey, and what things make it difficult. And so, I think that that's what the CNCF is really working hard to try to get rid of, is all this monotonous, all these monotonous things, filing issues, best practices. How do you adopt open-source within your organization? We have tips and tricks, and kind of playbooks in ways that you could accomplish that. So, that's what I find really useful for those kinds of situations. Then it becomes easier to adopt that within your organization. >> So, I asked Priyanka, CNCF executive director last night, a pretty tough question. And this is kind of in the meat of what you do. What happens when you? Let's pick on service mesh 'cause everyone likes to pick on service mesh. >> XXXX: Yeah. >> What happens when there's differences at that vendor level on the direction of a CIG or a project, or the ecosystem around service mesh? >> Yeah, so that's the fun part. Honestly, is 'cause people get to hash it out. And so, I think that's been the biggest thing for me finding out, was that there's more than one way to do thing. And so, I think it always comes down to use case. What are you trying to do? And then you get to solve after that. So, it really is, I know it depends, which is the worst answer. But I really do think that's the case, because if you have people that are using something within the automotive space, or in the financial services space, they're going to have completely different needs, wants, you know, some might need to run Coball or Fortran, others might not have to. So, even at that level, just down to what your tech stack looks like, audits, and those kinds of things, that can just really differ. So, I think it does come down to something more like that. >> So, the CNCF loosely has become kind of a standards body. And it's centered around the core project Kubernetes? >> Mm-hmm. >> So, what does it mean, when we're looking at larger segments such as service mesh or observability, et cetera, to be Kubernetes compliant? Where's the point, if any, that the CNCF steps in versus just letting everyone hash it out? Is it Kubernetes just need to be Kubernetes compliant and everything else is free for all? >> Honestly, in many cases, it's up to the communities themselves to decide that. So, the groups that are running OCI, the Open Container Interface, Open Storage Interface, all of those things that we've agreed on as ways to implement those technologies, I think that's where the CNCF, that's the line. That's where the CNCF gets up to. And then, it's like we help foster those communities and those conversations and asking, does this work for you? If not, let's talk about it, let's figure out why it might not. And then, really working closely with community to kind of help bring those things forward and create action items. >> So, it's all about putting the right people in the rooms and not necessarily playing referee, but to get people in the right room to have and facilitate the conversation? >> Absolutely. Absolutely. Like all of the booths behind us could have their own conferences, but we want to bring everybody together to have those conversations. And again, sprawling can be really wild at certain times, but it's good to have those cross understandings, or to hear from somebody that you're like, "Oh, my goodness, I didn't even think about that kind of context or use case." So, really inclusive conversation. >> So, organizations like Boeing, Adobe, Microsoft, from an end user perspective, it's sometimes difficult to get those organizations into these types of communities. How do you encourage them to participate in the conversation 'cause their voice is extremely important? >> Yeah, that I'd also say it really is the community. I really liked the Kubernetes documentary that was put out, working with some of the CNCF folks and core, and beginning Kubernetes contributors and maintainers. And it just kind of blew me away when they had said, you know, what we thought was success, was seeing Kubernetes in an Amazon Data Center. That's when we knew that this was going to take root. And you'd rarely hear that, is like, "When somebody that we typically compete with, its success is seeing it, seeing them use that." And so, I thought was really cool. >> You know, I like to use this technology for my community of skipping rope. You see the girls and boys jumping double Dutch rope. And you think, "I can do that. Like it's just jumping." But there's this hesitation to actually, how do you start? How do you get inside of it? The question is how do you become a member of the community? We've talked a lot about what happens when you're in the community. But how do you join the community? >> So, really, there's a whole bunch of ways that you can. Actually, the shirt that I'm wearing, I got from the 114 Release. So, this is just a fun example of that community. And just kind of how welcoming and inviting that they are. Really, I do think it's kind of like a job breaker. Almost you start at the outside, you start using these technologies, even more generally like, what is DevOps? What is production? How do I get to infrastructure, architecture, or software engineering? Once you start there, you start working your way in, you develop a stack, and then you start to see these tools, technologies, workflows. And then, after you've kind of gotten a good amount of time spent with it, you might really enjoy it like that, and then want to help contribute like, "I like this, but it would be great to have a function that did this. Or I want a feature that does that." At that point in time, you can either take a look at the source code on GitHub, or wherever it's hosted, and then start to kind of come up with that, some ideas to contribute back to that. And then, beyond that, you can actually say, "No, I kind of want to have these conversations with people." Join in those special interest groups, and those meetings to kind of talk about things. And then, after a while, you can kind of find yourself in a contributor role, and then a maintainer role. After that, if you really like the project, and want to kind of work with community on that front. So, I think you had asked before, like Microsoft, Adobe and these others. Really it's about steering the projects. It's these communities want these things, and then, these companies say, "Okay, this is great. Let's join in the conversation with the community." And together again, inclusivity, and bringing everybody to the table to have that discussion and push things forward. >> So, Taylor, closing message. What would you want people watching this show to get when they think about ecosystem and CNCF? >> So, ecosystem it's a big place, come on in. Yeah, (laughs) the water's just fine. I really want people to take away the fact that... I think really when it comes down to, it really is the community, it's you. We are the end user ecosystem. We're the people that build the tools, and we need help. No matter how big or small, when you come in and join the community, you don't have to rewrite the Kubernetes scheduler. You can help make documentation that much more easy to understand, and in doing so, helping thousands of people, If I'm going through the instructions or reading a paragraph, doesn't make sense, that has such a profound impact. And I think a lot of people miss that. It's like, even just changing punctuation can have such a giant difference. >> Yeah, I think people sometimes forget that community, especially community-run projects, they need product managers. They need people that will help with communications, people that will help with messaging, websites updating. Just reachability, anywhere from developing code to developing documentation, there's ways to jump in and help the community. From Valencia, Spain, I'm Keith Townsend, and you're watching "theCUBE," the leader in high tech coverage. (bright upbeat music)

(upbeat music) >> Welcome, everyone, to theCUBE's presentation of the AWS Startup Showcase. And this episode two of season two is called "Data as Code," the ongoing series covering exciting new startups in the AWS ecosystem. I'm John Furrier, your host of theCUBE. Today, we're excited to be joined by Jon Dahl, who is the co-founder and CEO of MUX, a hot new startup building cloud video for developers, video with data. John, great to see you. We did an interview on theCube Conversation. Went into big detail of the awesomeness of your company and the trend that you're on. Welcome back. >> Thank you, glad to be here. >> So, video is everywhere, and video for pivot to video, you hear all these kind of terms in the industry, but now more than ever, video is everywhere and people are building with it, and it's becoming part of the developer experience in applications. So people have to stand up video into their code fast, and data is code, video is data. So you guys are specializing this. Take us through that dynamic. >> Yeah, so video clearly is a growing part of how people are building applications. We see a lot of trends of categories that did not involve video in the past making a major move towards video. I think what Peloton did five years ago to the world of fitness, that was not really a big category. Now video fitness is a huge thing. Video in education, video in business settings, video in a lot of places. I think Marc Andreessen famously said, "Software is eating the world" as a pretty, pretty good indicator of what the internet is actually doing to the economy. I think there's a lot of ways in which video right now is eating software. So categories that we're not video first are becoming video first. And that's what we help with. >> It's not obvious to like most software developers when they think about video, video industries, it's industry shows around video, NAB, others. People know, the video folks know what's going on in video, but when you start to bring it mainstream, it becomes an expectation in the apps. And it's not that easy, it's almost a provision video is hard for a developer 'cause you got to know the full, I guess, stack of video. That's like low level and then kind of just basic high level, just play something. So, in between, this is a media stack kind of dynamic. Can you talk about how hard it is to build video for developers? How is it going to become easier? >> Yeah, I mean, I've lived this story for too long, maybe 13 years now, when I first build my first video stack. And, you know, I'll sometimes say, I think it's kind of a miracle every time a video plays on the internet because the internet is not a medium designed for video. It's been hijacked by video, video is 70% of internet traffic today in an unreliable, sort of untrusted network space, which is totally different than how television used to work or cable or things like that. So yeah, so video is hard because there's so many problems from top to bottom that need to be solved to make video work. So you have to worry about video compression encoding, which is a complicated topic in itself. You have to worry about delivering video around the world at scale, delivering it at low cost, at low latency, with good performance, you have to worry about devices and how every device, Android, iOS, web, TVs, every device handles video differently and so there's a lot of work there. And at the end of the day, these are kind of unofficial standards that everyone's using. So one of the miracles is like, if you want to watch a video, somehow you have to get like Apple and Google to agree on things, which is not always easy. And so there's just so many layers of complexity that are behind it. I think one way to think about it is, if you want to put an image online, you just put an image online. And if you want to put video online, you build complex software, and that's the exact problem that MUX was started to help solve. >> It's interesting you guys have almost creating a whole new category around video infrastructure. And as you look at, you mentioned stack, video stack. I'm looking at a market where the notion of a media stack is developing, and you're seeing these verticals having similar dynamics with cloud. And if you go back to the early days of cloud computing, what was the developer experience or entrepreneurial experience, you had to actually do a lot of stuff before you even do anything, provision a server. And this has all kind of been covered in great detail in the glory of Agile and whatnot. It was expensive, and you had that actually engineer before you could even stand up any code. Now you got video that same thing's happening. So the developers have two choices, go do a bunch of stuff complex, building their own infrastructure, which is like building a data center, or lean in on MUX and say, "Hey, thank you for doing all that years of experience building out the stacks to take that hard part away," but using APIs that they have. This is a developer focused problem that you guys are solving. >> Yeah, that's right. my last company was a company called Zencoder, that was an API to video encoding. So it was kind of an API to a small part of what MUX does today, just one of those problems. And I think the thing that we got right at Zencoder, that we're doing again here at MUX, was building four developers first. So our number one persona is a software developer. Not necessarily a video expert, just we think any developer should be able to build with video. It shouldn't be like, yeah, got to go be a specialist to use this technology, because it should become just of the internet. Video should just be something that any developer can work with. So yeah, so we build for developers first, which means we spend a lot of time thinking about API design, we spend a lot of time thinking about documentation, transparent pricing, the right features, great support and all those kind of things that tend to be characteristics of good developer companies. >> Tell me about the pipe lining of the products. I'm a developer, I work for a company, my boss is putting pressure on me. We need video, we have all this library, it's all stacking up. We hired some people, they left. Where's the video, we've stored it somewhere. I mean, it's a nightmare, right? So I'm like, okay, I'm cloud native, I got an API. I need to get my product to market fast, 'cause that is what Agile developers want. So how do you describe that acceleration for time to market? You mentioned you guys are API first, video first. How do these customers get their product into the market as fast as possible? >> Yeah, well, I mean the first thing we do is we put what we think is probably on average, three to four months of hard engineering work behind a single API call. So if you want to build a video platform, we tell our customers like, "Hey, you can do that." You probably need a team, you probably need video experts on your team so hire them or train them. And then it takes several months just to kind of to get video flowing. One API call at MUX gives you on-demand video or live video that works at scale, works around the world with good performance, good reliability, a rich feature set. So maybe just a couple specific examples, we worked with Robin Hood a few years ago to bring video into their newsfeed, which was hugely successful for them. And they went from talking to us for the first time to a big launch in, I think it was three months, but the actual code time there was like really short. I want to say they had like a proof of concept up and running in a couple days, and then the full launch in three months. Another customer of ours, Bandcamp, I think switched from a legacy provider to MUX in two weeks in band. So one of the big advantages of going a little bit higher in the abstraction layer than just building it yourself is that time to market. >> Talk about this notion of video pipeline 'cause I know I've heard people I talk about, "Hey, I just want to get my product out there. I don't want to get stuck in the weeds on video pipeline." What does that mean for folks that aren't understanding the nuances of video? >> Yeah, I mean, it's all the steps that it takes to publish video. So from ingesting the video, if it's live video from making sure that you have secure, reliable ingest of that live feed potentially around the world to the transcoding, which is we talked a little bit about, but it is a, you know, on its own is a massively complicated problem. And doing that, well, doing that well is hard. Part of the reason it's hard is you really have to know where you're publishing too. And you might want to transcode video differently for different devices, for different types of content. You know, the pipeline typically would also include all of the workflow items you want to do with the video. You want to thumbnail a video, you want clip, create clips of the video, maybe you want to restream the video to Facebook or Twitter or a social platform. You want to archive the video, you want it to be available for downloads after an event. If it's just a, if it's a VOD upload, if it's not live in the first place. You have all those things and you might want to do simulated live with the video. You might want to actually record something and then play it back as a live stream. So, the pipeline Ty typically refers to everything from the ingest of the video to the time that the bits are delivered to a device. >> You know, I hear a lot of people talking about video these days, whether it's events, training, just want peer to peer experience, video is powerful, but customers want to own their own platform, right? They want to have the infrastructure as a service. They kind of want platform as a service, this is cloud talk now, but they want to have their own capability to build it out. This allows them to get what they want. And so you see this, like, is it SaaS? Is it platform? People want customization? So kind of the general purpose video solution does it really exist or doesn't? I mean, 'cause this is the question. Can I just buy software and work or is it going to be customized always? How do you see that? Because this becomes a huge discussion point. Is it a SaaS product or someone's going to make a SaaS product? >> Yeah, so I think one of the most important elements of designing any software, but especially when you get into infrastructure is choosing an abstraction level. So if you think of computing, you can go all the way down to building a data center, you can go all the way down to getting a colo and racking a server like maybe some of us used to do, who are older than others. And that's one way to run a server. On the other extreme, you have just think of the early days of cloud competing, you had app engine, which was a really fantastic, really incredible product. It was one push deploy of, I think Python code, if I remember correctly, and everything just worked. But right in the middle of those, you had EC2, which was, EC2 is basically an API to a server. And it turns out that that abstraction level, not Colo, not the full app engine kind of platform, but the API to virtual server was the right abstraction level for maybe the last 15 years. Maybe now some of the higher level application platforms are doing really well, maybe the needs will shift. But I think that's a little bit of how we think about video. What developers want is an API to video. They don't want an API to the building blocks of video, an API to transcoding, to video storage, to edge caching. They want an API to video. On the other extreme, they don't want a big application that's a drop in white label video in a box like a Shopify kind of thing. Shopify is great, but developers don't want to build on top of Shopify. In the payments world developers want Stripe. And that abstraction level of the API to the actual thing you're getting tends to be the abstraction level that developers want to build on. And the reason for that is, it's the most productive layer to build on. You get maximum flexibility and also maximum velocity when you have that API directly to a function like video. So, we like to tell our customers like you, you own your video when you build on top of MUX, you have full control over everything, how it's stored, when it's stored, where it goes, how it's published, we handle all of the hard technology and we give our customers all of the flexibility in terms of designing their products. >> I want to get back some use case, but you brought that up I might as well just jump to my next point. I'd like you to come back and circle back on some references 'cause I know you have some. You said building on infrastructure that you own, this is a fundamental cloud concept. You mentioned API to a server for the nerds out there that know that that's cool, but the people who aren't super nerdy, that means you're basically got an interface into a server behind the scenes. You're doing the same for video. So, that is a big thing around building services. So what wide range of services can we expect beyond MUX? If I'm going to have an API to video, what could I do possibly? >> What sort of experience could you build? >> Yes, I got a team of developers saying I'm all in API to video, I don't want to do all that transit got straight there, I want to build experiences, video experiences on my app. >> Yeah, I mean, I think, one way to think about it is that, what's the range of key use cases that people do with video? We tend to think about six at MUX, one is kind of the places where the content is, the prop. So one of the things that use video is you can create great video. Think of online courses or fitness or entertainment or news or things like that. That's kind of the first thing everyone thinks of, when you think video, you think Netflix, and that's great. But we see a lot of really interesting uses of video in the world of social media. So customers of ours like Visco, which is an incredible photo sharing application, really for photographers who really care about the craft. And they were able to bring video in and bring that same kind of Visco experience to video using MUX. We think about B2B tools, videos. When you think about it, all video is, is a high bandwidth way of communicating. And so customers are as like HubSpot use video for the marketing platform, for business collaboration, you'll see a lot of growth of video in terms of helping businesses engage their customers or engage with their employees. We see live events obviously have been a massive category over the last few years. You know, we were all forced into a world where we had to do live events two years ago, but I think now we're reemerging into a world where the online part of a conference will be just as important as the in-person component of a conference. So that's another big use case we see. >> Well, full disclosure, if you're watching this live right now, it's being powered by MUX. So shout out, we use MUX on theCUBE platform that you're experiencing in this. Actually in real time, 'cause this is one application, there's many more. So video as code, is data as code is the theme, that's going to bring up the data ops. Video also is code because (laughs) it's just like you said, it's just communicating, but it gets converted to data. So data ops, video ops could be its own new category. What's your reaction to that? >> Yeah, I mean, I think, I have a couple thoughts on that. The first thought is, video is a way that, because the way that companies interact with customers or users, it's really important to have good monitoring and analytics of your video. And so the first product we ever built was actually a product called MUX video, sorry, MUX data, which is the best way to monitor a video platform at scale. So we work with a lot of the big broadcasters, we work with like CBS and Fox Sports and Discovery. We work with big tech companies like Reddit and Vimeo to help them monitor their video. And you just get a huge amount of insight when you look at robust analytics about video delivery that you can use to optimize performance, to make sure that streaming works well globally, especially in hard to reach places or on every device. That's we actually build a MUX data platform first because when we started MUX, we spent time with some of our friends at companies like YouTube and Netflix, and got to know how they use data to power their video platforms. And they do really sophisticated things with data to ensure that their streams well, and we wanted to build the product that would help everyone else do that. So, that's one use. I think the other obvious use is just really understanding what people are doing with their video, who's watching what, what's engaging, those kind of things. >> Yeah, data is definitely there. You guys mentioned some great brands that are working with you guys, and they're doing it because of the developer experience. And I'd like you to explain, if you don't mind, in your words, why is the MUX developer experience so good? What are some of the results you're seeing from your customers? What are they saying to you? Obviously when you win, you get good feedback. What are some of the things that they're saying and what specific develop experiences do they like the best? >> Yeah, I mean, I think that the most gratifying thing about being a startup founder is when your customers like what you're doing. And so we get a lot of this, but it's always, we always pay attention to what customers say. But yeah, people, the number one thing developers say when they think about MUX is that the developer experience is great. I think when they say that, what they mean is two things, first is it's easy to work with, which helps them move faster, software velocity is so important. Every company in the world is investing and wants to move quickly and to build quickly. And so if you can help a team speed up, that's massively valuable. The second thing I think when people like our developer experience is, you know, in a lot of ways that think that we get out of the way and we let them do what they want to do. So well, designed APIs are a key part of that, coming back to abstraction, making sure that you're not forcing customers into decisions that they actually want to make themselves. Like, if our video player only had one design, that that would not be, that would not work for most developers, 'cause developers want to bring their own design and style and workflow and feel to their video. And so, yeah, so I think the way we do that is just think comprehensively about how APIs are designed, think about the workflows that users are trying to accomplish with video, and make sure that we have the right APIs, make sure they're the right information, we have the right webhooks, we have the right SDKs, all of those things in place so that they can build what they want. >> We were just having a conversation on theCUBE, Dave Vellante and I, and our team, and I'd love to get you a reaction to this. And it's more and more, a riff real quick. We're seeing a trend where video as code, data as code, media stack, where you're starting to see the emergence of the media developer, where the application of media looks a lot like kind of software developer, where the app, media as an app. It could be a chat, it could be a peer to peer video, it could be part of an event platform, but with all the recent advances, in UX designers, coders, the front end looks like an emergence of these creators that are essentially media developers for all intent and purpose, they're coding media. What's your reaction to that? How do you see that evolving? >> I think the. >> Or do you agree with it? >> It's okay. >> Yeah, yeah. >> Well, I think a couple things. I think one thing, I think this goes along through saying, but maybe it's disagreement, is that we don't think you should have to be an expert at video or at media to create and produce or create and publish good video, good audio, good images, those kind of things. And so, you know, I think if you look at software overall, I think of 10 years ago, the kind of DevOps movement, where there was kind of a movement away from specialization in software where the same software developer could build and deploy the same software developer maybe could do front end and back end. And we want to bring that to video as well. So you don't have to be a specialist to do it. On the other hand, I do think that investments and tooling, all the way from video creation, which is not our world, but there's a lot of amazing companies out there that are making it easier to produce video, to shoot video, to edit, a lot of interesting innovations there all the way to what we do, which is helping people stream and publish video and video experiences. You know, I think another way about it is, that tool set and companies doing that let anyone be a media developer, which I think is important. >> It's like DevOps turning into low-code, no-code, eventually it's just composability almost like just, you know, "Hey Siri, give me some video." That kind of thing. Final question for you why I got you here, at the end of the day, the decision between a lot of people's build versus buy, "I got to get a developer. Why not just roll my own?" You mentioned data center, "I want to build a data center." So why MUX versus do it yourself? >> Yeah, I mean, part of the reason we started this company is we have a pretty, pretty strong opinion on this. When you think about it, when we started MUX five years ago, six years ago, if you were a developer and you wanted to accept credit cards, if you wanted to bring payment processing into your application, you didn't go build a payment gateway. You just probably used Stripe. And if you wanted to send text messages, you didn't build your own SMS gateway, you probably used Twilio. But if you were a developer and you wanted to stream video, you built your own video gateway, you built your own video application, which was really complex. Like we talked about, you know, probably three, four months of work to get something basic up and running, probably not live video that's probably only on demand video at that point. And you get no benefit by doing it yourself. You're no better than anyone else because you rolled your own video stack. What you get is risk that you might not do a good job, maybe you do worse than your competitors, and you also get distraction where you've just taken, you take 10 engineers and 10 sprints and you apply it to a problem that doesn't actually really give you differentiated value to your users. So we started MUX so that people would not have to do that. It's fine if you want to build your own video platform, once you get to a certain scale, if you can afford a dozen engineers for a VOD platform and you have some really massively differentiated use case, you know, maybe, live is, I don't know, I don't have the rule of thumb, live videos maybe five times harder than on demand video to work with. But you know, in general, like there's such a shortage of software engineers today and software engineers have, frankly, are in such high demand. Like you see what happens in the marketplace and the hiring markets, how competitive it is. You need to use your software team where they're maximally effective, and where they're maximally effective is building differentiation into your products for your customers. And video is just not that, like very few companies actually differentiate on their video technology. So we want to be that team for everyone else. We're 200 people building the absolute best video infrastructure as APIs for developers and making that available to everyone else. >> John, great to have you on with the showcase, love the company, love what you guys do. Video as code, data as code, great stuff. Final plug for the company, for the developers out there and prospects watching for MUX, why should they go to MUX? What are you guys up to? What's the big benefit? >> I mean, first, just check us out. Try try our APIs, read our docs, talk to our support team. We put a lot of work into making our platform the best, you know, as you dig deeper, I think you'd be looking at the performance around, the global performance of what we do, looking at our analytics stack and the insight you get into video streaming. We have an emerging open source video player that's really exciting, and I think is going to be the direction that open source players go for the next decade. And then, you know, we're a quickly growing team. We're 60 people at the beginning of last year. You know, we're one 50 at the beginning of this year, and we're going to a add, we're going to grow really quickly again this year. And this whole team is dedicated to building the best video structure for developers. >> Great job, Jon. Thank you so much for spending the time sharing the story of MUX here on the show, Amazon Startup Showcase season two, episode two, thanks so much. >> Thank you, John. >> Okay, I'm John Furrier, your host of theCUBE. This is season two, episode two, the ongoing series cover the most exciting startups from the AWS Cloud Ecosystem. Talking data analytics here, video cloud, video as a service, video infrastructure, video APIs, hottest thing going on right now, and you're watching it live here on theCUBE. Thanks for watching. (upbeat music)

(bright music) >> Hey everyone, welcome to this CUBE conversation featuring Ahana, I'm your host Lisa Martin. I've got two guests here with me today. Steven Mih joins us, the Presto Foundation governing board member, co-founder and CEO of Ahana, and Girish Baliga Presto Foundation governing board chair and senior engineering manager at Uber. Guys thanks for joining us. >> Thanks for having us. >> Thanks for having us. >> So Steven we're going to dig into and unpack Presto in the next few minutes or so, but Steven let's go ahead and start with you. Talk to us about some of the challenges with the open data lake house market. What are some of those key challenges that organizations are facing? >> Yeah, just pulling up the slide you know, what we see is that many organizations are dealing with a lot more data and very different data types and putting that all into, traditionally as the data warehouse, which has been the workhorse for BI and analytics traditionally, it becomes very, very expensive, and there's a lot of lock in associated with that. And so what's happening is that people are putting the data semistructured and unstructured data for example, in cloud data lakes or other data lakes, and they find that they can query directly with a SQL query engine like Presto. And that lets you have a much more approach to dealing with getting insights out of your data. And that's what this is all about, and that's why companies are moving to a modern architecture. Girish maybe you can share some of your thoughts on how Uber uses Presto for this. >> Yeah, at Uber we use Presto in our internal deployments. So at Uber we have our own data centers, we store data locally in our data centers, but we have made the conscious choice to go with an open data stack. Our entire data stack is built around open source technologies like Hadoop, Hive, Spark and Presto. And so Presto is an invaluable engine that is able to connect to all these different storage and data formats and allow us to have a single entry point for our users, to run their SQL engines and get insights rather quickly compared to some of the other engines that we have at Uber. >> So let's talk a little bit about Presto so that the audience gets a good overview of that. Steven starting with you, you talked about the challenges of the traditional data warehouse application. Talk to us about why Presto was founded the open, the project, give us that background information if you will. >> Absolutely, so Presto was originally developed out of the biggest hyperscaler out there which is Facebook now known as Meta. And they donated that project to the, and open sourced it and donated it to the Linux Foundation. And so Presto is a SQL query engine, it's a storage SQL query engine, that runs directly on open data lakes, so you can put your data into open formats like 4K or C, and get insights directly from that at a very good price performance ratio. The Presto Foundation of which Girish and I are part of, we're all working together as a consortium of companies that all want to see Presto continue to get bigger and bigger. Kind of like Kubernetes has a, has an organization called CNCF, Presto has Presto Foundation all under the umbrella of the Linux Foundation. And so there's a lot of exciting things that are coming on the roadmap that make Presto very unique. You know, RaptorX is a multilevel caching system that it's been fantastic, Aria optimizations are another area, we Ahana have developed some security features with donating the integrations with Apache Ranger and that's the type of things that we do to help the community. But maybe Girish can talk about some of the exciting items on the roadmap that you're looking forward to. >> Absolutely, I think from Uber's point of view just a sheer scale of data and our volume of query traffic. So we run about half a million Presto queries a day, right? And we have thousands of machines in our Presto deployments. So at that scale in addition to functionality you really want a system that can handle traffic reliably, that can scale, and that is backed by a strong community which guarantees that if you pull in the new version of Presto, you won't break anything, right? So all of those things are very important to us. So I think that's where we are relying on our partners particularly folks like Facebook and Twitter and Ahana to build and maintain this ecosystem that gives us those guarantees. So that is on the reliability front, but on the roadmap side we are also excited to see where Presto is extending. So in addition to the projects that Steven talked about, we are also looking at things like Presto and Spark, right? So take the Presto SQL and run it as a Spark job for instance, or running Presto on real-time analytics applications something that we built and contributed from Uber side. So we are all taking it in very different directions, we all have different use cases to support, and that's the exciting thing about the foundation. That it allows us all to work together to get Presto to a bigger and better and more flexible engine. >> You guys mentioned Facebook and I saw on the slide I think Twitter as well. Talk to me about some of the organizations that are leveraging the Presto engine and some of the business benefits. I think Steve you talked about insights, Steven obviously being able to get insights from data is critical for every business these days. >> Yeah, a major, major use case is finding the ad hoc and interactive queries, and being able to drive insights from doing so. And so, as I mentioned there's so much data that's being generated and stored, and to be able to query that data in place, at a, with very, very high performance, meaning that you can get answers back in seconds of time. That lets you have the interactive ability to drill into data and innovate your business. And so this is fantastic because it's been developed at hyperscalers like Uber that allow you to have open source technology, pick that up, and just download it right from prestodb.io, and then start to run with this and join the community. I think from an open source perspective this project under the governance of Linux Foundation gives you the confidence that it's fully transparent and you'll never see any licensing changes by the Linux Foundation charter. And therefore that means the technology remains free forever without later on limitations occurring, which then would perhaps favor commercialization of any one vendor. That's not the case. So maybe Girish your thoughts on how we've been able to attract industry giants to collaborate, to innovate further, and your thoughts on that. >> Yeah, so of the interesting I've seen in the space is that there is a bifurcation of companies in this ecosystem. So there are these large internet scale companies like Facebook, and Uber, and Twitter, which basically want to use something like Presto for their internal use cases. And then there is the second set of companies, enterprise companies like Ahana which basically wanted to take Presto and provide it as a service for other companies to use as an alternative to things like Snowflake and other systems right? So, and the foundation is a great place for both sets of companies to come together and work. The internet scale companies bring in the scale, the reliability, the different kind of ways in which you can challenge the system, optimize it, and so forth, and then companies like Ahana bring in the flexibility and the extensibility. So you can work with different clouds, different storage formats, different engines, and I think it's a great partnership that we can see happening primarily through the foundational spaces. Which you would be hard pressed to find in a single vendor or a, you know, a single-source system that is there on the market today. >> How long ago was the Presto Foundation initiated? >> It's been over three years now and it's been going strong, we're over a dozen members and it's open to everyone. And it's all governed like the Linux Foundation so we use best practices from that and you can just check it out at prestodb.io where you can get the software, or you can hear about how to join the foundation. So it includes members like Intel, and HPE as well, and we're really excited for new members to come, and contribute in and participate. >> Sounds like you've got good momentum there in the foundation. Steven talk a little bit about the last two years. Have you seen the acceleration in use cases in the number of users as we've been in such an interesting environment where the need for real-time insights is essential for every business initially a few couple of years ago to survive but now to be, to really thrive, is it, have you seen the acceleration in Presto in that timeframe? >> Absolutely, we see there's acceleration of being more data-driven and especially moving to cloud and having more data in the cloud, we think that innovation is happening, digital innovation is happening very fast and Presto is a major enabler of that, again, being able to get, drive insights from the data this is not just your typical business data, it's now getting into really clickstream data, knowing about how customers are operating today, Uber is a great example of all the different types of innovations they can drive, whether it be, you know, knowing in real time what's happening with rides, or offering you a subscription for special deals to use the service more. So, you know, Ahana we really love Presto, and we provide a SaaS manage service of the open source and provide free trials, and help people get up to speed that may not have the same type of skills as Uber or Facebook does. And we work with all companies in that way. >> Think about the consumers these days, we're very demanding, right? When I think one of the things that was in short supply during the last two years was patience. And if I think of Uber as a great example, I want to know if I'm asking for a ride I want to know exactly in real time what's coming for me? Where is it now? How many more minutes is it going to take? I mean, that need to fulfill real-time insights is critical across every industry but have you seen anything in the last couple years that's been more leading edge, like e-commerce or retail for example? I'm just curious. >> Girish you want to take that one or? >> Yeah, sure. So I can speak from the Uber point of view. So real-time insights has really exploded as an area, particularly as you mentioned with this just-in-time economy, right? Just to talk about it a little bit from Uber side, so some of the insights that you mentioned about when is your ride coming, and things of that nature, right? Look at it from the driver's point of view who are, now we have Uber Eats, so look at it from the restaurant manager's point of view, right? They also want to know how is their business coming? How many customer orders are coming for instance? what is the conversion rate? And so forth, right? And today these are all insights that are powered by a system which has a Presto as an front-end interface at Uber. And these queries run like, you have like tens of thousands of queries every single second, and the queries run in like a second and so forth. So you are really talking about production systems running on top of Presto, production serving systems. So coming to other use cases like eCommerce, we definitely have seen some of that uptake happen as well, so in the broader community for instance, we have companies like Stripe, and other folks who are also using this hashtag which is very similar to us based on another open source technology called Pino, using Presto as an interface. And so we are seeing this whole open data lakehouse more from just being, you know, about interactive analytics to driving all different kinds of analytics. Having anything to do with data and insights in this space. >> Yeah, sounds like the evolution has been kind of on a rocket ship the last couple years. Steven, one more time we're out of time, but can you mention that URL where folks can go to learn more? >> Yeah, prestodb.io and that's the Presto Foundation. And you know, just want to say that we'll be sharing the use case at the Startup Showcase coming up with theCUBE. We're excited about that and really welcome everyone to join the community, it's a real vibrant, expanding community and look forward to seeing you online. >> Sounds great guys. Thank you so much for sharing with us what Presto Foundation is doing, all of the things that it is catalyzing, great stuff, we look forward to hearing that customer use case, thanks for your time. >> Thank you. >> Thanks Lisa, thank you. >> Thanks everyone. >> For Steven and Girish, I'm Lisa Martin, you're watching theCUBE the leader in live tech coverage. (bright music)

(bright upbeat music) >> Okay, welcome back everyone to the live CUBE coverage here in Las Vegas for in-person AWS re:Invent 2021. I'm John Furrier host of theCUBE two sets, live wall to wall coverage, all scopes of the hybrid events. Well, great stuff online. That was too much information to consume, but ultimately as usual, great show of new innovation for startups and for large enterprises. We've got a great guest, Paul Duffy head of startups Solutions Architecture for North America for Amazon Web Services. Paul, thanks for coming on. Appreciate it. >> Hi John, good to be here. >> So we saw you last night, we were chatting kind of about the show in general, but also about start ups. Everyone knows I'm a big startup fan and big founder myself, and we talk, I'm pro startups, everyone loves startups. Amazon, the first real customers were developers doing startups. And we know the big unicorns out there now all started on AWS. So Amazon was like a dream for the startup because before Amazon, you had to provision the server, you put in the Colo, you need a system administrator, welcome to EC2. Goodness is there, the rest is history. >> Yeah. >> The legacy and the startups is pretty deep. >> Yeah, you made the right point. I've done it myself. I co-founded a startup in about 2007, 2008. And before we even knew whether we had any kind of product market fit, we were racking the servers and doing all that kind of stuff. So yeah, completely changed it. >> And it's hard too with the new technology now finding someone to actually, I remember when we stood with our first Hadoop and we ran a solar search engine. I couldn't even find anyone to manage it. Because if you knew Hadoop back then, you were working at Facebook or Hyperscaler. So you guys have all this technology coming out, so provisioning and doing the heavy lifting for start is a huge win. That's kind of known, everyone knows that. So that's cool. What are you guys doing now because now you've got large enterprises trying to beat like startups. You got startups coming in with huge white spaces out there in the market. Jerry Chen from Greylock, and it was only yesterday we talked extensively about the net new opportunities in the Cloud that are out there. And now you see companies like Goldman Sachs have super cloud. So there's tons of growth. >> Paul: Yeah. >> Take us through the white space. How do you guys see startups taking advantage of AWS to a whole another level. >> And I think it's very interesting when you look at how things have changed in those kind of 15 years. The old world's horrible, you had to do all this provisioning. And then with AWS, Adam Szalecki was talking in his keynote on the first day of the event where people used to think it was just good for startups. Now for startups, it was this kind of obvious thing because they didn't have any legacy, they didn't have any data centers, they didn't have necessarily a large team and be able to do this thing with no commitment. Spin up a server with an API call was really the revolutionary thing. In that time, 15 years later, startups still have the same kind of urgency. They're constrained by time, they're constrained by money, they're constrained by the engineering talent they have. When you hear some of the announcements this week, or you look what is kind of the building blocks available to those startups. That I think is where it's become revolutionary. So you take a startup in 2011, 2012, and they were trying to build something maybe they were trying to do image recognition on forms for example, and they could build that. But they had to build the whole thing in the cloud. We had infrastructure, we had database stuff, but they would have to do all of the kind of the stuff on top of that. Now you look at some of the kind of the AIML services we have things like Textract, and they could just take that service off the shelf. We've got one startup in Canada called Chisel AI. They're trying to disrupt the insurance industry, and they could just use these services like text extracts to just accelerate them getting into that product market fit instead of having to do this undifferentiated (indistinct). >> Paul, we talk about, I remember back in the day when Web Services and service oriented architecture, building blocks, decoupling APIs, all that's now so real and so excellent, but you brought up a great point, Glue layers had to be built. Now you have with the scale of Amazon Web Services, things we're learning from other companies. It reminds me of the open source vibe where you stand on the shoulders of others to get success. And there's a lot of new things coming out that startups don't have to do because startup before then did. This is like a new, cool thing. It's a whole nother level. >> Yeah, and I think it's a real standing on the shoulders of giants kind of thing. And if you just unpick, like in Verna's announcement this morning, his key to this one, he was talking about the Amplify Studio kind of stuff. And if you think about the before and after for that, front-end developers have had to do this stuff for a long period of time. And in the before version, they would have to do all that kind of integration work, which isn't really what they want to spend that time doing. And now they've kind of got that headstart. Andy Jassy famously would say, when he talked about building AWS, that there is no compression algorithm for experience. I like to kind of misuse that phrase for what we try to do for startups is provide these compression algorithms. So instead of having say, hire a larger engineering team to just do this kind of crafty stuff, they can just take the thing and kind of get from naught to 60 (indistinct). >> Gives some examples today of where this is playing out in real time. What kinds of new compression algorithms can startups leverage that they couldn't get before what's new that's available? >> I think you see it across all parts of the stack. I mean, you could just take it out of a database thing, like in the old days, if you wanted to start, and you had the dream that every startup has, of getting to kind of hyper scale where things bursting that seems is the problem. If you wanted to do that in the database layer back in the day, you would probably have to provision most of that database stuff yourself. And then when you get to some kind of limiting factor, you've got to do that work where all you're really wanting to do is try and add more features to your application. Or whether you've got services like Aurora where that will do all of that kind of scaling from a storage point of view. And it gives that startup the way to stand on the shoulders of giants, all the same kind of thing. You want to do some kind of identity, say you're doing a kind of a dog walking marketplace or something like that. So one of the things that you need to do for the kind of the payments thing is some kind of identity verification. In the old days, you would have to have gone pulled all those premises together to do the stuff that would look at people's ID and so on. Now, people can take things like Textracts for example, to look at those forms and do that kind of stuff. And you can kind of pick that story in all of these different stream lines whether it's compute stuff, whether it's database, whether it's high-level AIML stuff, whether it's stuff like amplify, which just massively compresses that timeframe for the startup. >> So, first of all, I'm totally loving this 'cause this is just an example of how evolution works. But if I'm a startup, one of the big things I would think about, and you're a founder, you know this, opportunity recognition is one thing, opportunity capture is another. So moving fast is what nimble startups do. Maybe there's a little bit of technical debt. There maybe a little bit of model debt, but they can get beach head quickly. Startups can move fast, that's the benefit. So where do I learn if I'm a startup founder about where all these pieces are? Is there a place that you guys are providing? Is there use cases where founders can just come in and get the best of the best composable cloud? How do I stand up something quickly to get going that I could regain and refactor later, but not take on too much technical debt or just actually have new building blocks. Where are all these tools? >> I'm really glad you asked that one. So, I mean, first startups is the core of what everyone in my team does. And most of the people we hire, well, they all have a passion for startups. Some have been former founders, some have been former CTOs, some have come to the passion from a different kind of thing. And they understand the needs of startups. And when you started to talk about technical debt, one of the balances that startups have always got to get right, is you're not building for 10 years down the line. You're building to get yourself often to the next milestone to get the next set of customers, for example. And so we're not trying to do the sort of the perfect anonymity of good things. >> I (indistinct) conception of startups. You don't need that, you just got to get the marketplace. >> Yeah, and how we try to do that is we've got a program called Activate and Activate gives startup founders either things like AWS credits up to a hundred thousand dollars in credits. It gives them other technical capabilities as well. So we have a part of the console, the management console called the Activate Console people can go there. And again, if you're trying to build a backend API, there is something that is built on AWS capability to be launched recently that basically says here's some templatized stuff for you to go from kind of naught to 60 and that kind of thing. So you don't have to spend time searching the web. And for us, we're taking that because we've been there before with a bunch of other startups, so we're trying to help. >> Okay, so how do you guys, I mean, a zillion startups, I mean, you and I could be in a coffee shop somewhere, hey, let's do a startup. Do I get access, does everyone gets access to this program that you have? Or is it an elite thing? Is there a criteria? Is it just, you guys are just out there fostering and evangelizing brilliant tools. Is there a program? How do you guys- >> It's a program. >> How do you guys vet startup's, is there? >> It's a program. It has different levels in terms of benefits. So at the core of it it's open to anybody. So if you were a bootstrap startup tomorrow, or today, you can go to the Activate website and you can sign up for that self-starting tier. What we also do is we have an extensive set of connections with the community, so T1 accelerators and incubators, venture capital firms, the kind of places where startups are going to build and via the relationships with those folks. If you're in one, if you've kind of got investment from a top tier VC firm for example, you may be eligible for a hundred thousand dollars of credit. So some of it depends on where the stock is up, but the overall program is open to all. And a chunk of the stuff we talked about like the guidance that's there for everybody. >> It's free, that's free and that's cool. That's good learning, so yeah. And then they get the free training. What's the coolest thing that you're doing right now that startups should know about around obviously the passionate start ups. I know for a fact at 80%, I can say that I've heard Andy and Adam both say that it's not just enterprising, well, they still love the startups. That's their bread and butter too. >> Yeah, well, (indistinct) I think it's amazing that someone, we were talking about the keynote you see some of these large customers in Adam's keynote to people like United Airlines, very, very large successful enterprise. And if you just look around this show, there's a lot of startups just on this expert floor that we are now. And when I look at these announcements, to me, the thing that just gets me excited and keeps me staying doing this job is all of these little capabilities make it in the environment right now with a good funding environment and all of these technical building blocks that instead of having to take a few, your basic compute and storage, once you have all of these higher and higher levels things, you know the serverless stuff that was announced in Adam's keynotes early, which is just making it easy. Because if you're a founder, you have an idea, you know the thing that you want to disrupt. And we're letting people do that in different ways. I'll pick one start up that I find really exciting to talk to. It's called Study. It's run by a guy called Zack Kansa. And he started that start up relatively recently. Now, if you started 15 years ago, you were going to use EC2 instances building on the cloud, but you were still using compute instances. Zack is really opinionated and a kind of a technology visionary in this sense that he takes this serverless approach. And when you talk to him about how he's building, it's almost this attitude of, if I've had to spin up a server, I've kind of failed in some way, or it's not the right kind of thing. Why would we do that? Because we can build with these completely different kinds of architectures. What was revolutionary 15 years ago, and it's like, okay, you can launch it and serve with an API, and you're going to pay by the hour. But now when you look at how Zack's building, you're not even launching a server and you're paying by the millions. >> So this is a huge history lesson slash important point. Back 15 years ago, you had your alternative to Amazon was provisioning, which is expensive, time consuming, lagging, and probably causes people to give up, frankly. Now you get that in the cloud either you're on your own custom domain. I remember EC2 before they had custom domains. It was so early. But now it's about infrastructures code. Okay, so again, evolution, great time to market, buy what you need in the cloud. And Adam talked about that. Now it's true infrastructure is code. So the smart savvy architects are saying, Hey, I'm just going to program. If I'm spinning up servers, that means that's a low level primitive that should be automated. >> Right. >> That's the new mindset. >> Yeah, that's why the fun thing about being in this industry is in just in the time that I've worked at AWS, since about 2011, this stuff has changed so much. And what was state of the art then? And if you take, it's funny, when you look at some of the startups that have grown with AWS, like whether it's Airbnb, Stripe, Slack and so on. If you look at how they built in 2011, because sometimes new startups will say, oh, we want to go and talk to this kind of unicorn and see how they built. And if you actually talked to the unicorn, some of them would say, we wouldn't build it this way anymore. We would do the kind of stuff that Zack and the folks studied are doing right now, because it's totally different (indistinct). >> And the one thing that's consistent from then to now is only one thing, it has nothing to do with the tech, it's speed. Remember rails front end with some backend Mongo, you're up on EC2, you've got an app, in a week, hackathon. Weekend- >> I'm not tying that time thing, that just goes, it gets smaller and smaller. Like the amplify thing that Verna was talking about this morning. You could've gone back 15 years, it's like, okay, this is how much work the developer would have to do. You could go back a couple of years and it's like, they still have this much work to do. And now this morning, it's like, they've just accelerated them to that kind of thing. >> We'll end on giving Jerry Chan a plug in our chat yesterday. We put the playbook out there for startups. You got to raise your focus on the beach head and solve the problem you got in front of you, and then sequence two adjacent positions, refactor in the cloud. Take that approach. You don't have to boil the ocean over right away. You get in the market, get in and get automating kind of the new playbook. It's just, make everything work for you. Not use the modern. >> Yeah, and the thing for me, that one line, I can't remember it was Paul Gray, or somehow that I stole it from, but he's just encouraging these startups to be appropriately lazy. Like let us do the hard work. Let us do the undifferentiated heavy lifting so people can come up with these super cool ideas. >> Yeah, just plugging the talent, plugging the developer. You got a modern application. Paul, thank you for coming on theCUBE, I appreciate it. >> Thank you. >> Head of Startup Solution Architecture North America, Amazon Web Services is going to continue to birth more startups that will be unicorns and decacorns now. Don't forget the decacorns. Okay, we're here at theCUBE bringing you all the action. I'm John Furrier, theCUBE. You're watching the Leader in Global Tech Coverage. We'll be right back. (bright upbeat music)

(bright upbeat music) >> Hello everyone. And we're back at AWS Re:Invent. You're watching theCUBE and we're here, day two. Actually we started Monday night and we got wall-to-wall coverage. We going all the way through Thursday, myself. I'm Dave Volante with the co-host, David Nicholson. Lisa Martin is also here. Of course, John Furrier. Partners, technologists, customers, the whole ecosystem. It's good to be back in the live event. Of course we have hybrid event as well a lot of people watching online. Anshu Sharma is here. He is the co-founder and CEO of Skyflow, new type of privacy company, really interested in this topic. Great to see you. Thanks for coming on. >> Thank you, thanks for bringing me here. >> It's timely, you know. Privacy, security, they're kind of two sides of the same coin. >> Yes. >> Why did you found Skyflow? >> Well, the idea for Skyflow really comes from my background in some ways. I spent my first nine years at Oracle, six years at Salesforce. And whether we were building databases or CRM products, customers would come to us and say, "Hey, you know, I have this very different type of data. It's things like social security numbers, frequent flyer card numbers, card numbers. You know, can you secure it better? Can you help me manage things like GDPR?" And to be honest, there was never a clear answer. There's a lot of technology solutions out there that do one thing at a time, you can walk around the booths here, there's like a hundred companies. And if you use all those hundred things correctly, maybe you could go tell your board that maybe a social security number is not going to be lost anymore. And I was like, "You know, we've simplified everything else. Why is it so hard to protect my social security number? It should be easy. It should be as easy as using Stripe or Twilio." And this idea just never went away and kept coming back till a few years ago, we learned about the Facebook privacy challenges, the Equifax challenges. And I was like, boy, it's the time. It's time to go do it now. >> You started the company in 2019. Right? >> Yes. >> I mean, your timing was pretty good, right? So what are the big sort of Uber trends that you're seeing? Obviously GDPR, the California Consumer Privacy Act. I heard this morning. Did you hear this? That like, if you post a picture on social media now without somebody's permission, you're now violating their privacy. It's like, you can see the smiles on Anshu's face. >> Its like every week, we're like every week, there's a new story that could be like, well, Skyflow. The new story is the question, the answer is Skyflow. But honestly I think what's happened is, the issue is put very simple. You know all we're trying to do is protect people's social security numbers, phone numbers, credit card numbers, things we hold dear. At the same time, it's complex. Like what does it mean to protect your social security number let's say? Does that mean I don't get to use it for filing your taxes? Well, I need your credit card number to process a payment. And we were like, this is just too complicated. Why, how do companies like Apple do it? How do companies like Netflix manage not have as many breaches as my hotel that barely has any data. And the answer is those companies actually have evolved to a completely different architecture, the zero trust data architecture. And that was our inspiration for starting this company. >> Yeah. I mean. How many times have you been asked to give your social security number? And you're like, why? why do you want it? What are you going to do with it? How do you protect it? And they go, "I don't know." >> You know, what's even, my favorite is like, you give your social security number to say TurboTax, how many days of the year do they need to use it? One. How many days of the year do they have it? And the thing is, it's a liability for those CTOs too. >> Yeah right. >> The CTO of Walgreens, the CTO of Intuit. They don't really want that social security number just so they can process your card once a year, or your social security number once a year. It's almost like we're forcing them to hold onto data. And then they have to bear the burden of having these stories. Like, you know, everybody wants to prevent a New York Times story that says, what Robin Hood had a breach, Twitter had a breach. >> So walk us through how Skyflow would address something like that. So take the, you know, take the make a generic version of TurboTax, social security members. There they are right now, they're sitting in a database somewhere. Hopefully there's some security wrapped around it in some way or another. What would you advise a customer like that to do? And what are you actually doing for them? >> So, look, it's very simple. You are not going to put your username passwords in a generic database. You're going to use something like OD Zero or Octa to do it. We're living in a world where we have polyglot data stores. Like there's a key value store. There's a time series database. There is a search database like Elastic. There's a log database like Splunk. But PII data, Somehow we think just fine. If it's in a hundred places and our answer is that we should do the same thing that companies like Apple, Netflix, Google, everybody, does. They take this data. They completely isolate it from the databases. And it gets stored in a custom data store in our case, that would be Skyflow. And essentially we'd give you encrypted tokens back and you can use these encrypted tokens that look like fake social security number. It's called a Format Preserving Encryption. So if you think about all the breakthroughs we've had in homomorphic encryption, on secure elements, like the way your phone works, the credit card number is stored in a secure element. So it's the same idea. There's a secure part of your data stack, which is Skyflow. That basically keeps the data always protected. And because we can compute and search on encrypted data, this is important, everybody can encrypt data at rest. Skyflow is the first company that's come out and said, "Look, you can keep your phone number and social security number, encrypted while I can run an aggregation query." So I can tell you what's the balance of your customer's account balance. And i can run that query without decrypting, a single row of data. The only other company I know that can do that internally is a certain Cupertino based company. >> So think about it. Anybody can walk something up to a certain degree, but allowing frictionless access at the same time. >> While it's encrypted. So how do you make that? Are you, is a strategy to make that a horizontal service? That I can put into my data protection service or my E-commerce service or whatever. >> It's a cloud-based service that runs on AWS and other clouds. We basically given instance just like, you'll get an instance of a post-grad store or you get an API handled to OD Zero. You basically instantiate Skyflow of what gets created. It can be in your AWS environment, dedicated VPC. So it's private to you and then you have a handle and then basically you just start using it. >> So how, how do you, what's the secret sauce? How do you do that? >> The secret source. Well, now that we filed the patents on it, I can reveal the secret sauce. So the holy grail of encryption right now, if you go talk to people at a leading company, is there's something called Fully Homomorphic Encryption. That's fundamentally the foundation on which things like Bitcoin are built actually. But the hard part about Fully Homomorphic Encryption is it works. You can actually do mathematical computations on it without decrypting the data, but it's about a million times slower. >> Yes slower, right. >> So nobody uses it. My insight was that we don't need to do multiplications and additions on phone numbers. You never take my phone number and divide by your social security number. (Dave laughing) These numbers are not numbers, they are data structures. So our insight was if you treat them as specialized data structures, we're all talking about basically about 80 different types of data across the globe. Every human being has an ID, date of birth, height, color of eyes. There's not that many fields. What we can do then is create specialized encryption schemes for each data type. We call this polymorphic data encryption. Poly means multiple. As a result of that, we can actually store the data encrypted and build indexes on it. Since we can index interpret data, it's kind of like, imagine you can run real-time queries on data that's encrypted. Every other data store, When you encrypt the data, it becomes invisible to database. And that's why we had to build this as a full stacked service. Just like the Snowflake guys had to start with the foundation of storage, rethink indexing, and build Snowflake. We did the same thing, except we built it for encrypted indexes Whereas they built it for encrypted, for regular data stores. >> So thinking, if you think about today's tech stack, it's evolving, right? The data protection and security are coming together. Where does this fit? Is it sort of now becoming a fundamental part of the-- >> We think every leading company, whether you're building a new brokerage application or you are the largest bank in the world, and we're talking to some of them right now. They're all going to have an internal service called a PII wall. This wall just like Apple and Google have their own internal walls. You're going to have a wall service in your service oriented architecture, essentially. And it's going to basically be the API. Every other application and database in your company is not going to store my social security number. The SSNs don't belong in 600 databases at a leading bank. They don't belong inside your customer support system. Think about what happened with Robinhood two weeks ago, right? Someone tricked one call center guy into giving the keys up, which is fine happens. But why did the call center guy have access to like a million email addresses? He's never used going to use that. So we think if you isolate the PII, every leading company is going to end up with a PII Wall, as part of their core architecture. Just like today, we have an Alt API, you have a Search API, you have a Logging API, you're going to have a PII API. And that's going to be part of your modern data stack. >> So okay. So this is definitely not a bolt on, right? It's going to be a fundamental company, just like security is, just like backup is. It's now, you got to have it. It's-- >> Yes. I mean, if you think about it, it just logically makes sense. Like you should be isolating this data. You don't keep your money and gold around at home. You put it either in a locker or a bank. I think the same applies for PII. We just haven't done it because companies would pay off a fine for $10,000 or a million dollars. And. >> Yeah. So you've recently raised $45 million to expand your efforts. Obviously that means that people are looking at this and saying there's opportunity, right? What does that look like when you think of growth, where during your go to market strategy at first you're convincing people that it's a good idea to do it. Do you think or hope for, hope one day that there's an inflection point where it's not that people are thinking, you know, let's do this because it's a good idea, but people are like, I have to do this because if I don't, it's irresponsible and I'm going to be penalized for not having it. It becomes something that isn't really a choice. It's something where you just do it. >> So, you know, when we were starting the company, we didn't even have a word to explain what we were trying to do. We would say things like what if there was a cloud service for XYZ. And, but over the last one year, I don't want to take credit for creating this market, but this market has been created in the last year and a half. And you know, we get tons of people, including some of the largest institutions emailing us, saying, "I'm looking to build a PII wall, API service inside my company. Can you tell me why your product meets that need?" And I thought that would take us three to five years to get there. And, you know, we've ended up creating a category, basically just like other companies have. And I think, you know, you don't get, I believe in market permission. You don't get to create a category. The market gives somebody the permission to create a category. Saying, "Look, this makes sense. Something like this should emerge." And if you're there at the right time, like you said. >> Yep. >> You get to take the opportunity. >> So where are you at as a company say for some, some capital is great. When do you scale? >> We're scaling now? So we just doubled our headcount in the last nine to 10 months. We're now 75 people. We think we'll be about 150 to 200 people in the next year. We are hiring across all regions. We just hired a head of Asia pack from segment.com. We just hired our first, you know, lead on international expansion. And in the US, we have an office in Palo Alto. We have an office in Bangalore. We just announced a data residency solution for Europe, data residency solution for India and emerging markets. Because data residency is another one of those things that's just emerging right now. And irrespective of whether you believe in security and privacy. Data residency is one of those things that you are mandated to implement. >> And where are you hiring? Is it combination to go to market? Tell me about your go to market. >> The go to market. We are direct sales organization, but we work with partners. So we haven't announced some of these partnerships, but you're working with some of the companies here who either are large database companies, large security companies. We think there is a win-win relationship between us and some of the partner. >> You're a partner model, partner channel model. >> So, direct sales but partner assisted. >> Yeah. Right. All right. We got to go. Hey, awesome story. Congratulations. Best of luck. >> Very interesting. >> Love to have you back and track the progress. >> Thank you, thank you so much. >> Okay. Thank you for watching theCUBE, the leader in and high-tech coverage. We're at Re-Invent 2021. Be right back (upbeat music)

(upbeat music) >> Welcome back, everyone, to theCUBE's live coverage, day one wrap-up. I'm John Furrier, with Dave Vellante. We have Jerry Chen, special guest who's been with us every year on theCUBE since inception. Certainly every AWS re:Invent, nine years straight. Jerry Chen, great to see you for our guest analyst's wrap up VC general partner, Greylock partners, good to see you. >> John, Dave, it's great to see you guys. Thanks for having me again. It wouldn't be re:Invent without the three of us sitting here and we missed last year, right, because of COVID. So we have to make up for lost time. >> John: We did a virtual one- >> Dave: we did virtual stuff= >> John: wasn't the same as in-person. >> Dave: Definitely not the same. >> Jerry: Not the same thing. So, it's good to see you guys again in person, and less than 6 feet apart. >> Cheers, yeah. >> And 7,000 people here, showing that the event's still relevant. >> Jerry: Yeah. >> Some people would kill for those numbers, it's a bad year for Amazon, down from 60,000. >> Jerry: Yeah. >> So, ecosystem's booming. Okay, let's get to it. Day one in the books, new CEO, new sheriff in town, his name's Adam Selipsky. Your take? >> Well, Adam's new, but he's old, right? Something, you know, like something new, something old, something blue, right? It's so, Adam was early Amazon, so he had that founding DNA. Left, you know, CEO of Tableau, acquired by Salesforce, came back few months ago. So I think it was a great move, because one, he's got the history and culture under Jassy, so he's definitely the Bezos Jassy tree of leadership, but yet he's been outside the bubble. Right? So he actually knows what it means to run a company not on the Amazon platform. So, I think Adam's a great choice to lead AWS for what we call it, like maybe act two, right? Act one, the first X years with Jassy, and maybe this is the second act under Adam. >> Yeah. And he's got- and he was very technical, hung around all the techies, James Hamilton, DeSantis, all the engineers, built that core primitives. Now, as they say, this cloud next gen's here, act two, it's about applications. >> Jerry: Yeah. >> Infrastructure as code is in place. Interesting area. Where's the growth come from? So, look, you know, the ecosystem has got to build these super clouds, or as you say, Castles on the Cloud, which you coined, but you brought this up years ago, that the moats and the value has to be in there somewhere. Do you want to revise that prediction now that you see what's coming from Selipsky? >> Okay, well, so let's refresh. Greylock.com/castles has worked out, like we did, but a lot of thought leadership and the two of you, have informed my thinking at Castles in the Cloud, how to compete against Amazon in the cloud. So you'd argue act one, the startup phase, the first, you know, X years at Amazon was from 2008 to, you know, 2021, the first X years, building the platform, digging the moats. Right? So what did you have? You have castle the platform business, economies of scale, which means decreasing marginal costs and natural network effects. So once the moat's in place and you had huge market share, what do you for act two, right? Now the moats are in place, you can start exploring the moats for I think, Adam talked about in your article, horizontal and verticals, right? Horizontal solutions up the stack, like Amazon Connect, CRM solutions, right? Horizontal apps, maybe the app layer, and verticals, industrials, financials, healthcare, et cetera. So, I think Jassy did a foundation of the castle and now we're seeing, you know, what Adam and his generation would do for act two. >> So he's, so there's almost like an act one A, because if you take the four hyperscalers, they're about, maybe do 120 billion this year, out of, I don't know, pick a number, it's many hundreds of billions, at least in infrastructure. >> Jerry: Correct. >> And those four hyperscalers growing at 35% collectively, right? So there's some growth there, but I feel like there's got to be deeper business integration, right? It's not just about IT transformation, it's about deeper- So that's maybe where this Connect like stuff comes, but are there enough of those? You know, I didn't, I haven't, I didn't hear a lot of that this morning. I heard a little bit, ML- >> Jerry: Sure. >> AI into Connect, but where's the next Connect, right? They've got to do dozens of those in order to go deeper. >> Either, Dave, dozens of those Connects or more of those premise, so the ML announcement was today. So you look at what Twilio did by buying Segment, right? Deconstruct a CRM to compete against Adam Selipsky's old acquire of Salesforce.com. They bought Segment, so Twilio now has communicates, like texting, messaging, email, but all the data come from Segment. >> Dave: With consumption-based pricing. >> With consumption-based pricing. So, right? So that's an example of kind of what the second act of cloud looks like. It may not look like full SaaS apps like Salesforce.com, but these primitives, both horizontally vertically, because again, what does Amazon have as an asset that other guys don't? Install based developers. Developers aren't going to necessarily build or consume SaaS apps, but they're going to consume things like these API's and primitives. And so you look around, what's cloud act two look like? It may not be VM's or containers. It may be API's like Stripe and Billing, Twilio messaging, right? Concepts like that. So, we'll see what the next act at cloud looks like. And they announced a bunch of stuff today, serverless for the data analytics, right? So serverless is this move towards not consuming raw compute and storage, but APIs. >> What about competition? Microsoft is nipping at the heels of AWS. >> Dave: John put them out of business earlier today. [John and Dave Laugh] >> No, I said, quote, I'll just- let me rephrase. I said, if Amazon goes unchecked- >> Jerry: Sure. >> They'll annihilate Microsoft's ecosystem. Because if you're an ISV, why wouldn't you want to run on the best platform? >> Jerry: Sure. >> Speeds and feeds matter when you have these shifts of software development. >> Jerry: You want them both. >> So, you know, I mean, you thought about the 80's, if you were at database, you wanted the best processor. So I think this Annapurna vertical integrated stacks are interesting because if my app runs better and I have a platform, prefabricated or purpose-built platform, to be there for me, I'm going to build a great SaaS app. If it runs faster and it cost less, I'm going to flop to Amazon. That's just, that's my prediction. >> So I think better changes, right? And so I think if you're Amazon, you say cheaper, better, faster, and they're investing in chips, proprietary silicon to run better, faster, their machine learning training chips, but if you're Azure or Google, you got to redefine what better is. And as a startup investor, we're always trying to do category definition, right? Like here's a category by spin. So now, if you're Azure or Google, there are things you can say that are better, and Google argued their chips, their TensorFlow, are better. Azure say our regions, our security, our enterprise readiness is better. And so all of a sudden, the criteria "what's better" changes. So from faster and cheaper to maybe better compliance, better visibility, better manageability, different colors, I don't know, right? You have to change the game , because if you play the same game on Amazon's turf, to your point, John, it- it's game over because they have economies of scale. But I think Azure and Google and other clouds, the superclouds, or subclouds are changing the game, what it means to compete. And so I think what's going on, just two more seconds, from decentralized cloud, being Web 3 and crypto, that's a whole 'nother can of worms, to Edge compute, what Cloudflare are doing with R2 and storage, they're trying to change the name of the game. >> Well, that's right. If you go frontal against Amazon, you're got to get decimated. You got to move the goalposts for better. And I think that's a good way to look at it, Dave. What does better mean? So that's the question that's on the table. What does that look like? And I think that's an unknown, that's coming. Okay, back to the start-ups. Category definition. That's an awesome term. That to me is a key thing. How do you look at what a category is on your sub- on your Castles of the Cloud, you brought up how many categories of- >> Jerry: 33 markets and a bunch of submarkets, yeah. >> Yeah. Explain that concept. >> So, we did Castle in the Clouds where my team looked at all the services offered at Azure, Google, and Amazon. We downloaded the services and recategorized them to like, 30 plus markets and a bunch of submarkets. Because, the reason why is apples to apples, you know, Amazon, Google, Azure all have databases, but they might call them different things. And so I think first things first is, let's give developers and customers kind of apples to apples comparisons. So I think those are known markets. The key in investing in the cloud, or investing in general, is you're either investing in budget replacement, replacing a known market, cheaper, better database, to your point, or a net new market, right? Which is always tricky. So I think the biggest threat to a lot of the startups and incumbents, the biggest threat by startups and incumbents, is either one, do something cheaper, better in a current market, or find a net new market that they haven't thought about yet. And if you can win that net new market before the rest, then that's unbelievable. We call it the, you know, the blue ocean strategy, >> Dave: Is that essentially what Snowflake has done, started with cheaper, better, and now they're building the data cloud? >> Jerry: I think there's- it's evolution, correct. So they said cheaper, better. And the Castle in the Cloud, we talked about, they actually built deep IP. So they went a known category, data warehouses, right? You had Teradata, Redshift, Snowflake cheaper, better, faster. And now let's say, okay, once you have the customers, let's change the name of the game and create a data cloud. And it's TBD whether or not Snowflake can win data cloud. Like we talked about Rockset, one of my investments that's actually move the goalpost saying, oh, data cloud is nice, but real time data is where it's at, and Snowflake and those guys can't play in real time. >> Dave: No, they're not in a position to play in real time data. >> Jerry: Right. >> Dave: I mean, that's right. >> So again, so that's an example of a startup moving the goalpost on what previously was a startup that moved the goalpost on an incumbent. >> Dave: And when you think about Edge, it's going to be real-time AI inferencing at the Edge, and you're right, Snowflake's not set up well at all for that. >> John: So competition wise, how do the people compete? Because this is what Databricks did the same exact thing. I have Ali on the record going back years, "Well, we love Amazon. We're only on Amazon." Now he's talking multicloud. >> So, you know, once you get there, you kind of change your tune cause you've got some scale, but then you got new potential entrants coming in, like Rockset. >> Jerry: Correct. >> So. >> Dave: But then, and if you add up the market caps of just those two companies, Databricks and Snowflake, it's much larger than the database market. So this, we're defining new markets now. >> Jerry: I think there's market cap, especially Snowflake that's in the public market, Databricks is still private, is optimism that there's a second or third act in the database space left to be unlocked. And you look at what's going on in that space, these real-time analytics or real-time apps, for sure there's optimism there. But, but to John's point, you're right, like you earn the right to play the next act, but it's tricky because startups disrupt incumbents and become incumbents, and they're also victims their own success, right? So you're- there's technical debt, there's also business model debt. So you're victims of your own business model, victims of your own success. And so what got you here may not get you to the next phase. And so I think for Amazon, that's a question. For Databricks and Snowflake, that's a question, is what got them here? Can they play to the next act? And look, Apple did it, multiple acts. >> John: Well, I mean, I think I- [Crosstalk] >> John: I think it's whether you take shortcuts or not, if you have debt, you make it a little bit of a shortcut bet. >> Jerry: Yeah. >> Okay. That's cool. But ultimately what you're getting at here is beachhead thinking. Get a beachhead- >> Jerry: Correct. >> Get in the market, and then sequence to a different position. Classic competitive strategy, 101. That's hard to do because you want to win the beachhead- >> I know. >> John: And take a little technical debt and business model debt, cheat a little bit, and then, is it not fortified yet? So beachhead to expansion is the question. >> Jerry: That's every board meeting, John and Dave, that we're in, right? It's called you need a narrow enough wedge to land. And it is like, I don't want the tip of the spear, I want the poison on the tip of a spear, right? [Dave and John Laugh] >> You want, especially in this cloud market, a super focused wedge to land. And the problem is, as a founder, as investor, you're always thinking about the global max, right? Like the ultimate platform winner, but you don't get the right to play the early- the late innings if you don't make it out of the early innings. And so narrow beachhead, sharp wedge, but you got to land in a space, a place of real estate with adjacent tan, adjacent markets, right? Like Uber, black cars, taxi's, food, whatever, right? Snowflake, data warehouse, data cloud. And so I think the key with all startups is you'll hit some ceiling of market size. Is there a second ramp? >> Dave: So it's- the art is when to scale and how fast to scale. >> Right. Picking when, how fast, in which- which best place, it was tough. And so, the best companies are always thinking about their second or third act while the first act's still going. >> John: Yeah. And leveraging cloud to refactor, I think that's the key to Snowflake, was they had the wedge with data warehouse, they saw the position, but refactored and in the cloud with services that they knew Teradata wouldn't use. >> Jerry: Correct. >> And they're in. From there, it's just competitive IP, crank, go to market. >> And then you have the other unnatural things. You have channel, you have installed base of customers, right? And then you start selling more stuff to the same channel, to the same customers. That's what Amazon's doing. All the incumbent's do that. Amazon's got, you know, 300 services now, launching more this week, so now they have channel distribution, right? Every credit card for all the developers, and they have installed base of customers. And so they will just launch new things and serve the customers. So the startups had to disrupt them somehow. >> Well, it's always great to chat with Jerry. Every year we discover and we riff and we identify, in real time, new stuff. We were talking about this whole vertical, horizontal scale and kind of castles early on, years ago. And now it's happened. You were right. Congratulations. That's a great thesis. There's real advantages to build on a cloud. You can get the- you can build a business there. >> Jerry: Right. >> John: That's your thesis. And by the way, these markets are changing. So if you're smart, you can actually compete. >> Jerry: I think you beat, and to Dave's earlier point, you have to adapt, right? And so what's the Darwin thing, it's not the strongest, but the most adaptable. So both- Amazon's adapt and the startups who are the most adaptable will win. >> Dave: Where are you, you guys might've talked about this, where do you stand on the cost of goods sold issue? >> Jerry: Oh, I think everything's true, right? I think you can save money at some scale to repatriate your cloud, but again, Wall Street rewards growth versus COGS, right? So I think you've got a choice between a dollar of growth versus a dollar reducing COGS, people choose growth right now. That may not always be the case, but at some point, if you're a company at some scale and the dollars of growth is slowing down, you definitely have to reduce the dollars in cost. And so you start optimizing cloud costs, and that could be going to Amazon, Azure, or Google, reducing COGS. >> Dave: Negotiate, yeah. >> John: Or, you have no visibility on new net new opportunities. So growth is about new opportunities. >> Correct. >> If you repatriating things, there's no growth. >> Jerry: It's not either, or- >> That's my opinion. >> Jerry: COGS or growth, right? But they're both valid, definitely, so you can do both. And so I don't think- it's what's your priorities, you can't do everything at once. So if I'm a founder or CEO or in this case investor, and I said, "Hey, Dave, and John, if you said I can either save you 25 basis points in gross margin, or I can increase another 10% top line this year", I'm going to say increase the top line, we'll deal with the gross margin later. Not that it's not important, but right now the early phase- >> Priorities. >> Jerry: It's growth. >> Yeah. All right, Jerry Chen, great to see you. Great to have you on, great CUBE alumni, great guest analyst. Thanks for breaking it down. CUBE coverage here in Las Vegas for re:Invent, back in person. Of course, it's a virtual event, we've got a hybrid event for Amazon, as well as theCUBE. I'm John Furrier, you're watching the leader in worldwide tech coverage. Thanks for watching. (Gentle music)

(upbeat music) >> Welcome back everyone to theCUBE's continuous coverage of AWS re:Invent 2021. I'm John Furrier, your host of theCUBE. We're here with James Watters, CTO of Modern Applications at VMware here to talk about the big Tanzu cloud native application wave, the modernization's here. James, great to see you. Thanks for coming on. >> Hey John, great to have you back on. And really excited about re:Invent this year. And I've been watching your coverage of it. There's lots of exciting stuff going on in this space. >> Awesome. Well, James, you've been riding the wave of, I would call cloud 1.0, 2.0 what do you want to call it, the initial wave of cloud where the advent of replatforming is there. You know all these benefits and things are moving fast. Things are being developed. A lot of endeavors, things are tracking. Some are kicking, Kubernetes kicks in, and now the big story is over the past year and a half. Certainly the pandemic highlighted is this big wave that's hitting now, which is the real, the modernization of the enterprise, the modernization of software development. And even Amazon was saying that in one of our talks that the sovereign life cycles over it should be completely put away to bed. And that DevOps is truly here. And you add security, you got DevSecOps. So an entirely new, large scale, heavy use of data, new methodologies are all hitting right now. And if you're not on that wave your driftwood, what's your take? >> Oh, I think you're dead right, John, and you know, kind of the first 10 years of working on this for sort of proving that the microservices, the container, the declared of automation, the DevOps patterns were the future. And I think everyone's agreed now. And I think DevSecOps and the trends around app modernization are really around bringing that to scale for enterprises. So the conversations I tend to be having are, Hey, you've done a little Kubernetes. You've done some modern apps and APIs, but how do you really scale this across your enterprise? That's what I think is exciting today. And that's what we're talking about. Some of the tools we're bringing to Amazon to help people achieve faster, consumption, better scale, more security. >> You know, one of the things about VMware that's been impressive over the years is that on the wave of IT, they already had great operational install base. They did a deal with Amazon Ragu did that. I think 2016, that kind of cleared the air. They're not going to do their own cloud or they have cloud efforts kind of solidifies that. And then incomes, Kubernetes, and then you saw a completely different cloud native wave coming in with the Tanzu, the Heptio acquisition. And since then a lot's been done. Can you just take us through the Tanzu evolution because I think this is a cornerstone of what's happening right now. >> Yeah, that's a great question, John. I think that the emergence of Kubernetes as a common set of APIs that every cloud and almost every infrastructure agrees on was a huge one. And the way I talked to our clients about is that VMware is doing a couple of things in this space. The first is that we're recognizing that as an infrastructure or baking Kubernetes into every vSphere, be it vSphere on-prem, be it VMC on Amazon. You're just going to find Kubernetes is a big part of each year. So that's kind of a big step one, but it's in some ways the same way that Amazon is doing with EKS and Azure is doing with AKS, but like every infrastructure provider is bringing Kubernetes everywhere. And then that kind of unleashes this really exciting moment where you've got this global control plane that you can program to be your DevSecOps platform. And Kubernetes has this incredible model of extensibility where you can add CRDs and program, right against the Kubernetes APIs with your additional features and functions you want your DevSecOps pipeline. And so it's created this opportunity for Tanzu to kind of have then a global control plane, which we call Tanzu Mission Control to bring all of those Kubernetes running on different clouds together. And then the last thing that we'll talk about a little bit more is this Tanzu Application Platform, which is bringing a developer experience to Kubernetes. So that you're not always starting with what I like to say, like, oh, I have Git, I have Kubernetes, am I done? There's a lot more to the story than that. >> I want to get to this Tanzu Application Platform on EKS. I think that's a big story at VMware. We've seen that, but before we do that for the folks out there watching who are like, I'm now seeing this, whether they're young, new to the industry or enterprises who have replatforming or refactoring, trying to understand what is a modern application. So give us the definition in your words, what is a modern application? >> You know, John, it's a great question. And I tend to start with why and like, hey, how did we get here? And you, you and I both, I think, used to work for the bigger iron vendors back in the day. And we've seen the age of the big box Silicon Valley. I don't know, I worked at Sun just across the aisle here and basically we'd sell you a big box and then once or twice a year, you'd change the software on it. And so in a sense, like there was no chance to do user-oriented design or any of these things. Like you kind of got what you got and you hope to scale it. And then modern applications have been much more of the age of like what you might say, like Instagram or some of these modern apps that are very user-oriented and how you're changing that user interface that user design might change every week based on user feedback. And you're constantly using big data to adjust that modern app experience. And so modern apps to me are inherently iterative and inherently scalable and amenable to change. And that's where the 12 factor application manifesto was written, a blog was written a decade ago, basically saying here's how you can start to design apps to be constantly upgradable. So to me, modern apps, 12 of factors, one of them Kubernetes compatible, but the real point is that they should be flexible to be constantly iterated on maybe at least once a week at a minimum and designed and engineered to do that. And that takes them away from the old vertically scaled apps that kind of ran on 172 processors that you would infrequently update in the past. Those are what you might call like cloud apps. Is that helpful? >> Yeah, totally helpful. And by the way, those old iron vendors, they're now called the on-premise vendors and, you know, HPE, Dell and whatnot, IBM. But the thing about the cloud is, is that you have the true infrastructure as code happening. It's happened, it's happening, but faster and better and greater the goodness there. So you got DevSecOps, which is just DevOps with security. So DevSecOps is the standard now that everyone's shooting for. So what that means is I'm a developer, I just want to write code, the infrastructure got to work for me. So things like Lambda functions are all great things. So assuming that there's going to be this now programmable layer for developers just to do stuff. What is, in context to that need, what is the Tanzu Application Platform about and how does it work? >> Yeah, that's a great question, John. So once you have Kubernetes, you have this abundance of programmable, inner infrastructure resources. You can do almost anything with it, right? Like you can run machine learning workflows, you can run microservices, you can build APIs, you can import legacy apps to it, but it doesn't come out of the box with a set of application patterns and a set of controllers that are built for just, you know, modern apps. It comes with sort of a lot of flexibility and it expects you to understand a pretty broad surface area of APIs. So what we're doing is we're following in the footsteps of companies like Netflix and Uber, et cetera, all of which built kind of a developer platform on top of their Kubernetes infrastructure to say, here's your more templatized path to production. So you don't have to configure everything. You're just changing the right parts of the application. And we kind of go through three steps. The first is an application template that says, here's how to build a streaming app on Kubernetes, click here, and you'll get in your version control and we'll build a Kubernetes manifest for it. Two, is an automated containerization, which is we'll take your app and auto create a container for it so that we know it's secure and you can't make a mistake. And then three is that it will auto detect your application and build a Kubernetes deployment for it so that you can deploy it to Kubernetes in a reliable way. We're basically trying to reduce the burden on the developer from having to understand everything about Kubernetes, to really understanding their domain of the application. Does that make sense? >> Yeah, and this kind of is inline, you mentioned Netflix early on. They were one of the pioneers in inside AWS, but they had the full hyperscaler developers. They had those early hardcore devs that are like unicorns. No, you can't hire these people. They're just not many enough in the world. So the world's becoming, I won't say democratization, that's an overused word, but what we're getting to is if I get this right, you're saying you're going to eliminate the heavy lifting, the boring mundane stuff. >> Yeah, even at Netflix as is great of a developers they have, they still built kind of a microservices or an application platform on top of AWS. And I think that's true of Kubernetes today, which if you go to a Kubernetes conference, you'll often see, don't expose Kubernetes to developers. So tons of application platforms starts to really solve that question. What do you expose to a developer when they want to consume Kubernetes? >> So let's ask you, I know you do a lot of customer visits, that's one of the jobs that make you go out in the field which you like doing and working backwards on the customers has been in the DNA of VMware for years. What is the big narrative with the customers? What's their pain point? How else has the pandemics shown them projects that are working and not working, and they want to come out of it with a growth strategy. VMware is now an independent company. You guys got the platform, what are the customers doing with it? >> Well, I'll give you one example. You know, I went out and I was chatting with the retailer, had seen their online sales goes from one billion to like three billion during the pandemic. And they had been using kind of packaged shopping cart software before like a basic online store that they bought and configured. And they realized they needed to get great at modern apps to keep up with customer demand. And so I would say in general, we've seen the drive, the need for modern apps and digital transformation is just really skyrocketing and everyone's paying attention to it. And then I think they're looking for a trusted partner and they're debating, do we build it all in-house or do we turn to a partner that can help us build this above the cloud? And I think for the people that want an enterprise trusted brand, they'll have a lot of engineering talent behind it. There's been strong interest in Tanzu. And I think the big message we're trying to get out is that Tanzu can not only help you in your on-prem infrastructure, but it can also really help you on public cloud. And I think people are surprised by just how much. >> It's just in the common thread. I see that it's that point is right on is that these companies that don't digitize their business and build an application for their customer are going to get taken away by a startup. I mean, we've seen, it's so easy if you don't have an app for that, you're out of business. I mean, this is like, no, no, it's not like maybe we should do the cloud, let's get proactive. Pretty much it's critical path now for companies. So I'm sure you agree with that, but what's the progress of most of the enterprises? What percentage do you think are having this realization? >> I would say at least 70, 80%, if not more, are there now, and 10 years ago, I used to kind of have to tell stories, like, you know, some startups going to come along and they might disrupt you and people kind of give you that like, yeah, yeah, yeah. You know, I get it. And now it's sort of like, hey, someone's already in our market with an API. Tell me how to build API first apps we need to compete. And that's the difference in the strategic conversation kind of post pandemic and post, you know, the last 10 years. >> All right, final question for you 'cause this is right great thread. I've seen having a web interface it's not good enough, to your point. You got to have an application that they're engaging with, with all the modern capabilities, because the needs there, the expectation for the customers there. What new things are you seeing beyond mobile that are coming around the pike for enterprises, obviously web to mobile, mobile to what? What's next? >> I think the thing that's interesting is there is a bigger push to say more and more of what we do should be an API both internally, like, hey, other teams might want to consume some of these services as a well-formed API. I call it kind of like Stripe MB. Like you look at all these companies, they're like, Hey, stripes worth a hundred billion dollars now because they built a great API. What about us? And so I've seen a lot of industries from automotive to of course financial services and others that are saying, what if we gave our developers internally great APIs? And what if we also expose those APIs externally, we could get a lot, a more rat, fast moving business than the traditional model we might've had in the past. >> It's interesting, you know, commoditizing and automating a way infrastructure or software or capable workflows is actually normal. And if you can unify that in a way that's just better I mean, you have a lower cost structure, but the value doesn't go away, right? So I think a lot of this comes down to, beauty's in the eye of the beholder. I mean, that's how DevSecOps works. I mean, it's agile, it's faster, but you still have to achieve the value of the net is lower cost. What's your take on that? >> Well, I think you're dead right, John. And I think this is what was surprising about Stripe is it was possible before Stripe to go out as a developer and kind of pulled together a backend that did payments, but boy, it was hard. And I think that's the same thing with kind of this tons of application platform and the developer experience focus is people are realizing they can't hire enough developers. So this is the other thing that's happened during the pandemic and the great resignation, if you will, the war for talent is on. And you know, when I talked to a customer, like we might be able to help you, even 30% with your developer productivity, there's like one out of four developers. You might not have to be able to have to recruit they're all in. And so I think that API first model and the developer experience model are the same thing, which is like, it doesn't have to just be possible. It should be excellent. >> Well, great insight learning a lot. Of course, we should move to theCube API and we'll plug into your applications. We're here in the studio with our API, James. Great to have you on. Final word, what's your take this, the big story for re:Invent. If you had to summarize this year's re:Invent going in to 2022, what would you say is happening in this industry right now? >> You know, I'm just super excited about the EKS market and how fast it's growing. We're seeing EKS in a lot of places. We're super excited about helping EKS customers scale. And I think it's great to see Amazon adopting that standard API from Kubernetes. And I think that's going to be, just awesome to watch the creativity the industry is going to have around it. >> Well, great insight, thanks for coming on. And again, we'll work on that Cube API for you. The virtualization of theCUBE is here. We're virtual, which we could be in-person and hope to see you in-person soon. Thanks for coming on. >> You too John, thank you. >> Okay, Cube's coverage of alias re:Invent 2021. I'm John Furrier, your host. Thanks for watching. (upbeat music)