Again, let's raise it for Tatsu kudo and his presentation.
Thank you. So I talk about, I did component as a service and in a 10 minutes. So I've been this industry for 23 years. And so I like the infrastructure as a isolated environment, but this is the, our implication. So I think I have to reconsider this implication. So the current old architecture, the under infrastructure should be a considers to be separated in a service architecture infrastructure. And there are two kinds of user interface for each user and they, in a API environment, there should be two kinds of API endpoints. So this is a very simple of in this industry. So this is a IM software and I, the other service is successor of this architecture or D so Ida should be considered as a isolated real. And so service provider should create this service in the, their service infrastructure. So this API clients should be access to another API endpoint and the user as well.
So, so I think this is some kind of beautiful. I know, but so I've heard many voices from outside of our industry. So they want to create the consistent user experience customer experience or the pre their pre first language is a goal or scholar or other modern languages to develop their own identity infrastructure or the agility and control their, the mother. So they don't want to rely on other parties environment. The subsid says the, they won't want to depend on the other vendors components like Ida. So, so we have to think about the identity service, where is the best place for deciding service. So it should be the trade as one of service. So they want develop or manage the designing service, other, other as well as other services and operate it. So this increases a couple of components, for example, use authentication or token management or other things of identity matters.
So, but we know these kinds of functions is very complicated and not so average group should not develop these kinds of functions. So in that case, so I think we should consider seriously about the adding components as a service outside of this it infrastructure. And then this component should be externalized as needed. So for example, this service provider would like to manage their own identity or use credentials. They can manage in their service, but other functions like, or connect operations or token management, they can be externalized or, or level leveraging ING external services. So I just, this is the accurate naming, but I just call some kinds of ICO. So I did components as a service. So ICOs is opposite to traditional old I AMDA soda or is bound. So all functions should be included in the single box or this have to managing the user interface or management interface, which is headed the, so that is the, the controller of the identity interactions, as well as API interactions, API author interactions, but ICA should be unbundled.
So this component should be independent and this is, this doesn't have head. So don't, this is a API based. And so this is just a component. So this should be a usable for other service providers or service brokers. Okay. So let me interest one example, which is lead. So, which is our solutions in terms of all and body collect protocol processing, as well as access to lifecycle management. So we provide APIs for service providers to develop their own author service or identity providers without developing the complicated functions of open connect. So this is headless. So the customers can develop their own customer experience, you know, in line with other services. So this, so we don't have any, I don't have any time. So this is, I like this second diagram, but short. So also it provide APIs, the process, the author of requests, or token, or other actual or openly collect requests and the author server in the customer side, just pass this premises to our APIs.
So they offer it will process this premises. And then the wake response, that includes what next. So this is the other server or adding providers is very, is simple or thing, and can be, can leverage other functions like a user authentication. So this is a very futuristic, but you may think, but it is not true. So we have lot of customers who are right, including our final swing sectors, like Newbank in bra Brazil or other E or other sales vendors. So, so the actual customer use case is I will introduce the first one is DPG media in Belgium media company. So they evaluated lot of solutions. I also, I am software or opposite based tool, but that didn't work because they wanted to manage whole stack of identity infrastructure. So they chose also to implement the whole identity infrastructure. So the next case is a core.
So which is a Brazilian fin company. So the one of interesting points is they wanted to develop their own open banking, compliant, and provider using Golan. So I don't think other solutions can customize the, their logic using their one, the model languages. So, and other example is a fol. So they're using scholar. So again, the very unique approach to develop their infrastructure, not API client. It is core of a API authorization using their pre preferred or standard programming language or frameworks. The last example is poli, which is a Japanese company. They provide B2B is software, and they had evaluated the old zero, but it doesn't work because it doesn't provide enough capability of customizing the user interface. So they want to provide a consistent user experience for other their customers. So they provide digital users, us the, the takeaways. So M I soft patterns. So it is good for traditional use case, but so let's look other people outside of our industry. They want to develop their own service with their own program languages to build our consistent customer experience. So IGA, so I think component of service is one of the solutions to enable that. Okay. So the last, so Martin has prepared our, the introduction, our solutions. So if you are interested, you have solutions. So let me check the, the white paper or product brief. Thank you. Great. Thank you very much.
