Salesforce, Inc. (CRM) Earnings Call Transcript & Summary

Hello. Hello, everyone. And thank you all for joining today's session. Before we begin, I just want to cover a few quick notes about our webinar platform. Today's webinar will be available on demand after we wrap up. It will be accessible through the URL you are on now and will also be sent to you via e-mail tomorrow, so please keep an eye out for an e-mail with a link to watch the on-demand version of today's session. Please note the slides will advance automatically throughout the presentation. If you need to enlarge the slide area or any other widget, simply drag the bottom right corner to resize that widget. If you need any technical assistance, please click on the help widget located on the bottom left corner of your console. We've also added some additional resources, which are available to you through the resources library, to the right of your slides. And there you'll be able to find additional related content, including white papers, webinars, e-books and so much more. In addition to the content there, please keep an eye out for QR codes within today's presentation for you to get access to amazing content shared by our speakers today. We also encourage you to submit questions at any time throughout the presentation using the "submit a question" widget. We will be sure to answer as many questions as we can at the end of today's presentation. If we're not able to answer your question, we will be sure to follow up with you off-line, so please know your question will be addressed. Last but not least, let us know what you think of today's presentation by sharing your feedback via our webinar survey available on your console below. This survey will also populate once today's webinar has ended, but if you want to access it at any point to share your feedback, it's available right there on your console. We also welcome you to share your excitement with us in the moment by using the emoji reactions on your screen, so feel free to use the thumbs up, smiley face, celebration and heart emoji reactions available to you now to let us know what you love most about today's presentation. So with that, I will hand it over to Sameer to kick us off. Sameer, over to you.

Awesome. Thank you, Moya. Hello, everybody. Welcome to today's webinar. We're excited to talk to you about how to build, manage and secure any API using the MuleSoft API management platform. A quick intro about me: Sameer Parulkar, product marketing here at Salesforce, focused on MuleSoft API management technologies. And I'm joined today by Sue. Sue, do you want to do a quick intro?

Yes. Hi, everyone. I'm Sue. I'm a technical product marketing manager for Salesforce, and I focus on API management as well as our run time and monitoring services. Happy to be here.

Awesome, all right. So let's get started. So the key thing we're going to talk about today is, as we think about APIs, how can you provide a holistic platform or holistic solution to -- all the way from building, managing as well as securing all your APIs. So we're going to talk about that. And towards the end -- so I'll kick it off; give a quick overview, market landscape, what's happening, why the need for a new API management solution; and give a quick overview about what are we doing from a product perspective, what are some of the key updates coming up in the product area? And then at the end -- towards the end, Sue is going to give you a quick demo of this product capability. So that's kind of like how we're going to do it today. As Moya said, please do use those emojis to let us know whether you liked it. As well as, obviously, at the end of the -- of our session, please let us know how did you like the session, your feedback. Because we always want to improve on our content. So let's get started. Before I begin, a quick forward-looking statement: we're going to talk about new products' capabilities, but please make your purchasing decisions on the products that are available today. Wanted to, first, quickly thank you, thank our customers, our partners, our MuleSoft community as well as Trailblazer community for being our partners and helping shape our road map. Thank you so much for that. Before I begin, I -- we wanted to take a quick poll from you all just to understand your API management journey today. Now everybody is in a different state, so before I begin and before we go ahead, if you can take a quick poll, that would really be helpful. I'm going to give you like maybe the next 30 seconds to kind of take this poll. [Voting]

Again, please take the poll. And the idea is like we just want to just know your state of API management adoption within your enterprise today. Okay, probably another few seconds. All right, let's see what we're -- what the audience is telling us. Okay, cool. So an equal number is just starting out. Some are managing a couple of APIs, okay, but specifically so we see equal number just started with API management journey, managing a couple of APIs, but also, very few know of APIs that are protected, so -- and then very few are experts, right? So now I'm going to talk about that one pool over there that talks about very few know the APIs that are protected within their environment. And this is going to be a significant risk within your environment, right, within your business environment. We're going to talk about that in the next few slides. All right. So let's, first, begin with, in today's world, right, why do you need a different approach with managing our entire API life cycle. I mean again APIs are not new. APIs provide incredible value, but how you protect them and how do you get the most value from them is actually changing and you need a different approach. I'm going to talk about it, first, about why you need a different approach for this. So let's start it out, right. So before I begin, a thing that I really want to restate again is that APIs continue to drive business value and across different verticals. You take any business services today, right. At a high level, right, what APIs do, APIs allow you to connect different applications together so that different applications can talk to each other. At the same time, APIs allow you to exchange data between these different applications, right? At a very high level, that's what the APIs do and share your data with your customers or your partners. Now what happens is, as you start adopting APIs, APIs become even more important to deliver on different business services, right? For example, if you look at financial services, when you think about digital banking experience or you think about e-commerce and payments, all of that is driven using an API interface behind the scenes, right? As a consumer or an end user, you don't necessarily care about it, but behind the scene, this is all implemented using an API. Similarly, now when you look at even health care, when you think about unified patient experience or patient onboarding or a provider and patient experience, all of that is actually delivered via APIs. Similarly, if you look more now from a retail organization perspective, when you look at inventory, supply chain, all of that is -- majority of that is driven using an API. In a recent Connectivity Benchmark Report that we do every year, we found that 39% of respondents said that APIs were part of increasing their revenues. When you look at how APIs are being used within their organizations, 39% said that they actually help them increase their revenue. In the same report, we saw that 49% mentioned that they allowed them with greater agility across the team. So now as they were delivering their business services, using an API-led approach or APIs helped them deliver those services quickly. Now what is also happening is now, obviously, APIs are delivering that incredible business value. At the same time, the volume and velocity of APIs is increasing. How? The recent Connectivity Benchmark, the same research that we did, we found that an organization, on an average, uses 991 applications, so like almost 1,000 applications. Now there is no good correlation between an application and an API, but we can safely assume that it's at least at a scale of 30x to 40x, right? So like a single application may have, at least at a minimum, 30 to 40 APIs, right? Now you think about it, right, when you are dealing with almost 1,000 applications, how many APIs you have to deal with. Now at the same time, what the APIs are being used for, we found that 54% use those APIs to build integrations or connectivity and 46% use APIs to manage APIs as a product, right? Now what is also happening, interestingly, now with the adoption of AI and gen AI, it is actually going to increase to this, right? It's going to lead to more APIs. Because if you look at AI or if you look at gen AI or LLMs, right, a way to interface with those AI applications or LLMs is API. APIs are the most common ways to -- APIs are not the only way, but they are -- it's the most common way to interface with them. So you're going to see that the volume of APIs as well as the velocity across these use cases is increasing. Now before I talk about the next thing, what I wanted to also know is, in your organization today or in your experience, who is charge of API management in your organization? So whether it's IT, you don't know, each department has its own thing or there are multiple departments. So this is like a quick poll I wanted to just take before I share the next -- I go to the next -- go further ahead because this will actually help me set the context of what I'm going to talk about later. And the idea here is like who is in charge of API management through your experience, whether it's IT, whether it's each department, multiple department working together or you don't know. [Voting]

All right. So this is a quick -- thank you, everybody, for responding. So we see here that almost 58% said that IT is responsible for API management. 22% said that each department has its own thing, and almost 16% said that multiple departments work together. So what I think -- this is probably aligns a lot kind of like what we are -- what we see in the market today, right? And the key thing we are trying to -- what I wanted to convey here is that across your organization, you're going to see each and every department or each and every LOB has -- sometimes they have their own standards. They're adopting APIs in their own way. And a lot of times, there is -- you need to kind of like have a standard approach across all these different API-led innovations. So let me talk about that next, okay? So setting that context, right, so what we -- this is an -- so as you saw, what I mentioned about increase in API volume as well as velocity, what is also happening is that, as customers are adopting APIs to now connect their applications as well as their interface, now we do see that MuleSoft has been a pioneer in the industry for the last 7-plus years promoting the API-led approach, right. API-led approach to now connect your applications together, provide those set of business services all the way from like your system APIs, to process APIs, to experience APIs. And if you do this within MuleSoft, you obviously have the API-led architecture as well as the right control and governance with MuleSoft. But what is also happening, as you saw earlier in the poll, was more APIs are being developed as part of your different business initiatives. For example, your different LOB teams may be developing their own business initiatives using different API technologies, right? Similarly, you may have a microservices or modernization initiative, developing more APIs. As you're adopting event-driven architecture, event-driven architecture itself will create more APIs. And the example that I gave earlier, AI experiences itself create more APIs. Now all these APIs are using different set of technology standards as well as different deployments, right? Either they are deployed on prem or they're deployed in the public cloud or in a hybrid cloud. Now what happens is, right, we -- a lot of times, customers have told this is -- they call this API proliferation or API sprawl. What it means is that you have lack of visibility into all the APIs that you have. You have inconsistent enforcement of policy and governance across this API landscape. And again, it's -- and then this in turn has, when you look more from an operational perspective, complex operations across your environment. A recent report from Gartner also said that, by 2025, almost 50% of APIs are going to go unmanaged by 2025, again creating a big security risk within your environment, right? So on one hand, you do have like -- as you saw earlier in the poll, that you do have like almost like 40% IT responsible for API management, but you also have API management in different LOBs. So now when you look at all these APIs that are across these different technologies and landscape, how do you make sure you have the right visibility, control and governance across these APIs? And that's where MuleSoft, we believe that you need a different approach to API management. We call this universal API management. We -- and what -- universal API management is essentially expanding the scope of API management to any API deployed anywhere in any environment, right? With this approach, it allows you to: a, discover, build and catalog any API; ensure consistent API quality and security; control and secure access to any API; and engage and create API ecosystem. So providing now you the set of capabilities across your API life cycle regardless of whether API is developed or deployed. Now we do this using a set of capabilities on a unified platform, a unified platform to manage the entire API life cycle, all the way from build to discover, to govern, to manage, to engage. And then part of it is then, once you engage, you reuse these APIs for your different business initiatives. Now customers like Standard Bank almost -- they've used this set of approach as well as our set of capabilities to now almost -- within just 3 months, 70% of their APIs are cataloged and governed. So again, we are seeing customers who have adopted this approach and set of capabilities with incredible value. So I kind of like give you now the, first, an update on more the overall market state and the need for a universal -- a different approach to API management with universal API management. Now let's talk about the products that we offer and what are some of the capabilities that we offer. So if you look at MuleSoft API management, right? I like to think of what is a 3 key capability pillars. First one is protect APIs running anywhere, right? And this one is more about, as you try to build responsive experiences using modern architectures, how can you make sure that you can build those experiences much more quicker but have the right set of security and control. To do that, we provide API gateway capabilities and a centralized control plane, right? So first, we provide 3 sets of -- we provide 2 sets of gateway capabilities, a microservices gateway, again based on Envoy, which is a Flex Gateway that we launched around 2 years back. With Flex Gateway, you can control any API, right, deploy it anywhere. It supports multiple deployment options. And you can secure -- and it's Envoy-based. And you can have fine-grain control for all your APIs, right? Similarly, we also have Mule Gateway, which was part of our portfolio for more than 4, 5 years now, and we have seen great customer traction with Mule Gateway. The thing with Mule Gateway, it's basically an -- embedded within the Anypoint platform itself, right? Idea behind this is we have 2 sets of gateway options available to you. Depending upon the use case, you can use those API -- gateway options to protect now your APIs, but the most important aspect is we also have a centralized control plane, which is the API Manager, to manage and secure any of your APIs and to assign, align -- and to assign the policies. For example, if you have APIs that are now distributed across your environment, use the same centralized control plane to now manage the policies and deploy them across. So essentially you can control the APIs where they are, for the optimal performance, but at the same time, you have a centralized control plane to now manage all of this at one point. So exactly the picture that I showed earlier about the API proliferation. You can use APIs, you can -- with your technology of choice, but protect it using the distributed gateway then control it using -- within a centralized control plane. So that's kind of like the capabilities that we offer. Recently, as part of the Flex Gateway, we launched Policy Development Kit. And the idea behind the Policy Development Kit is that, within MuleSoft and within the different gateway options, we provide a lot of out-of-box policies, right, to protect your APIs, all the way from like making sure that denial-of-service attack is taken care of, that each API should have the right protection. We provide all of this out-of-box policies. Now what happens is we know that in most cases your use cases are -- could be specific for your own business requirement. And maybe there are cases where our existing out-of-box policies don't work, so we provided this Policy Development Kit, which is kind of like a framework that allows you to now develop your own custom policies, depending upon your business requirement, and deploy them within your environment but use the same tooling that we use for out-of-box policies to help you now manage those policies. Essentially, think about it this way. We have a bunch of out-of-box policies that we support, providing you, then, the framework and tool set allowing you through API Manager to now deploy those policies, configure them, but at the same time, using Policy Development Kit, you can create your own custom policies and then still use the same framework to deploy them. Specifically, when now you think about your specific AI use cases, right, if you now think about, how can I protect PII data going to my AI API? You can start developing a -- specific custom policies for that. So these are some of the use cases that we are seeing, and we are helping customers with that. Next, API Manager. I mentioned about it. It's a centralized control plane. And it actually allows API teams to manage, secure and analyze all your APIs and microservices. In simple steps, developers, architects and product managers can configure and deploy policies to different API gateways. As I mentioned, Flex Gateway or Mule Gateway manage the client access as well as group APIs as products. And the most important thing is allows you to now have successful API programs. Next, let's talk about our second capability pillar, about discovering and governing the entire API program to gain consistent security and quality across your APIs. Now as we think about the discovery and governing your entire API program, right, as I mentioned earlier, about the API proliferation, right, think about it this way. There are -- the first step about you is you cannot manage and protect an API that you don't know, right? It's like how are you going to even manage them, right? So discovering an API and cataloging them in one place is becoming very important. So that's our first set of capability. We provide a capability called API Catalog CLI that allows you to now put that CLI in your development pipelines, extract the API and its documentation and catalog them into Anypoint Exchange for a single source of truth for your API. Now once it's cataloged, that's when you can start now thinking about, how can I protect it and how I can govern it. Next is how can you have continuous API assessment? And this is more about how can you actually govern this API so that you can have the -- you can ensure that your APIs conform to the best practices that you define or best practices from an industry perspective, right? How can you ensure that the API have the right quality and security, all the way from designing an API to implementing an API. And we also know that the first discovering of external APIs work for known APIs, but there are also cases where sometimes you don't even know where that API is. And this is where we partner with some of our security vendors like Salt Security, Noname, Cequence or Traceable to help you now discover and catalog unmanaged APIs. API Governance. This is a product that we launched around 2 years back and allows you to now provide a consistent security and governance across your API, again as I said, all the way from design of an API to ensure that your design -- API is designed in the right way, the right format, to now allowing more of a continuous assessment of API to ensure you that all your APIs conform to that design. And also now to Runtime: As you deploy that API on the MuleSoft platform, in Runtime, it will introspect and tell you whether a specific number of APIs are actually conforming to your standard. We provide a governance dashboard that allows your security teams as well as your architect teams to then look at your entire API landscape and make sure that all your APIs are conforming, if not, generating the reports as well as allowing you to now connect to the developers. So essentially the whole idea with API Governance is using the same unified control plane, providing you with the consistent security and allowing the different architects as well as your security teams and your developers to work together to ensure the right conformance. What's coming up on the API governance side is this new capability called API Insights. And API Insights is more around getting you the state of union of all your APIs. For example, you can get a one quick dashboard to tell you what's happening with all your APIs, right, whether your APIs are being managed, whether they are not being managed, whether they're being governed, whether they're not governed; essentially like an entire posture of an API. Why is this important? Because once you have that, that actually helps us make the right decisions for your successful API programs. As you're developing all your business services, this allows you to now take an overall holistic view of your entire API program. So again, really excited about it. This is something that's coming up in Q2 of this year. Next, take a -- let's take a look at the third pillar, capability pillar. And that's more about creating vibrant API ecosystems. And think about this as like, as you're now a product manager, how you can now get the most value from your APIs, right? Now you have an API. You developed an API. You went through the entire protection, the governance, but then how can you ensure that your APIs actually get the most value? How they can be reused, shared within your organization, right? Because, I mean, a simple thing is, right, I can have my API, but if the API is not being used by anybody or just used by one application, you're going to reduce the value of that API, right? So how you can actually ensure that. Today, in Anypoint, we provide multiple options to you, right? We have the Anypoint Exchange, which is basically a single source of truth for all your API assets, right, your APIs, your integration as well as their automations. It provides you one single place where you can go and look at all your APIs, your documentation, your design and everything around it. Now -- but at the same time, what -- API Exchange provides you all of that, but now think about your situation, right, where you may have like, say, 100 or you may have like 500 APIs now in Anypoint Exchange. By the way, you're also cataloging those -- the non-MuleSoft APIs into Exchange, bringing everything into one place for universal visibility for all your APIs, but not all your APIs are equivalent, right? How can you ensure that the right APIs are now being shared in a way that is easy for your customers -- for your internal teams as well as your customers and partners to consume them? That's where we launched API Experience Hub last year. And what API Experience Hub allows you to do is as a API product manager as well as an architect as well as a developer, allows you to now build these API portals, curated API portals, personalized portals, in minutes for better API engagement. API Experience Hub is built on the Salesforce Experience Cloud, so what it allows you to do is now create these portals very quickly, customize it to your own requirement, select the APIs that you want them to be -- now to be shared within internally as well as with your external customers and partners. But not only that, you can start adding elements like forums for your API, right, help for your API, question-and-answers, like chat, for your APIs. So again it allows you to now create much more engagement with your API. We're excited, actually, coming up is a new feature coming up about controlling the API visibility in the portals, right? With user -- and this is about the API Experience Hub user groups. With user groups, portal administrators will have the ability to control visibility of APIs in the developer portal by creating custom user groups and assigning members to those groups. This means you can ensure that the right API consumers have access to the right APIs based on a predefined user criteria. Now really excited about this. And this is a capability that's coming up in -- again, in Q2 of this year, so stay tuned for that. Now I kind of like gave an overview about our vision, what's happening in the market, why API management, universal API management, is needed, the value of unified platform. Then I kind of like walked you through the product, the 3 key capability pillars as well as the products within each of them, what is coming. I think let's have Sue actually demonstrate all of this for you, right, to kind of like bring it all together. Sue, to you.

All right. Thanks, Sameer. So yes. So let me first walk you through what I'll be showing during the demo. And then I'll go ahead and share my screen and we'll dive deep into the actual product. So yes. So during this demo, I'll be walking you through kind of the management, governance, and what Sameer talked about last, of like sharing that API externally and internally so that other people can use it. So here I have 3 APIs. One is running currently on Anypoint Platform, CloudHub. So it's built -- it's an API that's built within MuleSoft's product and deployed there. And it's managed, yes, on CloudHub, but then I also have APIs that are actually outside of Anypoint Platform. So it's not built like within like Anypoint Platform, but it's built somewhere else. And then now it's deployed in a AWS ECS container. So then we have 2 APIs. So what I'll be doing is showing you, first -- yes, showing you how can we gate all these APIs that are deployed in multiple places and then be able to apply the policies as well as SLA or service license agreements so that you can kind of limit who has access and how much access that they have. And then we'll even take a look at how we can govern, what policies are applied so that, as a security officer, as they're looking at all these APIs that are being managed, they can ensure that it's being properly protected and has the proper policies that they require. And then lastly, we'll be putting them all on Anypoint API Experience Hub, our developer portal, so that external users who are approved can now go ahead and access these APIs and make them part of their application and get the data that they need. So let me go ahead and share my screen. Okay, so this is a slide. I'm just going to go back to it and then, so these are the 3 APIs. And then we'll now put them on gateways and apply policies. So this is Anypoint Platform. This is kind of that single platform that you can bring all of your APIs in regardless of where they're built, running; and then manage them and integrate them and do the whole thing here. So just like as a quick tour. We have Anypoint Code Builder, which allows you to integrate -- build your integration projects and use it in Visual Studio Code, where a lot of developers are already living in and building their applications. You can build API specifications, which kind of specifies this and puts boundaries on what that particular API can do. And then we also have Anypoint Exchange, where all of these APIs that are built as well as connectors and templates live so that, within your internal users, they can access those APIs or make requests to it through there. One that I will be going into now is API Manager. And that's where, once you have your APIs deployed and running, this is where you go to have that single source of view of all the APIs that you're managing, access to or controlling like how much access someone has. So as you can see, depending on where that API gateway is deployed, we can see that difference. So if it's Flex Gateway, it could be a containerized gateway that's built or deployed as closest to that API as possible. So like, for Flex Gateway, you can spin it up as a Kubernetes container and then put it as close to like, let's say, the inventory API which is running in our AWS ECS service. And that allows you to have the highest performance, whereas if you want a gateway that is managed, as Sameer talked about earlier, you can go ahead and deploy a proxy or use our built-in functionality so that, when you're deploying an API into CloudHub or in MuleSoft service, then you can also create -- start managing that -- or putting policies and SLAs right away without even having to spin another gateway up. So from there, another feature that I wanted to call out is the automated policies. This is where you can basically set a certain number of policies that are automatically applied to APIs when they are created or added to API Manager. So these are the included policies that comes with the gateways. Some are for Mule Gateway and others are for Flex Gateway, but there's a lot of crossovers that you can use. And then as you can see, we -- I do have custom policies. And these were built using the Policy Development Kit as mentioned earlier. And these policies are basically, if none of these included policies quite fit your use case or you have another use case that you want to implement, you can definitely use the Policy Development Kit to get you started and build out that policy. So let me just put in the policies so that all the APIs I already have, have the SLA-based rate-limiting. So going back to API administration, we'll go into product inventory API. So that's -- so these 3 APIs, I've already added. In the product API, you can see a summary. And in the summary, you have the option to also put in what the endpoint URI is as well as what's the back end, so that API in the back that you're trying to protect as well as see key metrics such as requests over time, policy violations and errors and response time. So right now I've implemented the rate limit policy, so if I go into Postman and make this call -- hold on. It's because [indiscernible]. Let me remove that SLA policy for you, yes. Okay, so right now I don't have any policies applied to this inventory API, which means that it's completely unprotected. If anyone has access to my endpoint right here, then you can make calls to it and get the data that you need, which means that it's not secure. And back in the Anypoint Platform, as you can see, there is this flag here called instance conformance. And that's where you can check for governance, and we'll be diving deeper into it later. So as we can see, here in the policies, I have one applied, which is our custom policy. So for Flex Gateway, we can see other policies applied. So for today's use case, we'll put in authentication. So this is really neat because, with all the included policies, all of it is UI-based, so it's don't need to know code as an API manager. We can just use anything on the UI to apply these policies. If you are more familiar with CI/CD pipelines or you want to automate this process, you can definitely do this programmatically using our Anypoint CLI. So because I just applied it, now we have that instance conformance. That is now all good, so basically I don't have any violations or warnings. So as a security officer, when you're looking at this report, you can know that, oh, I've -- yes, I've met that requirement. And for that API manager who's particularly looking at this one API, they're able to go ahead and just check off all the requirements that they need. And then another part that I wanted to show you in API Manager was, okay, now that I have the policy set, how can I control how much access someone has. So that's where SLA tiers come into play. So I have one that's already set up to be free. And that one requires automatic approval, so when someone makes a request to have access to that API, it will be automatic, but if you -- let's say you want to do a paid tier. Then you can make that approval manual because you want to make sure that they pay before you have access to it. And then you can add. All right. So with this, now you can manage who has access by going into contracts. So from API Manager, essentially you can -- it becomes that single source of truth where you can manage all of your APIs. And then we saw how the API Manager can -- or the -- yes, API Manager, the person can go in and look at the governance, but as a security officer, you can also have access to this dashboard and see which APIs are conforming or not conforming according to the rule sets that we provide. So just a quick -- so with the rule sets, MuleSoft does provide some out-of-the-box ones that are -- what we consider best practices from talking to a lot of customers and from our own internal uses of APIs. And we provide them for you within Anypoint Exchange, but if you are like, "I want to create custom rule set that mixes and matches what's provided," you can go ahead and create that one, new one, a custom rule set. So like, for here I created an Alpine policy best practices that fits my organization's requirements. And what is really neat is that, for each API, you can see what rule sets have been applied to it as well as what passed and what failed. And you can even go into a full validation report to see it in conformance breakdown based on the API specification. So like, let's say, if you want to look at the policies, for example, you can click on instances. If you want to see if it passed documentation within Anypoint Exchange, we can go ahead and see that. All right. So now that I know that all my APIs are protected, are on the gateway, behind the gateway; and went through the governance checks to make sure the proper policies are in order. The next place that a product -- API product, manager can go into is in API Experience Hub. So this is where you can manage your developer portal that's either meant for your external customers, partners or, let's say, someone external to your department or organization that doesn't have access to your Anypoint Platform. So setting this up is pretty simple. It's a 4 step -- like a walk-through process where you can click the brand and change the colors and set up APIs. So here I've already added product catalog API and phone sync API. Let's go ahead and add product inventory API. And once that's added, I can set visibility as to who can see my APIs and make requests to them, so it could be everyone, members or admins. So I'll click members for this one. And then you can also do user management here. And so this determines who is a member versus not. So on the site later on, you'll see like where you can log in and create an account. That request will go into this page, pending request. And the product manager or whoever is in charge of Experience Hub will need to come in and approve them. Another option is to set up single sign-on, so instead of doing a manual approval, you can just open it up to a certain group within your organization. So yes. So let's take a look at how we can modify and update this portal. So API Experience Hub is built on Salesforce Experience Cloud, so if you're familiar with it, you should -- this setup page should be familiar to you. What's really neat about the -- about this is that now you have access also to out-of-the-box like widgets and like features that comes with Experience Cloud. And if you are using -- and so you can set up feeds, chatters, if you want to create like contact us or even create service cases. Or if a customer wants to contact support, you can even set that up and have them connect to your Salesforce organization to really provide that curated experience for the developers that you have in mind. We also provide components that are out-of-the-box with Experience Hub. So it doesn't come with the regular Experience Cloud, but these are the features that we built on top of for that ideal API developer portal. So from here, once it's done, you can go to the actual published page to take a look. So right now, I am not logged in -- just real quick, and I can only see APIs that are available for everyone, but once I log in -- yes. So here, if you click not a member, you can like put in your information. And then it will send that request to the user management tab, and then you can get approved. So I have an account. And once I log in, I am able to see a lot more APIs, including the product inventory API that we created. And if I click into that API, I can now see auto-generated documentation that's based on the APIs, API specification. I can go ahead and take a look and even make -- try it out, using our mocking service, to make sure that this is what I want. And then request access through here. So this pulls in that SLA tier that we created that's free and paid. So going back to our slide. Yes, we put these APIs behind an API gateway, and then using API Manager, applied policies and SLAs. And then checked them with our governance engine, and then used Experience Hub to expose them to our developers that we want them to be used or make them part of their application. So that is the demo, and I will stop sharing. All right. So back in the slide, yes. So as you've seen, we've just kind of shown you a snippet of the universal API management product's capabilities that we have. It's our vision to ensure that, wherever you are in your -- wherever the API is in its life cycle, we have the tools and functionalities that allow you to manage and govern and discover any API into this one platform. So the key takeaway is that API sprawl is a reality. Microservices are, yes, pretty much just proliferating and growing. And it's becoming a huge part of innovation but as well as something that we want to secure and control. So you can do that with Anypoint Flex Gateway and Anypoint API Manager. And for all these APIs, as you apply policies to them or as you build them or even document them, we need those checks necessary for security but also for reusability. So you can automate those governance checks using Anypoint API governance. So if you want to learn more. We have all these QR codes for you. And so a lot of the statistics that Sameer shared earlier comes from our 2024 Connectivity Benchmark Report. And then if you want like a higher overview -- high-level overview of universal API management, you can check out the CIO guide. And then if you want to dive deeper into any of the products, we have a demo series called API Management With Anypoint Platform. So you can scan that QR code. And if you're new to MuleSoft and want to check it out and get a 30-day free trial, you can scan that last code right there. So yes. So thank you so much for joining us. And then Sameer and I will use, yes, the remaining time to answer any questions that you have. Thanks.

Awesome. Thank you, Sue, yes. I think there are a couple of questions. I think some of them were general, about when they can get access to this webinar and the recording. That should be -- you should get an access to the webinar recording in the next 24 hours, so stay tuned for that. I think somebody -- I think Alex had this question about integration is what percentage. I think this might be the slide that I presented earlier about the Connectivity Benchmark Report and how many -- like how many customers are using APIs for what use cases. And I think that report indicated that almost 50% of our customers, those who were interviewed in that overall survey, were using -- 54% of them were using APIs for integration. I hope, Alex, that's probably what you were asking. Then do you provide an out-of-box authorization policy? I believe you covered that, right, Sue, the SLA tier policy that you showed, right?